Results 1 to 8 of 8

Thread: Installing Knoppix on the same hd with MD9.1

  1. #1
    Junior Member registered user
    Join Date
    Oct 2003
    Location
    Florida
    Posts
    13

    Installing Knoppix on the same hd with MD9.1

    Can I install Knoppix on my hdd that has MD9.1 already running?

    Thanks
    pbearseven

  2. #2
    Senior Member registered user
    Join Date
    Mar 2003
    Location
    colorado springs, colorado
    Posts
    1,933
    Of course.

  3. #3
    Junior Member registered user
    Join Date
    Oct 2003
    Location
    Florida
    Posts
    13
    Would somebody explain how I would go about installing Knoppix on my hdd, I'm still a little fuzzy when it comes to Linux installs.

    Thanks
    pbearseven

  4. #4
    Junior Member registered user
    Join Date
    Oct 2003
    Location
    Florida
    Posts
    13
    I forgot to add I have the live Knoppix cd 3.3.

    pbearseven

  5. #5
    Junior Member
    Join Date
    Sep 2003
    Posts
    9
    the knoppix installation will reformat the partition you are installing to, so you will loose your mandrake system if you use the same partition. if you want to keep it you need to use another partition.

  6. #6
    Junior Member registered user
    Join Date
    Oct 2003
    Location
    Florida
    Posts
    13
    I am a noobie, so would you please explain how I would go about creating another partition for Knoppix. I do want to keep MD9.1.

    Thanks
    pbearseven

  7. #7
    Junior Member
    Join Date
    Nov 2002
    Location
    EU
    Posts
    7
    Quote Originally Posted by pbearseven
    I am a noobie, so would you please explain how I would go about creating another partition for Knoppix. I do want to keep MD9.1.
    I've just done this - with Mandrake & Knoppix on the same disk. But I keep spare space free for testing new distros and general messing about, so there was no problem - I made sure to tell knx-hdinstall to not overwrite my MBR with LILO, and added an option in Mandrake's LILO to boot it.

    Without the luxury of spare space, you need to resize a partition to make some free space (I used 4GB for Knoppix). You can use GNU Parted for this, but be warned it is not for the faint of heart. If you are at all unsure about what you're doing, and can't afford to lose your Mandrake install then don't do it.

    If you have a Windoze installation you could also try Partition Magic or similar to do the same thing... if they can resize ext2 or whatever your Mandrake uses, non-destructively. I forget. Good luck!

    Andrew Preater

  8. #8
    Junior Member registered user
    Join Date
    Jun 2003
    Posts
    14

    What to do when I overwrote MBR while installing 2. linux?

    Hi,

    unfortunatelly while installing a second knoppix (hda9) to play with, I overwrote the mbr.

    So cannot start the original knoppix installation (hda6), as it is not listed in lilo anymore.

    But I still do have the original lilo.conf file in mnt/hda6/etc/lilo.conf.

    How to make the original knoppix installation on hda6 bootable again?

    Listed:
    1) cfdisk
    2) original lilo.conf
    3) new lilo.conf

    Any help very appreciated,
    JanMartin

    cfdisk looks like this:

    cfdisk 2.12
    Disk Drive: /dev/hda
    Size: 60011642880 bytes, 60.0 GB
    Heads: 255 Sectors per Track: 63 Cylinders: 7296

    Name Flags Part Type FS Type [Label] Size (MB)
    ---------------------------------------------------------
    hda1 Boot Primary W95 FAT32 4721.32
    hda5 Logical W95 FAT32 10783.35
    hda6 Logical Linux ReiserFS 11128.81
    hda7 Logical Linux swap 666.25
    hda8 Logical Linux ReiserFS 21912.15
    hda9 Logical Linux ReiserFS 5000.98
    Pri/Log Free Space 5798.83

    original lilo.conf:
    vga=791
    # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
    # --------------- `install-mbr(8)', `/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/hda6

    # 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(8)'.
    #
    # 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

    default=Linux
    image=/boot/vmlinuz
    label=Linux
    read-only

    image=/vmlinuz.old
    label=LinuxOLD
    initrd=/boot/initrd.gz


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

    #image=/vmlinuz.old
    # label=LinuxOLD
    # read-only
    # optional
    #o restricted
    #o 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="Windows(hda1)"

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



    new lilo.conf
    vga=791
    # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
    # --------------- `install-mbr(8)', `/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/hda9

    # 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(8)'.
    #
    # 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.22-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="Windows(hda1)"

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

Similar Threads

  1. Installing Knoppix
    By GenneX in forum Hdd Install / Debian / Apt
    Replies: 1
    Last Post: 02-04-2005, 11:59 PM
  2. installing knoppix to hdd
    By marijn in forum Hdd Install / Debian / Apt
    Replies: 1
    Last Post: 12-09-2004, 10:10 PM
  3. Installing Knoppix..
    By williamb in forum Hdd Install / Debian / Apt
    Replies: 2
    Last Post: 11-21-2004, 05:36 PM
  4. Installing Knoppix 3.3
    By knoppixman2004 in forum Hdd Install / Debian / Apt
    Replies: 3
    Last Post: 07-03-2004, 08:18 AM
  5. installing knoppix vs installing Linux from scratch
    By jza in forum Hdd Install / Debian / Apt
    Replies: 1
    Last Post: 05-03-2003, 11:30 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •