Diskless_Network_Boot_NBD_Root merge and rewrite
There was a bunch of extraneous stuff that was clogging up the old articles, and most information was duplicated between the two. This is the result of the cleanup effort. That gPXE stuff, for example, deserves its own article in my opinion. Yet-another refactoring/merging of the related PXE article is also planned--the two should be sub-articles of a larger "PXE" article that describes "PXE" in general, with sub-articles describing booting installation media or an arch installation (minimizing duplicated information yet even more). --Buhman (talk) 14:31, 9 October 2012 (UTC)
If DNSmasq is not appropriate for the job, please write a section explaining why this is the case. Since I use dnsmasq, I'd be interested to know why exactly you think it's not appropriate. What definitely is not appropriate, however, is undoing my edits, for which I've gone to pains to explain my reasoning. Giddie (talk) 10:38, 11 December 2012 (UTC)
- No, we don't write sections explaining why sections don't exist. That's just plain stupid. --Buhman (talk) 10:42, 11 December 2012 (UTC)
- We write sections explaining why an obvious choice is actually not a good idea, so others can be informed and avoid the same mistake. (Assuming they agree that it is actually a mistake.) Seriously: this wiki is not here to reflect only your own opinions; it's here so that we can all share our knowledge. It's all about collaboration and compromise, and I'm seeing very little of that from you right now. Giddie (talk) 11:34, 11 December 2012 (UTC)
- dnsmasq is a problem because it's a little unwieldy primarily due to its crazy amount of scope-creep. What was originally just a dns server got way out of hand. If you say things like listen-address=192.168.0.1, that is only applicable for the DNS part, and not, e.g: DHCP. This becomes problematic if say you want your stuff that also runs isc-dhcp just on wlan0, and then decide you want to PXE boot some stuff off the wired-lan really quick. Nope; have to shut down dhcpd4 to allow dnsmasq to hog all the interfaces and bind wildcard on everything BUT dns. But oh wait, you said port=0? That controls what, just DNS? So DNS is disabled now, and listen-address in this case does absolutely nothing, as well as listen-interface.
- It's just a dirty ugly quick "omfg I want dhcp+tftp NAOW" hack, rather than something that should be considered sane to actually systemctl enable. Lots of features, really crappy defaults, and, most importantly, no way to un-configure those defaults (aside from making a fork that would just end up being a less-good isc bind/tftp/dhcp). And compared to bind it's a lousy DNS server anyway. So why it even exists I don't know.
This article seems to be undergoing an edit war between User:Buhman and User:Giddie, and this is bad for the wiki and its users: I remind both users that the articles of the wiki belong to everybody and can't be treated as personal notebooks. Entering more into the merits of the discussion, I also remind that it's a common policy of the ArchWiki to always explain all the possible ways to achieve a particular result, never hiding anything and always leaving the final choice to the end users; if some methods are working but discouraged for some reasons, they are to be left in the article together with those reasons of discouragement; if some methods are working only under some conditions, these conditions are to be described, possibly adding an appropriate article status template. Different subsections can be created to keep the various methods separate.
Furthermore, I invite to always sign with the full signature in discussion pages (~~~~) and to always thoroughly justify the edits with the edit summary, avoiding expressions like "why the fsck was this even created?" or empty summaries (in particular when undoing edits), since these practices don't help in any way. Finally, please avoid expressions like "NFSv3 sucks", "Kthx", "I couldn't care less about your migration woes; it doesn't belong on the wiki, end of discussion", "That's just plain stupid", ... since this is considered flaming, and flamers are not welcome here, regardless of the effective quality of their edits.
This section is more of a notice than a real discussion, so replies are not expected, please go on with the other discussions peacefully and constructively: once the situation has calmed down, this section can just be deleted.
Per-host mountpoints (was: Separate /var)
I feel like treating just
/var specially isn't fair. I mean, how would
/etc feel? In all seriousness, I think this needs to be reorganized into something like "per-host special mountpoints". --Buhman (talk) 15:30, 12 December 2012 (UTC)
- That sounds fine to me, if you want to do that. I'm pretty sure that
/varcontains everything that makes a host unique (or that's the intention), and I'm keen for people to think about it, since it's an added complication that can easily be overlooked when planning the cluster. Giddie (talk) 15:39, 12 December 2012 (UTC)
- As I tried to imply somewhat, I still don't think its a good idea to do *all* of var, maybe a few application-specific subdirectories. For example it's actually desirable in a non-diskless scenario like this to put /var/cache/pacman on a NFS share--effectively working like a local repository mirror. Only in this scenario, we get that for free :D --Buhman (talk) 16:41, 12 December 2012 (UTC)
- Yeah, in my setup I share
/var/lib/pacmanbetween all clients, and
/var/cache/pacmanbetween all clients and the host. Some other directories in
/var/cachecould probably be safely shared, but my general stance is to opt-in to sharing certain directories in
/varfor convenience (or storage space), rather than to determine which directories can't safely be shared. I have no problem with providing suggestions for both points of view ("share all of /var except for certain dirs" vs "/var is node-specific except for certain dirs"); it's helpful for readers to have a chance to consider both views and decide what fits their usecase best. Giddie (talk) 09:57, 13 December 2012 (UTC)
- Yeah, in my setup I share
Is installation ISO needed ?
I am trying to merge PXE into this article. While I am quite familiar with PXE, I do not know what exactly need to be done in the Network installation guide. Should I download ISO installation media? Where to put/get installation packages? -- Fengchao (talk) 04:44, 13 December 2012 (UTC)
- PXE talks about booting installation media via PXE, whereas this article talks about creating an installation from an already-installed system. A proper merge will be highly difficult in my opinion, which is why I have not yet attempted it. --Buhman (talk) 08:16, 13 December 2012 (UTC)
- The article titles are currently very non-helpful in determining what the content of each article is, but I'm not confident on how to fix this. For example "Network Installation" could mean both booting installation media via a network, or, as used in this article, creating an installation that happens to exist on network'ed storage media. In all cases, for example, you end up 1) preparing the TFTP root, whether it be a mounted Archiso, or part of a complete installation 2) actually setting up a TFTP and DHCP server, and the only real difference is 3) what exactly is contained on the root filesystem and how it is delivered to the client. I would love to hear ideas on how to reorganize this sanely. --Buhman (talk) 09:38, 13 December 2012 (UTC)