i made this kde installation over a week in bits and pieces. i went about solving dependencies for applications one by one using ldd command.

you will require puppy 1.0.5
a fresh pup file ~400 Mb
usr_devx.sfs

a working SLAX ( download from slax.linux-live.org ~179 Mb)

128 Mb
200 Mb swap

i did not make a note of what all i have done so i will make a fresh kde install, jot down all steps and post them over here. with the instructions it should take a couple of hours to make the installation.

Hi. If I understood the last remaster script AlienX has put together, this
script takes all changes+new files inside pup001 and make a usr_more.sfs
out of them.. So that one can copy this to /mnt/home together with a fresh
pup001 file and seeing and having the same environment as just before the
remaster step... basically meaning all alterations are in usr_more.sfs ready
to rumble...

Maybe that could easily make a usr_more.sfs, that result in a kde puppy...?!

Yes i know that the installation can be converted into usr_more.sfs. But the size of my final installation comes to around 250 Mbs so for puppy users it would be best if the packets are broken into much smaller packets(dotpups) i.e. arts (15 Mb), kdebase(20 Mb), ...

i have been using free servers on the net to post my stuff that usually have a limit of 50 mb. i have a internet connection as slow as a sloth. i have to try number of times before my files get sucessfully uploaded.

bit torrent is good for uploading files with a slow and unreliable connection

1) it breaks the uploads into small pieces

2) it automatically checks each piece ... when the torrent has finished downloading, the file(s) should be perfect copies of the original

3) as soon as another machine has a chunk, they will upload it too, at high speed if they have a high speed connection ... other computers with high speed connections can take over seeding the file(s)

4) super seeder mode will upload a different chunk to each downloader, so you don't have to upload the same chunk to a lot of different computers, so you only have to upload the file(s) once

the main problem with torrents is when people don't upload as much as they downloaded, because then someone else will have to upload what the leecher should have uploaded, or the torrent will break, because there won't be a seeder

when i decided how dotpups should work, the way i chose to make it is not very efficient in terms of space ... i figured that most dotpups would be relatively small, and any large packages could be downloaded and installed by the dotpup rather than be contained inside the dotpup ... basically, a dotpup is automatically unzipped in /root, which may have limited space if your pup001 file is not very big ... so you could have the dotpup and the unzipped dotpup in /root at the same time, which means you probably need at least twice as much free space as the size of the dotpup ... one thing i have thought of doing is to allow a user to choose where the dotpups unzip, so they could unzip on a mounted drive with lots of free space, for example

You could split the file using "split" and send it to Ted_Dog.
You can split with "MToolsFM" in the filemanager-menue.
He could restore it with
touch newfile
cat kde.aa >>newfile
cat kde.ab >>newfile
cat kde.ac >>newfile
and so on.

Ted offers to host Puppys.
As a KDE-Package is larger than a puppy-iso, he might host that too.

I think Puppy should stay away from KDE and GNOME and all the other major window managers. Don't we have enough of bloated distributions featuring those already!? It's been done to death! I don't want yet another Knoppix clone look-a-like. Puppy should stick with IceWM and downloadable themes. It's part of what makes Puppy unique. Keep it small and simple and pick out anything redundant. Please remove the games and make a 1.0.6 barebones version. Concentrate on solving bugs. If possible switch to the latest stable browser in the Mozilla Suite 1.7 series. Put in CUPS. Consolidate the package managers. Improve the fonts. Work on the multi-session live-dvd. Don't waste time on redundant window managers... Focus!

KDE is a standard environment, and several programs are available for KDE only.
So I think it is good to have that option (though basically I think like you).
If KDE goes to a usr_more.sfs, i see no problem.

You can load/unload it optionally by simply renaming that file.
I think it might be quite fast with puppy, I just loaded OpenOffice-Writer from Grafpup in 12 Seconds. Well thats fast

If you upload that file to me, I will redistribute it and put it on any ftp space I can get my hands on (I have a couple of friends with space + big bandwidth, more if my uni gets involved) plus i'll upload it to anyone with ftp space on here. I'm planning on making an electronic engineering live cd based on puppy for manchester university with all the electronics programs I need for the course. But most require KDE

