SliTaz Forum
You are not logged in.
@tazpider
Oh, yes, I forgot:
You boot from a CD. The filesystem, your filesystem, is in RAM. You change now this and that - anyway, the directory ,,/media/cdrom" is empty, a virtual something.
So copy the content of your CD (the fresh, untamed content) just into /media/cdrom. Then use ,,tazlito writeiso".
By the way: if you boot from a ,,frugal hdd" install this error message will not appear. How to do it? One example from my machine:
Make on some ext3-partition a directory ,,boot.slitaz". Copy the whole cd just into this directory. Then adjust the grub legacy command line accordingly:
title slitaz 2.0 hda3 frugal
root (hd1,2)
kernel /boot.slitaz/bzImage root=/dev/ram0 rw
initrd /boot.slitaz/rootfs.gz
boot
That's it. Now you boot, change this and that and use ,,tazlito writiso". Then you will recognize something new:
/home/slitaz/distro/rootcd/boot/rootfs.gz
=> This rootfs.gz is a new (!) one and it is bigger than your original rootfs.gz.
Now you rename your original one, like ,,rootfs.0.gz" and now you copy the new one to
/boot.slitaz/ - with this style you always have 2 rootfs-files: the original, untamed one and the new one, that you have changed. This new one is not compressed, though, quite bigger than the original 35 MB something.
Offline
I noticed a problem with desktop wallpaper using rolling iso from March 20, but it seems it goes back to earlier versions of SliTaz as well. My monitor has 16:10 aspect (widescreen & usually use 1280x800x16 @75.0) though I sometimes apply a 4:3 setting (usually 1024x768x16 @60.0). It's normal for me to use no wallpaper, just a background color. I played with background images more today and noticed that, when I select an image and select stretch image to FILL the screen, odd results are produced. Example: with monitor set to 1024x768 and applying the default wallpaper (is 1600x1200 I believe), the image is not fit to the size of the screen, it seems to be still the original size. The image is also offset to the right a couple hundred pixels, leaving a black bar on the left edge of the screen. Is this something that can be addressed or is it an issue with the WM itself?
tazweb: after upgrade to tazweb 1.6 only can run from command line. no icon on menu list. folder /usr/share/tazweb is empty. I finally created its own file in /usr/share/applications/tazweb.desktop. there you have this problem too?
Offline
@rd.nmc
tazweb 1.6.1 is complete,it's not on the mirror yet.
http://cook.slitaz.org/packages/tazweb-1.6.1.tazpkg
Offline
@mojo: thanks, bro ... I'l try ...
mmmmm ... what different about http://cook.slitaz.org/packages/ and http://mirror.slitaz.org/packages/cooking/ ? and today I can't access http://mirror.slitaz.org/packages/cooking/
Offline
Figured out my problem with desktop wallpaper not fitting to the screen. Realized that SliTaz was not recognizing correctly EDID info from my monitor, an Acer AL1917W widescreen monitor. Once I manually edited the Xorg config files for the screen and monitor, the display began acting as it should. Odd though that the EDID info in the Xorg log was pretty much on target, Xorg still didn't like it.
This is a potential security issue I have found in 4.0-RC3. The open ports 80,82 and 6000 are open to ip addresses outside of localhost by default. An nmap of the port show them all open. I am able to connect to the busybox web server hosted on a fresh slitaz install from another computer on my network.
*UPDATE*: I added a bug report. Sorry about the forum post for a plain bug report.
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]