Salix Live Xfce 14.1 beta1 is ready for testing.
The Salix Live XFCE 14.1 beta1 ISO includes the same programs as the installation ISO, with the addition of gslapt and deps for it, need for partitioning before making the installation. It is build using Slackware Live scripts from Slackware Live -LiNomad and includes the SLI installer from Slackware Live -LiNomad which it is written in c (gtk+2) and glade. Slackware Live scripts and SLI installer has been further developed adding support for user creation and gparted connectivity for managing partitions, setting locale, keyboard and support for core, basic and full installation modes. From SLI installer gui user can set new username and password ( there is no root account, as in the installation ISO). (e)Lilo is used as the boot loader for 32 and 64 bit systems, same with the installation ISO image's.
Also can install the system in a usb (frugal) and use persistent changes, having Salix in your pocket. On isos image in syslinux folder there are scripts to install on usb. Just mount iso image and copy everything to usb. Then cd to boot/syslinux folder on usb and run sudo sh install_on_usb.sh script to make the usb bootable. Same can be done with bootinst.sh script. Choose what you like. From windows the scripts are install_on_USB.cmd and bootinst.bat. Using this method everything else you have already on usb will not be erased.
You can do the same from the live environment using the SLI installer. In this case everything on usb will be erased.
Another option is to use dd command to install on usb. In this case everything on usb will be erased as well.
There is no live kernel. The kernel used is exactly the same with the 3.10.17 kernel of Slackware.
With this approach creating the installation iso's, at the same time using the already downloaded packages can build the live flavor too.
source's on github for creating live isos.
You don't need a password for the regular user and auto-logged in user one
Password for user one is “one”.
screenshots
You can download iso images from our sourceforge project page, using the following links:
Live ISO images
32-bit (i686):
(size: 745 MB, md5sum: 4997c7eadca5850124571c0718af34d0)
http://sourceforge.net/projects/salix/f ... o/download
64-bit (x86_64):
(size: 791 MB, md5sum: 044466be4d7cfba4e1fa38f75a16f1eb)
http://sourceforge.net/projects/salix/f ... o/download
Thanks for testing.
Salix Live Xfce 14.1 beta1
Re: Salix Live Xfce 14.1 beta1
Thank you very much for providing this LiveCD,
Am downloading. Will test and provide comments if needed.
Things seem to be moving ... Nice!
Am downloading. Will test and provide comments if needed.
Things seem to be moving ... Nice!
Re: Salix Live Xfce 14.1 beta1
After half a day working / playing with Salix Live Xfce 14.1 beta1 i would like to say that this LiveCD is almost perfect. Congratulations.
Did a frugal install on a usbstick my own way (booting with grub legacy). All the programs I have been using up to now just worked. Was able to make / use some personal modules (gvim, ruby, mplayer. ffmpeg, ...)
Have only two remarks for the time being :
1. - 'find' gives some unusual remarks: wondering whether these are error messages or not
2. Was unable to build "chromium" with SLKBUILD. (On i3 machine with 4GB memory) Any help?
Again : thank you for providing this nice piece of work.
PS : am sending this message from within the LiveCD.
Did a frugal install on a usbstick my own way (booting with grub legacy). All the programs I have been using up to now just worked. Was able to make / use some personal modules (gvim, ruby, mplayer. ffmpeg, ...)
Have only two remarks for the time being :
1. - 'find' gives some unusual remarks:
Code: Select all
find: Filesystem loop detected; `/live/union/usr/share/icons/hicolor/96x96/stock/form' has the same device number and inode as a directory which is 2 levels higher in the file system hierarchy
find: Filesystem loop detected; `/live/system/usr/share/icons/hicolor/96x96/stock/form' has the same device number and inode as a directory which is 2 levels higher in the file system hierarchy
find: Filesystem loop detected; `/live/system/usr/share/locale/fy/LC_MESSAGES' has the same device number and inode as a directory which is 5 levels higher in the file system hierarchy
find: Filesystem loop detected; `/live/system/usr/share/geany/colorschemes' has the same device number and inode as a directory which is 2 levels higher in the file system hierarchy
2. Was unable to build "chromium" with SLKBUILD. (On i3 machine with 4GB memory) Any help?
Again : thank you for providing this nice piece of work.
PS : am sending this message from within the LiveCD.
Re: Salix Live Xfce 14.1 beta1
As you say everything are working fine. You did the installation on usb your own way and worked.
About these messages has to do with union and not every user dig his system so deep.
About building chromium on live environment and why you could not do it i cannot tell. Even if you have 4GB of memory chromium is not a regular build.
Thanks for testing.
About these messages has to do with union and not every user dig his system so deep.
About building chromium on live environment and why you could not do it i cannot tell. Even if you have 4GB of memory chromium is not a regular build.
Thanks for testing.
Re: Salix Live Xfce 14.1 beta1
This is just an initial report. I copied the image to USB with dd, and it boots fine - very fast as well. Someone in the jabber chat mentioned it not working with dd, but for me, it did.
On boot, user is asked to select language, which also defines the keyboard. But the keyboard should be a separate step. For example, I might have a Brazilian Portuguese keyboard, but want UK locale. In this case, I have a UK laptop, chose English language, and I have got US keyboard layout, which is different from UK. Pipe comes out as >.
In my view this keyboard selection should include all possible options, as in the classic installer, not just a selection of some common ones. There are several for each language, and it makes a big difference. Especially for users not using persistence, fixing this manually after boot is an unacceptable hassle.
I launched the installer, but haven't actually tried it out yet. It looks nice, though. How does it decide whether to install lilo or elilo? One minor thing: the text @Actions needed ... @ etc is gammatically incorrect. I suggest: Actions needed before proceeding with system installation.
As noted above, there is a lot going on just in the background that I don't recall seeing with the old Live, for instance:
On boot, user is asked to select language, which also defines the keyboard. But the keyboard should be a separate step. For example, I might have a Brazilian Portuguese keyboard, but want UK locale. In this case, I have a UK laptop, chose English language, and I have got US keyboard layout, which is different from UK. Pipe comes out as >.
In my view this keyboard selection should include all possible options, as in the classic installer, not just a selection of some common ones. There are several for each language, and it makes a big difference. Especially for users not using persistence, fixing this manually after boot is an unacceptable hassle.
I launched the installer, but haven't actually tried it out yet. It looks nice, though. How does it decide whether to install lilo or elilo? One minor thing: the text @Actions needed ... @ etc is gammatically incorrect. I suggest: Actions needed before proceeding with system installation.
As noted above, there is a lot going on just in the background that I don't recall seeing with the old Live, for instance:
Code: Select all
one[~]$ df -h
Filesystem Size Used Avail Use% Mounted on
none 935M 9.6M 926M 2% /
/dev/sdb 791M 791M 0 100% /live/media
/dev/loop0 206M 206M 0 100% /live/modules/01-core.slm
/dev/loop1 179M 179M 0 100% /live/modules/02-basic.slm
/dev/loop2 316M 316M 0 100% /live/modules/03-full.slm
/dev/loop3 2.0M 2.0M 0 100% /live/modules/04-common.slm
/dev/loop4 33M 33M 0 100% /live/modules/05-kernel.slm
/dev/loop5 19M 19M 0 100% /live/modules/06-live.slm
unionfs 755M 755M 0 100% /live/system
unionfs 1.7G 765M 926M 46% /live/union
unionfs 1.7G 765M 926M 46% /bin
unionfs 1.7G 765M 926M 46% /boot
unionfs 931M 0 931M 0% /dev
unionfs 1.7G 765M 926M 46% /etc
unionfs 1.7G 765M 926M 46% /home
unionfs 1.7G 765M 926M 46% /lib
unionfs 1.7G 765M 926M 46% /lib64
unionfs 1.7G 765M 926M 46% /media
unionfs 1.7G 765M 926M 46% /mnt
unionfs 1.7G 765M 926M 46% /opt
unionfs 1.7G 765M 926M 46% /root
unionfs 935M 332K 935M 1% /run
unionfs 1.7G 765M 926M 46% /sbin
unionfs 1.7G 765M 926M 46% /srv
unionfs 1.7G 765M 926M 46% /tmp
unionfs 1.7G 765M 926M 46% /usr
unionfs 1.7G 765M 926M 46% /var
tmpfs 935M 332K 935M 1% /run
devtmpfs 931M 0 931M 0% /dev
cgroup_root 935M 0 935M 0% /sys/fs/cgroup
/dev/sda3 14G 12G 738M 95% /run/media/one/Data
/dev/sda5 9.7G 8.3G 921M 91% /run/media/one/622161b3-e88d-43ce-8ab5-08073d5e0824
one[~]$
Re: Salix Live Xfce 14.1 beta1
Experienced a small problem...
Some strange characters are sometimes appearing around a file name in a reply to a bash command :
EG
In my 'vim' editor they show as codes :
Any comments?
Some strange characters are sometimes appearing around a file name in a reply to a bash command :
EG
In this mail most of these characters are not shown the same way as on the command line. (Only "â" is showing)one[~]$ rm squashfs-root/home/one/.gvimrc
removed âsquashfs-root/home/one/.gvimrc~â
In my 'vim' editor they show as codes :
.â<80><98>squashfs-root/home/one/.gvimrc~â<80><99>
Any comments?
Re: Salix Live Xfce 14.1 beta1
ikke, what locale do you use?
I'm not sure whether it makes any difference (to this, or to anything else) but the intention is for you to use the normal path, in this case, ~/.gvimrc.
I'm not sure whether it makes any difference (to this, or to anything else) but the intention is for you to use the normal path, in this case, ~/.gvimrc.
Re: Salix Live Xfce 14.1 beta1
Thank you for your reaction.
Thank you.
You made me think. And I found what was wrong: the xfce4-terminal didn't have UTF-8 encoding. Problem solved!mimosa wrote:ikke, what locale do you use?.
For your info : I was just updating an home made module.I'm not sure whether it makes any difference (to this, or to anything else) but the intention is for you to use the normal path, in this case, ~/.gvimrc.
Thank you.
Re: Salix Live Xfce 14.1 beta1
dd the iso to a usb stick and did a successful legacy boot into Salix Live Xfce. That's as far as I got.
edit: found out that my desktop system boots in CMS mode and when I did boot SalixLive it was actually in legacy mode, not uefi.
edit: found out that my desktop system boots in CMS mode and when I did boot SalixLive it was actually in legacy mode, not uefi.
Last edited by laprjns on 26. Sep 2014, 18:18, edited 1 time in total.
Reason: I was wrong, it did not uefi boot,
Reason: I was wrong, it did not uefi boot,
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"
Re: Salix Live Xfce 14.1 beta1
This one: salixlive-xfce-14.1-64-beta1.iso MD5 matchedJust mount iso image and copy everything to usb. Then cd to boot/syslinux folder on usb and run sudo sh install_on_usb.sh script to make the usb bootable.
Tried this way and got "usr/bin/startx: line198:can not create tempfile for here document: permission denied :
and ...................... "usr/bin/startx: line215:can not create tempfile for here document: permission denied "
Tried again with dd and got the menu-selected English-selected persistent-and it started up fine, but did not save anything. Made sure the save session was checked and tried restarting from the regular space on the left(Menu) and the other button on the right side. I must be missing something on persistence.