1.- Can the siduction installer partition the disks using LVM? If not, will it be able to straightforwardly install on a system with preconfigured volumes?
I think to remember that the aptosid installer was rather limited to that respect.
2.- I have been happily running plain Sid in my laptop for months without major issues (just some minor problems with Xfce at certain point and the incompatibility of the proprietary Nvidia drivers with kernel 3.10). Being a sidux user for several years, I used to faced similar and even worse issues. My (innocent) question is:
Is there a real advantage in terms of stability in running some Sid derivative such as siduction or aptosid?
3.- Are there other advantages?
Zitat von: "mirix"...
Is there a real advantage in terms of stability in running some Sid derivative such as siduction or aptosid?
No derivative will ever be more stable than Debian/sid is as they aim to be 100% Debian/sid compatible. But they try to help the user to circumvent problems. This makes it not only look more stable.
Yes, this answer is contradictory. But it explains very well what you may expect: *All* Debian/sid pitfalls but also warnings, hints, suggestions, advices and possibly fixes for those who read and follow the respective section of the particular forum.
Zitat von: "mirix"...
3.- Are there other advantages?
What they offer is
- a (Debian/sid-) installer
-
help to avoid or solve problems
- temporary fixes (such as nvidia fixed for 3.10)
- artwork (if you feel it is important)
But these aren't advantages over Debian/sid. I consider them being "plug-in" features to help out Debian/sid.
siduction has a fine and excellent experimental-repo and KDE-next is availble too.
OK. I will give siduction a try on my new laptop when it arrive, depending on the answer to the first question:
Can the installer handle preconfigured LVM volumes?
In addition, I would also like to ask you why would you use siduction rather than other Sid derivatives such as Semplice or Vsido:
http://semplice-linux.org/
http://vsido.org/index.php/topic,12.0.html
I will try siduction first because:
1.- It is more current than Semplice.
2.- I am used to XFCE and like it.
3.- They said the towo-kernel is quite sound (and more current than the one from Semplice).
4.- It is an aptosid fork and it should therefore be of good technical quality; plus the aptosid manual is excellent.
5.- It is supposed to be more community-oriented than aptosid is.
6.- Having the experimental repos mentioned by Lanzi available sounds great.
7.- There is little information available about Vsido and it seems to be a new one-man project...
By the way, you can also install plain Sid directly from an official Debian iso:
https://wiki.debian.org/InstallFAQ#Q._How_do_I_install_.22unstable.22_.28.22sid.22.29.3F
I have used this method:
Use netboot "mini.iso" image. You will find it on any of the Debian mirrors under debian/dists/unstable/main/installer-*/current/images/netboot/mini.iso. During the installation choose "Advanced options" -> "Expert install". In the step "Choose a mirror of the Debian archive" choose version "sid - unstable".
Zitat von: "mirix"...
In addition, I would also like to ask you why would you use siduction rather than other Sid derivatives ...
It's Debian. The rest is history, habit, knowing people (over the net).
BTW, I hate each new Debian/sid derivate (as much as I liked the simple semplice artwork). I wonder how popular Debian/sid would be if all these duplications of effort would be orchestrated. Unfortunatly I have no clue how to contribute to this fight against a windmill.
So which derivate to install? One of them.
siduction developers are also experimenting with systemd, which we hope will become a default in a later release. Debian moves slowly changing it's defaults. Systemd is in the Debian repos, and, anyone can choose to use it or not, but, using a distro like siduction means you'll see the newest technology adopted faster as default, and a community that will help you with the transition.
Zitat von: "mirix"
Can the installer handle preconfigured LVM volumes?
I guess you are going to tell us about that! :lol:
Seriously, as you already know, the Debian innovations first appear in sid, and so we siduction users often find ourselves helping each other to get past a new challenge. As GoinEasy9 said, some of us are already converted to systemd (I have 6 machines booting via systemd), and towo does a great job with special packaging issues that come up with the new video drivers and such. Santa has built the latest KDE for us when it was first available and before other sid users had access. The kernel-remover utility (came from aptosid/sidux) is very handy for us old guys that can't remember the names of the packages that have to be removed. So you can expect the usual sid challenges, and friendly help here to collaborate on solutions.
mirix, there is a (german only :( ) entry in the siduction wiki explaining how to use the installer after LVM is configured first: http://wiki.siduction.de/index.php?title=Siduction_unter_der_Kontrolle_des_Logical_Volume_Manager_installieren
From that I would say it works, but never used LVM myself.
Other posters said it before, siduction is sid plus some extra spices and a community (forum/IRC), so you would do nothing wrong if you already used sid. Have a look at http://packages.siduction.org/ , you can see siduction sometimes provides already the "next" versions of XFCE or KDE, for instance.
When you know the aptosid manual already, the siduction manual will look familiar to you :), have you seen the link to the manual in the left menu?
Semplice is a nice one, but as far as I can tell a lightweight openbox only, so not for me KDE-addicted one. About Vsido I cannot say something, looking at your link it seems to use the siduction sources plus sid and some experimental.
Zitat von: "mirix"1.- Can the siduction installer partition the disks using LVM? If not, will it be able to straightforwardly install on a system with preconfigured volumes?
I think to remember that the aptosid installer was rather limited to that respect.
...
Sidu-disk-center should be able to partition disk using LVM, although I always prepare LVM partitions with KVPM. The siduction installer would then install into these partitions.
Why should the aptosid installer be rather limited? I used it lately. No concerns.
Best regards,
Bequimão
OK. Thanks. I will give it a try as soon as the machine arrive. This probably means no sooner than one week...
OK, I have downloaded the Firestarter 64-bit LXDE image and burned it to a CD.
Then I tried to use sidu-disk-center to partition the drives, but it said: command not found. Then I tried to install it, but it was already installed.
Not knowing what is the right command to invoke it, I ended up setting up the partitions from the command line.
The installer fails when mounting certain LV:
E: Mounting of /dev/mapper/VolGroupBackup-lvbackup:/backup failed. Some messages from mount: mount: can't find /fll/hdinstall/backup in /etc/fstab or /etc/mtab
O: siduction-installer ended abnormally
/etc/fstab does not exist, whereas /etc/mtab contains:
/dev/mapper/VolGroupBackup-lvbackup /tmp/partinfo-mount/p008 ext4 ro,relatime,data=ordered 0 0
/dev/mapper/VolGroupSSD-lvroot /fll/hdinstall ext4 rw,relatime,data=ordered 0 0
/dev/mapper/VolGroupSSD-lvhome /fll/hdinstall/home ext4 rw,relatime,data=ordered 0 0
Should I tinker with those files or should I leave lvbackup unconfigured and then edit fstab after installation?