Mkinitcpio-nfs-utils hook for net without wireless

nomorewindows · 2013-10-04 00:30:27

Is there a way to make a net hook for diskless clients without including wireless? Make one called net-nowireless or something like that. If my diskless client has a wireless card, I'd have to go into emergency shell to connect the wireless network device to a wireless network if it would even let me do that. Otherwise, I have to blacklist any perceivable wireless module and include it in my mkinitcpio.conf. Some wireless devices can be canned just by not including the firmware. Anyways, my diskless client hangs on the wireless deadlock when initializing network interfaces. It would also probably remove firmware messages and make the initramfs-linux.img smaller. The PXE clients can only boot from the hardwired ethernet clients for now.

Doing a mkinitcpio -L doesn't even list the net hook, but mkinitcpio -H net shows the details.

Last edited by nomorewindows (2013-10-05 12:22:32)

Lone_Wolf · 2013-10-05 11:26:05

$ mkinitcpio -H net
==> ERROR: Hook 'net' not found
$ mkinitcpio --version
mkinitcpio 0.15.0

The hooks section on the mkinitcpio wiki page does list a net hook though, maybe it was removed ?

nomorewindows · 2013-10-05 12:22:11

You have to have mkinitcpio-nfs-utils for the net hook to be present. This is just what it is installed to make the diskless client work.

Lone_Wolf · 2013-10-05 13:55:22

Found it, and looked into the hook files.

It does look like the hook tries to connect using all autodetected network devices, regardless of number and type of devices.
While it may be possible to differentiate between wired and wireless devices, that will still give issues if there are multiple wired/wireless devices.

Maybe a configuration file could be added that specifies which devices nfs should use.
If there's no config file present in the initramfs, it should just default to all detected devices as it does now.

I suggest you ask about this on the arch-projects mailing list, or create a feature request for mkinitcpio-nfs-utils to add this functionality.

nomorewindows · 2013-10-05 14:45:31

Lone_Wolf wrote:

It does look like the hook tries to connect using all autodetected network devices, regardless of number and type of devices.
While it may be possible to differentiate between wired and wireless devices, that will still give issues if there are multiple wired/wireless devices.
Maybe a configuration file could be added that specifies which devices nfs should use.
If there's no config file present in the initramfs, it should just default to all detected devices as it does now.

Although I haven't tried it this way, it makes sense because that's what it does with the wireless, which just has the unresolvable problem, whereas dual ethernet or more, as long as it satisfies getting an address via dhcp, can probably still boot. Maybe this is the reason why OpenBSD is still anal about using stateful routines through rarpd and bootparamd. I've tried to boot OpenBSD under Arch, using rarp, but I guess it doesn't answer satisfactory to OpenBSD's diskless request. The purpose of stateless is to boot anybody. Various options can be set in pxelinux.cfg based on MAC address, but maybe these aren't known ahead of time to boot a customized initramfs-linux.img.

The real boon was to turn on a dumb-terminal and as soon as it came on, the login prompt was present. This was probably a function of getty.

Arch Linux

#1 2013-10-04 00:30:27

Mkinitcpio-nfs-utils hook for net without wireless

#2 2013-10-05 11:26:05

Re: Mkinitcpio-nfs-utils hook for net without wireless

#3 2013-10-05 12:22:11

Re: Mkinitcpio-nfs-utils hook for net without wireless

#4 2013-10-05 13:55:22

Re: Mkinitcpio-nfs-utils hook for net without wireless

#5 2013-10-05 14:45:31

Re: Mkinitcpio-nfs-utils hook for net without wireless

Board footer