Mailinglist Archive: opensuse-factory (818 mails)

[Josef Reidinger <jreidinger@xxxxxxx>]

Carlos E. R. wrote:
> El 2008-10-30 a las 15:26 +0100, Josef Reidinger escribió:
>
> [ sending back to mail list ]
>
> > > So, boot is there, mounted. However, when I chroot, it dissapears:
> > >
> > >
> > > nimrodel:~ # chroot /otros/test_d/ /bin/bash --login
> > > nimrodel:/ # mount
> > > /dev/hdd14 on / type reiserfs (rw,acl,user_xattr)
> > > /proc on /proc type proc (rw)
> > > sysfs on /sys type sysfs (rw)
> > > debugfs on /sys/kernel/debug type debugfs (rw)
> > > udev on /dev type tmpfs (rw)
> > > devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
> > > securityfs on /sys/kernel/security type securityfs (rw)
> > >
> > >
> > > What's happened? This worked before. :-?
>
> > I think that's problem in powerpc, try in chroot what do if you instead
> > chroot use cat /proc/mounts it should work, I tested it now and looks
> > fine for me. (so after beta4 this should work, I didn't fix it before
> > deadline for beta4).
>
> I don't have powerpc, just pentium4.
>
> But I don't understand what you sugest I do?
>
>
> I was thinking that it is not a problem in chroot, but in the script
> that the kernel installation runs, something has changed there since
> some months. The partition is mounted, simply that it is not listed in
> mtab.
>
> NOT_nimrodel:~ # mount /boot/
> mount: /dev/hda8 already mounted or /boot busy
>
> See?
>
> Perhaps I have to write myself to mtab :-?
>
> -- Saludos
>        Carlos E.R.

Yes, change is in perl-Bootloader which now check if you have separate
boot and if so if you have mounted that. Because if it isn't mounted
then you during kernel upgrade run to serious problem like unbootable
system. Please check if in chroot enviroment is /proc/mounts correct,
because it will be used to fix this problem.
thanks JR
-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx