View previous topic :: View next topic |
Author |
Message |
Match Tux's lil' helper
Joined: 22 Mar 2004 Posts: 117 Location: England
|
Posted: Mon Nov 08, 2004 8:27 pm Post subject: |
|
|
It's enabled - compiled in. But what good would that do when I'm in a chrooted environment anyway? Does compiling it automatically set it up?
*goes off to recompile the kernel just to make sure*
(Thanks for all the info on udev by the way, it's really helpful )
Edit: I've done an ls /dev and loop0 is certainly there. I get the same error though. _________________ O_o |
|
Back to top |
|
|
Match Tux's lil' helper
Joined: 22 Mar 2004 Posts: 117 Location: England
|
Posted: Wed Nov 10, 2004 8:19 am Post subject: |
|
|
I'm going to try booting from the partition I've been doing all this on, see if that works. I can't think of anything else. Does anyone have any other ideas? _________________ O_o |
|
Back to top |
|
|
veezi Apprentice
Joined: 10 Nov 2003 Posts: 226
|
Posted: Wed Nov 10, 2004 4:29 pm Post subject: |
|
|
Match wrote: | I'm going to try booting from the partition I've been doing all this on, see if that works. I can't think of anything else. Does anyone have any other ideas? |
May be your forgot to 'mount -o bind /dev source/dev'. Not really sure.
Anyway, you can always create the initrd image from outside the chroot environment. It really doesn't make a difference.
Good luck |
|
Back to top |
|
|
chunderbunny Veteran
Joined: 31 May 2004 Posts: 1281 Location: 51°24'27" N, 0°57'15" W
|
Posted: Wed Nov 10, 2004 5:10 pm Post subject: |
|
|
Gah, this is irritating me now. I made a new image with a load of extra programs on, but now it hangs when trying to run /sbin/init. If I press some keys I get the error message "vt: argh, driver_data is NULL".
I edited linuxrc to execute /bin/sh instead of /sbin/init and it all works up until "exec /sbin/init ${CMDLINE}" which just hangs. I tried using "exec /sbin/init 3" (as well as various other runlevels) but that hangs as well.
Is there anyway I can get some debug info on what's going wrong? |
|
Back to top |
|
|
Cqwense n00b
Joined: 28 Nov 2003 Posts: 52
|
Posted: Wed Nov 10, 2004 5:50 pm Post subject: |
|
|
Quote: | warning: can't open /etc/fstab: No such file or directory |
I also recieved this message, I carelessly forgot to :
inside the souce directory.
I added it, rebuilt the image, and seems to be working now.
Hope this helps,
~ Cqwense _________________ Windows has noticed that you moved your mouse.
Please reboot to allow for the changes. |
|
Back to top |
|
|
Match Tux's lil' helper
Joined: 22 Mar 2004 Posts: 117 Location: England
|
Posted: Wed Nov 10, 2004 7:55 pm Post subject: |
|
|
veezi wrote: | Match wrote: | I'm going to try booting from the partition I've been doing all this on, see if that works. I can't think of anything else. Does anyone have any other ideas? |
May be your forgot to 'mount -o bind /dev source/dev'. Not really sure.
Anyway, you can always create the initrd image from outside the chroot environment. It really doesn't make a difference.
Good luck |
I didn't mount /dev to source/dev because it's not in your guide, but I tried it now and it still doesn't work
Also, even if I did make the initrd image outside of the chroot, if I can't do this step then surely nothing's going to work anyway?
Incidently, I just tried running the losetup command outside the chroot, on my normal installation: I get the same error message.
Is there any way of me doing this if I keep on getting this message, or does anyone know of how to solve this problem? Otherwise I guess I'll just have to give up
(Thanks for the tutorial anyway, veezi - not your fault if I can't get it to work) _________________ O_o |
|
Back to top |
|
|
veezi Apprentice
Joined: 10 Nov 2003 Posts: 226
|
Posted: Thu Nov 11, 2004 5:14 pm Post subject: |
|
|
Match wrote: |
I didn't mount /dev to source/dev because it's not in your guide, but I tried it now and it still doesn't work
Also, even if I did make the initrd image outside of the chroot, if I can't do this step then surely nothing's going to work anyway?
|
You're right about that.
Can you post the output of the following commands:
Code: |
cat /usr/src/linux/.config | grep LOOP
ls -l /dev/loop*
modinfo loop
|
|
|
Back to top |
|
|
duby2291 Guru
Joined: 17 Oct 2004 Posts: 583
|
Posted: Thu Nov 11, 2004 9:28 pm Post subject: |
|
|
I can boot to the cd and it loads the kernel. Then it craps out saying that it couldnt find init. Then it says to edit "init=" line in grub.conf. I don't have an exact copy of the error, but it is something along that line.
Any suggestions? |
|
Back to top |
|
|
Match Tux's lil' helper
Joined: 22 Mar 2004 Posts: 117 Location: England
|
Posted: Fri Nov 12, 2004 8:46 am Post subject: |
|
|
veezi wrote: |
Can you post the output of the following commands:
Code: |
cat /usr/src/linux/.config | grep LOOP
ls -l /dev/loop*
modinfo loop
|
|
These are the bits of my .config:
Code: | CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y |
Here are the loop*s:
Code: | brw-rw---- 1 root disk 7, 0 Jul 18 01:13 /dev/loop0
brw-rw---- 1 root disk 7, 1 Jul 18 01:13 /dev/loop1
brw-rw---- 1 root disk 7, 2 Jul 18 01:13 /dev/loop2
brw-rw---- 1 root disk 7, 3 Jul 18 01:13 /dev/loop3
brw-rw---- 1 root disk 7, 4 Jul 18 01:13 /dev/loop4
brw-rw---- 1 root disk 7, 5 Jul 18 01:13 /dev/loop5
brw-rw---- 1 root disk 7, 6 Jul 18 01:13 /dev/loop6
brw-rw---- 1 root disk 7, 7 Jul 18 01:13 /dev/loop7
|
modinfo tells me it can't find module loop, though.
Quote: | modinfo: could not find module loop |
_________________ O_o |
|
Back to top |
|
|
veezi Apprentice
Joined: 10 Nov 2003 Posts: 226
|
Posted: Fri Nov 12, 2004 3:38 pm Post subject: |
|
|
Match wrote: |
These are the bits of my .config:
Code: | CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y |
Here are the loop*s:
Code: | brw-rw---- 1 root disk 7, 0 Jul 18 01:13 /dev/loop0
brw-rw---- 1 root disk 7, 1 Jul 18 01:13 /dev/loop1
brw-rw---- 1 root disk 7, 2 Jul 18 01:13 /dev/loop2
brw-rw---- 1 root disk 7, 3 Jul 18 01:13 /dev/loop3
brw-rw---- 1 root disk 7, 4 Jul 18 01:13 /dev/loop4
brw-rw---- 1 root disk 7, 5 Jul 18 01:13 /dev/loop5
brw-rw---- 1 root disk 7, 6 Jul 18 01:13 /dev/loop6
brw-rw---- 1 root disk 7, 7 Jul 18 01:13 /dev/loop7
|
modinfo tells me it can't find module loop, though.
Quote: | modinfo: could not find module loop |
|
Very strange. Your setup seems fine.
Can you do this as root:
Code: |
touch test.img
dd if=/dev/zero of=test.img bs=1M count=10
mke2fs test.img <--- answer yes
mount -o loop test.img /mnt/floppy
|
|
|
Back to top |
|
|
AnGel_Guardian n00b
Joined: 06 Nov 2004 Posts: 7
|
Posted: Fri Nov 12, 2004 9:40 pm Post subject: |
|
|
Quote: | modinfo: could not find module loop |
and what returns:
and then:
and what returns:
Code: | find /lib/modules/ | grep loop |
|
|
Back to top |
|
|
chunderbunny Veteran
Joined: 31 May 2004 Posts: 1281 Location: 51°24'27" N, 0°57'15" W
|
Posted: Fri Nov 12, 2004 11:14 pm Post subject: |
|
|
You're not going to have any luck with the loop module, since from your kernel config you appear to have compiled it right into the kernel, and not as a module. It's possible that if you recompiled your kernel with the loop device as a module rather than built in then it might work. |
|
Back to top |
|
|
Match Tux's lil' helper
Joined: 22 Mar 2004 Posts: 117 Location: England
|
Posted: Sat Nov 13, 2004 1:25 pm Post subject: |
|
|
veezi wrote: |
Very strange. Your setup seems fine.
Can you do this as root:
Code: |
touch test.img
dd if=/dev/zero of=test.img bs=1M count=10
mke2fs test.img <--- answer yes
mount -o loop test.img /mnt/floppy
|
|
This gives:
Code: | mount: Could not find any loop device. Maybe this kernel does not know
about the loop device? (If so, recompile or `modprobe loop'.) |
modprobe loop returns:
Code: | FATAL: Module loop not found. |
AnGel_Guardian wrote: |
and what returns:
Code: | find /lib/modules/ | grep loop |
|
Nothing.
Now, these are all with the loop thing as a module.
veezi wrote: |
Code: |
touch test.img
dd if=/dev/zero of=test.img bs=1M count=10
mke2fs test.img <--- answer yes
mount -o loop test.img /mnt/floppy
|
|
This gives the same message as before:
Code: | mount: Could not find any loop device. Maybe this kernel does not know
about the loop device? (If so, recompile or `modprobe loop'.) |
modprobe loop now gives this error:
Code: | FATAL: Error inserting loop (/lib/modules/2.6.8-gentoo-r10/kernel/drivers/block/loop.ko): Invalid module format |
modinfo loop now gives this:
Code: | parm: max_loop:Maximum number of loop devices (1-256)
license: GPL
alias: block-major-7-*
vermagic: 2.6.8-gentoo-r10 486 gcc-3.3
depends: |
_________________ O_o |
|
Back to top |
|
|
veezi Apprentice
Joined: 10 Nov 2003 Posts: 226
|
Posted: Sat Nov 13, 2004 9:23 pm Post subject: |
|
|
Perhaps you should start a new thread with your 'loop device' issue. Or, even file a bug report. The 'invalid module format' message is strange.
I would test another kernel. Different version, or even plain vanilla one, just to make sure. Loop devices shouldn't be that hard to get working after all, we all just take them for granted |
|
Back to top |
|
|
duby2291 Guru
Joined: 17 Oct 2004 Posts: 583
|
Posted: Sat Nov 13, 2004 11:39 pm Post subject: |
|
|
I finally was able to boot up my first livecd My next question is there a way that X can be configured on the fly, each time the disc is booted? Also is there a way that a user can be automagicaly logged in on boot up? |
|
Back to top |
|
|
veezi Apprentice
Joined: 10 Nov 2003 Posts: 226
|
Posted: Sun Nov 14, 2004 1:24 am Post subject: |
|
|
duby2291 wrote: | I finally was able to boot up my first livecd My next question is there a way that X can be configured on the fly, each time the disc is booted? Also is there a way that a user can be automagicaly logged in on boot up? |
For X config, there's a script around (I thing it's called makexconfig) that's borrowed from knoppix. It does that.
However, I personally use a generic X config that uses 'vesa' device. It's guaranteed to work on most PCs. |
|
Back to top |
|
|
Nutterpc Tux's lil' helper
Joined: 02 Feb 2004 Posts: 83
|
Posted: Sun Nov 14, 2004 7:12 am Post subject: |
|
|
after finding this guide, following it to the letter, I'm stuck on the emerge system bit, and its complaining to me while trying to update groff that it needs a working C++ compiler :S:S
Any idea whats goin on? _________________ If it isn't broke, you ain't tweaked it right
Registered Linux User 353232 |
|
Back to top |
|
|
Nutterpc Tux's lil' helper
Joined: 02 Feb 2004 Posts: 83
|
Posted: Sun Nov 14, 2004 7:32 am Post subject: |
|
|
looks like all I had to do atm, not sure till it finishes, was to logout of the chroot, copy some config files across, namely resolv.conf & sysctl.conf, relogin....and then re emerge gcc
hopefully, all goes well _________________ If it isn't broke, you ain't tweaked it right
Registered Linux User 353232 |
|
Back to top |
|
|
AnGel_Guardian n00b
Joined: 06 Nov 2004 Posts: 7
|
Posted: Sun Nov 14, 2004 8:47 am Post subject: |
|
|
Quote: | duby2291 wrote: way that X can be configured on the fly, each time the disc is booted? |
I am using mkxorgconf.sh and xorg.conf.in (xorg.conf.in is basic configuration file, which is used by mkxorgconf.sh and output is xorg.conf modified for your monitor and VGA) from the Jollix livecd. If you are using xorg-x11, you can download it here:
http://193.179.144.16/files/mkxorgconf.tar.gz
(i hope, both files are gpl-2 licensed......perhaps yes, because are derived from mkxf86config).
Info: mkxorgconf.sh is using ddcxinfo-knoppix tool to recognize your monitor!
Info: mkxorgconf.sh is using hwdata-knoppix tool to recognize your vga!
Last edited by AnGel_Guardian on Sun Nov 14, 2004 11:43 am; edited 2 times in total |
|
Back to top |
|
|
AnGel_Guardian n00b
Joined: 06 Nov 2004 Posts: 7
|
Posted: Sun Nov 14, 2004 10:31 am Post subject: autologin |
|
|
Quote: | duby2291 wrote: Also is there a way that a user can be automagicaly logged in on boot up? |
Yes, there is the way:
! Warning ! Method used in next lines is unsecure, bacause automatical root rights can be dangerous using incompetent hands....blah blah.
Code: | emerge mingetty -av |
this line in your /etc/inittab
Code: | c1:12345:respawn:/sbin/agetty 38400 tty1 linux |
replace with:
Code: | c1:12345:respawn:/sbin/mingetty --autologin root tty1 |
Try restart your system - wow - root is logged in!
Info: I have no idea, if RMNOLOGIN daemon can affect autologin. I take precautions against:
Code: | rc-update del rmnologin boot default |
|
|
Back to top |
|
|
Illissius Guru
Joined: 31 Jul 2004 Posts: 395 Location: Hungary
|
Posted: Sun Nov 14, 2004 1:16 pm Post subject: |
|
|
Well, emerge system is working now. Guess what the problem was? Emerge listed linux-headers as a blocker, so I unmerged it. It then failed to compile, apparently because linux-headers was missing. Emerging linux26-headers seems to have fixed it.
*smacks head against desk*
EDIT -
Also. There isn't anything that would theoretically prevent me from installing the 'livecd' on a random USB mass storage device of choice or something, is there? (in my case, an iRiver iHP-120) _________________ Work is punishment for failing to procrastinate effectively.
last.fm |
|
Back to top |
|
|
veezi Apprentice
Joined: 10 Nov 2003 Posts: 226
|
Posted: Sun Nov 14, 2004 7:26 pm Post subject: Re: autologin |
|
|
AnGel_Guardian wrote: | Quote: | duby2291 wrote: Also is there a way that a user can be automagicaly logged in on boot up? |
Yes, there is the way:
! Warning ! Method used in next lines is unsecure, bacause automatical root rights can be dangerous using incompetent hands....blah blah.
Code: | emerge mingetty -av |
this line in your /etc/inittab
Code: | c1:12345:respawn:/sbin/agetty 38400 tty1 linux |
replace with:
Code: | c1:12345:respawn:/sbin/mingetty --autologin root tty1 |
Try restart your system - wow - root is logged in!
Info: I have no idea, if RMNOLOGIN daemon can affect autologin. I take precautions against:
Code: | rc-update del rmnologin boot default |
|
Just keep in mind that when using 'livecd' flag the init scripts will change all the getty lines in /etc/inittab with a default value automatically at boot time. So, don't be surprized if you see that whatever getty line you put in /etc/inittab is not working |
|
Back to top |
|
|
AnGel_Guardian n00b
Joined: 06 Nov 2004 Posts: 7
|
Posted: Sun Nov 14, 2004 8:42 pm Post subject: re: autologin |
|
|
Quote: | veezi said: Just keep in mind that when using 'livecd' flag the init scripts will change all the getty lines in /etc/inittab with a default value automatically at boot time. So, don't be surprized if you see that whatever getty line you put in /etc/inittab is not working Smile |
Yes you right. After livecd boot is the line in inittab changed to:
Code: | c1:12345:respawn:/sbin/agetty -nl /bin/bashlogin 38400 tty1 linux |
.....but it is still working for me. My login is automatical and logged user is root. No problem for me. (i don't know why is it so, but ti is functional). (perhaps the "-nl" option behind the AGETTY.....) |
|
Back to top |
|
|
duby2291 Guru
Joined: 17 Oct 2004 Posts: 583
|
Posted: Mon Nov 15, 2004 12:21 am Post subject: |
|
|
Quote: | Also. There isn't anything that would theoretically prevent me from installing the 'livecd' on a random USB mass storage device of choice or something, is there? (in my case, an iRiver iHP-120) |
I don't see any reason why it wouldn't work, but you will need to find a boot loader that supports USB booting. I don't think that grub does. Also it may be a good idea to leave the filesystem readonly, and use a ramdrive, the same way the livecd does. I'd be interested in making a bootable flashdrive if anyone has any idea's feel free to share |
|
Back to top |
|
|
Illissius Guru
Joined: 31 Jul 2004 Posts: 395 Location: Hungary
|
Posted: Mon Nov 15, 2004 3:28 pm Post subject: |
|
|
Yes, I still intend to use SquashFS (possibly with a few strategically chosen dirs mounted rw from the other partition), mainly because 700MB-1GB is acceptable, but 4GB is not.
Speaking of which. Is it possible to mount /etc from a seperate partition than /? I'm just asking, because fstab itself is in /etc, so... _________________ Work is punishment for failing to procrastinate effectively.
last.fm |
|
Back to top |
|
|
|