Hey linus72


a big thanks for the links and info for the patches
I have to update a kernel for some testing (this will take some time )

I am downloading your latest work of the live slackware cd

side note :
ATM I the way I go about building the TXZ iso using packages then run it through package tools to build but it depends on a root filing system that I want to get rid of because you have to edit the initrd each time for new modules (when you compile a new kernel)


*basically I want to remove any "hard coded puppy stuff" thats a pain to manually update and I am getting very close to doing that now

and the LLS seems a better solution since it is developed and modified to
follow current distros

a side note :
a work in progress I have is to remove all the specialized programs used and made by the puppy developers and make them linux/slackware compatible so they can be used on any light weight distro their package format is not linux compatible but I will convert them to correct packages using the TXZ format

I "was" one of the main packagers for puppy so I can unravel the pet packages
I compile and make all my packages slackware compatible now

so I'll link you to some nice small custom apps you could use


thanks friend for helping with the info

Colossians 3:15

Joe

I applaud your efforts!

so, you basically are creating a small slax-like derivative?
but will it retain puppy's attributes as well?
and will you still use JWM or some other WM?

cant wait to see what you come up with?

[QUOTE=linus72;4105622
so, you basically are creating a small slax-like derivative?
but will it retain puppy's attributes as well?
and will you still use JWM or some other WM?

[/QUOTE]


Hey linus72

I had a chance today to read over most of this post today
and I would like to say this to you and anyone else reading

that all the naming and rules and legal notes are followed
and credit given to those that wrote code as always nothing new for linux users

apart from the legal side of things the tinkering stuff to make things happen (only a very few people are thoughtful to document and share their efforts transparently )


It is a very complex process just to build a live cd an have it work
because of many reasons here is only a small list of gotchas
1.) kernel patches
2.) live scripts /or home made scripts to to join it all together
3.) the incredible amount of trial and error of finding fixing and writing new code to keep up to date with all the changes

where I see a conflict is the naming and that can be corrected

there is a need to have a live cd version of your favorite distro
I wont name any here but as just a personal opinion I like the official trade marked version of slackware ™ © ® to have installed on my computer
for the full version feel (a priceless fine work of art )

I also have need for a live cd for many reasons
and that niche isnt filled any other way but by having a live cd

and having a kit or a how to generate the live cd of whatever "official"
distro is welcomed by those that want to do that

linus72
maybe if you focused in this tread on "the how to" then link to your website for your special version and special info for those versions you would appease
all

I for one value the information you posted in the how to for the live cd
its just a matter of sorting this information to its correct locations

and just dont forget to link me

ahhhh! I forgot to answer your question I am very interested to discuss details just PM me or I ´ll PM you and post all "code" in pastebin for others to use


a full installed version of slackware ™ © ® rules

small live cd´s of famous distros rule

peace brothers
be creative

Joe

hey big_bass

I finally figured out how to make a AUR pkg for the live ARCH 2.6.35.7 kernel
http://aur.archlinux.org/packages.php?ID=41353

I have to update some stuff on it too, just minor editing,etc
and the tuxonice works on my old K8 I have it on
just grab the AUR pkgs hibernate-script and tuxoniceuserui
http://aur.archlinux.org/packages.php?ID=24613

http://aur.archlinux.org/packages.php?ID=37110

even though it doesnt list it as a depends fbsplash is really needed
too
http://aur.archlinux.org/packages.php?ID=13541

and I now got a 2.6.35.7 kernel for the slack builds too

I still have to create the pkg for ARCH that gives one the scripts etc to make livecd from the livez kernel,etc

have you ever made a ARCH pkg?
its not very easy...compared to Slackware

I really wish Slackware would put out a official livecd or DVD

you know the linux-live-scripts dont just make a livecd

it's also a way to backup your complete system and reinstall it somewhere else or whatever
you can clone machines and their state is frozen at the time their created

and the builds can be modified after making them, they can be deconstructed and remade

you can rescue a installed system by turning it into a livecd
you can do this from the livecd without chrooting
just copy the kernel/modules and lls to messed up system, run the build script and point it to your install and bam, instant backup

I think its easier than clonezilla, dd, etc
and foolproof and repeatable

I agree its pretty complex to make the arch/slackware builds as the parts to do so come from various unofficial sources

the linux-live-6.3.0_x86 & linux-live-6.3.0x86_64 scripts are a modification of the original because
1) the OG lls 6.3.0 only works with squashfs 3.4
2) the OG lls 6.3.0 only does x86

All thanks go to Ritchie at Slax Forum for the Linux-Live rebuilds for squashfs-lzma 4.1 cvs

All thanks go to Fathom at Slax forum, maker of the slackware current based SlaxRemix08 for the kernel patches aufs2 and squashfs-lzma

All thanks go to anyone/everyone from LQ and ARCH forums, who's advice,etc helped create everything I have made via Remastersys and Linux-Live scripts

