Перейти к содержанию

User-Mode-Linux (бутылка в кораблике)


Рекомендуемые сообщения

И так... соорудил я кораблик с бутылкой - User-Mode-Linux

Это своего рода, еще одна альтернатива BSD Jile.

Откомпилил я ее, запустил... все по документации (только слаку 10.2 поставил).

Но... возникла проблема... файловая система RO Sad

и никак не могу я ее в RW переделать... Sad

root@PANDORA:~# ./linux ubd0rw=root_fs
Checking for the skas3 patch in the host...not found
Checking for /proc/mm...not found
Checking PROT_EXEC mmap in /tmp...OK
tracing thread pid = 17886
Checking for /dev/anon on the host...Not available (open failed with errno 2)
Checking for /dev/anon on the host...Not available (open failed with errno 2)
Checking for /dev/anon on the host...Not available (open failed with errno 2)
Checking for /dev/anon on the host...Not available (open failed with errno 2)
Linux version 2.4.27-1um (root@PANDORA) (gcc version 3.3.6) #1 Thu Oct 5 18:41:43 MSD 2006
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: ubd0rw=root_fs root=/dev/ubd0
ubd_setup : Expected '='
Calibrating delay loop... 1123.94 BogoMIPS
Memory: 28744k available
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Checking for host processor cmov support...Yes
Checking for host processor xmm support...No
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...missing
Checking that host ptys support output SIGIO...Yes
Checking that host ptys support SIGIO on close...No, enabling workaround
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Journalled Block Device driver loaded
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS version 1.0, © 1999, 2000  Axis Communications AB
JFFS2 version 2.1. © 2001 Red Hat, Inc., designed by Axis Communications AB.
pty: 256 Unix98 ptys configured
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
Universal TUN/TAP device driver 1.5 ©1999-2002 Maxim Krasnyansky
SCSI subsystem driver Revision: 1.00
scsi0 : scsi_debug, Version: 0.61 (20020815), num_devs=1, dev_size_mb=8, opts=0x0
  Vendor: Linux     Model: scsi_debug        Rev: 0004
  Type:   Direct-Access                      ANSI SCSI revision: 03
blkmtd: error: missing `device' name

Initializing software serial port version 1
mconsole (version 2) initialized on /root/.uml/EcwpNb/mconsole
Partition check:
 ubda: unknown partition table
UML Audio Relay (host dsp = /dev/sound/dsp, host mixer = /dev/sound/mixer)
Initializing stdio console driver
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: ubd(98,0): orphan cleanup on readonly fs
EXT3-fs warning (device ubd(98,0)): ext3_orphan_get: bad orphan inode 1120220!  e2fsck was run?

ext3_test_bit(bit=763, block=2260993) = 0
inode=00000000
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
INIT: version 2.84 booting
/etc/rc.d/rc.S: line 11: /sbin/mount: Permission denied
/etc/rc.d/rc.S: line 12: /sbin/mount: Permission denied
cat: /proc/filesystems: No such file or directory
Testing root filesystem status:  read-only filesystem
Checking root filesystem:
fsck 1.38 (30-Jun-2005)
/dev/ubd/0: clean, 105478/1281696 files, 455210/2560000 blocks
Remounting root device with read-write enabled.
/etc/rc.d/rc.S: line 108: /sbin/mount: Permission denied

Attempt to remount root device as read-write failed!  This is going to
cause serious problems.

If you're using the UMSDOS filesystem, you **MUST** mount the root partition
read-write!  You can make sure the root filesystem is getting mounted
read-write with the 'rw' flag to Loadlin:

loadlin vmlinuz root=/dev/hda1 rw   (replace /dev/hda1 with your root device)

Normal bootdisks can be made to mount a system read-write with the rdev command:

rdev -R /dev/fd0 0

You can also get into your system by using a boot disk with a command like this
on the LILO prompt line:  (change the root partition name as needed)

LILO: mount root=/dev/hda1 rw

Please press ENTER to continue, then reboot and use one of the above methods to
get into your machine and start looking for the problem.
/bin/rm: cannot remove `/etc/mtab': Read-only file system
/etc/rc.d/rc.S: line 165: /sbin/mount: Permission denied
Checking non-root filesystems:
fsck 1.38 (30-Jun-2005)
/etc/rc.d/rc.S: line 246: /sbin/mount: Permission denied
/bin/rm: cannot remove `/var/run/utmp': Read-only file system
/bin/rm: cannot remove `/var/run/inetd.pid': Read-only file system
/bin/rm: cannot remove `/var/run/klogd.pid': Read-only file system
/bin/rm: cannot remove `/var/run/syslogd.pid': Read-only file system
touch: cannot touch `/var/run/utmp': Read-only file system
chmod: changing permissions of `/var/run/utmp': Read-only file system
/etc/rc.d/rc.S: line 290: /etc/motd: Read-only file system
Using /etc/random-seed to initialize /dev/urandom.
chmod: changing permissions of `/etc/random-seed': Read-only file system
INIT: Entering runlevel: 3
Going multiuser...
cannot (un)set powersave mode
/etc/rc.d/rc.M: line 31: /var/log/dmesg: Read-only file system
chmod: changing permissions of `/tmp': Read-only file system
chmod: changing permissions of `/var/tmp': Read-only file system
Updating shared library links:  /sbin/ldconfig
/sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Read-only file system
Updating X font indexes:  /usr/X11R6/bin/fc-cache
/etc/rc.d/rc.M: line 156: /var/log/cron: Read-only file system
Killed
Ссылка на комментарий
Поделиться на другие сайты

Есть еще вот такой документ, но тут я никак не могу понять, что есть "../distros/slackware_7.0/inst_fs_slackware_7_0"

Ссылка на комментарий
Поделиться на другие сайты

Присоединяйтесь к обсуждению

Вы можете написать сейчас и зарегистрироваться позже. Если у вас есть аккаунт, авторизуйтесь, чтобы опубликовать от имени своего аккаунта.

Гость
Ответить в этой теме...

×   Вставлено с форматированием.   Вставить как обычный текст

  Разрешено использовать не более 75 эмодзи.

×   Ваша ссылка была автоматически встроена.   Отображать как обычную ссылку

×   Ваш предыдущий контент был восстановлен.   Очистить редактор

×   Вы не можете вставлять изображения напрямую. Загружайте или вставляйте изображения по ссылке.

Загрузка...
×
×
  • Создать...