Smaller graphical install than basic on Eee PC 701.

[globetrotterdk]

@caitlyn: For what it is worth, I have been experimenting with using PekWM as a drop-in replacement for Openbox on my Eee PC 701, with a Peppermint Ice (Ubuntu derivative) install. Peppermint Ice has a small enough footprint to fit on the internal HD of the Eee PC. My results so far are promising. By copying the contents of the /etc/xdg/lxsession/Peppermint_Ice/autostart file into the ~/.pekwm/start file I have largely been able to recreate the look and feel of the original install. This could probably be done with the Salix LXDE version as well, to create a Salix version with a smaller footprint. Only about 1.3 GB of the 2 GB are used, despite my installing Abiword, aspell, Vim and a few other bits

[zAchAry]

I took a look at the slackbuilds for the SalixOS repo and I must say that what you do with slackpkg looks entirely different than what sbbuilder produces. I would literally have to rebuild every package I've done, both 32- and 64-bit, in order to fit into the SalixOS family. Considering the work involved I am simply not going to do that. It seems SalixOS will have a derivative distro after all. Sorry...

That sounds severe, do you have any solutions for that?

[thenktor]

For what it's worth, pekwm is now in the repositories.

Thanks, wanted to test this one, too

[gapan]

@caitlyn,

no problem at all. Maybe this thread can help you somehow: http://www.linuxquestions.org/questions ... -x-838437/

[caitlyn]

That sounds severe, do you have any solutions for that?

You have to understand that I was very near a public alpha release when I jumped into the middle of this thread. The main hold up is getting things like repositories, a website and forums in place. I would love to avoid all that work. OTOH, SalixOS uses very different methodology for package building than VectorLinux. I came to SalixOS from Vector and that is what I know and, quite frankly, really like. If I was just starting this I would probably just do things the SalixOS way. The fact is that I am way past that point. Rebuilding everything would be a ton of work.

Tell you what I'll do. Sometime today or tomorrow I'll put a few packages where people can get to them and announce them here and in the Contributed Packages section. Then you all can look at what the differences are and make your own judgments.

Let me say this very clearly: I really like SalixOS. I have no intention of competing with SalixOS and almost certainly will continue to recommend it. What I am doing is making it convenient for people who don't want to do a lot off manual work to use something like SalixOS in situations where doing so isn't all that easy.

[caitlyn]

For what it's worth, pekwm is now in the repositories.

Thanks, wanted to test this one, too

One missing piece I use is Esetroot to set the background. See: http://www.jnrowe.ukfsn.org/projects/esetroot.html (xli would also work.) Add that + a good panel app + a file manager and you end up with a very nice desktop. If the file manager doesn't automagically handle desktop icons like pcmanfm or dfm do you can add a small app like mkdesktophdico if you want them.

[linus72]

That's funny as I made a PekWM centered livecd based off of Kmason's script that installs a customized PekWM Desktop in your ARCH install
http://linux.softpedia.com/get/System/O ... 9727.shtml

heres the site and forum page
Afterglow ARCH linux forums thread is here
https://bbs.archlinux.org/viewtopic.php?id=101780&p=1

Website here
http://afterglowlinux.co.cc/

I believe he's using pekwm-opacity

give you some ideas at least