ISO boot from FAT/NTFS/USB (GRUB.exe, grldr from boot.ini)

Quote:

---

Originally Posted by ruymbeke

Hello,
Please find below the link to the Knoppix 5.2 update of the iso boot minirt:
http://s94002264.onlinehome.us/grub/minirt_520.gz
Have fun, and please provide some feedback...
Gilles
.

---

Hi Gilles,
starting with the first 4*-DVD of Knoppix I went from a loadlin-install of Knoppix to your version with grub and the patched minirt.gz

I just tryed to go to the 5,2 c't-Version, but I'm running into some trouble:
The Kernel shows correctly as 2.6.19.5, it tells me that my iso is found on /dev/hda6 OK (ext3-filesystem), but then, when it should say something like "accessing KNOPPIX CDROM -
/cdrom2.loop/*.iso " it only says

acessing KNOPPIX CDROM failed; can't find KNOPPIX filesystem

...and I'm in the limited shell.

I went ahead and burned the iso to a dvd => this runs just fine.
The md5 of my iso is:
fdbff1d8b93d4c1a724cb68b4e4f8bf2 knx520.iso

Any suggestions?

Thatnks in advance!

poor_mans_knoppix

Quote:

---

Originally Posted by poor_mans_knoppix

... I just tryed to go to the 5,2 c't-Version, but I'm running into some trouble:
The Kernel shows correctly as 2.6.19.5, it tells me that my iso is found on /dev/hda6 OK (ext3-filesystem),
but then, when it should say something like "accessing KNOPPIX CDROM - /cdrom2.loop/*.iso "
it only says acessing KNOPPIX CDROM failed; can't find KNOPPIX filesystem ...

---

Hello,
Please accept my deep apologies, it should now be fixed using this new link:
http://s94002264.onlinehome.us/grub/minirt_52.gz
This minirt_52.gz also includes a (dynamically) patched knoppix-autoconfig file for persistent home (cf below)

I also created a new Knoppix 5.2 c't virtual machine for VmWare 6-RC (build 44426):
http://s94002264.onlinehome.us/grub/vmk520_44426.zip (10MB)

As usual, I really apreciate feedback.
Best Regards,
Gilles

Ps1: It looks like that the lang=us kernel cheat code changes the keyboad mapping but not the menus yet...

PS2: I think I have found 3 typos in the official /etc/init.d/knoppix-autoconfig script, cf bug report:
http://www.knoppix.net/wiki/Bugs/5.20 and a patch: http://s94002264.onlinehome.us/grub/...onfig_520.diff

Ps3: For the long story, sorry for the delay in my response but I have been very busy at work this last month
and I only got the time now to fix a very stupid (and known) bug in my modified linuxrc boot script:
if [ -f $TARGET/$KNOPPIX_DIR/$KNOPPIX_NAME ] --> if test -r $TARGET/$KNOPPIX_DIR/$KNOPPIX_NAME
(When I was running my tests previously I didn't realize that the iso used was a left over from a test on Fat32)

Thanks Gilles. It is a pity that knoppix essentially remains a one-man stunt. There's no bugzilla anymore, and requests to the mailing list are often ignored. Have you considered submitting your NTFS/VMWare additions to sidux for inclusion? Not to belittle knoppix, but they at least are working as a team, and take HD-installation to heart.

Hello,
I received this very good question in a private message:

Quote:

---

Originally Posted by skisteven1

... I downloaded vmk511_39849b.zip from your website, and booted up the virtual machine in that file.
I reset the ISO image to the location of the KNOPPIX_V5.1.1DVD-2007-01-04-EN DVD ISO file that I have.
The machine boots and seems to work, but I was wondering if there is a specific method for making persistent changes...

---

and since I believe it can can be usefull to others please find below a copy of my answer:

Quote:

---

Yes, Knoppix can be used with a persistent image and this persistent image can also be used with vmware.
I actually use a persistent image in the process of creating my Knoppix virtual machine.

So obviously you can create a vmware virtual machine with a persistent image stored on a vmware virtual hdd.
You don't need to use my zip file, just create an empty virtual machine and install everything
as you would do on a real machine, including formatting the hdd, installing a disk boot loader and
installing the vmware tools before creating the persistent image, so it can be used for the next boot.
By doing so you will be able to store changes and keep your data for the next boots.
The draw back of this approach is in my opinion the large size of the virtual machine.
As an example, it is quite hard to get a persistent image smaller than 100MB if you install the vmware tools...

This is the reason why I decided to use an other customized & optimized mechanism to load
the vmware tools which is not really compatible with the existing persistent image mechanism.
My goal is to provide a ready to use and ultra compact Knoppix vmware virtual machine (<10MB) which can be used
to have a quick access to the native linux tools and/or as a very fast free X server to access an other Linux box.

So as a quick answer, I do not see an easy way to use my zip file to create a persistent image.
Since I used a persistent image to create my setup, I would recommend you to do the same:
Create a virtual machine and install Knoppix as it should be done on a real machine.
You may still want to consider re-using my bootlaoder and/or my boot ram disk in order to boot from
the iso with custom kernel cheatcodes (to enable the loading of persistent image as an example).

After a second thought, I did not try to create a persistent image after having booted from my Knoppix vm.
It may work ... (with some tweaking)

---

I hope this is helpful information.
Best Regards,
Gilles

Quote:

---

Originally Posted by skisteven1

cut/paste would be totally fine.

I noticed with some more playing around that when i try using the persistent image within knoppix (that saves to a .img file), it breaks your vmware-tools install. Same goes for when I do a knoppix saveconfig (which saves settings and changes to /etc to a .tgz file or something). I feel like there must be a way to implement these changes to the UNIONFS after loading the things that come from your custom setup. (by the way, now that i've been playing with this stuff for a few hours, i can really appreciate how elegant and well done your virtual machine zip file is. Kudos to you!)

Let me see if I've got this straight:
the virtual machine loads to disk, encounters grub, which simply boots knoppix with various cheatcodes from the ISO image on /dev/hdc. It also uses your custom initrd instead of the standard one. I'm not sure what "vga=791" does, or why the ramdisk is set to 1gb. It also pulls a custom hostname and sets the screen to 1024x768.

Then it runs the custom knoppix.sh file in /dev/hda1. I even see the part where you merge in the "vmware-tool" cusomization from /mnt/hda1/boot/vm_....tgz I'm not sure what HGFS is, but that seems to fail. Interestingly enough, when it initializes the X server with the vmware video card to 1024x768 max, but when X starts up it starts iwth some HUGE resolution (2048x1500 or something). I can't figure that part out.

---

"ramdisk_size=100000" and "vga=791" are from the original isolinux.cfg file on the original Knoppix cdrom.
hostname is one of my add-on in my custom initrd and the "screen=1024x768" parameter is useless
since overrided by the vm tools. (Resolution is defined by the vmware tools configuration script)
hgfs is created in /mnt by the vmware tools setup to store the shared directories (between host and guest).
The vmware tools configuration script creates a new xorg.conf (X11 config file) which I have setup for
the max resolution since vmware allows for an easy window shrink (especially in full screen mode)
but not to enlarge if a small screen size has been previously defined. Since I like the option to use
a large screen (in full screen mode) I had to select the largest screen size as a default...
This problem will be solved in the new upcoming vmware workstation 6.0 since it will allow to limit the maximum
guest screen resolution by a parameter in the vmware config file and as such can now be very easily customized.
BTW, my Knoppix 5.2 zip file is already using this feature and can be used with the "freely downloadable"
release candidate of vmware workstation 6.0.

Quote:

---

Originally Posted by skisteven1

At this point -- everything works as it should, including vmware tools. The problem is that if I try to make configuration changes (like, say, changing the screen resolution in Xorg down to 1024x768 or something), and save that using either of knoppix's built-in methods for saving settings -- it totally mucks up your stuff, and vmware tools doesn't integrate properly on the next reboot.

I wonder, how much do you know about the way that knoppix does persistent settings (it has two built-in methods)? I wonder if there is a way to make the knoppix-style changes at the same time, or BEFORE your knoppix.sh script makes changes. As long as your changes come 2nd, it should be ok (i think).

Do you have any thoughts or ideas on the subject? Any ideas why the screen resolution of X starts off so funky? is that just me or everyone?

Thanks,
Steven

---

As I wrote previously, it is probably best not to use both mechanism at the same time.
I basically let Knoppix create a new root file system including the /etc and /home/knoppix directories
and I overwrite (thanks to the UnionFS) the files modified by the vmware tools install using a compact gzip file.
The persistent approach is quite different in the sense that it will use the knoppix.sh script to "mount" the persistent
/home/knoppix user directory and merge the custom system settings in the /etc.

So the way I would try it would be to create a persistent image after having booted from my Knoppix vm
and modify the knoppix.sh script (or use an original one created by Knoppix outside the vm context) in order to load
the persistent image instead uncompressing my zip file which would override the changes made in the persistent file.
If you use the persistent mount after my vm.tgz it would drop the vmware tools settings changes.
What I just suggested is basically equivalent to unzip (once only) the content of my vm.tgz into your persistent image.
(which is by the way exactly the inverse of what I used to create my gzip file from a persistent image
after having installed the vmware tools from a clean Knoppix cd boot within a brand new vm with a hdd)

Now if your problem is only the default screen size, I would suggest you to just edit the /etc/x11/xorg.conf file
included in my /mnt/hda1/boot/vm.tgz file in order to permanently change the default screen resolution.

Hope this helps,
Gilles

Quote:

---

Originally Posted by ruymbeke

As I wrote previously, it is probably best not to use both mechanism at the same time.
I basically let Knoppix create a new root file system including the /etc and /home/knoppix directories
and I overwrite (thanks to the UnionFS) the files modified by the vmware tools install using a compact gzip file.
The persistent approach is quite different in the sense that it will use the knoppix.sh script to "mount" the persistent
/home/knoppix user directory and merge the custom system settings in the /etc.

So the way I would try it would be to create a persistent image after having booted from my Knoppix vm
and modify the knoppix.sh script (or use an original one created by Knoppix outside the vm context) in order to load
the persistent image instead uncompressing my zip file which would override the changes made in the persistent file.
If you use the persistent mount after my vm.tgz it would drop the vmware tools settings changes.
What I just suggested is basically equivalent to unzip (once only) the content of my vm.tgz into your persistent image.
(which is by the way exactly the inverse of what I used to create my gzip file from a persistent image
after having installed the vmware tools from a clean Knoppix cd boot within a brand new vm with a hdd)

---

Gilles,

How exactly did you go about producing your tgz file to modify the UNIONFS? You said that you did it by recording modifications to the filesystem after installing vmware tools to a clean knoppix install -- but not through what method you did that. My thoughts are that I might be able to use the very same method to make more changes and simply update the tgz file. Additionally, i'd like to reset the homedirectory for the knoppix user to be at /dev/hda1/homes/ . I think that by doing that (perhaps via symlinks?) most of the changes on a day to day basis would NOT have to be added to your tgz file. Any suggestions?

Thanks,
Steven

Quote:

---

Originally Posted by skisteven1

How exactly did you go about producing your tgz file to modify the UNIONFS? You said that you did it by recording modifications to the filesystem after installing vmware tools to a clean knoppix install -- but not through what method you did that. My thoughts are that I might be able to use the very same method to make more changes and simply update the tgz file. Additionally, i'd like to reset the homedirectory for the knoppix user to be at /dev/hda1/homes/ . I think that by doing that (perhaps via symlinks?) most of the changes on a day to day basis would NOT have to be added to your tgz file. Any suggestions?

---

Hi Steven,
It is built-in the Unionfs: by definition no file changes can be stored within the iso file nor the hdd since they are mounted as read only,
so the data changes have to be stored into the only writable media available which is the ramdisk. So if you get the ramdisk content,
remove the unwanted files (as temporary files, or files re-created at boot time) and make a tgz file of it that you will load at boot time,
you should more or less have it... I would guess that you most likely can use a symlink (created in the knoppix.sh script)
to redirect the the Knoppix home directory to your local hdd.
Hope this helps,
Gilles

Hello,
Please find below the new VmWare Workstation 6.0.0 or Player 2.0.0 (build 45731) virtual machines for:
http://s94002264.onlinehome.us/grub/vmk511_45731.zip Knoppix 5.1.1 (no persistence)
http://s94002264.onlinehome.us/grub/vmk520_45731.zip Knoppix 5.2.0 (no persistence)
http://www.vmware.com/vmtn/appliances/directory/866 (VmWare appliances listing link)
http://www.knoppix.net/forum/viewtop...=114363#114363 (vm for VMWare Server 1.0.3 build 44356)
http://www.knoppix.net/forum/viewtop...=113141#113141 (with prog & data persistence)
Have fun, and please provide some feedback...
Gilles

MD5 & size of the files:
eb54a7cc3f36e2c1d0008e3bbed26e34 *vmk511_45731.zip (10'031'566)
8e47a0d41e64e907cf971e40577b560c *vmk520_45731.zip (9'650'467)

Old vm links for reference:
http://www.knoppix.net/forum/viewtop...=112830#112830
http://www.knoppix.net/forum/viewtop...=110240#110240
http://www.knoppix.net/forum/viewtop...=110103#110103
http://www.vmware.com/vmtn/appliances/directory/662
http://www.vmware.com/vmtn/appliances/directory/554

PS: In order to change the maximum screen size please edit the following text lines of the vmx file:
(since the edit display config menu is not accessible from winthin the vmware player)
svga.maxWidth = "640" "800" "1024" "1280" "1280" "1600"
svga.maxHeight= "480" "600" "768" "1024" "1200" "1200"
svga.vramSize = "1228800" "1920000" "3145728" "5242880" "6144000" "7680000"

Hi there,

first of all thx for this vm Gilles. I ve followed this threat as an observer for some time, now im ready for a few questions...
My goal is to use ur appliance and install a few programms and of course save my config (Home).
Ideally id like to write a persistent home to hda1, which is read only.
1. Any chance to change that? i tried to add a "rw" for hda1 into the fstab but im not sure if the change actually survived a reboot.

2. What u said last about putting the ramdisk into tgz: do i only have to change the line in knoppix.sh that loads the vm4xxxx.tgz? And which knoppix.sh should i change, there 2 of them? (one in / and one in boot)

thx for the help
Jeff

Hello,
To respond to a strong request of persistence of data with Knoppix running as a guest under vmware
I had to give it a try ... So please use it at your own risk and provide feedback ...
http://s94002264.onlinehome.us/grub/vmk511_45731p2.zip Knoppix 5.1.1 with persistence
http://s94002264.onlinehome.us/grub/vmk520_45731p2.zip Knoppix 5.2.0 with persistence
http://www.vmware.com/vmtn/appliances/directory/866 (VmWare appliances listing link)
http://www.knoppix.net/forum/viewtop...=113100#113100 (previous vm link)
Have fun (and do not forget to make a clean shutdown since you now have persistence...)
Gilles

MD5 & size of the files:
754a074adbd70b99da9eaec50b1040a3 *Vmk511_45731p2.zip (10'071'232)
cab57232ccd71d566190a8ef0c8b3412 *vmk520_45731p2.zip (9'677'762)

PS: The persistent data (home & config) deltas from the default are now saved in a separate disk hdb1.
Please do not write into hdb1 directly since it is handled by the unionfs and may lead into data corruption.
Just use the system normally: /home/knoppix, /etc, /usr/ /var, ... (but not /media/hdb1 nor /mnt/hdb1)
If for some reason the data on sdb1 gets corrupted, just remove all the files as a super user (su)
(except your valuable data of course) and reboot. Knoppix should rebuild the missing info for you...
Using the built-in precedence of the unionfs (persistent_disk=rw, ramdisk_autodetection=ro, Knoppix_iso=ro),
I tried to leverage the powerfull Knoppix hw autodetection with the persistence of the customisation (done by the user).
BTW, this is something that Klaus may consider even without vmware...

PS2: I updated the Knoppix 5.1.1 & 5.2.0 vm link to the latest update, cf:
http://www.knoppix.net/forum/viewtop...=113174#113174
http://www.knoppix.net/forum/viewtop...=113213#113213

Thx Gilles,

thats a really fast response.
i tried it out and it works real well under vmware 6.
lets see what it all go inside...

Jeff

Hello,
Please find below an other Knoppix 5.1.1 VmWare virtual machine update
with an on/off selection (in grub) of the data & program persistence:
http://s94002264.onlinehome.us/grub/vmk511_45731p2.zip Knoppix 5.1.1
This Rescue mode (persistence off) will allow to run "fsck /dev/sdb2" (as a root)
to clean a persistent partiton not properly unmounted (or after crash).
Have fun and please give me some feedback...
Gilles

PS: I did not update the Knoppix 5.2 vm ... yet.

Hello,
I finally got the time to update the Knoppix 5.2 VmWare virtual machine
with an on/off selection (in grub) of the data & program persistence:
http://s94002264.onlinehome.us/grub/vmk520_45731p2.zip
This Rescue mode (persistence off) will allow to run "fsck /dev/sdb2" (as a root)
to clean a persistent partiton not properly unmounted (or after crash).
Have fun and please give me some feedback...
Gilles

Gilles,

Works great! IBM X40 laptop w/ 1.2 cpu. Very snappy! :D

ksudoku blacked out the screen when I launched it from the menu. Behaves much better from a konsole.

Thanks!

Lachie

hi there,

im encountering one little problem in my workstation6 and ur newest vm.
i have to run the netcardconfig script on each boot, assigning all the parameters like ip, gateway and so on manually. on other vm it connects automatically. on the ifconfig dialog it doesnt show the eth0 until i have run the mentionned script.
i know this is probably not really connected to ur vm but maybe u got an idea...
thx
jeff

Ruymbeke,

I have been using your modified minirt.gz files ever since this thread started in order to do a Knoppix 'Poor Man's Install' on NTFS systems.

I was recently asked whether Damn Small Linux could be started this way. I can get DSL to start from a FAT32 partition but not NTFS, presumably because the minirt24.gz needs altering.

This got me to wondering. We are all totally reliant on you for these updates with each new Knoppix. Have you ever documented what you have altered - or is it closed source?

Of course, I am interested at this minute to see how to change the DSL minrt24.gz. However, I shudder to think that I will not be able to use Knopix this way, should you become indisposed to provide these updates for us in the future.

ICPUG

Quote:

---

Originally Posted by ICPUG

Ruymbeke,
I have been using your modified minirt.gz files ever since this thread started in order to do a Knoppix 'Poor Man's Install' on NTFS systems.
I was recently asked whether Damn Small Linux could be started this way. I can get DSL to start from a FAT32 partition but not NTFS, presumably because the minirt24.gz needs altering.
This got me to wondering. We are all totally reliant on you for these updates with each new Knoppix. Have you ever documented what you have altered - or is it closed source?
Of course, I am interested at this minute to see how to change the DSL minrt24.gz. However, I shudder to think that I will not be able to use Knopix this way, should you become indisposed to provide these updates for us in the future.
ICPUG

---

ICPUG,
First of all, this is not black magic nor close source code, but only inclusion within the minirt boot ramdisk
of kernel modules (already on the cd) and linuxrc boot script edits to add the double loop back from ntfs.
The list of changes is quite long and I would suggest you to use a diff of the linuxrc scripts and a tree comparison between the two minirt.
(This is what I do when working on a new Knoppix release) All the changes are quite obvious when you dig in the bootstrap mechanism.
But the linuxrc boot script is quite hard to read as it is now and would need to be rewritten from scratch since it is a real patch work.
I have asked several times Klaus to include these changes in the official Knoppix release and as far as I know, he is open to consider it.
I do not plan to disappear any time soon and will do my best to provide updates until Klaus includes these changes in his official release.
I worked on these improvements for my own use and since I found them quite useful, I like to share the results with others.
Best regards,
Gilles

Hi,

i use the VMware Server 1.0.3.
The Image for Knoppix 5.2 is only for VMware Workstation V6. :cry:
I can´t find one for the VMware Server.

Is it possible to transfer the Diskimage in the Server Format?,
or can somewhere make a installation in these one? :?:

I think the Configuration must be functional for both Versions
or is there some limitations for working only in VMware Workstation6? :idea:

Thank you

Quote:

---

Originally Posted by Netblitz

i use the VMware Server 1.0.3.
The Image for Knoppix 5.2 is only for VMware Workstation V6. :cry:
I can´t find one for the VMware Server...

---

Here they are for VMWare Server 1.0.3 build 44356: (vm downgraded from workstation 6 to 5)
http://s94002264.onlinehome.us/grub/Vmk511_44356.zip Knoppix 511 vm no data persistence
http://s94002264.onlinehome.us/grub/Vmk511_44356p2.zip Knoppix 511 vm with data persistence
http://s94002264.onlinehome.us/grub/Vmk520_44356.zip Knoppix 520 vm no data persistence
http://s94002264.onlinehome.us/grub/Vmk520_44356p2.zip Knoppix 520 vm with data persistence
Have fun and please let me know if it works for you !
Best Regards,
Gilles

Quote:

---

Originally Posted by ruymbeke

Quote:

---

Originally Posted by Netblitz

i use the VMware Server 1.0.3.
The Image for Knoppix 5.2 is only for VMware Workstation V6. :cry:
I can´t find one for the VMware Server...

---

Here they are for VMWare Server 1.0.3 build 44356: (vm downgraded from workstation 6 to 5)
http://s94002264.onlinehome.us/grub/Vmk511_44356.zip Knoppix 511 vm no data persistence
http://s94002264.onlinehome.us/grub/Vmk511_44356p2.zip Knoppix 511 vm with data persistence
http://s94002264.onlinehome.us/grub/Vmk520_44356.zip Knoppix 520 vm no data persistence
http://s94002264.onlinehome.us/grub/Vmk520_44356p2.zip Knoppix 520 vm with data persistence
Have fun and please let me know if it works for you !
Best Regards,
Gilles

---

Wow, that was a fast answer.....
Thank you. It seems to be running.

But i am a new linux user 8)
First priblem i see is that there is no network.
Vmware is configured properly.

Is it possible, that the network card is designed for vmware 6, and not compatible with the vmware
server version? But this is my first try - I take a look tomorrow and tell you more about my test.

Good Night
netblitz

ruymbeke....

I downloaded your minirt_usb4.gz today, and successfully booted knoppix-4.0.2.iso on a fat32 - awesome!!

Only problem I'm having, is even though I specify lang=us in the batchfile, the desktop is still popping up German. Minor if using the desktop, just change from taskbar. ... But, I also made a runlevel 3 batchfile - but I can't run it - it screws up my keyboard. /mnt/hda1 becomes -mnt-hda1.

Here's my desktop.bat:

Code:

---

@echo off
C:
cd \boot\knoppix
..\grub\loadlin.exe linux initrd=minirt~1.gz ramdisk_size=100000 init=/etc/init bootfrom=/dev/hda1/boot/knoppix/*.iso dma noapm acpi=off noapic pci=bios vga=791 lang=us quiet apm=power-off nomce noprompt

---

Here's my run3.bat:

Code:

---

@echo off
C:
cd \boot\knoppix
..\grub\loadlin.exe linux initrd=minirt~1.gz ramdisk_size=100000 init=/etc/init bootfrom=/dev/hda1/boot/knoppix/*.iso 3 dma noapm acpi=off noapic pci=bios vga=791 lang=us quiet apm=power-off nomce noprompt

---

So then I decided to extract and modify the minirt_usb4.gz:

Code:

---

gunzip minirt_usb4.gz
mkdir todelete
mount minirt_usb4 todelete -t ext2 -o loop

edit the knoppix-autoconfig to default from LANG="de" to LANG="us"

umount todelete
gzip -9 minirt_usb4
rmdir todelete

---

But now, it disabled my mouse (??).

I've successfully modified the minirt.gz when I did my own remaster, but the minirt_usb4.gz is giving me problems.

Any suggestions? Or, is there a version defaulted to English?

Thanks in advance :)

ps:

After trying for 3 days with loadlin, I was extremely impressed with your package!!


cheers :D

got it....

needed to put the lang=us right after the /boot/knoppix/*.iso

I have created a directory called /build to which I want to loopmount your patched minirt.gz file. The following works fine with an unpatched minirt.gz file:
First I ungzip minirt.gz. Then I enter: mount minirt /build -o loop
Then I'm able to see all the files inside and look at linuxrc script.

However, when I do all of the above with your minirt_52.gz ntfs patched file I can't get it to loop mount at all. Is there something special I need to do apart from the above. I've tried adding the extra option -t ext2 since the mount command seems to think its an ntfs image (I think...?). I also tried some of your other patched versions and none of them would loop mount by this method. I must be missing something/ doing something wrong. :-(
Any help would be appreciated because I'd like to play around with linuxrc for my own mods.

Hello,
I just mounted my minirt_511.gz in a ~knoppix/build directory with Knoppix 5.1.1
and I do not see any problem. Cf below or the following link:
http://s94002264.onlinehome.us/grub/loopback511.jpg
Be carefull not to mount the loopback into /build (build directory at the root level)
since the root directory is quite small, it is only 5.8Meg !
Hope this help... and please let me know how this works for you.
Gilles

Quote:

---

knoppix@vm-knoppix511:~$ su
root@vm-knoppix511:/ramdisk/home/knoppix# mkdir build
root@vm-knoppix511:/ramdisk/home/knoppix# gunzip minirt_511.gz
root@vm-knoppix511:/ramdisk/home/knoppix# mount -o loop minirt_511 build
root@vm-knoppix511:/ramdisk/home/knoppix# ls build
KNOPPIX cdrom hosts linuxrc.402 linuxrc.new mnt proc sys
bin dev lib linuxrc.501 linuxrc.old modules sbin tmp
boot etc linuxrc linuxrc.51 media opt static usr
root@vm-knoppix511:/ramdisk/home/knoppix#

---

Quote:

---

Originally Posted by mcewanw

I have created a directory called /build to which I want to loopmount your patched minirt.gz file...
Any help would be appreciated because I'd like to play around with linuxrc for my own mods.

---

Thanks for that. It works fine from Knoppix (I just have a very old Knoppix 3.1), but interestingly it doesn't work from Puppy Linux. In Puppy I was able to loop mount its own minirt*.gz no problem but not your patched Knoppix one (or from the patched minirt from the old japanese version of knoppix). In the latter case I kind of remember some error message about a wrong NTFS signature? Any idea what that could mean? I thought these were all ext2 image files (according to the unix "file" command they are).

Is there some special signature you had to write to the file you had to write to the image file to make it work from ntfs as well as insmod ntfs script code lines (device type or something)?

Ignore my last question. I must have done something daft yesterday. I just tried loop mounting your patched minirt from puppy linux again, and this time it worked fine...!*?!!

Thanks again.

Hello ruymbeke

Great to be able to boot Knoppix from ntfs with your patched minirt.gz. However it is also frustrating that noone seems to have produced a similar thing for the very popular Knoppix-derived Damn Small Linux. I've spent hours today trying to do just that... unsuccessfully :-(
First I ungzipped your minirt52.gz, loop mounted the result, and looked at linuxrc.
Then I did the same with DSL's minirt24.gz and used diff to see the differences.
Based on the side by side diff window I tried copying and pasting what seemed like the relevant parts over from your patched linuxrc to the DSL one. In particular I copied over your versions of the functions: mount_it(); boot_from(); boot_from2(); copy_to(); and loadmodule(). I also copied the line: loadmodule fuse ... and appended ntfs to the BUILTIN_FS line. Finally I reassembled everything into a new minirt24.gz.
But, as I say, it didn't boot - still couldn't find KNOPPIX whatever...
I even tried making a second version by also copying over the modules directory out of your patched minirt...
I didn't manually include any ntfs.o anywhere, so no manual insmod. Fact is, there wasn't any ntfs.o in the modules directory. Is that why this method doesn't work with DSL - is ntfs support compiled into KNOPPIX's kernel but not into DSL's kernel do you think? Or is the lengthy procedure I outlined above simply no good!

I really think it would be great if you could possibly do the same job for DSL you did for Knoppix - perhaps it would be easy for you to do since the linuxrc is very similar inside DSL to the Knoppix one?!

Quote:

---

Originally Posted by gluni

hi there,

im encountering one little problem in my workstation6 and ur newest vm.
i have to run the netcardconfig script on each boot, assigning all the parameters like ip, gateway and so on manually. on other vm it connects automatically. on the ifconfig dialog it doesnt show the eth0 until i have run the mentionned script.
i know this is probably not really connected to ur vm but maybe u got an idea...
thx
jeff

---

I have the same issue and have seen several other posts to that effect here and in http://www.knoppix.net/forum/viewtopic.php?t=25656. It seems to be specific to Knoppix running in VMware. dmesg indicates the card is recognized and configured by DHCP and eth0 brought up, then something happens afterward to take it down. For me, on boot-up, eth0 is configured but down, yet running ifup eth0 tells me it is already up. Attempting to configure the card with DHCP fails. I've searched the forum and don't find an answer, so I am working around it by configuring my network card to a static IP after each boot. Persistence doesn't help this, though my other configuration changes are preserved on next boot. The other thread I referenced suggests that the broadcast setting of 255.255.255.255 is to blame, which makes sense, except that my Debian etch virtual machine also has that broadcase setting and works fine. I'm really liking the ruymbeke virtual machine with persistence (5.1.1) and can live with this, but it would be nice for the network configuration to persist too.

Hi!

I downloaded your "minirt_511.gz" for booting knoppix ON a old aladding V motherboard( acer V72ma MB,amd K6-2 550 CPU, 128M ram), a few seconds of grub(grub did find the knoppix filesysytem and booting ).... The screen went into blank and hang there, couldn't go on booting any more....
while I runing "minirt_511.gz" on other PC no problem of booting at all..

Should I try adding code " vga=0" instead of vga = 799?

any other codes to fix up blank screen at booting?

Quote:

---

Originally Posted by musclemania20079

Hi!
I downloaded your "minirt_511.gz" for booting knoppix ON a old aladding V motherboard( acer V72ma MB,amd K6-2 550 CPU, 128M ram), a few seconds of grub(grub did find the knoppix filesysytem and booting ).... The screen went into blank and hang there, couldn't go on booting any more....
while I runing "minirt_511.gz" on other PC no problem of booting at all..
Should I try adding code " vga=0" instead of vga = 799?
any other codes to fix up blank screen at booting?

---

Hello you may want to try vga=788 or vga=768 as described in this document:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions (under Linux video mode numbers)
Pease let us know if this works for you.
Best Regards,
Gilles

hi!

I tried using 'vga=0 'at "menu.lst" of grub boot,it worked.
--------------------------------------------------
title Knoppix511 from hda7 ISO cloop scan

kernel (hd0,6)/boot/knoppix.402/linux ramdisk_size=100000 init=/etc/init nomce lang=us vga=0 noprompt apm=power-off fromhd=/dev/hda7 knoppix_dir=/boot/knoppix.402 knoppix_name=KNOPPIX
initrd (hd0,6)/boot/knoppix.402/minirt_511.gz
--------------------------------------------------

Now I can get rid of blank screen at booting on acer V72ma Motherborad,but the booting stalled at
"..check if image is initramfs...it isn't (bad gzip magic numbers),looks like a initrd"

what should I do next to boot into knoppix 511 normally?

Quote:

---

Originally Posted by musclemania20079

hi!
I tried using 'vga=0 'at "menu.lst" of grub boot,it worked.
--------------------------------------------------
title Knoppix511 from hda7 ISO cloop scan
kernel (hd0,6)/boot/knoppix.402/linux ramdisk_size=100000 init=/etc/init nomce lang=us vga=0 noprompt apm=power-off fromhd=/dev/hda7 knoppix_dir=/boot/knoppix.402 knoppix_name=KNOPPIX
initrd (hd0,6)/boot/knoppix.402/minirt_511.gz
--------------------------------------------------
Now I can get rid of blank screen at booting on acer V72ma Motherborad,but the booting stalled at
"..check if image is initramfs...it isn't (bad gzip magic numbers),looks like a initrd"
what should I do next to boot into knoppix 511 normally?

---

Hello,
Greetings from France and Switzerland.
I assume that you have overwritten the Knoppix 4.02 files with the Knoppix 5.11 files.
(you are still using a knoppix.402 directory, and obviously you cannot mix versions of Knoppix)
Anyway, does your system boot properly with a Knoppix cdrom ?
If if doesn't, most likely the boot from the iso will behave the same way and will not work.
Since the iso boot works on all the system I got the chance to try and I do not have a system like yours,
I don't really know how to investigate. This may be a limitation from Knoppix not my iso boot customization.
Did you verify the integrity of the iso file, or did you try kernel cheatcodes as decribed in the knoppix-cheatcodes.txt file:
knoppix noagp noaudio noapm noapic acpi=off nodma nopcmcia noscsi nousb, ...
Please share your findings with everybody.
Hope this helps,
Gilles

Here: http://www.knoppix.net/forum/viewtop...=110555#110555

Quote:

---

Originally Posted by ruymbeke

Hello,
If updated the linuxrc to use fusermount -uz /cdrom (and not umount /cdrom) in order to not mess up
the /etc/mtab. The partition hosting the iso file is now mounted properly in /media with a link to /mnt
and is now accessible from KDE. But I still cannot make it writable from kde nor from a su shell.
As a dirty work around I added two kernel cheatcodes: ntfs_rw & linuxrc_exit=...
in order to boot with the partition holding the iso file as writable (ntfs_rw) and
run any program before exiting the linuxrc for debug purpose (linuxrc_exit=/static/bash)
Please find below a link to this updated alpha test version of minirt:
http://s94002264.onlinehome.us/grub/minirt_511a.gz
FYI, ntfs-3g -o remount is not supported yet, but if the ntfs partition is not used to boot
mount -o remount works just fine... Any help to investigate why the ntfs-3g driver behaves differently
for the mount/umount and prevent to write in the iso boot partition will be greatly apretiated.
Best Regards,
Gilles

---

Well Gilles,
The cheatcode ntfs_rw worked for me. The boot drive has the knoppix.iso, which is also ntfs format... and was always stuck on read only. I copied about 15 files in a knoppix subdirectory over to the windows side. All using an iso image. No extracting KNOPPIX and KNOPPIX2 or anything. Funny I had a problem using the minirt_511.gz. I had to get the "a" version. http://www.knoppix.net/forum/viewtop...=110240#110240 didn't mention it... just the 511 version.
Thanks Gilles.

John Woods

Hello,
Can someone please help. I am trying to get an ISO of a Knoppix 5.11 CD working for a poor man's install in a similar way that I have 3.7 working. My setup with Win2K SP4 on NTFS is as follows:-

C:\
- grldr (from grub4dos-0.4.3)
- boot.ini

Code:

---

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
c:\grldr="Start Grub"

---

- menu.lst

Code:

---

        timeout=30
        default=0

title Windows 2000
        rootnoverify (hd0,0)
        chainloader +1
        boot

title Knoppix 3.7 kernel 2.6 from NTFS hda1 ISO scan ramdisk=32MB
        kernel (hd0,0)/boot/knoppix.37/linux26 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.37/*.iso config=scan home=scan ramdisk=32768 noprompt
        initrd (hd0,0)/boot/knoppix.37/minirt26_ntfs.gz
        boot

title Knoppix 5.11
        kernel (hd0,0)/boot/knoppix.511/linux ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.511/*.iso config=scan home=scan ramdisk=32768 noprompt
        initrd (hd0,0)/boot/knoppix.511/minirt_511.gz
        boot

---

- C:\BOOT\Knoppix.37 directory contains the following files

Code:

---

k37.iso
linux24
linux26
memtest
minirt24_ntfs.gz
minirt26_ntfs.gz

---

- C:\BOOT\Knoppix.511 directory contains the following files

Code:

---

KNOPPIX_V5.1.1CD-2007-01-04-EN.iso
linux (extracted from the above iso)
minirt_511.gz

---

The 3.7 boots fine. With 5.11, although it looks good initially, I get the error:

Code:

---

/dev/hda1/boot/knoppix.511/*.iso: ISO not found, search for alternate locations:
Use of this ISO: /dev/hda1/boot/knoppix.511/*.iso
Can't find KNOPPIX filesystem, sorry.

---

something briefly flashes up about /dev/hda1/boot/knoppix.511/*.iso
being unmountable and then it drops me into a very limited shell.

Any constructive comments welcome.
Hal.

Well it looks like you have used a Knoppix.511, in the directory name... and specified a knoppix.511 in all your menu.lst stuff.
Try renaming your Knoppix.511 to knoppix.511 and see.

Windows may not see any difference if you cd to C:\Boot (which should also be lowercase according to your menu.lst) and try and:
ren Knoppix.511 knoppix.511 in a dos box, and do nothing. I have usually used an intermediate name and never had a problem when doing it that way.

cd C:\Boot
ren Knoppix.511 tempdir
ren tempdir knoppix.511

Or you could adjust your menu.lst to be a case sensitive match to your directory names.
Secondly... try using a full name to specify your iso filename. I always rename them to something simple like knoppix.iso.

Hello,
Please find below the link to my first shoot at an updated Knoppix 5.3.1 minirt supporting ISO boot from ntfs, fat, ext, reiser,...
http://s94002264.onlinehome.us/grub/knx531.zip (Md5: 5516434f6c74b3fd3f7cb941de6edd47 *knx531.zip )
For your convenience, the zip file includes: grldr, grub.exe, menu.lst, linux (kernel) and minirt_531.gz.
Please note that as requested by John Woods, I also included the "ntfs_rw" kernel cheatcode
(besides all the previously added cheatcodes as hostname=[mycustomname|auto-clock|auto-mac], ...)
FYI, this is the grub menu.lst config file I used:

Code:

---

title Knoppix 5.3.1 from sda1 ISO
        kernel (hd0,0)/boot/knoppix.531/linux ramdisk_size=100000 init=/etc/init bootfrom=/dev/hda1/boot/knoppix.531/*.iso vga=791 noprompt apm=power-off nomce quiet lang=us dma screen=1024x768 hostname=knx531 highres=off loglevel=0 libata.atapi_enabled=1 SELINUX_INIT=NO nmi_watchdog=0 ntfs_rw
        initrd (hd0,0)/boot/knoppix.531/minirt_531.gz
        boot

---

Have fun and please provide some feedback !
Best Regards,
Gilles

PS: It looks like that the VmWare Tools 6.0.3 (build 80004) do not install properly on the Knoppix 5.3.1 kernel 2.6.24.4 (help would be apreciated)

Gilles,

Your miniroots... well I just can't do without them. They have become indispensible.

This one... Works for me!
(Now maybe I can have a look at Knoppix 5.3.1 and see what's new.)

I have my iso as /dev/hdb9/Knoppix-5.3.1/Knoppix.iso ... and it found it.
That would be an ext3 partition... I'll test my ntfs later as I have to move some around.
Since I've stopped using Windows nowadays... I have less need for ntfs partitions.

Thank You.

Hello,

I have used your system to boot the Knoppix 5.1.1 ISO from a hard drive via GRUB4Win (thanks!!), but I'd now like to also boot it from a USB key that already boots via Syslinux. (I setup the key to boot UBCD4Win using someone else's Syslinux config files; I'm a Syslinux newbie.)

I thought it should be simple enough to copy the linux, minirt_511a.gz and Knoppix ISO to /knoppix.511, and convert my HDD version of your GRUB boot config:

Code:

---

title Knoppix 5.1.1 from hda7 ISO
        kernel (hd0,0)/boot/knoppix.511/linux ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 ntfs_rw nomce quiet bootfrom=/dev/hda7/ISO/knoppix.511/*.iso config=scan home=scan ramdisk=32768 noprompt noaudio
        initrd (hd0,0)/boot/knoppix.511/minirt_511a.gz
        boot

---

to what I think should be the equivalent Syslinux config on the USB (looking at the other existing Syslinux boot entries), by changing all the path references and reversing the KERNEL (but not cheatcode) slashes:

Code:

---

LABEL KNOPPIX
  MENU LABEL Launch Knoppix 5.11a
  KERNEL \knoppix.511\linux ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 ntfs_rw nomce quiet bootfrom=/knoppix.511/*.iso config=scan home=scan ramdisk=32768 noprompt noaudio
  APPEND initrd=/knoppix.511/minirt_511a.gz

---

However, when I boot from the key and select the Knoppix entry, it says it's booting from /knoppix.511/linux, but then says

Code:

---

Could not find kernel image /knoppix.511/minirt_511a.gz

---

I tried reversing the slashes to "\" (since the other boot menu entries use backslashes) but get the same result.

Can someone explain what I'm missing here? Thanks!

I just noticed... this thread has over 400,000 views... wow.
First, I would take the backslashes out.

Syslinux seems to be booting... so if you edit syslinux.cfg using a good editor that will preserve your line endings (kwrite is good enough) and
use mine you will be almost there. I formatted my 8GB thumbdrive with a small FAT partition, and then the rest as ext3. Why ext3? Windows XP...
in it's infinite wisdom decided to allow only one partition on removable media. It refused to recognize the second partition properly. As an ext3 partition, it ignores it... at least.

The small FAT partition holds the minirt and kernel and the files from the /boot/isolinux directory in the root directory. I have a knoppix.img(persistent $home file) in sda2 as well as the tohd KNOPPIX/KNOPPIX files. The ntfs_rw cheatcode is Gilles' solution to having a home on the same drive as a KNOPPIX/KNOPPIX tohd installation. Without that cheatcode... you would need to make another partition for your knoppix.img file. Up to you.

Quote:

---

DEFAULT linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=mini511a.gz nomce dma noeject loglevel=0 quiet ntfs_rw home=/media/sda2/knoppix.img myconfig=/media/sda2 BOOT_IMAGE=knoppix 2
TIMEOUT 300
PROMPT 1
DISPLAY boot.msg
F1 boot.msg
F2 f2
F3 f3
LABEL knoppix
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt.gz nomce noeject loglevel=0 quiet home=scan myconfig=scan BOOT_IMAGE=knoppix 2
LABEL expert
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt.gz nomce BOOT_IMAGE=expert 2
LABEL memtest
KERNEL memtest
APPEND foo
LABEL knoppix-txt
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=normal initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix 2
LABEL debug
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=normal initrd=minirt.gz debug BOOT_IMAGE=debug 2
LABEL fb1280x1024
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=794 xmodule=fbdev initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix 2
LABEL fb1024x768
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 xmodule=fbdev initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix 2
LABEL fb800x600
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=788 xmodule=fbdev initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix 2
LABEL dos
KERNEL balder.img
LABEL failsafe
KERNEL linux
APPEND ramdisk_size=100000 init=/etc/init lang=us vga=normal atapicd nosound noapic noacpi pnpbios=off acpi=off nofstab noscsi nodma noapm nousb nopcmcia nofirewire noagp nomce nodhcp xmodule=vesa initrd=minirt.gz BOOT_IMAGE=knoppix 2
LABEL userdef
KERNEL linux
APPEND ################################################## ################################################## ################################################## ################################################## ################################################## ################################################## ################################################## ################################################## ################################################## ################################################## ###########

---

Hello,
Why do you want to use isolinux to boot from your usb dongle when grub could do it so much better ?
cf: http://www.knoppix.net/forum/viewtop...?p=93758#93758
As an example, the "e" command allow you to modify your boot parameter temporarely but on the fly, which is very usefull for debug !
The "c" command allow to enter the shell interactive mode and test for a new boot without even modifying the config file
and with auto-completion (by pressing tab). Grub can read data from multiple partition types and even
from the network (pxe) if compiled with network support. Grub is a great boot loader...

Why use KNOPPIX/KNOPPIX when you could use the iso file directly and have it ready for a friend to try Linux
by burning that same iso to a CD/DVD without duplicating data.

The ntfs_rw cheatcode is required only for ntfs partitions which cannot be re-mounted on the fly as a writable media
because ntfs-3g doesn't support remount yet. Other boot partition types (fat, ext, reiser) can use the command
mount -o rw,remount ... to write data to the boot partition (containing the iso file)

FYI, I have a multi boot configuartion on my USB dongle (formatted fat32) from which I can boot multiple OS and tools as:
various flavors of knoppix, memtest86, ghost (with dos network support), acronis echo & dd and Linux network installers
for OpenSuse, Mandrake, Ubuntu, ...
Best Regards,
Gilles