Yes this is the same one:
http://source.rfc822.org/pub/mirror/...-cebit-rip.iso
Printable View
Yes this is the same one:
http://source.rfc822.org/pub/mirror/...-cebit-rip.iso
Can this app also allow text edits in existing .bat and scripting files within an ISO and then save the results as a bootable ISO image when you're done?Quote:
Originally Posted by MichielioZ
Yes it can, but you can't do it "on-the-fly", you'll have to extract the script/file and edit it outside the ISO.. later you can reinsert the new file and let it replace the original.Quote:
Originally Posted by audioaficionado
Easiest way to use it for me though, was to just extract the entire ISO into a KNOPPIX folder on HDD and boot from a CD with the boot.img on it.
This way you can test the Knoppix ISO and even install to HDD from it...
Hope anybody found this info helpfull... 8)
Downloaded the BitTorrent iso, burned the CD, did the hard drive install, and I'm now posting this from my working linux installation.
Looks and works great! Thanks to all those who sacrificed some bandwidth to share the .iso!
Here's an ISO I am hosting on my website. It's the default German language. enjoy!
http://mienh.com/modules.php?name=Do...op=getit&lid=1
great. got it @ 90kbps. :)
still, boots up in 640x480 on my laptop, even if i start it with 'knoppix lang=us fb1024x786'
and still it wont detect my intel wlan card. :(
Here's my update:
At first I couldn't even boot into knx3.2, the default Xserver didn't work, default lang was DE and no wheel mouse :(
So I just hit F2 and typed in a long list of cheats to get me to where I wanted to go.
After I spent a few hours tweaking Knoppix I went to the 'K-menu/Knoppix/Configure/Save Knoppix Configurations. Well I clicked the button and chose save eveything to one of my spare HD partitions :wink:
Now when booting I just hit F2 and then type 'knoppix myconf=scan' and it all comes back except my imported wallpaper. I just remount the partition it's on and then get it back. It's still pathed in the desktop wallpaper menu as a choice but it couldn't load durring boot because the partitions don't auto mount.
I can't get the screensaver or my cups printer drivers to work yet. That's for tomorrow :lol:
Hi I've got it from my friend which was on CeBIT :D.
But I'll rather wait for official release, because I preffer EN version
and this one from CeBIT has by default german keyboard layout probably :?
Does somebody know if Klaus plan to add into official release some of
last days serious security updates (like samba, OpenSSL with patch against time sidechannel attack ...)? Is Klaus reading this news thread?
If so, hi, I am one of your fans! 8)
Really cool distribution, still playing with that and investigating. What I miss is some user-friendly VPN configurator ... because I am not a VPN guru :( - or maybe I'll try to run some VPN client from my Win installation through wine, but I dont believe it will work ... Or somebody already tried ?
cu, seth
BTW: When trying air-snort - I don't have wi-fi card - I am able freez Knoppix completelly via some menu actions ....
I have downloaded Knoppix 3.2 from http://source.rfc822.org/pub/mirror/...-cebit-rip.iso. I guess I have been having this problem with the releases after the November release. The problem is that after initial boot and hardware detection the X server never starts and the screen goes blank no error messages nothing. Reboot is needed to get out of this. I have a ATI Rage 128 32Mb video card. I'nm wondering if anyone has had this problem. Is there any cheat code that I can enter to solve this? Any help appreciated.
Thank you,
mag
:(
hi, this is the md5 for the iso I have just downloadedQuote:
Originally Posted by audioaficionado
5ab8f8e1900cf20f4e667f7c17f4e976 *drivers/knoppix-3.2-cebit-rip.iso
anybody may confirm it?
thanks
I had the same problem. Re-read the earlier posts on this thread as the answer has already been posted by me and others.Quote:
I have downloaded Knoppix 3.2 from http://source.rfc822.org/pub/mirror/...-cebit-rip.iso. I guess I have been having this problem with the releases after the November release. The problem is that after initial boot and hardware detection the X server never starts and the screen goes blank no error messages nothing. Reboot is needed to get out of this. I have a ATI Rage 128 32Mb video card. I'nm wondering if anyone has had this problem. Is there any cheat code that I can enter to solve this? Any help appreciated.
Thank you,
mag
Just run an md5 checksum utility on your ISO and compare it to the one posted at the mirror. They have to match exactly or some file corruption may have occured.Quote:
Originally Posted by oscar
Would you please tell me what cheatcodes you exactly entered to make it work? I appreciate your help.
Thank you,
mag
Quote:
Quote:
Originally Posted by audioaficionado
Also...Quote:
Originally Posted by audioaficionado
It's got English support but the default is German of course because Klaus is German. I'm in English mode now and it works great.
When you first boot it up hit F2 to get to the cheat codes. Then just type in 'knoppix lang=us' You'll have to use 'shift+0' to get an '=' due to that's where the Germans have it on their keyboards.
If you have a wheel mouse then type 'wheelmouse' after the first cheat code you entered. You only have to type knoppix once in front of all the other arguments/commands and then separate them with one space. If you have a problem with the default Xserver like I did, you just select another one from the cheat codes menu. I went with XFree86 and all went well.
Once you've gotten into knoppix and tweaked it for awhile, go to the K-menu/Knoppix/Configure/Save Knoppix configuration and click the buttons and save your configurations to a spare area of your HD.
Next boot hit F2 and just type in 'knoppix myconfig=scan' and it all will come back. This is very close to a HD install exept it's not installed to the HD. The only thing that goes on your HD is a ~10Mb config file and whatever size swap file you've configured through the same menu tree you use to setup the Persistant Home configuration files.
Note: You can just enter that master config cheat right from the first boot screen and not even bother with the F2 screen if you've memorized the codes.
Quote:
Originally Posted by audioaficionado
...thanks, the above md5 cheksum is the one calculated on my iso and is equal to the one posted at the mirror, the obvious first place to look into :oops:
I ran the hd install and now LILO is screwed up, how can i edit the file from the cd based distro once booted up? I run it but it wont let me save I guess i need to enable write ability for that hda7? If so how do I go about doing that? I would really love to get into this distro :D, instead of using the boot cd
Right click on your HD where Knoppix was installed, mount and then set it for read/write.Quote:
Originally Posted by LinuxIdiot
Open up a console and su to be root. ./vim or other text editor within the console.
(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.
Is there a linux version of WinISO? :?:
Thanks in advance for the help,
paul 8)
After you edit and save lilo.conf run /sbin/lilo to commit the changes then re-boot.Quote:
(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.
Quick question, how would i edit the iso to include my default settings? Such as 1024x768 wheelmouse stuff like that?
Oops! I should have been more specific than 'give it a whirl' :oops:Quote:
Originally Posted by Stephen
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.Quote:
Originally Posted by audioaficionado
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
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
laurentbon : please read the releasenotes from Klaus... 8)
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..
Douggghhhh!!!
That would explain a lot...
A shame for gnome... Have to wait for V3.3 then...
Thanks for the instructions Rock, I will give this a whirl when i get home.Quote:
Originally Posted by RockMumbles
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 :roll:
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.
I can not get it to save if i type
it opens i edit then in the shell console i get this errorQuote:
sudo kedit /mnt/hda7/etc/lilo.conf
here is a copy of my LILOQuote:
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) \x08
Major opcode: *
Question: If my windows partition is on hda1 and linux is on hda7 will i just need to change this one part?Quote:
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/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(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.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)"
To:Quote:
# 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
Quote:
# 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
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
Audioaficionado,
How did you configure grub to boot?
paul 8)
I kinda cheated and had Libranet install it by default. However GRUB has persisted on the MBR throughout two windows 2000 installs, complete formate/resinstall of Libernet and the apt-get conversion of Libranet to Debian testing.Quote:
Originally Posted by qa1433
If you have a linux system running, how helpful was 'man grub'?
I didn't install it but once you open the text config file (as root) you can see many commented lines about how to configure it. The only thing I did was to insert the example windows chain loader by cut and pasting it in front of the kernal loads without the # commenters.
Kool!
I am not strong at heart. Linux kind of scares me. I to use Libranet Grub installed when I bought 2.7 I need to give it a whirl. If I break it I can always re-install :cry:
Thanks for the help!
paul 8)