All thanks go to the members of LQ who have answered all my dumb questions and saved me time and effort in learning Linux


oh
you know I could use the default Slackware 2.6.33.4 kernel source
and use squashfs 4.0; the build will be bigger sans lzma, but it will boot faster due to quicker decompression of the compressed media
however, would it still have a the newest stuff like 2.6.35.7?
no, so theres a tradeoff there I guess??

I was gonna write a small book on the whole process and all the nuances, etc but I dont think it would sell

the advantage of following the official kernel version is
all the third party video drivers and wifi/modems and such have build scripts or will have available which is a big help when you need to get the hardware up and running

I compiled numerous video drivers and wifi drivers for hardware I dont have for other people to use (when you can test on your box its easy when you build packages for a special version for some else this is more
labor intensive so the build scripts help lighten the load
to just adding minor tweaks (if you get lucky )

*this is more important than any minor advantages to the latest kernel version number (unless some special patches are needed )

also since people will feel more at home compiling on the pre installed kernel version number so they have a quick fall back kernel if something went wrong and it fits well with the thread topic title

*sure* you would even get more positive feedback from the die hard veterans too

Joe

ok
thats a "can-do" I think
all thats really needed is the aufs2 patches, etc for 2.6.33.4

heres some patches
ftp://ftp.archlinux.org/other/aufs2/

I did
patch -p1 < ../aufs2-kbuild.patch
patch -p1 < ../aufs2-base.patch
patch -p1 < ../aufs2-standalone.patch

copy over {Documentation,fs,include} files to your kernel source tree
do make menuconfig and choose however you want to compile kernel
best aufs2 options are

then, you need Ritchie's/mine modified Linux-Live scripts
here link (place it in /root folder)

the one above is for squashfs 4.0 only
the kernel kits contain lls for squashfs-lzma
I have not found a squashfs-lzma patch for kernel 2.6.33.4?!
so you must use squashfs 4.0

the differences are
1) squashfs-lzma will make smaller build, but takes longer to boot
2) squashfs 4.0 will boot faster but the build will be exponentially bigger

so, my nFluxOS slackware builds are around 600-700MB using squashfs-lzma
if I used squashfs 4.0 it would be about 750-900MB
big difference

now, after compiling kernel with aufs2, reboot into new kernel
clean system of cruft,etc
cd into /root/linux-live-6.3.0_x86 folder and do
./build

thats it
though you still really need some of the other stuff/scripts to make it all work like Slax does
so I goota make all that up too

or you can get that stuff from the kernel kits here
http://multidistro.com/NFLUXNEW/SQ4/kkits/kkits.html

parts you need are

etc/rc.d/rc.slax
etc/rc.d/rc.local.new (optional)
etc/profile.d/slax.sh (runs stuff)
etc/X11/xorg.conf.new (vesa)
etc/X11/gui.conf

usr/bin/xconf (auto configure X script from Slax)

/usr/sbin/create-slxsave-xfs (SalixOS USB persistent slxsave.xfs maker)
/usr/sbin/create-slxsave-xfs-gui

usr/share/applications/persistence-wizard.desktop
usr/share/icons/create-slxsave-xfs.png

you need libgnomecanvas & zenity from SlackBuilds for the persistencewizard

OR

you can get the SalixOS stuff from JRD's repo and either build kernel or use his stuff
http://enialis.net/~jrd/salix/kernelive/

http://enialis.net/~jrd/salix/kernel....smp-i486-1cp/

if you use JRD's stuff you MUST use the linux-6.3.0_x86 for squashfs-lzma found in the kernel kits
http://multidistro.com/NFLUXNEW/SQ4/kkits/kkits.html

for reference
the mini SCR new I just made with squashfs-lzma is 298mb iso
in contrast the squashfs 4.0 build is 375mb iso

ahh
maybe you can have lzma compression with 2.6.33.4 slackware kernel source
just add the patches from JRD's repo

and make sure you put
CONFIG_SQUASHFS_LZMA=y

I am compiling the source now and will tell you how those lzma patches work when done

EDIT: sorry; it's squashfs-lzma 3.4
so thats no good...its just not as good as 4.0 or 4.1 cvs..

so, choices are 2.6.33.4 with aufs2/squashfs or
a higher kernel that the squashfs-lzma patch will work with

or get a zen patch
http://zen-kernel.org/releases

yeah that speaks loudly for bandwidth abuse
shaving off @75MB per iso is a major plus on the small iso the full version saving will be a lot


as a test I updated my kernel using "your kit"
and is working fine in all areas

*I do like JWM and Rox since they are light and fast and because I know how to modify them and feel comfortable using them

will keep you posted
there is a lot of good stuff coming
I tested your clutchmini a great Job you did there !

P.S the package tools GUI I updated there was an error with a file check when using slackware 13.1 but was working on my custom set up I updated the paste bin post


this is a very simple drag N Drop package installer
I call dnd-install



Joe