[Petter Reinholdtsen]
Did you test the patch? Did it work?
I gave it try, but it did not solve the problem, my system was still
unbootable ...
Just in case other readers experience this same problem, I've been able to
solve it by downgrading to 2.86.ds1-1 (as found in sarge).
--
BOFH
[Sébastien Phélep]
I gave it try, but it did not solve the problem, my system was still
unbootable ...
Strange. When I test the commands used in the patch, it work for me.
Any error messages or anything else you can tell us to make it easier
to pinpoint the problem?
Just in case other
På Fri, Sep 08, 2006 at 08:59:01AM +0200, Sébastien Phélep skrev:
Just in case other readers experience this same problem, I've been able to
solve it by downgrading to 2.86.ds1-1 (as found in sarge).
Downgrading to 2.86.ds1-15 works too.
mvrgr, Wouter
--
:wq
På Fri, Sep 08, 2006 at 09:18:33AM +0200, Petter Reinholdtsen skrev:
[Sébastien Phélep]
Just in case other readers experience this same problem, I've been able to
solve it by downgrading to 2.86.ds1-1 (as found in sarge).
Good. How did you downgrade when the system was unbootable? Did
[Petter Reinholdtsen]> Any error messages or anything else you can tell us to make it easier> to pinpoint the problem?Well, I must admit I didn't investigate that much.Just tried the patch, seen that the boot process hanged in the same way (as far as I can remember, the only difference was fsck
[Petter Reinholdtsen]
An option might be to mount a private tmpfs (aka mounting it, chdir
into it and umounting it, thus making it available only to the process
running within it), but this will not make the life of mtab.sh easier.
Here is a draft patch for the private tmpfs approach. It is
[Chip Salzenberg]
The checkroot.sh init script sometimes needs to mknod the root
filesystem device as /dev/shm/root so it can fsck. This worked
fine, until the recent change that mounts /dev/shm with the nodev
option. Now, any system that fscks /dev/shm/root is unbootable.
Right. Good
On Thu, Sep 07, 2006 at 04:11:07PM +0200, Petter Reinholdtsen wrote:
[Chip Salzenberg]
The checkroot.sh init script sometimes needs to mknod the root
filesystem device as /dev/shm/root so it can fsck. [...]
Right. Good point. I have forgotten about that code. It need to
stop using
[Chip Salzenberg]
Hrm. Shirley, there's some name in there it could use safely...?
Whatever that name is, checkroot.sh could mount a tmpfs on
/dev/shm/thatname and create the root dev node under it. BTW,
checkroot.sh *does* remove the 'root' node, once the fsck is done,
so what's the
Package: initscripts
Version: 2.86.ds1-16
Severity: critical
Justification: breaks the whole system
The checkroot.sh init script sometimes needs to mknod the root filesystem
device as /dev/shm/root so it can fsck. This worked fine, until the recent
change that mounts /dev/shm with the nodev
10 matches
Mail list logo
