On January 31, 2024 1:28:37 PM PST, hw wrote:
>On Wed, 2024-01-31 at 09:27 -0500, Gary Dale wrote:
>> On 2024-01-30 15:54, hw wrote:
>> > On Mon, 2024-01-29 at 11:42 -0500, Gary Dale wrote:
>> > > I'm running Debian/Trixie on an AMD64 workstation. I've lost the ability
>> > > to see the root di
On 1/31/24 21:50, Max Nikulin wrote:
On 31/01/2024 20:24, didar wrote:
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
How do I setup /etc/chrony/chrony.conf so it slams the system clock
to the
current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate c
On Tue 30 Jan 2024 at 07:05:55 (+), Tixy wrote:
> On Mon, 2024-01-29 at 23:49 -0600, David Wright wrote:
> > I would tend to think that:
> >
> > . The debian-installer installs ifupdown by default when you don't
> > install a Desktop Manager like Gnome,
> >
> > . The debian-installer instal
On 31/01/2024 20:24, didar wrote:
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.
You can us
On Wed 31/01/2024 at 23:04, Gareth Evans wrote:
> On Wed 31/01/2024 at 22:11, Steven Truppe wrote:
>> Hey,
>>
>>
>> i've the follwoing trouble: when i try to run certain apps it takes
>> forever tostart. i can get rid of the troble by typing $service apparmor
>> reload but that's not a partmanent
On Wed 31/01/2024 at 22:11, Steven Truppe wrote:
> Hey,
>
>
> i've the follwoing trouble: when i try to run certain apps it takes
> forever tostart. i can get rid of the troble by typing $service apparmor
> reload but that's not a partmanent soutoin.
>
> can someone pleae help me out here ?
>
>
>
On Wed, 2024-01-31 at 06:33 +0100, to...@tuxteam.de wrote:
> On Tue, Jan 30, 2024 at 09:47:35PM +0100, hw wrote:
> > On Mon, 2024-01-29 at 18:41 +0100, to...@tuxteam.de wrote:
> > > On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
> > >
> > > [...]
> > >
> > > > Ok in that case, hardware RAID
hw (12024-01-31):
> Well, I doubt it.
Well, doubt it all you want. In the meantime, we will continue to use
it.
Did not read the rest, not interested in red herring nightmare
scenarios.
--
Nicolas George
Hey,
i've the follwoing trouble: when i try to run certain apps it takes
forever tostart. i can get rid of the troble by typing $service apparmor
reload but that's not a partmanent soutoin.
can someone pleae help me out here ?
best regards!
On Tue, 2024-01-30 at 21:35 +0100, Nicolas George wrote:
> hw (12024-01-30):
> > Yes, and how much effort and how reliable is doing that?
>
> Very little effort and probably more reliable than hardware RAID with
> closed-source hardware.
Well, I doubt it. After all you need to copy a whole parti
On Wed, 2024-01-31 at 21:59 +0100, hw wrote:
> On Wed, 2024-01-31 at 08:02 +0100, Paul Leiber wrote:
> > Am 25.01.2024 um 22:28 schrieb Paul Leiber:
> > [...]
> > > Some people on xen-devel pointed out to me two unhandled SMC calls in
> > > the boot logs which could be the root of the problem. I a
Am 31.01.2024 um 19:07 schrieb Andrew M.A. Cater:
On Wed, Jan 31, 2024 at 08:02:47AM +0100, Paul Leiber wrote:
Am 25.01.2024 um 22:28 schrieb Paul Leiber:
Paul
[1]
https://lists.xenproject.org/archives/html/xen-devel/2023-10/msg00796.html
[2] https://developer.arm.com/documentation/den0098/la
On Wed, 2024-01-31 at 15:16 +, Andy Smith wrote:
> Hi,
>
> On Tue, Jan 30, 2024 at 09:50:23PM +0100, hw wrote:
> > On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> > > I think you should read it again until you find the part where it
> > > clearly states what the problem is with using MD
Darac Marjal wrote:
>
>The script works like this: if the root device is specified on the
>kernel command line AND the word "fixrtc" is specified, then get the
>time that the root file system was last mounted. The script then uses
>"date" to set the clock to that date stamp.
>
>I assume that
On Wed, 2024-01-31 at 12:56 -0500, gene heskett wrote:
> [...]
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: No suitable source for initstepslew
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec
On Wed, 2024-01-31 at 09:27 -0500, Gary Dale wrote:
> On 2024-01-30 15:54, hw wrote:
> > On Mon, 2024-01-29 at 11:42 -0500, Gary Dale wrote:
> > > I'm running Debian/Trixie on an AMD64 workstation. I've lost the ability
> > > to see the root directory even when I am logged in as root (su -).
> > >
On 1/31/24 13:19, Greg Wooledge wrote:
On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
# Stop bad estimates upsetting machine clock.
maxupdateskew 10.0
initstepslew 30 192.168.71.3
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock
On Wed, 2024-01-31 at 08:02 +0100, Paul Leiber wrote:
> Am 25.01.2024 um 22:28 schrieb Paul Leiber:
> > Dear Debian user list members,
> >
> > I am trying to run network related stuff (Samba, Zabbix) on a Raspberry
> > Pi 4B in a virtualized environment using Debian Bookworm and Xen. I am
> > ru
On Wed, Jan 31, 2024 at 01:58:41PM +, Schwibinger Michael wrote:
> Good afternoon
> I think
> maybe Im sure
> it is because of rescue mode.
>
Hi Sophie,
Once again: we need to you to show us what commands you run.
We need to see error messages.
if you cannot run sudo or su, we need you to r
On 31/01/2024 12:12, Max Nikulin wrote:
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
I think, the problem is no RTC on some *pi board, certainly c
On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
> # Stop bad estimates upsetting machine clock.
> maxupdateskew 10.0
> initstepslew 30 192.168.71.3
> # This directive enables kernel synchronisation (every 11 minutes) of the
> # real-time clock. Note that it can’t be used alo
On Wed, Jan 31, 2024 at 08:02:47AM +0100, Paul Leiber wrote:
> Am 25.01.2024 um 22:28 schrieb Paul Leiber:
> >
> > Paul
> >
> > [1]
> > https://lists.xenproject.org/archives/html/xen-devel/2023-10/msg00796.html
> > [2] https://developer.arm.com/documentation/den0098/latest/
> > [3]
> > https://d
On 1/31/24 10:44, Greg Wooledge wrote:
On Wed, Jan 31, 2024 at 10:25:40AM -0500, gene heskett wrote:
On 1/31/24 08:53, John Hasler wrote:
Gene writes:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
initstepslew
ma
On 29/01/2024 23:42, Gary Dale wrote:
"ls -l /" just hangs
It may dereference symlinks, call stat, etc. to colorize output. May it
happen that you have automount points or something related to network
mounts?
Does "echo /*" hangs?
Even bash prompt may do some funny stuff. I would try it fr
On Wed, Jan 31, 2024 at 10:25:40AM -0500, gene heskett wrote:
> On 1/31/24 08:53, John Hasler wrote:
> > Gene writes:
> > > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > > the current time on the first cycle as its rebooting?
> >
> > initstepslew
> >
> > man chrony.co
On 1/31/24 08:53, John Hasler wrote:
Gene writes:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
initstepslew
man chrony.conf
deprecated in favor of makestep, and did not work, John.
Thanks, John
Cheers, Gene He
Hi,
On Tue, Jan 30, 2024 at 09:50:23PM +0100, hw wrote:
> On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> > I think you should read it again until you find the part where it
> > clearly states what the problem is with using MD RAID for this. If
> > you still can't find that part, there is l
Max Nikulin wrote:
> I think, the problem is no RTC on some *pi board, certainly chrony out of
> box setup is not ready to such environment and its solution is not
> maxstep.
That's what makestep (initstepslew now being deprecated) is for.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 2024-01-29 at 11:42, Gary Dale wrote:
> I'm running Debian/Trixie on an AMD64 workstation. I've lost the
> ability to see the root directory even when I am logged in as root
> (su -).
>
> This has been happening intermittently for several months. I
> initially thought it might be related to fa
On 2024-01-29 12:55, Hans wrote:
Hi Gary,
before loosing any data, I suggest, to boot from a liuvefile linux. Please use
a modern livefile like Knoppix or Kali-Linux.
If it is not a BIOS problem, you should see the device again and are able to
mount it. If /root is on a seperated partition, you
On 1/31/24 07:13, Max Nikulin wrote:
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
Well, I do have other probs with that machine, mostly with the phys
On 2024-01-29 11:42, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 workstation. I've lost the
ability to see the root directory even when I am logged in as root (su
-).
This has been happening intermittently for several months. I initially
thought it might be related to failing NVME
On 2024-01-30 15:54, hw wrote:
On Mon, 2024-01-29 at 11:42 -0500, Gary Dale wrote:
I'm running Debian/Trixie on an AMD64 workstation. I've lost the ability
to see the root directory even when I am logged in as root (su -).
This has been happening intermittently for several months. I initially
t
On Wed, Jan 31, 2024 at 07:53:01AM -0600, John Hasler wrote:
> Gene writes:
> > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > the current time on the first cycle as its rebooting?
>
> initstepslew
>
> man chrony.conf
Debian 12 has chrony 4.3, and in *that* version of
Good afternoon
I think
maybe Im sure
it is because of rescue mode.
Normal booting did not have this problem.
Anybody familiar with panic?
Regards
Thank You
Sophie
Von: Andrew M.A. Cater
Gesendet: Donnerstag, 25. Januar 2024 18:40
An: debian-user@lists.debian.o
Gene writes:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> the current time on the first cycle as its rebooting?
initstepslew
man chrony.conf
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the other
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
I think, the problem is no RTC on some *pi board, certainly chrony out
of box setup is not ready to su
On Wed, Jan 31, 2024 at 05:29:56AM -, David Chmelik wrote:
> Earlier this or last year I tried to use Devuan to report os-prober
> detects in wrong order. It may detect current OS partition first, but if
> you have more than 10, then it continues from 10, and (if this is all you
> have) goe
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the other
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.
Now it appears to conflict with the other client/servers
Thanks
Cheers, Gene Heskett, CET.
--
"There are fo
41 matches
Mail list logo
