Knoppix 5.1.1

It was also possible to set up a "persistent home directory", where any documents or settings written to the user's home directory would automatically be redirected to a hard drive or removable media, which could be automatically mounted on bootup. A single file, knoppix.img, was cached on the rewritable media and used to simulate a file system into which files were written for later use. This allowed the user to transparently write to their home directory.

knoppix 5.1.1

Download Zip: https://www.google.com/url?q=https%3A%2F%2Furlcod.com%2F2u3EiE&sa=D&sntz=1&usg=AOvVaw1Q_qTS_mszymRryRTmI3UO

This functionality was only available through Knoppix 5.1.1 (CD release) or 5.3.1 (DVD release). Subsequently, the Live CD paradigm has transformed into portable operating systems that run on external storage.

Knoppix is a 32-bit Debian Linux based distro, but recent releases (including the latest version 7.6) have also been equipped with a 64-bit kernel on the DVD edition, where it will automatically boot up for 64-bit computers, or by using the boot option knoppix64 manually in the command-line prompt, while knoppix will boot up the 32-bit kernel. Neither PAE nor 64-bit applications are supported by Knoppix, and more than 4GB of system memory can only be used with a 64-bit kernel.

The DVD edition of Knoppix can also be loaded onto a USB flash drive, with flash-knoppix under the Knoppix system, such that "the KNOPPIX Live System starts and runs about factor 5 faster from USB flash disk than from CD or DVD!".[9] Besides that, the experimental UEFI support is provided for USB flash drive rather than DVD media. 32-bit UEFI firmware can only boot up the 32-bit kernel, while 64-bit UEFI firmware can only boot up the 64-bit kernel. The text interface for UEFI is similar with it for BIOS, one can also press key F2 and F3 to access information on boot options.

Web site: wiki.openvz.orgOrigin: Category: VirtualizationDesktop environment: KDEArchitecture: x86Based on: KnoppixWikipedia: Media: Live CDThe last version Released: 5.1.1 January 4, 2007

This book includes a copy of Knoppix 5.1.1 DVD from 2007-01-04 (KNOPPIX_V5.1.1DVD-2007-01-04-EN), which was the last release in the 5.1 series. All of the hacks have been tested and written in terms of this release, but most hacks should work fine across newer releases.

If you are unsure which device name to use, simply boot Knoppix from the CD and make note of the names on the hard-drive icons on your desktop. You can use any one of these devices that has enough available space. As with the toram cheat code, tohd requires you to have over 700 MB free on your partition for the CD, and over 4.4 GB free for the DVD. Knoppix copies its disk image into a directory called knoppix at the root of the partition that you specify.

One advantage to using the tohd cheat code is that the knoppix directory it copies is not deleted when you reboot. In subsequent boots, you can reference the already copied image by using the fromhd cheat code. So, if you have previously used the cheat code tohd=/dev/hda1 on a computer, type this command to use the same image again:

Just as you can tell Knoppix to run X directly through the framebuffer with the xmodule=fbdev cheat code, you can tell the Linux console to run through the framebuffer by passing fb along with the resolution you want to use. The fb cheat code is a bit different from most of the cheat codes in that it actually is specifying a special set of predefined kernel parameters to run the console specific resolution. To boot Knoppix into a 1280 by 1024 framebuffer console, type fb1280x1024 (not knoppix fb1280x1024).

EXE problems with Mke2fs.exe most often stem from a corrupt or missing executable file, which often occur duing the startup of Knoppix 5.1.1. Obtaining a new, uninfected copy of your EXE file will usually resolve the problem. Additionally, some Mke2fs.exe errors can be due to incorrect registry references, so we recommend conducting a registry scan to clean up any invalid entries.

Getting the Mke2fs.exe file location correct is critical in making sure these errors are resolved successfully, so it doesn't hurt to check to make sure. You can then re-open Knoppix 5.1.1 to see if the error message is still triggered.

Usually Mke2fs.exe errors with Knoppix 5.1.1 happen during startup or shutdown, while Mke2fs.exe related programs are running, or rarely during the OS update sequence. It's important to note when Mke2fs.exe issues happen, as it helps troubleshoot Knoppix 5.1.1 problems (and report to Linux Magazine).

Update 2007.11.30: With Knoppix 5.1.1 the built-in NTFS tools seem robust so I didn't need to add that capability. The chntpw Windows registry tool was added via apt-get from the Debian repository so it gets included in the base system and doesn't need a convenience wrapper. Given that, I didn't need to modify the KDE menus. I _did_ add some bootable floppy images to the isolinux menu - external to the Knoppix build - that got included in the final CD image. They were all hard drive diagnosis, repair, and parititioning tools.

