Re: installkernel first?
On Fri, Feb 21, 2003 at 04:27:47PM +1030, [EMAIL PROTECTED] wrote: Not being familiar with single user mode, I didn't realise that only / was mounted in that mode (so why does the handbook put fsck -p as the FIRST command, before mount -a ? sigh). That would be because fsck(8) only works effectively on unmounted file systems -- it really doesn't need anything else trying to write stuff to the filesystem while it's trying to fix it. In fact, in single user mode the root partition is initially mounted read-only, precisely so that fsck(8) can fix up the root filesystem without the danger of writes to the partition at the same time. It used to be the case that the instructions explicitly told you to remount the root fs read-write before doing a 'mount -a', but 'mount -a' has done all of that option changing stuff for you automatically for several years now. The new 'background fsck' capability in FreeBSD 5.0 (as I understand it) relies on the capability to treat the filesystems on the newly booted machine as 'snapshots', so that modifications to the fs are held in cache memory and only written out to the disk once the fsck(8) process has finished cleaning up the underlying stuff. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: installkernel first?
On 2003-02-21 16:27, [EMAIL PROTECTED] wrote: I had taken makeworld.html from the handbook and used links to save as formatted text prior to printing out the contents. Not being familiar with single user mode, I didn't realise that only / was mounted in that mode (so why does the handbook put fsck -p as the FIRST command, before mount -a ? sigh). Because you should never, and I mean NEVER, run fsck on a filesystem that is mounted read-write. All sorts of interesting corruption will keep you busy if you run fsck on read-write filesystems :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: installkernel first?
In [EMAIL PROTECTED], [EMAIL PROTECTED] typed: I'm tracking 4.7 stable. The handbook asks me to: go to single user mode and fsck -p (etc ...) Can't. /dev/ad2s1a: NO WRITE ACCESS /dev/ad2s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (Mounted RW according to fstab). This looks like you aren't running the fsck as root. Either that, or the file modes on the device are screwed up. after make buildworld as single user and reboot also to single user could not cd /usr/src - ls shows the /usr directory containing only /usr/local and no other directories. I CAN find /usr/src (and a number of other useful directories g) as root or user. Possibly something isn't mounted. I am next supposed to make buildkernel # make installkernel. This appeared to work ok (I didn't monitor), but no new kernel appeared in the / directory (I still had my 'old' one). So what does an ls of the kernels look like? Normally, installkernel moves your old kernel to kernel.old, removing any previous kernel.old, then installs the new kernel as kernel.; The next step was to be make installworld but I have not done this in view of the earlier errors. No, the next step is to reboot to the new kernel you just installed. You really haven't given us a lot of information to go on. Knowing exactly what commands you run, and seeing real error messages would help a lot. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: installkernel first?
On Feb 20, 2003, [EMAIL PROTECTED] wrote: I'm tracking 4.7 stable. The handbook asks me to: go to single user mode and fsck -p (etc ...) Can't. /dev/ad2s1a: NO WRITE ACCESS /dev/ad2s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (Mounted RW according to fstab). after make buildworld as single user and reboot also to single user could not cd /usr/src - ls shows the /usr directory containing only /usr/local and no other directories. I CAN find /usr/src (and a number of other useful directories g) as root or user. I am next supposed to make buildkernel # make installkernel. This appeared to work ok (I didn't monitor), but no new kernel appeared in the / directory (I still had my 'old' one). The next step was to be make installworld but I have not done this in view of the earlier errors. Can someone figure this out for me and point me in the right direction? Thanks. -- Brian As of /usr/src/UPDATING: To update from 4.0-RELEASE or later to the most current 4.x-STABLE -- make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE reboot (in single user) [1] make installworld mergemaster [2] reboot In single user mode only the root fs is mounted by default. So for making installworld you have to mount all the slices affected by such a process (usually all other slices like /usr, /var), and also, only the system itself boots up, nothing else is started preventing any problem caused by installing something new under a running old task in memory. If the new kernel fails you can return to the old one without risking incompatibility with the old kernel and the new world. Everything in this order has a reason :). fif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: installkernel first? [ a few additions to this reply ]
On Thu, Feb 20, 2003 at 04:37:10PM +0100, Peter Hollaubek wrote: On Feb 20, 2003, [EMAIL PROTECTED] wrote: I'm tracking 4.7 stable. The handbook asks me to: go to single user mode and fsck -p (etc ...) Can't. /dev/ad2s1a: NO WRITE ACCESS /dev/ad2s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (Mounted RW according to fstab). after make buildworld as single user and reboot also to single user could not cd /usr/src - ls shows the /usr directory containing only /usr/local and no other directories. I CAN find /usr/src (and a number of other useful directories g) as root or user. I am next supposed to make buildkernel # make installkernel. This appeared to ^ A # turns the rest of the line into a comment, I think you mean . So if you did this, you will not have a new kernel. work ok (I didn't monitor), but no new kernel appeared in the / directory (I still had my 'old' one). The next step was to be make installworld but I have not done this in view of the earlier errors. Can someone figure this out for me and point me in the right direction? Thanks. -- Brian As of /usr/src/UPDATING: To update from 4.0-RELEASE or later to the most current 4.x-STABLE -- make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE reboot (in single user) [1] Here first do.. mount -a mergemaster -p make installworld mergemaster [2] reboot In single user mode only the root fs is mounted by default. So for making installworld you have to mount all the slices affected by such a process (usually all other slices like /usr, /var), and also, only the system itself boots up, nothing else is started preventing any problem caused by installing something new under a running old task in memory. If the new kernel fails you can return to the old one without risking incompatibility with the old kernel and the new world. Everything in this order has a reason :). -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: installkernel first?
Quoting Peter Hollaubek [EMAIL PROTECTED]: As of /usr/src/UPDATING: To update from 4.0-RELEASE or later to the most current 4.x-STABLE -- make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE reboot (in single user) [1] make installworld mergemaster [2] reboot In single user mode only the root fs is mounted by default. So for making installworld you have to mount all the slices affected by such a process (usually all other slices like /usr, /var), and also, only the system itself boots up, nothing else is started preventing any problem caused by installing something new under a running old task in memory. If the new kernel fails you can return to the old one without risking incompatibility with the old kernel and the new world. Everything in this order has a reason :). Thanks to all, and particularly Peter for this complete explanation. I had taken makeworld.html from the handbook and used links to save as formatted text prior to printing out the contents. Not being familiar with single user mode, I didn't realise that only / was mounted in that mode (so why does the handbook put fsck -p as the FIRST command, before mount -a ? sigh). Not being familiar with sh (and not thinking too well either) I assumed that make buildkernel # make installkernel was two linked commands on the one line, wheras it should have been read as: # make buildkernel # make installkernel with the # simply indicating root prompt (Thanks, Sue). All-in-all there was actually nothing wrong (except my ignorance g) -- Brian --- This message sent through Adam Internet Webmail http://www.adam.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: installkernel first?
On Fri, Feb 21, 2003 at 04:27:47PM +1030, [EMAIL PROTECTED] wrote: Quoting Peter Hollaubek [EMAIL PROTECTED]: snip Not being familiar with sh (and not thinking too well either) I assumed that make buildkernel # make installkernel was two linked commands on the one line, wheras it should have been read as: # make buildkernel # make installkernel with the # simply indicating root prompt (Thanks, Sue). Yes, well # is the root prompt :). But it is also the start of a shell comment ;). make buildkernel make installkernel Means if and only if make buildkernel succeeds then do a make installkernel It is to do with the status a program terminates with (the exit status). In practise doing a make kernel is ok as well, since that will build and install it only if the build works, so achieving the same end. All-in-all there was actually nothing wrong (except my ignorance g) Naahh..ignorance is me never having learnt how to bang a nail straight into a piece of wood. I do recommend you study up a bit on the shell though. Indenspensible knowledge I am afraid. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
installkernel first?
I'm tracking 4.7 stable. The handbook asks me to: go to single user mode and fsck -p (etc ...) Can't. /dev/ad2s1a: NO WRITE ACCESS /dev/ad2s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (Mounted RW according to fstab). after make buildworld as single user and reboot also to single user could not cd /usr/src - ls shows the /usr directory containing only /usr/local and no other directories. I CAN find /usr/src (and a number of other useful directories g) as root or user. I am next supposed to make buildkernel # make installkernel. This appeared to work ok (I didn't monitor), but no new kernel appeared in the / directory (I still had my 'old' one). The next step was to be make installworld but I have not done this in view of the earlier errors. Can someone figure this out for me and point me in the right direction? Thanks. -- Brian --- This message sent through Adam Internet Webmail http://www.adam.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
