1 |
On Friday 20 May 2005 13:25, Alex Chumakov wrote: |
2 |
> > initrd (initial root disk) - "ÎÁÞÁÌØÎÙÊ ËÏÒÎÅ×ÏÊ ÄÉÓË (initrd)" |
3 |
> îÅ ÓÏ×ÓÅÍ ÔÁË. îÁÓËÏÌØËÏ Ñ ÚÎÁÀ, initrd ÐÒÏÉÓÈÏÄÉÔ ÏÔ Initial RAM Disk |
4 |
> Image. |
5 |
> üÔÏ ÏÂÒÁÚ, ËÏÔÏÒÙÊ ÚÁÇÒÕÖÁÅÔÓÑ × ÐÁÍÑÔØ ËÏÍÐØÀÔÅÒÁ ÎÁ ÐÅÒ×ÙÈ ÜÔÁÐÁÈ |
6 |
> ÚÁÇÒÕÚËÉ. |
7 |
> ðÅÒ×ÁÑ ÐÏÐÁ×ÛÁÑÓÑ ÓÓÙÌËÁ ÉÚ google: |
8 |
> http://www.xs4all.nl/~lennartb/bootloaders/node5.html (ÓÍ. × ÓÁÍÏÍ ÎÉÚÕ). |
9 |
> ôÁÍ ×ÓÅ ÒÁÓÐÉÓÁÎÏ. |
10 |
> |
11 |
> íÏÖÅÔ ÂÙÔØ :-) Ñ ÂÒÁÌ ÉÚ hb-install-x86-kernel, ÇÄÅ ÉÍÅÎÎÏ ÔÁË (initial |
12 |
> root disk) ÜÔÏ É ÒÁÓÛÉÆÒÏ×ÁÎÏ. |
13 |
äÁ, ÄÅÊÓÔ×ÉÔÅÌØÎÏ, ÔÁÍ ÔÁË ÎÁÐÉÓÁÎÏ. îÏ ×ÏÔ ÞÔÏ ÅÓÔØ × man initrd: |
14 |
|
15 |
NAME |
16 |
initrd - boot loader initialized RAM disk |
17 |
|
18 |
DESCRIPTION |
19 |
The special file /dev/initrd is a read-only block device. Device |
20 |
/dev/initrd is a RAM disk that is initialized (e.g. loaded) by the |
21 |
boot loader before the kernel is started. The kernel then can use |
22 |
the the block device /dev/initrd's contents for a two phased sys- |
23 |
tem boot-up. |
24 |
|
25 |
In the first boot-up phase, the kernel starts up and mounts an |
26 |
initial root file-system from the contents of /dev/initrd (e.g. |
27 |
RAM disk initialized by the boot loader). In the second phase, |
28 |
additional drivers or other modules are loaded from the initial |
29 |
root device's contents. After loading the additional modules, a |
30 |
new root file system (i.e. the normal root file system) is mounted |
31 |
from a different device. |
32 |
|
33 |
ëÏÒÏÞÅ ÇÏ×ÏÒÑ, initrd - ÜÔÏ RAM-ÄÉÓË, ËÏÔÏÒÙÊ ÓÏÄÅÒÖÉÔ ËÏÒÎÅ×ÕÀ ÆÁÊÌÏ×ÕÀ |
34 |
ÓÉÓÔÅÍÕ, ÉÓÐÏÌØÚÕÅÍÕÀ ÄÏ ÔÏÇÏ, ËÁË ÂÕÄÅÔ ÓÍÏÎÔÉÒÏ×ÁÎÁ ÆÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ Ó |
35 |
ÖÅÓÔËÏÇÏ ÄÉÓËÁ. ðÏÜÔÏÍÕ, ÍÎÅ ËÁÖÅÔÓÑ, ÐÒÁ×ÉÌØÎÅÅ ÒÁÓÛÉÆÒÏ×ÁÔØ initrd ËÁË |
36 |
'initial RAM disk', ÎÏ × ÎÅËÏÔÏÒÙÈ ËÏÎÔÅËÓÔÁÈ ÄÏÐÕÓÔÉÍÏ ÇÏ×ÏÒÉÔØ Ï ËÏÒÎÅ×ÏÊ |
37 |
ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÅ. |
38 |
|
39 |
-- |
40 |
ó Õ×ÁÖÅÎÉÅÍ, áÎÔÏÎ |
41 |
|
42 |
-- |
43 |
gentoo-doc-ru@g.o mailing list |