Jump to content

Talk:Booting process of Linux: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
SmackBot (talk | contribs)
m Subst: {{unsigned}} (& regularise templates)
GCFreak2 (talk | contribs)
Line 26: Line 26:
: I disagree on merge, for the reasons above. It is a standalone C library that can be used to link programs--not just boot programs. [[User:LtDonny|LtDonny]] ([[User talk:LtDonny|talk]]) 09:30, 7 June 2010 (UTC)
: I disagree on merge, for the reasons above. It is a standalone C library that can be used to link programs--not just boot programs. [[User:LtDonny|LtDonny]] ([[User talk:LtDonny|talk]]) 09:30, 7 June 2010 (UTC)
:: For what it’s worth, I’m hoping to / working on linking [[Korn_shell#Variants|mksh]]-static (in [[Debian]]) against [[klibc]] instead of [[dietlibc]] on as many architectures as possible. I indeed see it as a stand-alone, limited C library for random userspace programmes, just like [[Android_(operating_system)|Bionic]] is, just not a choice for most of them, or a popular one. [[User:Mirabilos|mirabilos]] ([[User talk:Mirabilos|talk]]) 13:53, 11 August 2010 (UTC)
:: For what it’s worth, I’m hoping to / working on linking [[Korn_shell#Variants|mksh]]-static (in [[Debian]]) against [[klibc]] instead of [[dietlibc]] on as many architectures as possible. I indeed see it as a stand-alone, limited C library for random userspace programmes, just like [[Android_(operating_system)|Bionic]] is, just not a choice for most of them, or a popular one. [[User:Mirabilos|mirabilos]] ([[User talk:Mirabilos|talk]]) 13:53, 11 August 2010 (UTC)
:: '''Disagree''' on merge. klibc is a standard library, just like every other minimal C standard library ([[uClibc]], [[newlib]] and others) and they would be just as suitable for inclusion in early user space, so if klibc got a mention on this page, maybe so would these other C standard libraries? <font color="#0000FF">[[User:GCFreak2|カ]]</font><font color="#00FF00">[[User_talk:GCFreak2|ラ]]</font><font color="#FF0000">[[Special:Contributions/GCFreak2|ム]]</font> 11:52, 30 November 2010 (UTC)


== Embedded Linux Startup ==
== Embedded Linux Startup ==

Revision as of 11:52, 30 November 2010

WikiProject iconLinux C‑class High‑importance
WikiProject iconThis article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
CThis article has been rated as C-class on Wikipedia's content assessment scale.
HighThis article has been rated as High-importance on the project's importance scale.

First sentence

The Linux startup process is the process of Linux-operating system initialize.

Is that a sentence? Shouldn't it be initialization instead of initialize.

—Preceding unsigned comment added by 88.68.65.225 (talkcontribs) 06:11, 24 June 2009

This was fallout from some edits by someone whose first language obviously isn't English. Chris Cunningham (not at work) - talk 10:39, 24 June 2009 (UTC)[reply]

I think that stub should be merged here unless the terminology is used outside Linux, which doesn't seem to be the case. Pcap ping 02:12, 27 December 2009 (UTC)[reply]

Agree, that’s definitively Linux specific. Some other OSes may have similar technologies, but neither is it used as widespread as with the Linux kernel, nor do they use this terminology. mirabilos (talk) 13:56, 11 August 2010 (UTC)[reply]

The klibc library doesn't seem to have much in the way of uses outside the scope of this article (the license seems to be the culprit). Proposing we merge that here. Pcap ping 22:22, 28 December 2009 (UTC)[reply]

I would agree that it could be merged with a redirect. Bpringlemeir (talk) 22:38, 29 December 2009 (UTC)[reply]
I disagree on merge: klibc is known to compile Debian Installer boot floppies, dash, mksh, udev, module-init-tools and other projects. So it is not only boot related. It is a libc and should stay on its own. 138.234.212.84 19:02 24 March 2010 (UTC)
I disagree on merge. klibc seems to be an entity on its own, thus meriting a separate article, even if it plays a major role in the Linux startup process. Intersofia (talk) 09:45, 12 April 2010 (UTC)[reply]
I disagree on merge, for the reasons above. It is a standalone C library that can be used to link programs--not just boot programs. LtDonny (talk) 09:30, 7 June 2010 (UTC)[reply]
For what it’s worth, I’m hoping to / working on linking mksh-static (in Debian) against klibc instead of dietlibc on as many architectures as possible. I indeed see it as a stand-alone, limited C library for random userspace programmes, just like Bionic is, just not a choice for most of them, or a popular one. mirabilos (talk) 13:53, 11 August 2010 (UTC)[reply]
Disagree on merge. klibc is a standard library, just like every other minimal C standard library (uClibc, newlib and others) and they would be just as suitable for inclusion in early user space, so if klibc got a mention on this page, maybe so would these other C standard libraries? 11:52, 30 November 2010 (UTC)[reply]

Embedded Linux Startup

While the heading of this page implies a general Linux startup it is highly PC specific and does not decribe the process for the devices starting with embedded Linux, say on ARM using other boot loaders. Either it should be brodened to include other cases or calrification added as to the above point. —Preceding unsigned comment added by 76.218.105.120 (talk) 11:07, 4 January 2010 (UTC)[reply]

I agree that the article currently is too specific to one platform, yet is written as if the mentioned startup process applies for all kinds of computers. For example: "In Linux, the flow of control during a boot is from BIOS, to boot loader, to kernel.[...]"
The "BIOS" exists only with IBM PC compatible computers, yet there are many other non-IBM PC compatible computers which can start up Linux in their own way. --Abdull (talk) 14:02, 7 March 2010 (UTC)[reply]

Is LILO able or not? Contradiction?

  1. Under LILO, this is done via the map installer[clarification needed] which reads the configuration file /etc/lilo.conf to identify the available systems.
  2. LILO does not understand file systems, so it uses raw disk offsets and the BIOS for data load.

How can LILO read a file system file, if LILO does not understand file systems? --Abdull (talk) 14:39, 7 March 2010 (UTC)[reply]

The map installer (used to be /sbin/lilo back when I used GNU/Linux) is a regular GNU/Linux userspace programme. It scans for available systems, writes the mapfile containing “pointers” to them to disc, and then embeds the location of the mapfile into the LILO bootblocks which, indeed, cannot parse any filesystems. HTH, HAND. mirabilos (talk) 13:55, 11 August 2010 (UTC)[reply]

Data vs. Program

"It may also optionally run Initrd to allow setup and device related matters (RAM disk or similar) to be handled before the root file system is mounted."

How can you run a file system? --Abdull (talk) 17:54, 7 March 2010 (UTC)[reply]