[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#312871: marked as done (initrd-tools: please provide support for udev _and_ selinux)

Your message dated Mon, 05 May 2008 10:23:25 +0200
with message-id <1209975805.297728.28809.nullmailer@xanadu.blop.info>
and subject line initrd-tools has been removed from Debian, closing #312871
has caused the Debian Bug report #312871,
regarding initrd-tools: please provide support for udev _and_ selinux
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
312871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312871
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: initrd-tools
Version: 0.1.77
Severity: wishlist


just like is done in FC2 and above's initrd, please could you consider
putting uclib'd udev into the initrd, and then making sure that the
programs in it are selinux-enabled / aware?

i had to make a pig's ear of debian/selinux when udev is installed
because of tmpfs extended attributes, because of mounting /dev,
because the recreation of the non-persistent entries in /dev end
up with the wrong selinux attributes, i had to run "restorecon" on
every single entry **AFTER** udev had run... it was awful.

such a mess, and the boot-time is adversely affected, too.

oh - and as for /.dev - CHRIST what an awful mess, and the selinux
maintainers on www.nsa.gov won't even LISTEN about supporting
correct restoration of file contexts in /.dev, so if you accidentally
end up losing the file contexts on anything in /.dev - YOU CAN'T BOOT
THE MACHINE.

[some types of filesystem corruption can result in extended
attributes being truncated.  if that happens to anything in
/.dev, you are xxxxxed for a boot.  at least with /dev being
managed by udev, the selinux file contexts on your device
inodes get recreated!]

i can't remember the details, but the half-way-house solution of debian
at the moment (where /dev is managed by and created by an initscript
/etc/init.d/udev) is a bolloxed up idea.

Fedora's solution - start udev from the initrd: correct.

Gentoo's solution - don't _have_ an initrd: correct.

Debian's solution - start up initially in a half-cocked
environment, move /dev out the way to /.dev and then start
udev later: total bollocks.

l.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux highfield 2.6.11-1-686 #1 Fri May 20 07:34:54 UTC 2005 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages initrd-tools depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  cpio                          2.5-1.1    GNU cpio -- a program to manage ar
ii  cramfsprogs                   1.1-4      Tools for CramFs (Compressed ROM F
ii  dash                          0.4.21     The Debian Almquist Shell
ii  fileutils                     5.2.1-2    The GNU file management utilities 
ii  util-linux                    2.12-6     Miscellaneous system utilities

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 0.1.84.2+rm

The initrd-tools package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/393092 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.
-- 
Lucas

--- End Message ---
Reply to: