[Pkg-sysvinit-devel] Some remaining work on sysvinit

Petter Reinholdtsen pere at hungry.com
Fri Jan 27 11:21:13 UTC 2006


[Thomas Hood]
> There are still some bugs in sysvinit that should be addressed.
> Please look for your name below.  :)
> 
> # 349984: [Debian GNU/kfreebsd] Cannot update from initscripts 2.86.ds-1.6 to 2.86.ds-1.11
> 
>   I know nothing about the hurd.  Can someone please reply to this?

I believe freebsd knowledge is needed, not hurd. :)

> # 349275: mountall.sh: "Mounting local filesystems... failed" when system has only a single partition
> 
>   I think that this requires a patch to the mount program so that it
>   will return different statuses for "already mounted" and "mount
>   failed".  Anyone disagree?

Another alternative is to update mtab with the file systems we mounted
while the root was read-only.  Perhaps having /run/ to write mtab
into? :)

> # 328474: sysvinit: selinux error message at boot time
> # 329328: sysvinit attempts to mount selinux when it is not available
> 
>   I believe that Ubuntu has added a patch to fix this.  Someone care
>   to investigate?

I believe I saw a patch to just hide the message.  Is that the correct
fix?

> # 349149: sysvinit: 40_selinux.dpatch printf errors to same console
> as rest of output
> 
>   Pere: Any comment?

Sounds good to me.  I just applied the patch provided by the selinux
community. :)

> # 339850: initscripts: Should check filesystems after an unclean shutdown
> 
>   Pere: I added a comment to the bug log.  Your reply?

Will try to have a look, but today. :)

> # 67321: sysvinit: Please provide a way to bypass sulogin in
> emergency (-b) mode
> 
>   Miquel: Can you please reply to this report?
> 
> # 181756: sysvinit: init: Please send output to all consoles
> 
>   Miquel: What do you think?

No idea.

> # 348172: halt: please spin down SATA disks as well
> 
>   Anyone have expertise in this area?

I have not, but believe it is a good idea. :)

> # 337444: initscripts: Boot process does not halt if both fsck and
> sulogin fail
> 
>   Any takers?

Should it halt?  how are one going to fix it if it does?



More information about the Pkg-sysvinit-devel mailing list