On 05/18/2010 05:05 PM, Gene Heskett wrote: > On Tuesday 18 May 2010, Tom H wrote: >> On Mon, May 17, 2010 at 9:52 PM, Dennis Gilmore<dennis@xxxxxxxx> wrote: >>> On Monday 17 May 2010 08:40:31 pm Ed Greshko wrote: >>>> On 05/18/2010 09:09 AM, Tom H wrote: >>>>> On Mon, May 17, 2010 at 7:49 PM, Rick Stevens<ricks@xxxxxxxx> wrote: >>>>>> On 05/17/2010 02:12 PM, Gene Heskett wrote: >>>>>>> Clarify here: I can do all that as the user. What I can't do, until >>>>>>> somebody decides to fix mkinitrd, is to run it as the user. That is >>>>>>> my specific bitch. And I think its perfectly valid. mkinitrd simply >>>>>>> will not run for anybody but root. >>>>>> >>>>>> And this is a bad thing? I, for one, don't want some low-level user >>>>>> installing a kernel on my machines. I don't want them installing >>>>>> ANYTHING that's global. >>>>> >>>>> +1 >>>> >>>> I get the feeling that Gene isn't talking about the actual installation >>>> of the initrd image. I think he is wondering why something like... >>>> >>>> mkinitrd /tmp/xxx 2.6.30.10-105.2.23.fc11.i686.PAE >>>> >>>> needs root privileges to run. Is there anything inherently wrong is >>>> expecting that to work? >>> >>> "dracut /tmp/test.img 2.6.33.3-85.fc13.x86_64" works just fine as an >>> unprivileged user >> >> I'll take your word for it although but in my F13 VM, neither mkinitrd >> nor dracut can create an initramfs when run as an unpriviledged user - >> which is exactly the behavior that I want. >> > I hadn't tried it yet, but I just did as root, chown -R gene:gene /boot > and a chown -R gene:gene /usr/src/linux-2.6.34-rc3 > Then replaced the mkinird in my script with dracut, and will find out how it > works in about 20 minutes. > > So far the only errors are warnings that the frame_size is greater than 1024 > bytes, sometimes nearly doubled. > > Grrr, I forgot to chown lib/modules/2.6.34-rc3, no perms. Which needs more > than that as my script saves the original if it exists, so gene must have > perms to do the touching and mv'ing too. > > After fixing that, I assume dracut is generating this: > echo in script says: now making a new initrd.2.6.34-rc3.img > W: Could not find program "dhclient" it might be required by network. > W: Could not find program "dhclient" it might be required by network. > W: Could not find program "dhclient" it might be required by network. > E: Failed to install dhclient > Command exited with non-zero status 1 > and no initrd was created. did you install dracut from source? > > Now, as for the dhclient, which I have never needed before as my router is > the only dhcp server on my local network and except for my lappy, all use > host files for local addressing, here is all that locate can find: > > gene@coyote linux-2.6.34-rc3]$ locate dhclient > /usr/share/dracut/modules.d/40network/dhclient-script > /usr/share/dracut/modules.d/40network/dhclient.conf > /usr/share/dracut/modules.d/40network/kill-dhclient.sh > /usr/share/zsh/4.3.10/functions/Completion/Unix/_dhclient > > None of which IMO, should have a bearing on this, so why is dracut bitching? > What makes it think that dhclient even has a dog in this fight? > > And what can I do about it? do not install dracut-network, or disable the dracut network modules $ dracut -o network .... or by editing /etc/dracut.conf: omit_dracutmodules+=" network " -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
