Re: f37/f38 "systemd still uses the old version"

2023-02-16 Thread Robert Nichols
The usual cause is keeping your hardware clock in local time when your timezone offset is negative. Systemd initially checks /etc/fstab _before_ the system clock has been adjusted for the timezone offset. The solution is to keep your hardware clock in UTC, controlled by the third line in /etc/a

Re: [f37] (hint) your fstab has been modified, but systemd still uses...

2022-09-18 Thread Robert Nichols
On 9/18/22 6:13 PM, Felix Miata wrote: # mountsrv mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-reload' to reload. mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-

Re: rpm database corrupted after fedeup from 20 to 21

2014-12-26 Thread Robert Nichols
On 12/24/2014 09:50 AM, Mick wrote: Hi Serge; It looks like reload time. Lots of errors 'Bad Magic Number', ' unexpected file type or format' If you have a list of all installed packages, such as in /var/log/rpmpkgs, then you could start with a clean /var/lib/rpm and install them all with "r

Re: Well, I have tried systemd now ...

2011-04-26 Thread Robert Nichols
On 04/26/2011 08:22 PM, Scott Robbins wrote: > On Tue, Apr 26, 2011 at 05:31:17PM -0700, Adam Williamson wrote: >> On Tue, 2011-04-26 at 16:41 -0400, Bill Nottingham wrote: >> >>> Perhaps I wasn't clear. I was asking what you're using separate-/usr >>> for. Is it just out of tradition, or do you ha

Re: cannot boot beyond runlevel 1

2011-01-03 Thread Robert Nichols
On 01/03/2011 11:55 AM, Bill Nottingham wrote: > Michal Jaegermann (mic...@harddata.com) said: >>> To be clear, as I alluded to in my previous replies, none of my (100+) OS >>> installations has rhgb or quiet on any kernel line in any stanza I ever use, >> >> Then I am at loss how to explain that y