Сообщения valery
вопрос по mail
не могу установил slack 12.1
ошибка lilo с initrd.img
mkinitrd error mountig
ус-ка slack 12.1 через mkinitrd
ус-ка через initrd
The easiest way to make the initrd is to use the mkinitrd script included in Slackware's mkinitrd package. We'll walk through the process of upgrading to the generic 2.6.24.5-smp Linux kernel using the packages found in Slackware's slackware/a/ directory.
First, make sure the kernel, kernel modules, and mkinitrd package are installed (the current version numbers might be a little different, so this is just an example):
installpkg kernel-generic-2.6.24.5_smp-i686-2.tgz installpkg kernel-modules-2.6.24.5_smp-i686-2.tgz installpkg mkinitrd-1.3.2-i486-2.tgz
Change into the /boot directory:
cd /boot
Now you'll want to run "mkinitrd". I'm using reiserfs for my root filesystem, and since it's an IDE system the reiserfs module will be the only one I need to load:
mkinitrd -c -k 2.6.24.5-smp -m reiserfs
This should do two things. First, it will create a directory /boot/initrd-tree containing the initrd's filesystem. Then it will create an initrd (/boot/initrd.gz) from this tree. If you wanted to, you could make some additional changes in /boot/initrd-tree/ and then run mkinitrd again without options to rebuild the image. That's optional, though, and only advanced users will need to think about that.
Here's another example: Build an initrd image using Linux 2.6.24.5-smp kernel modules for a system with an ext3 root partition on /dev/hdb3. Note that you need the mbcache, jbd, and ext3 modules to use ext3:
mkinitrd -c -k 2.6.24.5-smp -m mbcache:jbd:ext3 -f ext3 -r /dev/hdb3
Actually, mkinitrd is usually smart enough to figure out any "helper" modules that are needed, so this would work as well:
mkinitrd -c -k 2.6.24.5-smp -m ext3 -f ext3 -r /dev/hdb3
4. Now that I've built an initrd, how do I use it?
Now that you've got an initrd (/boot/initrd.gz), you'll want to load it along with the kernel at boot time. If you use LILO for your boot loader you'll need to edit /etc/lilo.conf and add a line to load the initrd. Here's an example section of lilo.conf showing how this is done: image = /boot/vmlinuz-generic-2.6.24.5-smp initrd = /boot/initrd.gz root = /dev/hda6 label = Lnx26245smp read-only The initrd is loaded by the "initrd = /boot/initrd.gz" line. Just add the line right below the line for the kernel image you use. Save the file, and then run LILO again ('lilo' at the command line). You'll need to run lilo every time you edit lilo.conf or rebuild the initrd. --------------- перегрузился появилось прглашение- /$ и что дальше - ни setup ни pkgtool не запускаются. И еще - создалась /boot/initrd-tree в ней есть /lib/modules/2.6.24.5 но директория оказалась незаполнена перекачал туда модули но эффект что с пустой
lilo and initrd
loadlin from dos
Your current LINUX kernel boot configuration is: image file: bzimage kernel version 2.6.24.5 (root@midas) #2 Wed Apr 30 14:13:52 CDT 2008 kernel size: 0x003FFE98 (high loaded) setup size: 0x2A00, heap: 0x1400 VGA mode: 0xFFFF command line (size 0x0012): BOOT_IMAGE=bzimage
Your current DOS/CPU configuration is: load buffer size: 0x00270000 VCPI, setup buffer size: 0x3E00 lowmem buffer: 0x00080000 (part of load buffer) total memory: 0x040FFC00 CPU is in V86 mode SetupIntercept: YES, legal intercept, setup header version 0207 stat4: VCPI_present, physmap=logmap, all OK for switch to realmode input params (size 0x000A): bzimage -t LOADLIN started from DOS-prompt WARNING: Not enough free memory (load buffer size) Option -t set, Linux not loaded
slackware 12.1 уст-ка через флоппи
не могу смонтироватить диск типа xfs
не определяются партиции диска
mount xfs
настройка прокси сервера
| ← предыдущие |