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

Reply via email to