SliTaz Forum
You are not logged in.
PCmanFM-Mod now has been renamed to SpaceFM now and Lxpanel also has been forked into versions like lxpanelx ( http://code.google.com/p/lxpanelx/ ). Would be nice to see them included too 
The last few rolling and cooking versions haven't been developed or fixed much at all the last few months. This new RC branch is being rapidly developed since pankso is back. Many of the common issues will be addressed and fixed. Don't worry, SliTaz 4 will work just as well as SliTaz 3 by the time it gets released as stable. Pankso is pretty strict on things like that, which is half the reason we didn't release last year - it just wasn't stable enough.
I also don't think adding more junk or creating a fully featured version would help much and the 30MB limit is more for how much RAM we can load in without locking the CD/DVD-ROM. The upper limit is 190MB although we prefer to aim for 160MB - this limits to how big the compressed iso image can be - I think that translates to a max of around 50MB. Any more than that and you just won't have any RAM left on a 256MB RAM machines without resorting to CD/DVD-ROM locking and data swapping (which is SLOW). I do agree in making a stripped down version just running the basic apps with lxpanel, busybox, slim, openbox, xterm and pcmanfm set
Offline
For myself I can help myself - in most cases, sometimes too slow. I think of how to do so one can give it away. For such a case one has to meet the following conditions:
- an Xscreen must be there, in any case
- one should be connected to the net with ease
- there must be one light but usable webbrowser (tazweb is ok, except the bookmarks issue)
- one filemanager
The rest must not be within slitaz itself. Let us assume LibreOffice AppRun or a desired Kompozer that would run in Slitaz. One can copy it to a CD and then to a harddrive and use with slitaz from there. Like this... at least ,,normal" people would insist on a more elaborated browser like Opera or Firefox and an easy method to keep their data. Most people would install Slitaz to their harddrive anyway, in case they like it. Then this RAM burden is less important.
<= The commandline option ,,home=/dev/sda2" fails very often. At least on my machine. The GRUB message comes like ,,...must be either a blockdevice or a pathname...", which means that he cannot recognize ,,home=/dev/sda2", right?
Offline
Yet it's LiveCDs that sell people on Linux. The RAM issue is important because of that
Offline
FYI a loram is available too. Works fully with 128M RAM.
http://mirror.slitaz.org/iso/cooking/flavors/slitaz-4.0-RC1-loram.iso
Offline
Hi,
4.0-RC2 will be ~38Mb with full Xorg. We not fixed on 30Mb no more, we always wanted slitaz to be usable with 256MB of RAM and 30Mb was a max regarding to that. But with the new 4in1 the default SliTaz is fine since you can install a full desktop with only 48Mb RAM.
We have one year release cycle, this time it's special and we needed that. We must handle more than 3000 packages now, we had to find/manage a new build server, we had to rewrite a new packaging system and this took us 2 year of active developement. More info: http://scn.slitaz.org/2011/05/new-build-bot-up-and-running/
We are not starting to ask for feedback, it's 1 years we work with new build tools and packages have been well tested, rebuild many time. Now we need fedback on the default LiveCD, we know it's a shame if people boot and end up with a console mode when they expected to have a desktop, so we focus on the default LiveCD actually.
I commited a GTK only flavor with just X, Openbox, slim, pcmanfm and lxpanel. It will be bootable as a single ISO or from the core boot menu since gtkonly will be one of the 4 version in the 4in1 core liveCD.
- Christophe
Offline
> michaelbischof wrote:
> Nouveau failed even when I booted with nomodeset
> llexam wrote:
> I tried adding rootdelay=8 to the boot code, with no change
I think it is a general problem of the boot menu:
http://bugs.slitaz.org/issue117
Offline
> Trixar_za wrote:
> PCmanFM-Mod now has been renamed to SpaceFM
> Would be nice to see them included too
In my eyes the SpaceFM menus are to "cluttered".
So I vote against it.
Offline
> pankso wrote:
> I commited a GTK only flavor with just X, Openbox, slim, pcmanfm and lxpanel.
Thumbs up for that. 
Offline
I'm suggesting SpaceFM as an ALTERNATIVE to and not a replacement for PCmanFM.
Also know that your vote has very little weight on if a package gets made or if it gets accepted into the repository.
Offline
It's always a bad sign when people work out my weakness - making me actually stand by what I say 
Offline
Was directed to this forum as SliTaz 4.0-RC2 Live using unetbootin to make a bootable usb pendrive crashed during startup with a kernel panic message. Bewildered by the boot choice (core justx gtkonly etc) they all got tried with no success however the http://is.gd/TazDevISO contributor flavor, 9th post from pankso (thx!), boots straight into a GUI on an Asus EEE 2G. As TazDevISO was based on 4.0-RC1 can another be made from 4.0-RC2 and put on the official download website and clearly identified as unetbootin friendly? Presumably both 4.0-RC1 and 4.0-RC2 are 4in1 that won't work with unetbootin and it'll be a retro step to go back to blowing CDs then copying to pendrives or even using command line idea (thx llexam).
Offline
May I come back to an unresolved issue, that MichaelBischof raised?
I, too, have the problem that up to now I booted a frugal SliTaz using only one initrd.gz.
Now I desperately try to modify my GRUB (legacy) menu.lst in order to boot the staged initrd's, which seems a beautiful solution for the different machines I equip for myself and different members of my family (keeping modificationys away from the original initrd).
I already tried to keep all 4 initrdX.gz in the initrd line of menu.lst, with comma it didn't work at all, with spaces only the first initrd4.gz was accepted, all others ignored (text mode only).
Using seperate lines for each initrd in descending order seems to be accepted, but on changing to tmp-fs on bootup the system crashes on not finding the root fs. ("no filesystem could mount root, ...")
So does anyone know a solution to this issue? Or is using syslinux succeeding grub the only possibility? Might GRUB2 be a better approach?
Offline
Try grub4dos or SliTaz grub.
SliTaz doesn't use legacy grub but an enhanced grub from grub4dos for some extra such as ntfs support.
See http://hg.slitaz.org/wok/file/e01952170f7c/grub4dos-linux/receipt
Offline
Thanx a lot!!!
installed grub4dos-linux.tazpkg
# grub-install root-directory=/media/[mounted root-partition] /dev/sda
got some error messages (segmentation fault ...)
but boots like a charm (even kept former menu.lst)
Thanx a lot again!!!
Offline
A solution: As Unetbootin generation of both 4.0-RC1 and 4.0-RC2 give kernel panic crash and using a CD or command line dd is ruled out we find ourselves with a working slitaz using Pankso's Unetbootin-friendly http://is.gd/TazDevISO 'contributor flavor' based on 4.0-RC1 running on a memory stick. Below is a way of upgrading this to the latest 4.0-RC2; hopefully someone will show a slicker way as this needs two USB memory sticks. Meantime steps are...
1. Use Midori to download the latest slitaz-4.0-RC2.iso
2. Upgrade tazusb from existing 3.0.1 as it fails on final stages.
Source of tazusb version 4.0.1: http://hg.slitaz.org/tazusb/raw-file/tip/tazusb
Also see article http://forum.slitaz.org/topic/installation-or-liveusb-prep-cannot-find-rootfsgz-on-slitaz-30-3-in-1-disk
Name new file say tazusb401.sh
3. Prepare a second destination memstick to later boot 4.0-RC2. A 2GB memory stick is ample.
Use gParted to make say two 1GB ext3 partitions so the second can be used for data. Make sure the first partition is empty and has a distinctive label.
4. Leave the destination memstick unmounted however Applications/System Tools/Mount devices 'Mountbox' is useful to locate the 'unmounted dev' /dev/sdd1 in our case.
su to root to get hash prompt and cd to folder containing the iso
Example use... /home/tux# sh tazusb401.sh gen-iso2usb slitaz-4.0-RC2.iso /dev/sdd1
5. Reboot with just the new stick in; beware some machines will only boot from one USB port.
6. Later you might like to append /boot/extlinux/extlinux.conf so that it doesn't keep prompting for key and local settings on startup.
After doing su root need to go say #cd /media/buf1/boot/extlinux then leafpad extlinux.conf and add to the append line for example lang=en_GB kmap=uk locale=en_GB
Hopefully this is useful for others.
Offline
Having got 4.0-RC2 running without kernel panic some findings on persistence...
a) su root so hash prompt shows...type [c]tazusb writefs none[/c]
after above answer No to the two remove questions.
b) Creates rootfs.gz without compression.
Moves rootfs.gz to 'media' - presumably a USB flash disk.
Says 'Remember to unmount for delayed writes!' not quite sure what this means.
mv: can't rename '/home/boot/rootfs.gz' : No such file or directory.
(NB Above warning only showed first time; possibly disregard first time as rootfs.gz did not exist before the first backup.)
c) Memstick now shows rootfs1.gz rootfs2.gz rootfs3.gz rootfs4.gz and newly saved rootfs.gz (155MBytes) in /home/boot/ and note /dev/sdb1 (first partition on boot memstick) was automounted as /home in our case so all five root*.gz are together.
d) On restart the software reads rootfs1.gz rootfs2.gz rootfs3.gz rootfs4.gz but rootfs.gz does not show as being read unless too fast to read. One wonders if rootfs.gz is meant to replace the original set of four or be added to them.
Firefox settings appear restored but not newly loaded packages e.g. python. Also removed pesky games keep coming back, surely if people want chess and suduko, however small a footprint, they can download them as packages after basic installation.
e) An improvement to SliTaz would be a backup system as Tiny Core uses where one can backup anytime with a single button press and that's all but in addition the user defaults to backup on exit (an option allows otherwise). The backup is in a single unique folder that is placed in any memory and this location can be easily changed.
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]