Re: Cleanout & rebuild of /dev on -current
On Wed, Oct 18, 2000 at 09:50:52PM -0700, John W. De Boskey wrote: >So, what would the correct sequence be to wipeout > /dev and recreate it? (create /dev in an alternate > location and compare the two...??) After mergemastering, and if /dev/MAKEDEV gets updated, I usually just do an 'sh MAKEDEV all', then use 'ls -lt' which will list all the old and non-standard devices at the bottom of the listing for easy identification. Then I selectively MAKEDEV the ones I still need, i.e., you may then need to selectly MAKEDEV devices such as da4 and higher, vn0, ccd0, etc if you use those. I think Doug mentioned that it won't re-create your disk slices. I always do that manually for the disk where the root filesystem is located. With a little scripting, all of this could be automated. -Brian -- Brian Dean [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Cleanout & rebuild of /dev on -current
On Thu, Oct 19, 2000 at 09:39:27AM +0200, Szilveszter Adam wrote: > >Given that the above can be automated on a live > > system, is this something that can/should be added > > to make installworld/world? (or atleast generate > > a report of changed devices, or devices that can > > nolonger be created..) > > It already is, if you do it the recommended way, also running mergemaster(8) > during the process, that is. It also does a MAKEDEV in /var/tmp/root *and* > automatically checks for differences. OK it seems I was just making this up. After checking the code for mergemaster(8), it only checks MAKEDEV itself for changes. Well, this way you certainly will catch all *new* devs, but will not delete old ones. But my other suggestion still stands. Also devfs may be an option, but I have never used it because it is still marked as highly experimental and "doesn't handle disk slices well" to quote the NOTES file. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Cleanout & rebuild of /dev on -current
Hello On Wed, Oct 18, 2000 at 09:50:52PM -0700, John W. De Boskey wrote: > Hi, > >Interesting question was posed to me which I can't > locate a straight answer to. > >We've been following -current for a few years now. > Over time, the devices in /dev have moved around, new > added, and old deleted (ie: we've never had to restage > one of these machines and/or purge it and reinstall). > >So, what would the correct sequence be to wipeout > /dev and recreate it? (create /dev in an alternate > location and compare the two...??) I think that just running MAKEDEV with all options you might need (like snd0 or whatever) and then (after making sure you did not forget anything, eg disk slices:-) simply do a find(1) for anything that is older than the recreated devices and removing them should be fine. (I remember doing this once sometime between 3.x and 4.x with no ill effects.) But your solution is certainly also workable. >Given that the above can be automated on a live > system, is this something that can/should be added > to make installworld/world? (or atleast generate > a report of changed devices, or devices that can > nolonger be created..) It already is, if you do it the recommended way, also running mergemaster(8) during the process, that is. It also does a MAKEDEV in /var/tmp/root *and* automatically checks for differences. Hope this helps:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Cleanout & rebuild of /dev on -current
On Wed, 18 Oct 2000, John W. De Boskey wrote: > Hi, > >Interesting question was posed to me which I can't > locate a straight answer to. > >We've been following -current for a few years now. > Over time, the devices in /dev have moved around, new > added, and old deleted (ie: we've never had to restage > one of these machines and/or purge it and reinstall). > >So, what would the correct sequence be to wipeout > /dev and recreate it? (create /dev in an alternate > location and compare the two...??) > >Given that the above can be automated on a live > system, is this something that can/should be added > to make installworld/world? (or atleast generate > a report of changed devices, or devices that can > nolonger be created..) Well, answer A) is that devfs makes this all meaningless. I've been running it on two machines (admittedly, both workstations) for several weeks now. Answer B) is, "How brave are you?" :) I've had success with 'cp -R /dev /dev-old; rm -rf /dev/[^M]*; cd /dev/; /bin/sh MAKEDEV all'. Of course, you have to remake your disk devices by hand after this, which mitigates against it being automated in my book. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Cleanout & rebuild of /dev on -current
Hi, Interesting question was posed to me which I can't locate a straight answer to. We've been following -current for a few years now. Over time, the devices in /dev have moved around, new added, and old deleted (ie: we've never had to restage one of these machines and/or purge it and reinstall). So, what would the correct sequence be to wipeout /dev and recreate it? (create /dev in an alternate location and compare the two...??) Given that the above can be automated on a live system, is this something that can/should be added to make installworld/world? (or atleast generate a report of changed devices, or devices that can nolonger be created..) Comments welcome. -John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
