Today K Knopper has puplished the new DVD version of Knoppix.
http://torrent.unix-ag.uni-kl.de/
http://www.knopper.net/knoppix-mirrors/
Printable View
Today K Knopper has puplished the new DVD version of Knoppix.
http://torrent.unix-ag.uni-kl.de/
http://www.knopper.net/knoppix-mirrors/
Having trouble finding an English version of the 7.41 release notes. Anyone got a link?
Despite the link's name, this might be it, actually.Quote:
Originally Posted by Harry Kuhman
Read the given material before you think otherwise.
http://www.knopper.net/knoppix/knoppix740-en.html
yup, English. Thanks.
FWIW
1. This link is probably an edit of a former page for Knoppix 7.4.0,
and may get re-named.
2. I think all the major programs Compiz thru PCManFM listed or 7.4.1
are the same versions as in 7.4.0.
3. It may be hard to tell what's different between 7.4.0 and 7.4.1,
from this page.
You can see the differences (done by kn-what.sh)
for DVD V7.2.0 versus V7.4.1
for DVD V7.4.0 versus V7.4.1
and an overview of packages maintained by K Knopper
Greetings, Werner.Quote:
Originally Posted by Werner P. Schulz
I am impressed at the completeness of your kn-what comparisons,
but it is hard to imagine that most of the small version differences
represent any significant consequencial differences. I must admit
I am not familiar with Knoppix's Adriane features.
I am also surprised that I can't find either more or some knoppix-specific
changes like for example Install-to-flash-disk, which I thought might be
the motivation for a Knoppix version change.
I now wonder if this version change might have been motivated more
by Adriane-specific modifications.
I don't see yet if there is a reason for me to upgrade from 7.4.0 to 7.4.1
since I don't know what of real consequence is different. A few words in
the release material would have been a great help in that regard.
I also suppose, this has been the motivation of KK and perhaps he will not offer a special CD version in the future.Quote:
I now wonder if this version change might have been motivated more by Adriane-specific modifications.
The script "flash-knoppix" is in a new version within 7.4.1; it isn't in the difference list because it's not a .deb file. You can copy it from the mailing list. I've seen this message in my email account with Icedove and there was this script within the email text and also as an addendum. I've tested the script of the addendum and this doesn't worked for me (see my message in the mailing list).
With the new version of the script I can still not do a flash disk install with the option "overlay image" by the usual way; it seems to be a udev problem. But strangely enough, the new option "add the name of the .iso file as commandline parameter" (=> Computers without DVD drive) can also handle with the option "overlay image".
For clarification, flash-knoppix in 7.4.1 and that given in the mailing list are different.Quote:
Originally Posted by Werner P. Schulz
The original has 721 lines vs the mailing list's 769.
The mailing list version was/is in response to some complaints about the original in 7.4.1.
I think Klaus K must consider laptop configurations without dvds pretty important.
Please disregard the previous.Quote:
Originally Posted by utu
I was interested in if there is a difference between flash-knoppix in 7.4.1 and that given in the mailing list.
I know flash knoppix in 7.4.0 has 721 lines and that in the mailing list has 769.
I don't know if the mailing llist represents 7.4.1 or a variation thereof.
The script posted in the mailing list is equal to this within V7.4.1 (checked by md5sum).
.
This new Distrowatch paragraph gives slightly more info about 7.4.1,
indluding a new, undefined, mkimage boot cheatcode:
http://distrowatch.com/?newsid=08603
Quote:
Originally Posted by utu
http://www.knopper.net/knoppix/knoppix741-en.html
Interesting. I'd like to try the "knoppix mkimage" option. I wonder if I can just extract the .iso and copy over the KNOPPIX file to update the distribution or do I have to remaster the whole thing from scratch? I am using a usb install.
My error in calling this news in post #12. I didn't pick up on 'mkimage'Quote:
Originally Posted by utu
until I went back to re-read the earlier 'release notes' and found the term
there. The ten-minute forum limit on editing posted material preserved my
error for posterity. My bad.
I can understand using something called 'mkimage' to transform a read/write
persistence file to a compact read/only cloop file. I do that myself;
but, I don't see how this would be useful as a (boot) cheatcode.
I hope mkimage is a bash script, and if so, I hope someone will post it here
so we can study it. IMO, I think it would be even better if our fearless leader, KK,
would document some of his inventions a little (or a lot) better.
Quote:
I hope mkimage is a bash script, and if so, I hope someone will post it here
so we can study it.
If you compare the new part of the init script with this old part (up to V7.4.0)Code:mountdata(){
local img base ext m mods found=""
for base in $home /mnt-system/"$knoppix_dir"/knoppix-data /mnt-system/knoppix; do
for ext in aes img inf; do
img="$base.$ext"
[ -r "$img" ] || continue
[ -b /dev/loop0 ] || mknod -m 755 /dev/loop0 b 7 0
[ -d /KNOPPIX-DATA ] || mkdir -m 755 /KNOPPIX-DATA
[ -d /dev/mapper ] || mkdir -m 755 /dev/mapper
found="true"
case "$ext" in
aes)
mountaes "$img" /KNOPPIX-DATA ext2 && return 0
;;
img)
checkfs "$img" ext2
message -e "\r${CRE}${GREEN}${USING} ${YELLOW}$img${NORMAL}"
mount -t ext2 -o loop,rw "$img" /KNOPPIX-DATA && return 0
losetup -d /dev/loop0 >/dev/null 2>&1
;;
inf) # Contains partition information in fstab format
local part="" mp="" fs="" opts=""
while read part mp fs opts; do
[ -n "$part" ] || continue
case "$mp" in *[Hh][Oo][Mm][Ee]) mp="/KNOPPIX-DATA" ;; esac
case "$opts" in
*aes*) mountaes "${ROOTDEV%[0-9]*}${part#/dev/}" "${mp:-/KNOPPIX-DATA}" "${fs:-ext2}" && return 0 ;;
*) checkfs "${ROOTDEV%[0-9]*}${part#/dev/}" "$fs"
message -e "\r${CRE}${GREEN}${USING} ${YELLOW}${ROOTDEV%[0-9]*}${part#/dev/}${NORMAL}"
mount -t "${fs:-ext2}" "${ROOTDEV%[0-9]*}${part#/dev/}" "${mp:-/KNOPPIX-DATA}" && return 0 ;;
esac
done <"$img"
;;
esac
done
done
if [ -z "$found" -a "$RW" = "rw" ]; then
if checkbootparam "mkimage"; then
createdata && return 0
fi
fi
[ -d /KNOPPIX-DATA ] && rmdir /KNOPPIX-DATA
return 1
}
you'll find only a little difference. Have a look at "Hint: 10"Code:mountdata(){
......
done
[ -z "$found" -a "$RW" = "rw" ] && createdata && return 0
[ -d /KNOPPIX-DATA ] && rmdir /KNOPPIX-DATA
return 1
}
.
Thanks, Werner for posting this 7.4.1 material.
A number of comments; I'd appreciate your critique on these.
1. Providing for encryption does complicate things.
2. I was surprised that mkisofs does not appear as an element of
of the mkimage process. I see only cloops and mount processes.
This may be a semantic distinction, since I know Klaus K uses
mkisofs in handling overlays in some of his own applications.
3. I think I have learned that, all along, knoppix-data.img must have
been a read/write cloop condensation of /KNOPPIX-DATA at shutdown, taking
two seconds or less to save or update on the USB. Correct me if I'm
wrong on this. One soon learns that a corrupt, saved, read/write
knoppix-data.img is really bad news.
4. It would appear that the mkimage cheatcode converts current
/KNOPPIX-DATA to a read/only saved cloop, and destroys the current
/KNOPPIX_DATA directory. Presumably the option to re-create a new
'empty' /KNOPPIX data directory will occur again at boot until one
is actually requested.
5. It's not clear if the mkimage option can be self-imposed on the
LiveUSB used as the KNOPPIX system du jour or only on another USB,
not on itself.
I worry that if the chosen /KNOPPIX-DATA to be converted is corrupt
that it may, in turn, corrupt the LiveUSB used as the KNOPPIX du jour
if option 5 is viable.
6. A corrupt knoppix-data.img will certainly poison any USB that receives it.
And, I'm not aware there is any test for whether /KNOPPIX-DATA has
become corrupt other than the unpleasant surprise which awaits on reboot.
Hello!
I fear there is a little misunderstanding. I've posted only the function "mountdata () {...}" of the new init of V7.4.1; it's the only thing, which has been changed against the version of V7.4.0.In earlier versions you has been asked for creation of persistent memory, if Knoppix couldn't found it in the startup; now you have to use the new cheatcode.Quote:
I've inserteda the new hint within Knoppix Wiki:
(10) If Knoppix isn't started in forensic mode and if no persistent image or partition is found, then Knoppix DVD version 7.4.1 and upward only offers the option to create persistent image or partition by this new cheatcode.
To examine the content of the init-file you can use this script within your Knoppix V7.4.0 (make it executable and use as root)Code:#! /bin/bash
if [ "$(id -u)" != 0 ]; then
echo " You must be root to use this script."
exit 1
fi
mkdir /home/knoppix/tmp
cd /home/knoppix/tmp
cp /mnt-system/boot/isolinux/minirt.gz /home/knoppix/tmp
zcat minirt.gz | cpio -imd --no-absolute-filenames
.
Greetings, Werner.
I have in my root 7.4.0 filesystem a file called init.
Is this the same or different than what I'd get by using
your script. Thanks.
Yes, it is the same.
.
My geany seg faults on 7.4.1 LiveCD and LiveUSB. With LiveUSB, syslog error reads:
Sep 20 19:38:37 Microknoppix kernel: [ 493.612638] geany[3278]: segfault at c6 ip 000000004c1a9b18 sp 00000000ffaf7640 error 4 in libglib-2.0.so.0.4000.0[4c158000+120000]
Failure using menu is silent. With command line, geany <enter> reports 'Segmentation fault'.
Both LiveCD & LiveUSB passed testdvd.
Problem persists with LiveUSB even with Synaptic reinstall.
My geany in a 7.4.0 LiveUSB works ok.
7.4.1 LiveUSB was made with 'retain personal data' (first option) using
what was another 7.4.0 LiveUSB.
7.4.1 LiveUSB preparation from LiveCD appears to have kept original partitioning
parameters in making the new LiveUSB.
7.4.1 LiveUSB otherwise apparently behaving quite well and predictably.
Nothing unusual about my 7.4.1 configuration not also in previous 7.4.0 configuration.
Is anyone else having this problem?
.
Rebooted; Called-up Synaptic again; Did geany mark for re-installation; Did Apply.
Did not re-install geany-common.
geany now behaving and can read /init material.
Can't explain what was different the second time around.
Hi Werner,
I installed 7.4.1 on my HD and intend to use it on a daily base because it is the most complete an fastest Linux distro I found so far for my needs. I know it is not recommended, but K i sooo cool, thx a million to KK . Also, in this version, I find the Audio to work better than the previous one....
Since I am a bit more familiar with the apt ecosystem, I pay more attention on how to play with package vesioning so as not to break the system.
One application I could not manage to make work, however, is the Plex Media Server :( .
Even though the pms service seems to run, I still can't fire up its interface on a navigator (e.g. 172.196.168:32400/web).
Could you please help? Thanks in advance
On the face of it those instructions make no sense, as a working Knoppix installation is needed to access that script, together with a downloaded DVD. I see a reference to a post with a script attached in this thread - but that is not mentioned in the release notes/wiki page on installation of 7.4.1 on a flash drive. How do we know what's the latest version of the script? By the way does it install the whole Ariadne works and so on using many GB or is there an option to just install a minimal system to the flash drive? I have no idea what an overlay image is. Things seem to have got very complicated over the years!Quote:
Originally Posted by Werner P. Schulz
.
FWIW, My experience with 7.4.1
----
1. Downloaded 7.4.1 iso; did testdvd & passed.
2. Used inert 7.4.0 LiveUSB formated with reiserfs as target;
3. Used 7.4.1 LiveCD Install to Flash using first option: carry over some personal stuff.
4. Booted 7.4.1 LiveUSB; did testdvd & passed.
----
Noted the following on 7.4.1 LiveUSB:
1. Reiserfs retained & working, but virtually empty at first.
2. Fat32 & Reiserfs parameters unchanged.
3. Mozilla bookmarks missing. These should be at ~/.mozilla.
4. Geany segfaulting; worked ok after re-install. Possibly mishandled ~/.config/geany.
5. Compiz has same problem as 7.4.0 not persisting changes.
6. Home-grown update*.tar.gz worked ok to re-constitute tweaks to files in:
/home/knoppix/, /etc/ and /mnt-system/.
7. Home-grown MakeOverlay worked ok to make read-only KNOPPIX1 overlay
from reiserfs /KNOPPIX-DATA.
8. Re-establishing syslog process used on 7.4.0 works ok with 7.4.1.
----
My suspicion is that using 7.4.1's built-in option to carry over any personal stuff
may be both incomplete and flawed. I'll probably not use that option next time.
Compiz difficulty could be overcome with some reasonable ccsm documentation.
----
I expected great things with a cheatcode labelled 'mkimage'.
I conclude it's only a miniscule change which might better be labelled 'enable persistence'.
Please, have a look at Hardrive installation.Quote:
I have no idea what an overlay image is. Things seem to have got very complicated over the years!
OK, I finally installed plexmediaserver following this guide here : http://ilovetechnique.wordpress.com/...ver-on-debian/Quote:
Originally Posted by pgradone
However, the library directories I configured plexmediaserver with would not appear before mounting the appropriate drives they are on - which raises another fundamental question:Code:# echo "deb http://shell.ninthgate.se/packages/debian wheezy main" >> /etc/apt/sources.list
# curl http://shell.ninthgate.se/packages/shell-ninthgate-se-keyring.key | sudo apt-key add -
# apt-get update
# apt-get install plexmediaserver
Since, unlike some "classic" Linux distributions I tried, Knoppix's /etc/fstab is being modified at boot time (therefore not persistent), how do I force mount my other hard drives at boot time?
Do I have to create a mount script myself in, say, /home/knoppix/.config/autostart/mount_my_other_hard_drives.desktop?
Where is the location of K's script creating /etc/fstab ? (in order to modify it eventually)
You can find it within the init-file of the RAM disk "minirt.gz". Have a look at Remastering HowTo, how to decompress the RAM disk file and how to rebuild a new one.Quote:
Where is the location of K's script creating /etc/fstab ?