I'm not going to go into all the details of the remastering process here. I pretty much followed the instructions detailed at www.knoppix.net/wiki/Knoppix_Remastering_Howto to the letter, and incorporated some of the suggestions at www.knoppix.net/wiki/Remastering_Hacks.

Update 2007.11.30: for the 5.1.1 version I followed the HOWTO and HACKS guides exactly, and other than adding the chntpw package and customizing some graphics I didn't do anything else _internal_ to Knoppix.

Update 2007.11.30: for 5.1.1 I didn't bother with the above additions. I added chntpw via apt-get, and the firewall fiddling isn't necessary after starting the ssh server from the standard Knoppix menu. Captive NTFS isn't needed any more either - the stock tools work well.

NOTE: the tools, scipts, and links are "inside" the compressed filesystem. They get added to the "source" in uncompressed form and included in the final compressed filesystem. The documentation (in this first go-around) is both inside and outside. One copy went to the "source" in /opt/beezix/docs, and one to the "master" in /knoppix. In the next version, the docs won't be duplicated. Docs useful at boot/browse time will be outside the filesystem and those more appropriate to a running systsem will be "inside" at /opt/beezix/docs.

Update 2007.11.30: for 5.1.1 I just put my doc files in /beezix/docs and didn't fiddle the KDE menus. They are linked from the opening index.html file or accessed directly with the running file browser.

Also in the root is index.html. This is used to "autorun" when the CD or fob is mounted or booted. In Knoppix it brings up a splash image and links to the main html file in several languages. I modified the splash (/KNOPPIX/images/knoppix-header.png) to use a picture of my wife swimming with an octopus and trimmed index.html down to just link to my (English) main html file.

The main html file is /KNOPPIX/index_en.html. My version adds a "BEEZIX" introduction, a description of my modifications and additions, links to the captive-ntfs chntpw sites, and links to my documentation to the "stock" Knoppix index_en.html. I modified the background image (/KNOPPIX/images/knoppix-24-1.jpg) to use the wife + octopus photo.

Update 2007.11.30: for the 5.1.1 version I added some bootable floppy images that can be selected from the isolinux boot menu. They get listed by the option at boot time. Editing the menu can be a challenge. Here are my boot.msg, isolinux.cfg, and menu, and here's a useful tool for editing it: Isolinux Mate. Also fixed a but that kept DOS from booting. See below.

To move the customizations into my "source". It is necessary to edit a script in the "source" to get the customizations to load correctly when the new remaster is booted. From "Lorenzo" posting at the knoppix.net forum, edit:

Update 2007.11.30: with the 5.1.1 version I didn't change the KDE menus since I hadn't really modified the internals of the Knoppix setup other than removing and adding packages. I didn't have to deal with the above. Nice.

Important Note: For reasons unknown, the smartctl utility is not included in the newest version of Knoppix 6.0.1. For this reason, it is necessary to use Knoppix 5.3.1 DVD or Knoppix 5.1.1 CD/DVD.

A breath of new life has come to an old but faithful Linux distribution, Knoppix. Version 5.1.1 was released in January 2007 and 2 years later no further activity convinced me that Knoppix was a dead project, maybe Klaus Knopper had other things to occupy his time.

First, get a Knoppix disk. I use a Knoppix 5.1.1 CD for this example, but I've been successful with much older Knoppix CDs. Mount the CD-ROM, andthen go to the boot/isolinux directory on the CD. Copy the miniroot.gz andvmlinuz files to your /var/lib/tftpboot directory, except rename themsomething distinct, such as miniroot-knx5.1.1.gz and vmlinuz-knx5.1.1,respectively. Now, edit your pxelinux.cfg/default file, and add lines likethe one I used above in my example:

Notice here that I labeled it 1, so if you already have a label with thatname, you need to decide which of the two to rename. Also notice thatthis example references the renamed vmlinuz-knx5.1.1 andminiroot-knx5.1.1.gz files. If you named your files something else, besure to change the names here as well. Because I am mostly dealing withservers, I added 2 after init=/etc/init on the append line, so it would bootinto runlevel 2 (console-only mode). If you want to boot to a fullgraphical environment, remove 2 from the append line.

The final step might be the largest for you if you don't have an NFS serverset up. For Knoppix to boot over the network, you have to have its CDcontents shared on an NFS server. NFS server configuration is beyond thescope of this article, but in my example, I set up an NFS share on 10.0.0.1at /mnt/knoppix/5.1.1. I then mounted my Knoppix CD and copied the fullcontents to that directory. Alternatively, you could mount a Knoppix CDor ISO directly to that directory. When the Knoppix kernel boots, it willthen mount that NFS share and access the rest of the files it needsdirectly over the network.