all the files get mounted to the /usr folder.
how to edit the rc.sysinit to load the files to their correct location

If I understand you correctly, you've made a squashfs with /filesystem as the top level directory and everything else underneeth it. Is that correct? And now you need a way to get the files from /filesystem/usr into /usr, /filesystem/opt into /opt, and /filesystem/etc into /etc. Am I still following you correctly?

I'd suggest a different approach myself. Puppy is not set up to use /opt at all and will not permanently store anything there. Most of the time files in /opt can be readily moved to /usr, so if it's in /opt/bin move it to /usr/bin, if it's in /opt/lib move it to /usr/lib. I don't know if that will work for your KDE install or not but it's the most 'correct' way to do things for Puppy. As for anything in /etc and /root it should only be configuration files and so take up little room. You could make a two part install with a squashfs for the bulk of it and a dotpup for everything in /root (including /root/.etc).

If you can't move things out of /opt you could try symlinking the files. Put them into a new directory in /usr and have rc.local create symlinks to them every time the machine boots. As for making the squashfs, I'd get your install up and running (with a fresh pupxxx) and then copy all of /root/.usr to somewhere convenient, like /mnt/home/tmp/.usr. Then just navigate to /mnt/home/tmp with rox, right click and open a terminal and type:

Code:

mksquashfs .usr usr_more.sfs

If you do this then you won't have to alter the way the computer boots in order to move the files to the appropriate places, as everything in .usr will go right into /usr where it belongs.

Of course this is all assuming that I understood your post and what you were asking.

I really think that a squashfs is the best way to go in making any kind of KDE package. This is exactly the sort of thing that that feature is good for.

Quote:

I think it might be quite fast with puppy, I just loaded OpenOffice-Writer from Grafpup in 12 Seconds. Well thats fast

I get a lot better than 12 seconds with my system, about 7-8 seconds. Anyway, I'm glad someone here tried it and I've been really pleased so far with the performance myself.

While I agree with the sentiment that KDE is way too overblown for it's actual usefulness, a lot of people like it and want it. Why not have it available? I put the smallest wordprocessor I could readily find into Grafpup (Ted) but made the squashfs with OpenOffice because I knew that for some Ted wouldn't cut it, or they would just really like to be able to run OpenOffice2.0 in Puppy.

Good luck with the project. I'd be willing to mirror it myself on the new Grafpup server as long as I don't overrun my bandwidth.

Following is the file structure of my kde installation
/root/.etc
/root/.opt/kde/etc
/root/.opt/kde/include
/root/.opt/kde/share

/root/.usr/bin <- /root/.opt/kde/bin moved over here
/root/.usr/lib <- /root/.opt/kde/lib moved over here

config files & folder in /root/

/root/.opt/kde/bin & /root/.opt/kde/lib <- link to /root/.usr/bin & /root/.usr/lib because some apps give errors when these links are not present

/root/.opt is mounted to /opt at boot time by rc.local using f/w commands
rmdir /opt
ln -s /root/.opt /opt

i will move the /root/.opt to /root/.usr/opt so that most of the installation then resides in /root/.usr which can then be converted to usr_more.sfs

however nathans idea of making a dotpup for the config files & .etc does not click because files in /.etc/X11 are overwritten, so reverting back to the original installation by just renaming usr_more.sfs will not be possible

I have secured some ftp space for the KDE puppy project, whatever form it takes. Its co-hosted at manchester university. I'm going to work on a modification of puppy for electronic engineers which will also be held there. If you need to transfer a big file, I suggest maileet which breaks the file up, sends it and verifies the parts of a file automatically via email and deletes them as it goes.

Their description
Super easy free web hosting on our dedicated servers! We are a new and dedicated web hosting service offering superb hosting 300mb upload space with no limits! We already have multiple servers available to host the site! Our servers are connected to a reliable datacenter managed by their dedicated professionals to keep this site running in top condition! Give our dedicated hosting a try, you won't be disappointed! Don't forget this is absolutely free and the web hosting are all on reliable managed dedicated servers!_________________Heaven is on the way, until then let's get the truth out!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum