CeBIT-news: Klaus presentated Knoppix 3.2

[audioaficionado]

(cd /mnt/hd**/etc/lilo.conf) Open up the HD lilo conf file in the text editor, save a backup and then have at it. Save when you're done and give it a whirl.

After you edit and save lilo.conf run /sbin/lilo to commit the changes then re-boot.

Oops! I should have been more specific than 'give it a whirl'

[hherb]

(cd /mnt/hd**/etc/lilo.conf) Open up the HD lilo conf file in the text editor, save a backup and then have at it. Save when you're done and give it a whirl.

After you edit and save lilo.conf run /sbin/lilo to commit the changes then re-boot.

Oops! I should have been more specific than 'give it a whirl'

I'd expect that you have to chroot first, else lilo might just not do what you want. Or pass the desired configuration file as command line parameter to lilo.

[RockMumbles]

LinuxIdiot

If you want to edit your cd so it boots with the proper boot parameters you would need to have the iso on your hd mount it and put your boot parameters in syslinux.cfg

Here are instructions I took from the S-Terminal website and edited for your purpose:

# Burning a modified KNOPPIX CD: Making minor changes to KNOPPIX is easy. It doesn't require huge resources like a full remastering, it just takes a little finesse. You just use the fact that the information from a KNOPPIX "floppyconfig" floppy can be added to the CD. The floppyconfig files can then be used to re-configure KNOPPIX automatically at boot time. Here's how to do it:

# First, mount the stock KNOPPIX iso and copy the files into a new directory:
# KNOPPIX-blah-blah.iso will be KNOPPIX_V3.1-2003-01-20-EN.iso etc.
mkdir /mnt/knoppix
losetup /dev/loop0 KNOPPIX-blah-blah.iso
mount /dev/loop0 /mnt/knoppix
mkdir /usr/src/new-knoppix

# This will take a while:
cp -r -a -p /mnt/knoppix/* /usr/src/new-knoppix/

# Clean up after ourselves:
umount /mnt/knoppix
losetup -d /dev/loop0


# Now, you will need to edit /usr/src/new-knoppix/KNOPPIX/syslinux.cfg
# add your boot parameters into the APPEND lines,
# for both:" DEFAULT vmlinuz " section and also " LABEL knoppix " section


# Finally, cook up the new iso image:
cd /usr/src/new-knoppix
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved \
-o /usr/src/new-knoppix.iso .

Note the mkisofs (3) line(s) will need to be copied carefully, don't forget final . (period) you might want to make the mkisofs part into a script.

Then burn a new cd from new-knoppix.iso

rock

[laurentbon]

I have done a HD install

3.2 seems to prevent me from starting another window manager than kde.
When I stop the kdm service and try to run ./xdm start, it says that xdm is not your default window manager so won't start it.

How can I run gnome instead of kde?

Any one an idea?

Cheers

[MichielioZ]

laurentbon : please read the releasenotes from Klaus...
It is stated in there that he took Gnome out of the loop for the time being, because it didn't work good yet...
It will return to you probebly in a later release..

[laurentbon]

Douggghhhh!!!
That would explain a lot...

A shame for gnome... Have to wait for V3.3 then...

[LinuxIdiot]

LinuxIdiot

If you want to edit your cd so it boots with the proper boot parameters you would need to have the iso on your hd mount it and put your boot parameters in syslinux.cfg

Here are instructions I took from the S-Terminal website and edited for your purpose:

# Burning a modified KNOPPIX CD: Making minor changes to KNOPPIX is easy. It doesn't require huge resources like a full remastering, it just takes a little finesse. You just use the fact that the information from a KNOPPIX "floppyconfig" floppy can be added to the CD. The floppyconfig files can then be used to re-configure KNOPPIX automatically at boot time. Here's how to do it:

# First, mount the stock KNOPPIX iso and copy the files into a new directory:
# KNOPPIX-blah-blah.iso will be KNOPPIX_V3.1-2003-01-20-EN.iso etc.
mkdir /mnt/knoppix
losetup /dev/loop0 KNOPPIX-blah-blah.iso
mount /dev/loop0 /mnt/knoppix
mkdir /usr/src/new-knoppix

# This will take a while:
cp -r -a -p /mnt/knoppix/* /usr/src/new-knoppix/

# Clean up after ourselves:
umount /mnt/knoppix
losetup -d /dev/loop0


# Now, you will need to edit /usr/src/new-knoppix/KNOPPIX/syslinux.cfg
# add your boot parameters into the APPEND lines,
# for both:" DEFAULT vmlinuz " section and also " LABEL knoppix " section


# Finally, cook up the new iso image:
cd /usr/src/new-knoppix
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved \
-o /usr/src/new-knoppix.iso .

Note the mkisofs (3) line(s) will need to be copied carefully, don't forget final . (period) you might want to make the mkisofs part into a script.

Then burn a new cd from new-knoppix.iso

rock

Thanks for the instructions Rock, I will give this a whirl when i get home.

Thanks for the help with LILO audio dun worry I knew about that part in fact I will have to run it again when I get home so it will boot into LILO instead of windows cuz I had to fixboot and fixmbr when I could not get my computer to boot into anything Hope this works I will let you all know if I met with success first off gonna try fixing my LILO problem then remastering knoppix to give to my friend hehe he hates having to type anything in to get this to work on his computer...lazy ass

[audioaficionado]

I'll remaster mine too. First I'll get rid of all but the one EN boot.img to give me an extra 2.88Mb. Next I'll work on the boot parameters so it always picks up my saved configs without having to inter the knoppix myconfig=scan cheat code every time. It also would be nice if the congfig would automaticly save when I log off but I'd settle for a save button just above the log-off button.

[LinuxIdiot]

I can not get it to save if i type

sudo kedit /mnt/hda7/etc/lilo.conf

it opens i edit then in the shell console i get this error

WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) \x08
Major opcode: *

here is a copy of my LILO

vga=791
# /etc/lilo.conf - See: `lilo(' and `lilo.conf(5)',
# --------------- `install-mbr(', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81

#disk=/dev/sda
# bios=0x80

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda7

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr('.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
# prompt
# single-key
# delay=100
# timeout=100

# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce"

# Boot up Linux by default.
#
default=Linux

image=/boot/vmlinuz-2.4.20-xfs
label=Linux
initrd=/boot/initrd.gz
read-only
# restricted
# alias=1

image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
other=/dev/hda1
label="WinNT(hda1)"

other=/dev/hda5
label="WinNT(hda5)"

other=/dev/hda6
label="Linux(hda6)"

other=/dev/hdb1
label="WinNT(hdb1)"

other=/dev/loop0
label="Other(loop0)"

Question: If my windows partition is on hda1 and linux is on hda7 will i just need to change this one part?

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

To:

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda1

[audioaficionado]

I've got GRUB installed inspite of Debian's insistance of installing LILO. Looking at you LILO config file just gave me a headache. GRUB was a lot shorter and much simpler to configure.

YMMV