Re: config(8) broken
Matthew Jacob wrote: > > *groan* I'm having trouble believing that *config* of all things is now > dependent on time to avoid bugs... This is *one* for the books Yep. That's why I disabled it and will replace it with something more robust. In hindsight it was Not A Good Thing. > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > Bruce Evans wrote: > > > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > > > > > Bruce Evans wrote: > > > > > Config now removes almost all headers: > > > > > ... > > > > > This is starting from compile directory populated by a previous versi on > > > > > of config. Starting from scratch, config seems to work for the first > > > > > run. The second run complains about all headers, deletes them all, a nd > > > > > doesn't create any. The third run seems to work... > > > > > > > > What are the chances that you did this on a mount -o noatime file syste m? > > > > > > Very high :-). > > > > Heh. :-) > > > > > I'm surprised the bug doesn't affect fast machines, since config doesn't > > > seem to sleep for >= 1 second to ensure that the atimes advance with > > > the standard mount options. > > > > I was primarily testing it on a dual P3-733 w/ 1G ram which was running > > config nearly instantly. I never saw this problem until I tested it > > on a fresh machine that (by sheer chance) happened to be running noatime (i t > > was a laptop). For what it's worth, I did roll the start time back by one > > second to give a bit more comfort - getting rid of the trays isn't all that > > critical. > > > > For UFS at least, we seem to update the atime instantly but schedule > > writeback to the inode "whenever". > > > > 148# date ; ls -lutT foo1 ; cat foo1 ; ls -lutT foo1; date > > Mon Jan 29 08:18:02 PST 2001 > > -rw-r--r-- 1 root wheel 4 Jan 29 08:16:25 2001 foo1 > > foo > > -rw-r--r-- 1 root wheel 4 Jan 29 08:18:02 2001 foo1 > > Mon Jan 29 08:18:02 PST 2001 > > > > This is all within the same second "tick" and the atime change was visible. > > > > > Bruce > > > > > > Cheers, > > -Peter > > -- > > Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: config(8) broken
*groan* I'm having trouble believing that *config* of all things is now dependent on time to avoid bugs... This is *one* for the books On Mon, 29 Jan 2001, Peter Wemm wrote: > Bruce Evans wrote: > > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > > > Bruce Evans wrote: > > > > Config now removes almost all headers: > > > > ... > > > > This is starting from compile directory populated by a previous version > > > > of config. Starting from scratch, config seems to work for the first > > > > run. The second run complains about all headers, deletes them all, and > > > > doesn't create any. The third run seems to work... > > > > > > What are the chances that you did this on a mount -o noatime file system? > > > > Very high :-). > > Heh. :-) > > > I'm surprised the bug doesn't affect fast machines, since config doesn't > > seem to sleep for >= 1 second to ensure that the atimes advance with > > the standard mount options. > > I was primarily testing it on a dual P3-733 w/ 1G ram which was running > config nearly instantly. I never saw this problem until I tested it > on a fresh machine that (by sheer chance) happened to be running noatime (it > was a laptop). For what it's worth, I did roll the start time back by one > second to give a bit more comfort - getting rid of the trays isn't all that > critical. > > For UFS at least, we seem to update the atime instantly but schedule > writeback to the inode "whenever". > > 148# date ; ls -lutT foo1 ; cat foo1 ; ls -lutT foo1; date > Mon Jan 29 08:18:02 PST 2001 > -rw-r--r-- 1 root wheel 4 Jan 29 08:16:25 2001 foo1 > foo > -rw-r--r-- 1 root wheel 4 Jan 29 08:18:02 2001 foo1 > Mon Jan 29 08:18:02 PST 2001 > > This is all within the same second "tick" and the atime change was visible. > > > Bruce > > > Cheers, > -Peter > -- > Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: config(8) broken
Bruce Evans wrote: > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > Bruce Evans wrote: > > > Config now removes almost all headers: > > > ... > > > This is starting from compile directory populated by a previous version > > > of config. Starting from scratch, config seems to work for the first > > > run. The second run complains about all headers, deletes them all, and > > > doesn't create any. The third run seems to work... > > > > What are the chances that you did this on a mount -o noatime file system? > > Very high :-). Heh. :-) > I'm surprised the bug doesn't affect fast machines, since config doesn't > seem to sleep for >= 1 second to ensure that the atimes advance with > the standard mount options. I was primarily testing it on a dual P3-733 w/ 1G ram which was running config nearly instantly. I never saw this problem until I tested it on a fresh machine that (by sheer chance) happened to be running noatime (it was a laptop). For what it's worth, I did roll the start time back by one second to give a bit more comfort - getting rid of the trays isn't all that critical. For UFS at least, we seem to update the atime instantly but schedule writeback to the inode "whenever". 148# date ; ls -lutT foo1 ; cat foo1 ; ls -lutT foo1; date Mon Jan 29 08:18:02 PST 2001 -rw-r--r-- 1 root wheel 4 Jan 29 08:16:25 2001 foo1 foo -rw-r--r-- 1 root wheel 4 Jan 29 08:18:02 2001 foo1 Mon Jan 29 08:18:02 PST 2001 This is all within the same second "tick" and the atime change was visible. > Bruce Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: config(8) broken
On Mon, 29 Jan 2001, Peter Wemm wrote: > Bruce Evans wrote: > > Config now removes almost all headers: > > ... > > This is starting from compile directory populated by a previous version > > of config. Starting from scratch, config seems to work for the first > > run. The second run complains about all headers, deletes them all, and > > doesn't create any. The third run seems to work... > > What are the chances that you did this on a mount -o noatime file system? Very high :-). I'm surprised the bug doesn't affect fast machines, since config doesn't seem to sleep for >= 1 second to ensure that the atimes advance with the standard mount options. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: config(8) broken
Bruce Evans wrote: > Config now removes almost all headers: > > Removing stale header: apm.h > Removing stale header: opt_userconfig.h > Removing stale header: opt_syscons.h > Removing stale header: opt_cpu.h > Removing stale header: opt_clock.h > ... > make: don't know how to make opt_global.h(continuing) > make: don't know how to make opt_user_ldt.h(continuing) > make: don't know how to make opt_posix.h(continuing) > make: don't know how to make opt_nfs.h(continuing) > make: don't know how to make opt_bootp.h(continuing) > ... > > This is starting from compile directory populated by a previous version > of config. Starting from scratch, config seems to work for the first > run. The second run complains about all headers, deletes them all, and > doesn't create any. The third run seems to work... > > Bruce What are the chances that you did this on a mount -o noatime file system? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
