From ArchWiki
Revision as of 16:10, 21 January 2012 by Karol (Talk | contribs) (keymap v. consolefont)

Jump to: navigation, search

Generic Kernel

wide-eye says: shouldn't the generic kernel options go into other pages? such as the "using net" "using lvm." also the copies of the grub/lilo pages should be elsewhere. they are just not part of the page subject. /me thinks a "Customizing the kernel command line" page is in order.

Re. About

Uh-Oh. I see geek-speak. Why not go back to the Arch Way and KISS? First explain what the thing is for and a little context to help with understanding, and only then go on to describe what it does and how to use it. - KitchM 15:39, 11 March 2009 (EDT)

The "About" section does not really explain the program. A statement like "mkinitcpio is the next generation of initramfs creation" implies the reader knows what is meant by "innitramfs creation". But that wasn't defined either.
What is mkinitcpio? What does it do? Why is it necessary? How does it help the OS? These are some of the questions that should be answered in the "About" section. Maybe Brain0 could come back and give us more info - KitchM 15:42, 24 January 2010 (EST)

There is no way in God's green earth that this problem has be fixed. Do not delete other's posts!!!!!! - KitchM 13:48, 15 February 2010 (EST)

I find it funny that you're so anal about this, seeing as how you have no such inhibitions about deleting my posts...
All the questions you raise are answered in the snippet copied from brain0's blog. Users looking for more information can view the entire article by following the link, or the link to the Wikipedia article above.
Maybe you could try editing the article and improving it yourself, rather than simply complaining that it doesn't meet your high standards?
-- pointone 15:19, 15 February 2010 (EST)
I've never deleted anyone's post like that. Not even yours. Even if you wish to be penile about it, I believe you may wish to check your facts. I simply wouldn't do that. I went over the history of your link and found that something was done between the time I responded to the good comment you wrote and the time I added a missed signature. Interesting how it isn't even in the history, don't you think? (I refreshed the page three times and it simply isn't there.)
At the end of the day, IMHO it is far better to try to be nice. Besides, isn't it you that is always being picky with people's syntax, tense, narrative forms and word usage? But since you mentioned it, the quoted text is crude, poorly formed and confusing. It simply doesn't fit the format needed here, nor does it add the explanation I was looking for as you claim.
I apologise if I have not made myself clear. If I had the knowledge of the subject matter, I wouldn't care if the article was good or bad. But I have one piece of knowledge you don't have; I can try it and see clearly what is missing because it simply doesn't answer my questions. Your assumptions do not help others. If you wish to help others, then you must know where they are coming from and find a way to communicate the missing information they are trying to find.
The big issue with wikis is that many "experts" believe they are making a huge contribution when they write down something they know, in the way they know it. But they are not helping anyone, unless they write it down so that it is goof-proof. If someone like me can't understand, they have failed. And if they knew me, they'd know they had failed miserably.
I will be glad to continue to proof-read and contribute, but please understand that I know what I'm talking about, and when something isn't right, it really isn't. It is far better to address my points and fix the articles than to waste time on complaining about legitimate issues. Even a geek can learn to be civil.
Thanks. - KitchM 20:41, 16 February 2010 (EST)
I have gone ahead and fixed the page up to where my knowledge ran out. I can't seem to find where the name mkinitcpio came from, nor the connection with mkinitrd and mkinitramfs. I just left those in a logical spot because I didn't know where they fit. Still, pretty damn good, if I do say so myself. - KitchM 21:27, 16 February 2010 (EST)

Still lots of problems with this page. Let's start with the phrase "initramfs creation". What does that mean? That should have been explained. Since it still isn't, let's work around it.

Next, please allow me to explain the difference between a quote and a paraphrase. A quote is a word-for-word copy of the original, set off within quotation marks. A paraphrase is a personal interpretation of the original. They are clearly different. Let's not edit without understanding that. Also, let's not edit without understanding the reason for the particular phraseology used.

In this case, the original had to be fixed because the thing was unclear, and because the person who claimed to quote something added something within the quote, thereby making it a paraphrase.

Now, I don't know about the origins of mkinitrd' and mkinitramfs scripts, but I do know that there is no sense including them if they aren't explained either.

The confusion of the writer has extended to rewriting the computer industry's historical perspective of the boot process. He has included a pre-boot period never before known. For over thirty years, everything that happens from the time the computer is turned on to the time the operating system is ready to use has always been called part of the boot process.

Now we find that there isn't an understanding between a drive and the file system that runs on it. Trying to edit something like that without such understanding is misleading others. To avoid that pitfall, one should think about the actual, and clearly specific, differences in words and phrases.

I'm sure we can do better than this. I know I can. - KitchM 02:04, 18 February 2010 (EST)


Please define "Hooks". - KitchM 19:37, 16 March 2010 (EDT)

"A hook is a script that executes in the initial ramdisk." -- Karol 18:43, 21 October 2011 (EDT)
Thank you. How is that sort of hook different from the type used in general programming? - KitchM 20:03, 21 October 2011 (EDT)

Encrypted Root

Shouldn't it be

root=/dev/mapper/root cryptdevice=/dev/sda5:root

instead of


? Tarqi 10:45, 4 September 2011 (EDT)

Maintain the same order describing /etc/mkinitcpio.conf in detail

It's modules, binaries, files, hooks and finally compression, yet hooks are being described in detail first. Any particular reason for this? -- Karol 18:50, 21 October 2011 (EDT)

No idea. I've fixed it, but it's sort of the least of the issues on this page. I've been doing some cleanup and correcting some flat out misinformation. -- Falconindy 11:47, 6 November 2011 (EST)
Thanks a lot, I was about to investigate the info about uncompressed image but you've fixed it already :-) -- Karol 13:37, 6 November 2011 (EST)

Needed in modern systems?

Thanks to Falconindy for cleaning this up.

My question has to do with the assumptions used at the start. If these features are needed in modern systems, why isn't it a part of the normal kernel? - KitchM 12:08, 6 November 2011 (EST)

keymap v. consolefont

Using the consolefont hook seems to work as advertised in /lib/initcpio/hooks/consolefont and mkinitcpio -H consolefont i.e. I get my font in the early stages of the boot process, while using keymap only sets the font a bit later and mangles Polish accented characters if I'm using DAEMON_LOCALE="yes". I think we need to add consolefont to the HOOKS list and fix keymap hook description. -- Karol 11:10, 21 January 2012 (EST)