Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-user
Navigation:
Lists: gentoo-user: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-user@g.o
From: Dale <rdalek1967@...>
Subject: Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
Date: Mon, 02 Apr 2012 20:19:33 -0500
Canek Peláez Valdés wrote:
> On Mon, Apr 2, 2012 at 7:19 PM, Dale <rdalek1967@...> wrote:
>> Canek Peláez Valdés wrote:
>>> On Mon, Apr 2, 2012 at 5:21 PM, Dale <rdalek1967@...> wrote:
>>>> Neil Bothwick wrote:
>>>>> zgrep DEVTMP /proc/config.gz
>>>>
>>>>
>>>> Ooops, it sort of snipped a bit much.  lol   Here you go:
>>>>
>>>> root@fireball / # zgrep DEVTMP /proc/config.gz
>>>> # CONFIG_DEVTMPFS is not set
>>>> root@fireball / #
>>>>
>>>> Looks like a nope to me.  ;-)
>>>
>>> That was the reason for asking for your /usr/src/linux/.config file.
>>> The udev ebuild ask for:
>>>
>>> CONFIG_CHECK="~BLK_DEV_BSG ~DEVTMPFS ~HOTPLUG ~INOTIFY_USER ~NET
>>> ~PROC_FS ~SIGNALFD ~SYSFS ~!IDE ~!SYSFS_DEPRECATED
>>> ~!SYSFS_DEPRECATED_V2"
>>>
>>> The dracut ebuild ask for:
>>>
>>> CONFIG_CHECK="~BLK_DEV_INITRD ~DEVTMPFS ~MODULES"
>>>
>>> So please check that you have all those options (and don't have the
>>> ones with !), recompile your kernel, and reboot.
>>>
>>> Also, the divergence between /boot/kernel... and (hd0,0)/kernel... in
>>> your grub could be causing  funny things. Check that also.
>>>
>>> Regards.
>>
>>
>> OK.  I hate modules.  Can they be built into the kernel?  The only
>> module I have is nvidia for my video card.
> 
> MODULES is only for the kernel to be *able* to load modules, not to
> *make* modules. If you use nvidia.ko, you must already have it. All
> the options can be compiled into the kernel; I had them like that:
> 
> $ grep "BLK_DEV_BSG\\|DEVTMPFS\\|HOTPLUG\\|INOTIFY_USER\\|NET=\\|PROC_FS\\|SIGNALFD\\|SYSFS"
> /usr/src/linux/.config
> # CONFIG_SYSFS_DEPRECATED is not set
> CONFIG_HOTPLUG=y
> CONFIG_SIGNALFD=y
> CONFIG_BLK_DEV_BSG=y
> # CONFIG_BLK_DEV_BSGLIB is not set
> # CONFIG_MEMORY_HOTPLUG is not set
> CONFIG_HOTPLUG_CPU=y
> CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
> CONFIG_ACPI_HOTPLUG_CPU=y
> # CONFIG_HOTPLUG_PCI is not set
> CONFIG_NET=y
> CONFIG_INET=y
> CONFIG_WIRELESS_EXT_SYSFS=y
> CONFIG_DEVTMPFS=y
> CONFIG_DEVTMPFS_MOUNT=y
> # CONFIG_SCSI_PROC_FS is not set
> # CONFIG_ISCSI_BOOT_SYSFS is not set
> CONFIG_ETHERNET=y
> CONFIG_USB_USBNET=y
> CONFIG_RTC_INTF_SYSFS=y
> # CONFIG_DMI_SYSFS is not set
> CONFIG_INOTIFY_USER=y
> CONFIG_PROC_FS=y
> CONFIG_SYSFS=y
> 
> 
>>
>> Also, if you can put this in one email, what about the /dev line in fstab?
> 
> /dev should not be in /etc/fstab; but since you had this error:
> 
>> switch_root: failed to mount moving /dev to /sysroot/dev: Invaild argument
>> switch_root: forcing unmount of /dev
>> switch_root: failed to unlink dev: Directory not empty
> 
> I thought that it was maybe because you had /dev  on fstab. Now we
> know it was because you didn't compile DEVTMPFS in your kernel.
> 
>> I didn't check the ebuild but I don't recall seeing anything when I
>> emerged dracut either.  o_O   Maybe we are on to something here.  ^_O
> 
> The messages appear for sure; CONFIG_CHECK is defined in
> /usr/portage/eclass/linux-info.eclass, and if a config option is
> missing, a non-fatal warning will appear. If you have them, check your
> emerge logs:
> 
> cat /var/log/portage/sys-fs\:udev-* | less
> 
> You can look for the string:
> 
>  * Checking for suitable kernel configuration options...
>  [ ok ]
> 
> (Obviously that's in my case).
> 
> You could also reemerge udev and dracut; if you haven't changed your
> kernel config options, they will complain loudly about it.
> 
> I think that will solve the mistery; however, we will not know until
> you reboot and actually test it (after recompiling your kernel, of
> course).
> 
> Regards.


I think I got it all sorted and am building a new kernel.  It will have
a -2 on the end instead of a -1.  I'll test it in a bit.  I got some
things to prepare for tomorrow plus we have storms coming in tonight.
The rain is already on the radar and it is a bit windy here.  May take a
bit before I reboot.  Just depends.  ;-)

I'm hoping to get this sorted so I can then move on to more issues, and
maybe a new thread. lol

Will reply in a bit on what blows up.  ROFL

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"


Replies:
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Dale
References:
Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Alan Mackenzie
Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Neil Bothwick
Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- che
RE: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Mike Edenfield
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Alan Mackenzie
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Alan McKinnon
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Alan Mackenzie
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Alan McKinnon
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Alan Mackenzie
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Neil Bothwick
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Alan Mackenzie
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Dale
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Canek Peláez Valdés
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Dale
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Canek Peláez Valdés
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Dale
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Canek Peláez Valdés
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Dale
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Neil Bothwick
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Dale
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Canek Peláez Valdés
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Dale
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
-- Canek Peláez Valdés
Navigation:
Lists: gentoo-user: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
Next by thread:
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
Previous by date:
Re: Re: After /usr conflation: why not copy booting software to /sbin rather than initramfs?
Next by date:
trouble understanding a slot conflict


Updated May 04, 2012

Summary: Archive of the gentoo-user mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.