Talk:Diskless system

From ArchWiki
Jump to: navigation, search

how to organize

Heh, we go back to 3+ articles again? :P We're actually agreeing here I think, but I would say "sub-articles" rather than dedicated articles--Buhman (talk) 10:22, 13 December 2012 (UTC)

Well, sub-articles does imply that the tasks are basically the same, which I don't think they are. I think they are very different tasks with different purposes, but which happen to share some configuration. No harm in a page that explains which article deals with what, I suppose. I don't feel too strongly about this, really. This is just what makes sense to me. Giddie (talk) 10:58, 13 December 2012 (UTC)
What would be really cool is if the reading went something like: the user reads about each of the ways that this could be done, then selects what he wants to see (whatever combinations), and then gets a tailored-to-order article with just the stuff he's interested in. --Buhman (talk) 10:16, 13 December 2012 (UTC)
I don't think that will be possible on this MediaWiki setup without the kind of duplication we're keen to avoid. Probably best to split out the common stuff into separate articles, and link from an article for each usecase. Giddie (talk) 10:19, 13 December 2012 (UTC)
Here is another idea: Instead of one index page for just Network Installation Guide and PXE, we can add a index page about all of the different installation methods in Category:Getting and installing Arch. There are 49 articles in the category, so a good index page can make them stay organized. -- Fengchao (talk) 13:14, 13 December 2012 (UTC)
This sounds like a good idea to me. Giddie (talk) 14:42, 13 December 2012 (UTC)

Bootstrapping installation


Should we not include that the network drivers for the client machines be in the MODULES section at /etc/mkinitcpio.conf as SOLVED Diskless - ipconfig: no devices to configure says?

It worked just like a charm for me after hours trying to troubleshoot the network. --Gabriel B. Casella (talk) 21:36, 24 January 2014 (UTC)

This isn't something that I ran into, but it sounds very sensible to me, if it is an issue for some. Giddie (talk) 10:27, 27 January 2014 (UTC)
I tested in two different machines, one with intel (e1000e, if I'm not wrong) and one with Broadcom. Neither recognized them automatically. --Gabriel B. Casella (talk) 11:39, 27 January 2014 (UTC)
I had some trouble with driver modules... also I had to add the nfs modules. Not sure if all are needed, but in the end, this worked:
MODULES="igb bnx2 e1000e ixgbe e1000 r8169 virtio_net virtio_blk virtio_pci virtio_ring virtio lockd nfs nfsv4 oid_registry rpcsec_gss_krb5 sunrpc"
Peetaur (talk) 12:04, 31 July 2015 (UTC)

Client installation


pacstrap ends with error (205499 blocks need, 175865 blocks available) with "truncate -s 1G /srv/arch.img". I tried change to 2G and all seems ok. Maybe article needs change? --Stempit (talk) 17:12, 08 August 2017 (UTC)

Server configuration

"Next, start NFS services: rpc-idmapd rpc-mountd."

# [root@MUSIC srv]# systemctl status rpc-idmapd rpc-mountd
Unit rpc-idmapd.service could not be found.
Unit rpc-mountd.service could not be found.


# systemctl status nfs-idmapd nfs-mountd

works. But i'am not sure. Stempit (talk) 08:50, 10 August 2017 (UTC)