Bug 375

Summary:	mkinitrd silently fails if /sys is not mounted.
Product:	Mageia	Reporter:	AL13N <alien>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	anssi.hannula, fundawang, marja11, pterjan, tmb
Version:	1	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mkinitrd	CVE:
Status comment:

Description AL13N 2011-03-15 02:47:46 CET

Description of problem:

internally mkinitrd uses modprobe to get module dependencies. but mkinitrd succeeds (but doesn't get dependencies) due to /sys not being mounted.

i would like modprobe not to use /sys if it's just getting dependencies (which it should only check the .dep file)

failing that, i would like mkinitrd to exit with an error if /sys isn't mounted.


when doing chrooted installs, this could be a huge improvement. ie: don't waste time trying to find out why ext4 in initrd is missing jbd2.

Reproducible: 

Steps to Reproduce:

Ahmad Samir 2011-04-21 06:43:27 CEST

CC: (none) => pterjan, tmb
Source RPM: module-init-tools => mkinitrd

Comment 1 Pascal Terjan 2011-04-21 15:00:12 CEST

I think having an error would be the best

Mounting /sys should be part of creating a chroot, together with mounting /proc. Many things will not work correctly without /sys.

Comment 2 Marja Van Waes 2011-10-05 21:14:40 CEST

@ AL13N

This enhancement still needed?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 3 AL13N 2011-10-05 23:18:46 CEST

yes, either an error message at the very least, but i would like mkinitrd to rely less on what's being used at the moment, and more on what system it has below, so i can more easily make initrds for other machines

in all actuallity, /sys is not used all that often in mkinitrd, except for getting dependencies of modules, afaict.

Marja Van Waes 2011-10-23 16:59:40 CEST

Keywords: NEEDINFO => (none)

Comment 4 Marja Van Waes 2011-12-16 08:17:37 CET

cc'ing some committers of mkinitrd that weren't in the cc of this  bug, yet

CC: (none) => anssi.hannula, fundawang

Comment 5 Marja Van Waes 2012-01-31 08:25:54 CET

@ AL13N

do you still use mkinitrd in cauldron? If not, do you agree on closing this bug?

Comment 6 Marja Van Waes 2012-05-26 13:07:57 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 7 Marja Van Waes 2012-06-11 19:13:58 CEST

Sorry AL13N, there were no "me too's" on this bug, you didn't reply to comment 5, nor to comment 6. We don't even know whether you still use mkinitrd

I'm closing this bug as OLD

You know how to reopen it when needed :)

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 8 AL13N 2012-06-11 19:53:17 CEST

i've switched it to  mga1, since mga2 uses dracut.

besides, it's not something anyone easily gets, you'd likely have to forget to mount /sys in a chrooted env and try to make initrd. it was more something the mkinitrd maintainer could fix, so i'm leaving it closed with old.

Version: Cauldron => 1