Salix OS

Hi everyone!

I have just uploaded the first RC for our Mate release. Not too many differences from the beta1 that was released a month or so ago. The very few bugs that were found with that should be fixed by now. This includes:
* the desktop not starting properly in basic mode installation
* firefox being unavailable as an option in the preferred applications tool
* totem not starting due to missing dependencies
* spi misbehaving when piping output instead of just displaying it to the standard output

All mate packages have been upgraded to their latest release in the 1.8.x branch and all other security fixes have been included in this release.

So, please try these out so we can have a final release by the end of the week. It's looking to become a very fine release in my opinion...

Sourceforge downloads and torrents are available:

Salix Mate 14.1RC1 (32-bit, i686)
(size: 739 MB, md5: 1b9d403403f5e5730eb55dabb7800fa0)
http://download.salixos.org/i486/14.1/i ... so.torrent
http://sourceforge.net/projects/salix/f ... o/download

Salix64 Mate 14.1RC1 (64-bit, x86_64)
(size: 754 MB, md5: 8b5a20bb7382bb2362ffff978849aa50)
http://download.salixos.org/x86_64/14.1 ... so.torrent
http://sourceforge.net/projects/salix/f ... o/download

Thanks for testing!

This is indeed shaping up to be an excellent release; all that's needed is some wider testing.

Please see the new testing guidelines on the wiki:

http://docs.salixos.org/wiki/How_to_Beta_Test

Nice to have a mate edition again..

May want to consider having unique boot labels for each of these different additions of Salix. Right now they all use "Salix" as the label and this causes issues with UEFI installs when you already have Salix installed. With the current installers, if you already have a Salix version installed, say Salix XFCE for an example, then in the UEFI boot partition (usually /dev/sda), there is a directory called "Salix" that has the boot information and boot loader (elilo) that boots into Salix XFCE. When you install another addition such as Salix Mate, to a separate partition, it over writes this Salix directory with the information to boot Salix Mate and you lose the Salix XFCE boot directory. If there was a unique label then the installer for the additional version will not over write the existing directories.

I was able to manually install a Salix_Mate directory by copying the existing Salix directory and editing the elilo.conf file to point to the correct root file system partition. Then after editing the file, I ran efibootmgr to add Salix_Mate to the boot menu. Now I can triple boot Win8, Salix XFCE and Salix Mate.

In order to get the installer to have unique labels, I believe that the eliloconfig file in /usr/bin of the elilo package needs to be edited to replace Salix with the unique label.

Here's my current UEFI boot partition directory with a unique boot directory for Salix XFCE (Salix) and Salix Mate: Hope this makes some sense.

laprjns, that's not a bad idea at all, and I think we can do that easily. I had no clue that such a conflict was possible myself. Are there any restrictions concerning those directory names? I could go one step further and name them after the edition + version as well, like Salix-MATE-14.1, but would it work? Or something even longer like Salix-Fluxbox-15.6789? It would require some testing, but I think it can be done.

However, if that's the only thing that's "wrong" with this RC, I won't make new isos just for that... We'll have to postpone it for future releases...

It would also be good to cover the situation where more than one installation of the same flavour and edition is present. I do this all the time (though it doesn't affect me because I don't have UEFI). So some way of creating a unique label would be ideal, maybe including a timestamp in the string or something like that.

gapan wrote:laprjns, that's not a bad idea at all,...

hmm... I'm exceeding expectations again

gapan wrote:Are there any restrictions concerning those directory names? I could go one step further and name them after the edition + version as well, like Salix-MATE-14.1, but would it work? Or something even longer like Salix-Fluxbox-15.6789?

I don't think so. The EFI System Partition (ESP) is required to be a FAT, usually FAT32, file systems so I would think that if the label meets there requirements of a FAT files system directory naming convention then it should work.

gapan wrote: It would require some testing, but I think it can be done.

Well I've got three systems that have uefi firmware (don't call it BIOS!!!), so I'm game

gapan wrote:lOr something even longer like Salix-Fluxbox-15.6789?

This naming structure works. Renamed my Salix_Mate directory in the EFI System Partition to Salix-Fluxbox-15.6789, ran efibootmgr to register the new label, and rebooted. The new boot entry showed up in the boot menu and I was able to boot without problems.

Installed salix mate and all went well, everything working but after reboot the Wicd did not detected my wireless network anymore... then i went to Wicd settings and the wireless interface was wlan1... change this manually to wlan0 and the wireless was back on

This has some explanation?

Installed on 4 computers:









No problems found and checked:
Salix MATE 14.1RC1+MLED


Bonus: ObsidianMetal (X11 Mouse Theme)