-
How can I force one of two KNOPPIX filesystems to be detected
I have a KNOPPIX boot stick and a KNOPPIX boot laptop.
If I insert the stick into the laptop and fire the laptop up and visit Boot Order I can require the stick to be detected.
(i.e. perfectly normal KNOPPIX practice for many of us.)
However there then seems to occur a kind of "search" and although the stick was initially engaged, it is the laptop's KNOPPIX system that is detected and utilised thereafter.
Can I force the stick to be the platform that is used?
(The point of doing this is that I want to mess about with the laptop's filesystem - and so I want it to be "dead" not live while I do this.)
Thank you!
-
If you look at /init file of Knoppix you will see the reason. Init file accomplishes this:
# Its purpose:
# 1. Mounting CD, DVD, Flashdisk or network drive,
# 2. unifying read-only compressed file system and ramdisk or file overlay,
# 3. give control to the real sysv init, which then continues to work like
# we booted from a single disk partition.
Init file is part of the initrd (in a running Knoppix OS it is: /init). You have to edit initrd to edit init file. The problem is that Knoppix's busybox (which is also part of initrd) does not support UUID detection. Instead, it uses the notations like /dev/sda, /dev/sdb ... But this method is not reliable: it can produce problems in case of multiple internal disks, external drives (USB stick) if more of them contains Knoppix OS because the first found instance will be used. The ideal solution would be that Knoppix use a busybox version that supports UUID detection so that can be applied a cheat code to give the UUID of boot device. Should be done a feature request...
But even in present situation you can solve this problem if you do not use ISO boot. Look at Knoppix cheatcodes.
### Configuration / Persistent image ###
knoppix knoppix_dir=KNOPPIX Directory to search for on the CD.
So, you have to rename your KNOPPIX directories with unique names and give the desired name as boot parameter. Of course, in case of Knoppix ISO this is impossible.
You can use this solution only if extract the ISO content and use your own boot parameters.
For example the ISO content is copied to a USB stick and you boot Knoppix with GRUB2 installed to that stick. And the boot params are given in grub.cfg file.
Last edited by szzsqing1; 04-14-2022 at 11:02 AM.
Reason: busibox >> busybox
-
Rectification: in case of ISO boot you can resolve the problem, too. You can specify the ISO image file as boot parameter:
knoppix bootfrom=/dev/sda1/KNX.iso Access image, boot from ISO-Image
So you can rename the ISO files or put them in directories with unique names.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules

HP Z420 Workstation Xeon E5-1650 V2 3.50 GHz 64GB RAM 256GB SSD 2TB Win 10 Pro
$250.00

Intel Xeon CPU E5-2667 V2 3.30GHz 25MB Cache 8 Core LGA2011 Processor SR19W
$16.00

Intel E5-2667 V4 Xeon Processor CPU 3.20GHz LGA2011-3 8-Cores 16-Threads Server
$37.99

CM8066002031501 INTEL XEON E5-2680V4 2.40GHZ 35MB 14-CORE 120W PROCESSOR
$23.98

Intel Xeon E5-2699 v3 2.3 GHz 45 MB 18 Core SR1XD LGA2011-3 Clean Pull CPU
$67.95

INTEL XEON E5-2697V4 18-CORE 2.30GHz SERVER PROCESSOR CPU SR2JV
$95.00

SR3B5 INTEL XEON GOLD 6138 2.00GHZ 27.5MB 20-CORE 125W PROCESSOR
$105.00

SR151 Intel Xeon E3-1270v3 Quad Core 3.5GHz LGA1150 CPU Processor Grade A
$26.69

Dell Precision T3500 Xeon Workstation Computer Windows 10 Home 8GB 250GB 500GB
$170.99

Dell Precision Tower T3610 Xeon E5-1620 v2 3.70GHz 16GB 6TB Win10 PRO K600 PC
$149.98