You removed the method 2 in Install from Existing Linux: I agree with your change
I saw you removed the method 2 (Direct bootstrapping Archlinux), and I must say that I agree with your change. The prefered method must be the live cd, and methods 1,3 and 4 use the archinstall scripts to do the installation, while method 2 completly ignores them. Since the archinstall scripts is the official installation method, the methods using them should be correct ones to explain.
By the way, I think method 4 (compiling pacman) maybe should be the second method, since is closer to the official way. That way it would be like this:
- Live cd
It uses the official iso and works with the archinstall scripts
- Compiling pacman
It uses the archinstall scripts, without the need of external scripts
- Bootstrapping the arch installation scripts
It uses the archinstall scripts, but uses an external script.
I'm not going to say the "Direct bootstrapping Archlinux" method lacks value (that one ignores the archinstall scripts, and works with an external script), I just feel that article is not the correct place for it to be, since the other methods play nice as additional steps to the Installation Guide, while method 2 is completly independent to the archinstall scripts, and therefore, to that guide.
It seems that someone has re-added the method 2 (according to the history, is the same person who added comments like "As a subjective conclusion, I, personally, would recommend using Direct bootstrapping")
So, I would like to ask you what you think it should be done about it? If you have an idea of how to deal with this, then edit the wiki or the discussion page of Install from Existing Linux. If you have a good idea of how to solve it, I'll support your proposition there. Chrisl (talk) 18:30, 26 February 2013 (UTC)
Remove of Daemon in Display Manager
In these edits, you remove Daemon method without an Edit summary. I am just want to double check why it is removed. Is it broken? Is it have some problem or disadvantage? -- Fengchao (talk) 12:34, 24 September 2012 (UTC)
- It isn't broken... it is just incorrect and to load via rc.conf. You lose the ability to use init for its purpose. init 3 should be straight into console, and init 5 should be the multi-user/graphical. A Display Manager (while it can be run as a daemon) is not a daemon and shouldn't be treated like one. They should be loaded through inittab, where they can actually behave properly. In fact, you could setup several display managers in inittab if you wanted to. Sorry I didn't include an Edit summary, but the fact that you can load DMs through rc.conf has been stripped from most actual display manager pages already, I was just cleaning up extra ones as I find them or they are mentioned in #archlinux... is there a macro to get the User: User talk stuff like there is for --> 16:26, 24 September 2012 (UTC) ? thanks
- Just use
- I know inittab is better long time ago, but just know the reason now. :) It is better to clearly telling people that it is incorrect and give the reason. Maybe something like "This method is deprecated and users of this method should change to inittab method."
- Fengchao (talk) 04:11, 25 September 2012 (UTC)
- Just use
Declare more mirrors for a file
- As I said in the summary, just because you can do something doesn't mean you should. Yes PKGBUILDs are bash scripts, but what you put on their goes against so many things in the Packageing guidelines, and you should never do that in a PKGBUILD gtmanfred (talk) 10:54, 24 November 2012 (UTC)
- > […] goes against so many things in the Packageing guidelines
- For example?
- --Grufo [ contribs | talk ] 11:31, 24 November 2012 (UTC)
- they are variables, don't run functions in them. If the file no longer exists, the PKGBUILD should be updated. check what one of the pacman developers said in your forum posts, or come to #archlinux or #archlinux-pacman to actually discuss why it is wrong gtmanfred (talk) 11:43, 24 November 2012 (UTC)