Boot disks to get to cdrom.

2001-03-30 Thread Ted Gervais
Can someone tell me how and where I can make up boot disks to get my system to see the cdrom and the cdrom iso image I have there. My computer can not boot to the cdrom so I am stuck. There must be a way with boot disks.. -- Ted Gervais Coldbrook, Nova Scotia Canada -- To UNSUBSCRIBE, ema

Re: 2.4.1: cramfs and initrd

2001-03-30 Thread Herbert Xu
Arthur Korn <[EMAIL PROTECTED]> wrote: > But isofs is read only, and we might need to write to the initrd > (at least if we want to allow installation with all-LVM, which > would be pretty nifty). tmpfs + pivot_root should be all you need. -- Debian GNU/Linux 2.2 is out! ( http://www.debian.org

Re: 2.4.1: cramfs and initrd

2001-03-30 Thread Herbert Xu
On Sat, Mar 31, 2001 at 01:03:17AM +1000, Glenn McGrath wrote: > > Im thinking that iso9600 might be a good format for the initrd, because > the initrd will be compressed anyway cramfs doesnt save us anything on > the boot disk. It really depends on how big the initrd is. For the boot floppies

Re: 2.4.1: cramfs and initrd

2001-03-30 Thread Arthur Korn
Glenn McGrath schrieb: > Im thinking that iso9600 might be a good format for the initrd, because > the initrd will be compressed anyway cramfs doesnt save us anything on > the boot disk. > > ISO9660 fs support adds less to the kernel size than any other fs. But isofs is read only, and we might n

Re: 2.4.1: cramfs and initrd

2001-03-30 Thread Glenn McGrath
Mark van Walraven wrote: > > On Wed, Mar 28, 2001 at 09:29:14PM +1000, Herbert Xu wrote: > > zhaoway <[EMAIL PROTECTED]> wrote: > > > > > Does anyone have this problem for kernel 2.4.1? When I compiled in > > > cramfs, initrd cannot work. Kernel message screen just say: > > > > > wrong magic <==

Re: 2.4.1: cramfs and initrd

2001-03-30 Thread Mark van Walraven
On Fri, Mar 30, 2001 at 10:49:37PM +1000, Herbert Xu wrote: > But why are you compiling cramfs in if you're using ext2 initrd images? > The images I make can't handle ext2 images anyway since ext2 isn't compiled > in. Well, I took it from the kernel-source changelog and the description in the mkc

Re: 2.4.1: cramfs and initrd

2001-03-30 Thread Herbert Xu
Mark van Walraven <[EMAIL PROTECTED]> wrote: > I think the cure is worse than the disease. :-) Suddenly your 1k/block > ext2 initrd fails to mount and the kernel panics without anything to > tell you it's because the filesystem blocksize now no longer matches > the new default ramdisk device blo

Re: 2.4.1: cramfs and initrd

2001-03-30 Thread Mark van Walraven
On Wed, Mar 28, 2001 at 09:29:14PM +1000, Herbert Xu wrote: > zhaoway <[EMAIL PROTECTED]> wrote: > > > Does anyone have this problem for kernel 2.4.1? When I compiled in > > cramfs, initrd cannot work. Kernel message screen just say: > > > wrong magic <== spit out by cramfs(?) which shouldn't be

Re: new mklibs.sh to test

2001-03-30 Thread Joey Hess
Ben Collins wrote: > Here's my working copy of mklibs.sh. I've only tested this with local > binaries, but it seemed to work well reducing a libc.so.6 et al with > binaries from /bin and /sbin on my workstation. It seems to work ok for reducing debian-installer .. actually, I don't think the old