[gentoo-user] file dates on system totally bodged

[gentoo-user] file dates on system totally bodged

[Alan E. Davis]

Over a period of a week or so, while I was celebrating the holidays,
my system experienced a hardware hiccough, causing system
clock/hardware clock time to change to 2020.  The upshot is that a
bunch of merges, a kernel compile, and various other system components
have files that are way out of date.

I have experimentally touched some files with the current date and
time.  Before I blow my holiday reverie in changing dates in this way,
piecemeal, I want to ask the list what special issues I need to be
aware of regarding system dates/file dates and times, etc., and any
advice on fixing this mess.

Thanks for help in the past, and I would also like to add my regards
and best wishes for a great 2006.

Alan Davis

"There are some people whom it is one's duty to offend."  ---Lord Reith

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] file dates on system totally bodged

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

On Mon, 2 Jan 2006 10:57:00 +1000, Alan E. Davis wrote:

> Over a period of a week or so, while I was celebrating the holidays,
> my system experienced a hardware hiccough, causing system
> clock/hardware clock time to change to 2020.  The upshot is that a
> bunch of merges, a kernel compile, and various other system components
> have files that are way out of date.
> 
> I have experimentally touched some files with the current date and
> time.

Changing dates manually will confuse portage, which keeps track of the
datestamps of all files it installs. The upshot is that it will no
remove files where the dates have changed. The safest method of correcting
the dates would be to re-emerge the affected packages. Use genlop --list
--date XXX to see which you installed during the problem period, then
emerge them all with the --oneshot option.


-- 
Neil Bothwick

If at first you don't succeed, call it Windows NT.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] file dates on system totally bodged

[Alan E. Davis]

On 1/2/06, Neil Bothwick <neil@digimed.co.uk> wrote:

> Changing dates manually will confuse portage, which keeps track of the
> datestamps of all files it installs. The upshot is that it will no
> remove files where the dates have changed. The safest method of correcting
> the dates would be to re-emerge the affected packages. Use genlop --list
> --date XXX to see which you installed during the problem period, then
> emerge them all with the --oneshot option.
>

Thank you for the uesful inshght.

 genlop just says:
#genlop --list --date 01/01/2020 01/01/2021
Date 2020010100:00:00 is in the future, not good

I got a list of packages with this:

#genlop --list | grep 2020 |cut -b 38- | emerge >2020list

Is it possible to run emerge using a list of files as input?  Or stdin?

Alan

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] file dates on system totally bodged

[Alan E. Davis]

Thank you.  I found out my cute genlop command doesn't work the way I
had intended.  However, I was able to appreciate and use your little
one-liners.  Fantastic.

In particular, I generated a file with a hybrid of your sed command
and my list-to-a-file idea, and edit the lines that didn't work as
shown by --pretend.  Then I used "cat ... ... ... " to update.

Thank you.  Now that that's out of the way, maybe, I wonder what else
may be stuck due to the date  blowup.  For sure, there are some config
files that the system points out.

Thank you again and again,

Alan
On 1/2/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 2 Jan 2006 22:14:27 +1000, Alan E. Davis wrote:
>
> >  genlop just says:
> > #genlop --list --date 01/01/2020 01/01/2021
> > Date 2020010100:00:00 is in the future, not good
>
> The solution to which is obvious, don't give a date in the future. --date
> works with a single argument, using the present time as the end time.
>
>
> > I got a list of packages with this:
> >
> > #genlop --list | grep 2020 |cut -b 38- | emerge >2020list
> >
> > Is it possible to run emerge using a list of files as input?  Or stdin?
>
> cat somefile | xargs emerge --oneshot --pretend
>
> or you could do it all in one step with, for example
>
> genlop --nocolor --list --date last week | grep '>>>' | sed 's/.*>>> /=/' | xargs emerge --oneshot --pretend
>
>
> --
> Neil Bothwick
>
> Photons have mass? I didn't know they were catholic!
>
>
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] file dates on system totally bodged

[Alan E. Davis]

I have been seeing a lot of these messages:

 * Some file in '/etc/{conf.d,init.d}' have Modification time in the future!

I post here a list of those files, as I contemplate what to do about this:

# ls -lrt /etc/conf.d

  shows the following with 2020 dates:

-rw-r--r--  1 root root   318 Dec 30  2020 net
-rw-r--r--  1 root root   217 Dec 30  2020 local.stop
-rw-r--r--  1 root root   117 Dec 30  2020 local.start
-rw-r--r--  1 root root   709 Dec 30  2020 keymaps
-rw-r--r--  1 root root    83 Dec 30  2020 hostname
-rw-r--r--  1 root root   415 Dec 30  2020 env_whitelist
-rw-r--r--  1 root root   561 Dec 30  2020 domainname
-rw-r--r--  1 root root   722 Dec 30  2020 consolefont
-rw-r--r--  1 root root   609 Dec 30  2020 clock
-rw-r--r--  1 root root   254 Dec 30  2020 bootmisc
-rw-r--r--  1 root root 27908 Dec 30  2020 net.example
-rw-r--r--  1 root root  6577 Dec 30  2020 rc



# ls -lrt /etc/init.d | grep 2020
-rwxr-xr-x  1 root root   915 Dec 30  2020 urandom
-rwxr-xr-x  1 root root   215 Dec 30  2020 shutdown.sh
lrwxrwxrwx  1 root root    23 Dec 30  2020 runscript.sh ->
../../sbin/runscript.sh
-rwxr-xr-x  1 root root   276 Dec 30  2020 rmnologin
-rwxr-xr-x  1 root root   221 Dec 30  2020 reboot.sh
-rwxr-xr-x  1 root root   670 Dec 30  2020 numlock
-rwxr-xr-x  1 root root  3055 Dec 30  2020 netmount
lrwxrwxrwx  1 root root     6 Dec 30  2020 net.eth0 -> net.lo
-rwxr-xr-x  1 root root  2956 Dec 30  2020 modules
-rwxr-xr-x  1 root root   620 Dec 30  2020 local
-rwxr-xr-x  1 root root  1859 Dec 30  2020 keymaps
-rwxr-xr-x  1 root root  1047 Dec 30  2020 hostname
-rwxr-xr-x  1 root root  5110 Dec 30  2020 halt.sh
lrwxrwxrwx  1 root root    23 Dec 30  2020 functions.sh ->
../../sbin/functions.sh
-rwxr-xr-x  1 root root  1526 Dec 30  2020 domainname
lrwxrwxrwx  1 root root    21 Dec 30  2020 depscan.sh -> ../../sbin/depscan.sh
-rwxr-xr-x  1 root root  1414 Dec 30  2020 consolefont
-rwxr-xr-x  1 root root  3022 Dec 30  2020 checkroot
-rwxr-xr-x  1 root root  1205 Dec 30  2020 checkfs
-rwxr-xr-x  1 root root  3637 Dec 30  2020 bootmisc
-rwxr-xr-x  1 root root   515 Dec 30  2020 cupsd
-rwxr-xr-x  1 root root  2589 Dec 30  2020 clock
-rwxr-xr-x  1 root root 26683 Dec 30  2020 net.lo
-rwxr-xr-x  1 root root  1319 Dec 30  2020 localmount


If I touch these as current, will it hurt anything?

Alan Davis

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] file dates on system totally bodged

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]

On Tue, 3 Jan 2006 13:44:09 +1000, Alan E. Davis wrote:

> If I touch these as current, will it hurt anything?

No, because /etc/conf.d/ and /etc/init.d are usually in CONFIG_PROTECT,
so portage wouldn't touch these files anyway.


-- 
Neil Bothwick

You sound reasonable...Time to up my medication.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]