Quote from: fatmac on May 22, 2013, 02:48:38 PM
Not quite sure if this will be relevant to your problem.
Being a first timer to VSIDO, I found problems with the installer.
What I did was open a tty, sudo su to root, run fdisk /dev/sda, deleted all partitions, created a new empty dos partition label, created new partitions, wrote them out to disk, went back to X & re ran the installer, & it worked for me. (May21 64bit)

Yes, that would work. What you actually did, was to delete all partition, and converted your disk to dos instead of gpt. The problem is that the installer doesn`t recognice partitions on a gpt-disk. It`s a issue of remastersys. The developer wouldn`t support gpt and/or EFI, because he personally didn`t see any need for it. He thought that it was something that would blow over, instead of becoming the new inddustry-standard like it without a doubt is turning out to be.

Anyway, If I wanted to start from scratch again, I could blank my harddrive, convert it to ms-dos, create all the partitions I would like to have, and then install VSIDO. No problems with that. My issue is that I`m going to install VSIDO into a SSD where I`m already running 3 other distros on GPT. It`s not possible to mix gpt and dos-partitions on the same disk, so therefore I have no way of installing VSIDO into my system as it is.

I could convert to dos, and use only dos-partitions and bios-boot, and that way I would be able to run all my distros on the same hdd. But I feel it gets totally wrong to change all my other distros to use old technology, just to be able to install VSIDO. Especially when VSIDO is based on Sid, and therefore should be able to use all the newest standards.

But it`s not a VSIDO issue. If Vastone gets the Debian-installer to work with VSIDO, then the problem is solved, and VSIDO will become the cutting-edge distro that it is in all other regards..... Then it also will be possible to install VSIDO without a swap partition, and it will be possible to set mount-points for existing partitions during install. Everything will automatically fall in place with the Debian-installer. Then VSIDO will be able to do a native uefi/gpt install ootb...

But personally I like best the installer that Crunchbang and lots of other Debian-distros use. It`s perfect... Easy and flexible..., even though it can not do a uefi-install ootb. I could live with the Crunchbang installer in VSIDO. LInux-bbq is another distro that`s very smooth to install. Maybe Vastone could check with machinebacon how he does it, because linux-bbq is very easy to take snapshots of and create new iso-images, kind of like with remastersys, but bbq has no issue with gpt or any swap requirements, because they use the easiest and best installer that exists.

Quote from: VastOne on March 24, 2013, 02:06:50 AM
Does everything have to be so serious all the time?

I am tired, just tired.. It is suddenly like I can't do a damned thing right

This thread is called a little feedback, and I appreciate the opportunity to give back a little of my own

I did not build this for any one individual, but to try and accommodate several needs.  If I happen to like Fluxbox and think OB is very lacking, that is no new news to anyone.  I have never hid my dislike of OB, but that does not mean I would ever drop it.

What I do expect is for people who do like OB to champion it, for people who do like conky to champion it, for people who do like tint2 to champion it and of course for anyone who likes VSIDO to champion it too

I fully understand. You should continue to develop VSIDO in the direction that best serves your needs and your goals for the distro, whether it`s to best suite your own needs and wants, or it is to reach a bigger crowd and perhaps getting a little commercial, reselling hosting, be sponsored, accepting donations and/or have a little shop like Crunchbang.

You have to take care of your own interests of the distro, so that you don`t end up like Fragadelic in Remastersys. As long as you`re not commercial you shouldn`t be so concerned with what the users wants, because most people here are able to install and configure a DE/WM themselves, if they are not happy with whatever is the default at the moment. But I guess it all depends what your intentions are... Please others, or please yourself first, or something in the middle... It`s your distro, do it your way, and those that want`s to use it... do just that...

But now I was serious, and you are quite right, everything hasn`t got to be so serious. This should be fun. After all, it`s our free-time we are using on this. If it`s not fun, then it`s simply not worth it... Just my 2 cents...

OK. That`s nice. I guess you need another solution anyway, because OS4 continues remastersys, and they will without a doubt fix the efi/gpt-issue, but it looks like they are on a standstill, awaiting that Fragadelic releases  the source code.... http://system-imaging.blogspot.no/

Hi Vastone,

I`ve tried the newest ISO, I never give up, as I really want to run VSIDO. Well, I booted the live-cd with some adjustment to the kernel-parameters. I`m used to that, and need to do it for all new kernels, so that`s ok. Not a VSIDO-issue, not a Debian-issue, but a Linux-issue that applies to every distro with new kernels on my hardware.

As for the installer, I see that swap is still required, and that`s fine. I created a root-partition, and a swap-partition, but when I closed GParted, the installer couldn`t detect any swap, and I had no other choice than to quit the installation. I assume that the issue is as before, that the installer(remastersys) doesn`t detect gpt-partitions. I`m, not using EFI anymore, but I`m still using GPT, and that seems to be incompatible with the VSIDO-installer/ remastersys. If anyone has successfully installed VSIDO on a GPT-disk, then I would like to know how they did it, besides the obvious, which is to convert the disk to MBR. I would do that if I was to run VSIDO exclusively on my disk, but as we all know. I`m running several distros, and several installs of the same distro...

So just give me a shout if at any point there are changes in the installer or remastersys, that makes it likely that gpt-partitions will be detected, and I will have another go at it..., because I really, really like VSIDO, and want it to be my primary xfce-distro

I`m sorry Jedi. You are clearly not updated. That ship has sailed. The big ones like Ubuntu and Fedora has already swollowed that camel, and are on board with gpt, efi and even secure boot. Even pc-distributors like Lenovo is producing pc`s with pure efi-bioses, and for most of them it is possible to disable secure boot, and some of them adds legacy support as a secondary option, but in a few years, nobody will produce pc`s with a ordinary bios, and the legacy support will disappear. You might as well swollow your pride. This is a lost cause. Anyway, I just installed linuxbbq, which had no issues with either gpt or efi. Installed perfect. If you want to do it the oldfashioned way, thats fine, but then this is no place for me, because I want to take part in the future, not row a sinking boat...

Arch, Gentoo, Fedora, Debian, and you name it, they are all embracing gpt and efi, and the only reason that It doesn`t work in VSIDO, is that the developer behind remastersys still lives in the past.

Can ssd work fast and fine with MBR? Yes, of course. I`ve done it myself because I knew that it would make distro-hopping a bit easier. But that`s beyond the point. Now I`m settling for a few installs on my ssd, and then I don`t take the other installs back to the past, because remastersys has decided to stay behind...

Besides, you are totally forgetting that people are dualbooting Linux with Windows. Very few are pure linux-users, and Windows 8 makes gpt and uefi the only option. Any distro has to be able to coexist with the latest Windows-edition. Or it will alianate anyone that do a little gaming now and then...

Anyway, I`m not going to hazzle you any more. I`ve moved on to BBQ, which supports my preference in this regard. I guess that`s why linux is so nice. There is always an option to use something that`s more suited for each and everyone of us. Now I`m leaving the building, and won`t be bothering you any more...

I`m replying to myself, as this will solve me a lot of debugging and work that is doomed to fail.

http://www.remastersys.com/forums/index.php?action=printpage;topic=2612.0

"Title: Re: Remastersys EFI version
Post by: fragadelic on September 14, 2012, 10:25:15 PM
At this time I have no plans to do anything with EFI and will wait to see what happens.  I have no efi enabled computers nor do I plan on getting any.

If debian mainline or ubuntu go efi then I will need to look at it.  At this time there is no need and I don't have time to support yet another version or 2 of remastersys for these rare cases(for now).

I also have no plans on purchasing a valid key and letting everyone and their uncle have it and reuse it.  I don't know much about efi as there has been no need for it but I will say for sure that if a time comes when you have to have a purchased registered efi key or whatever, then remastersys will no longer be developed and it will be legal reasons stopping it."

I guess that this means that it will be no vsidoing for me on my ssd, but I can install it on an external disk and boot that one in bios-mode. But I don`t want to take my two other installs back to the past, to be able to install VSIDO.

I really like VSIDO, but no gpt is a dealbreaker for me. Now it`s GPT and EFI that sets the standard. MBR and bios-mode is of the past. More and more new pc`s are not able to bios-boot at all. Clinging on to this old structure, is a lost struggle. GPT has been here a long time, and EFI is also starting to be the new default. Any system that requires mbr and bios-mode, is a system of the past. Regardless of how cutting-edge everything else might be.

Well, it`s been a while since I tried bbq. I`ll have to fill the space I cleared for VSIDO, and I have 3 alternatives, Arch, Gentoo and bbq. I think I choose the easiest one... But I will head back to VSIDO when and if Remastersys fully supports efi and gpt, or when VSIDO has choosed something else than Remastersys:)

Quote from: jedi on April 10, 2013, 09:07:33 PM
@ew, I've never tried another distro install using GPT.  My profound fanaticism for VSIDO is showing here!  The linked articles your reading regarding Trim, are over 2 years old.  The firmware for SSD's has changed drastically in those 2 years.  Also the Kernel after 2.6 has totally changed and improved in it's handling of Trim.  We are a dozen plus iterations past 2.6, and the FSTAB way of doing it has been the best I've seen.  I totally toasted an SSD drive that was manufactured in 2009 by bench mark testing it for writes/reads/deletes in the first test I ran on it.  The same bench mark tests on the mSATA SSD drive I'm currently running has withstood that same test more than 10 times in a months time.  The last 2 SSD drives I've owned, are a 256Gb LiteOn running Windows 7 Ultimate now in my wifes laptop, and in this laptop, a Mushkin Atlas 240Gb mSata SSD drive.

As I said in my first post, drives that are NEWER than 2 years old are better firmware enabled and thus support for Trim is better.  (along with the much improved Kernel support for Trim now.)

In the end, it is a matter of opinion I suppose, as to best practices.  I've been running Debian based distro's for the last couple of years, including Ubuntu and #!.  However, my sojourn into the UEFI/GPT world just started, and I'm willing to learn!  My failures with GPT are in my opinion based on the fact that I don't know how to correctly set it up in the BIOS to use the EFI method of booting in UEFI mode, which is the only way currently to utilize GPT.  Legacy BIOS will not support GPT I've been told...  I also know that GPT see's ONLY Primary partitions.  (Up to 128 bootable Primary partitions, which is where my fascination lies)

The issue on the LiveCD installer with VSIDO is most probably an issue with the Remastersys installer as VastOne said.  He is currently talking with the developer of Remastersys to try to get some changes made.  Most notably the ability to install without having a Swap partition.

I'd love to hear how you setup the EFI bootstrapping in BIOS to enable UEFI to boot Linux using a GPT formatted disc!

You probably are correct about trim and that stuff. I just do it with fstrim, because my setup isn`t permanent yet. I don`t know which partitions and which distros I will end up wit yet. Therefore I`m focusing on more pressing issues, and not engaging in the ultimate tweaking yet.

But as for SSD and swap, it`s not just the frequent writes that are a issue, it`s also the fact that ssd`s tend to be smaller, and the space is more limited. Therefore, with 8 GB RAM, it`s totally meaningless to use space for a swap partitions that actually never will be used. I manage fine with 2 GB and no swap. With 8 GB there isn`t even a questionmark. Swap is not needed. Also, with SSD I`m cold-booting in 10 seconds, and therefore never use hibernation. I turn the laptop off.

As for EFI, bootstrapping and all that. I don`t mess with it at all. Ubuntu does it right out of the box. If you install Ubuntu first, it`s easy. Boot the installation-media in uefi-mode, create a 200 mb EFI-partition, a root partition, and other partitions you want, just leave the grub choice as the default choice is, because regardless of your choice, Ubuntu will place it`s bootloader in efi, and you will be able to uefi-boot withoiut setting up anything at all. Ubuntu is also able to handle uefi secure boot, right out of the box.

Read this page(it`s very easy): https://help.ubuntu.com/community/UEFI

If you first have installed Ubuntu in uefi-mode and the ubuntu-bootloader is present in efi, then it`s just to install other distros as you always done, don`t think about efi or anything else. Create a root-partition, and the partition you want, let grub be installed to the root-partition. When installed. Boot Ubuntu, run sudo update-grub, and Ubuntu will add an entry for the other distros in the Ubuntu bootloader. Forget all the advanced stuff about efistub, efivars an all that, Ubuntu handles everything. All you need to do, is to create a EFI-partition. Thats it.

Quote from: VastOne on April 10, 2013, 12:06:50 PM
Yes the VSIDO installer sucks in some ways, other people say it's the best they have ever seen... I do know it is by far the fastest I have ever seen

I am wondering if what makes it work in #! and in Ubuntu and other distros is an application that is installed that is missing in VSIDO... This could very well be the cause

OTOH, I am disturbed by some recent developments with remastersys and it's code and do have another installer that I can use.  It is the LMDE installer and once I get the LMDE branding removed from it and replace it with VSIDO, I can use it along with the same installer we have now for people to test

Okidoki. I will try to find a way to install it anyway. I lost my internet connection last night, my isp obviously had some new firmware to force on me, that completely messed up my network. I`ve just recovered my network, so I haven`t been able to do any debugging yet. I will try to find the cause of my issue now... And as for the VSIDO installer, it`s very easy, and many people might like that. But I`m of those that like to have a lot of options available to me, and I don`t mind that the installer is so advanced that the common man isn`t able to get trough it. If you manage the Debian netinstall, then you manage all installers. I doubt that anyone that is trying VSIDO, is looking for something easy. Those people are over at Ubuntu or Linux Mint. That`s just as easy as Windows, but we generally don`t like the removing of options to make it easier for those that do not know what they are doing:)

Quote from: ozitraveller on April 10, 2013, 02:57:42 AM
jedi have you outside of VSIO  before?

I'm using it, but I did a debian sid install. It just worked.

It does that with every distro. It has to be the VSIDO live installer that isn`t handling this as it should. Nothing wrong with VSIDO, it`s just an insufficient installer that lack flexability. It`s normal to be able to do a lot more during install. Like choosing what partititions you want, set mount points, and select which partitions to mount at boot, and in the other installers like the one Crunchbang has(the same installer as with 80% of the distros I try), it`s possible to go back and redo steps. With the VSIDO installer you have to quit the installer when for example swap isn`t found. Whether or not I get it to work, I still will dislike the installer. But I guess it`s part of remastersys, and therefore there probably nothing to do about it...

Quote from: jedi on April 10, 2013, 02:33:28 AM
And on another note;  I should be honest here and mention that I've tried thrice (three times) to use GPT and failed!  If your successful at installing with your disk setup as GPT instead of msdos, I'd be very appreciative for some pointers.  I'm assuming something has to be done at the BIOS level that I haven't accomplished yet.
Anyway, if you are successful at getting VSIDO up and running using GPT let me know.  This is not a short-coming of VSIDO, it is a lack of knowledge of GPT installing on my part.

OK, then I guess that`s where the problem is. But I think you are wrong when you blame it on your knowledge of gpt, because I`ve used gpt for a very long time, and have never had a issue getting it to work. Ubuntu does it automatically, you don`t have to think about anything, the same with CrunchBang and at least 20-30 other distros that I`ve tried on gpt. Uefi could cause issues with some, but not gpt. Now I`m efi-booting, but gpt works just as fine with mbr(bios-mode). If it is a issue, then it is a issue in VSIDO or the VSIDO live-installer, because gpt is the default today, and should work right out of the box.

If both Ubuntu and CrunchBang are running fine on my gpt-disk, then the issue has to be with.... The difference is the installer, it would probably have worked perfect if VSIDO just the same installer as for example Crunchbang does. It`s also a more flexible installer...

Quote from: jedi on April 10, 2013, 01:38:21 AM
The grayed out Logical and Extended is because your disk is setup as GPT.  GPT can have many, many, partitions (did I mention GPT could have a lot of Primary partitions?) all of which will be Primary.  On a disc that is setup with msdos (the default in gparted) you can only have 4 Primary partitions.  That is why the Logical and Extended are there, for msdos setup discs.

As far as SWAP on an SSD, todays SSD's are basically 'write-proof' so to speak. (IN MY OPINION) Any drive newer than a couple of years will be this way.  The SWAP part of the VSIDO install is because of the Remastersys scripts as VastOne said.  Once installed you can indeed remove it.  (I have my swap file on a separate 7200rpm hdd so if I want hibernate I can.  Hibernate requires at least the amount of physical RAM to be enabled in SWAP)
If you are worried about 'writes' to the SSD, you can also edit the fstab and load several different folders/directories to RAM via the tmpfs setting.
You'll also want to be sure to enable TRIM in your fstab file on the main partitions, i.e. / and /home and any other separate partition you setup on your SSD.
In the /etc/fstab file you'll see to the right of each of your partitions, a section that says - errors=remount-ro 0 1
You'll want to change that in order to enable Trim support by changing the part that says - errors=remount-ro 0 1 to say noatime,discard 0 1
That enables Trim.

I load the following folders/directories into RAM to save 'writes' to the SSD
/tmp
/var/log
/var/tmp
/var/spool
(make note that if you use anacron, then loading /var/spool into RAM will prevent it from running)
Here is what a typical line looks like in /etc/fstab once it's added to the file;
tmpfs        /tmp           tmpfs      defaults,noatime,mode=1777    0 0
tmpfs        /var/log       tmpfs      defaults,noatime,mode=0755    0 0
tmpfs        /var/tmp      tmpfs      defaults,noatime,mode=1777    0 0
tmpfs        /var/spool    tmpfs      defaults,noatime,mode=1777    0 0

Doing this will load the aforementioned folders/directories to RAM, thus saving 'writes' to you SSD.

If you have any more questions, don't hesitate to ask.  Remember some of this stuff is just "OPINION" and others may recommend totally different settings. These are settings I use and they work for me!  Having an SSD drive is like switching from an old AMC Gremlin to a brand new Ferrari!!! Enjoy...

I have two other installs that works on this ssd, Ubuntu and #!. Trim is working fine for those. I`m not using online discard(fstab), because I read it was not recommended. I use the command "sudo fstrim -v /" in a shell script, so that I only have to use the command "trim" when I want to do it. I also could set it up as a daily cron job, but I see no need to do that. I don`t forget to run trim now and then. I followed these advices, and there it states that online discard is not recommended. Don`t know why:http://www.webupd8.org/2013/01/enable-trim-on-ssd-solid-state-drives.html

As for the Primary Partitions. I know that there isn`t a limit on 4 with gpt, and gpt was fully intentional because I`m uefi-booting and have no issues whatsoever doing that. I just thought that perhaps the VSIDO live installer have a issue with that, because after creating a etx4-partition and a swap partition in gparted,(and apply the changes of course), then I close the Gparted window to continue the installation,and get to the choose swap part, but then I only get the option to quit the installation.... No swap to choose from.

I registered a difference when trying to install from the lates install media. On earlier versions there has popped up a lot of windows with partitions being mounted, but no partitions gets mounted when I do it in this version.  Just to test, I tried installing Bodhi on the partitions I created for VSIDO, and that was no problem... So I don`t know whats off. I only know that I have to quit the installer because swap isn`t detected, even if it is there....

Quote from: VastOne on April 09, 2013, 11:04:18 PM
The installer is part of the remastersys build scripts that is created by fragadelic.  I will post on his forum to ask if he can develop and option to bypass the need for a swap and report back his thoughts about it

Several users have installed to SSD and will respond here soon I am sure

It`s probably not a big issue, because I can remove the swap after install, use it for something else, or merge it with the root-partition. My issue is probably something else. I shrinked my Ubuntu-partition and created an ext4 partition, and a swap-partition, but when closing gparted, no swap is found, and the only option is to quit the install. I`m not sure what`s wrong, because the partitions looks fine in gparted, and my shrinked Ubuntu-installation still works fine. Perhaps it has something to do with the fact that I have 5 primary partitions, i had 3 from before, EFI, and one root eavh for Ubuntu and CB. Gparted didn`t offer me to create the VSIDO partitions as logical. Both logical and extended was greyed out, so I had to choose primary. Well, I guess I can test it by trying to install something else in those partitions. Just to know if it`s a VSIDO-issue, or if there is something off with my partition-setup. Off I go:)

I`m currently trying to install VSIDO, and ran into problems with the installer. It seems like having a swap is required, and installing on an ssd as I`m doing, you really don`t want no swap... You want to swap only in RAM, to prolong the life of the SSD. Well, I spilt the partition to create a swap partition(can remove it later), but the installer now refuses to detect the swap, and I have to quit the installation. I have rebooted several times, but same things happen. It doesn`t detect my swap and I have to quit. I will find a way regardless. I have booted up in Ubuntu and prepared the partitions from here, hoping that the VSIDO live installer will detect it at next attempt. But you should really think about making the swap optional in the installer, because less and less people use it. Just my 2 cents, if I succeed with my next attempt to install it, I probably will think that this is a minor issue:)

Been visting a few times, but left again because my intel hd graphics didn`t like the new kernels. After months of struggle and ranting in the #!-forum, Debian Joe asked me if it was my intel graphics that was the issue, and in that case he had posted a workaround some time ago. Off I went with little faith, but it turned out that the fix worked perfect for me. The worst part is that it was an easy fix. I should have been able to solve it myself. Well, I cant help that I`m a bit slow, but that fix prepared me to haunt the VSIDO-forum. If you need to blaime anyone, blaim Debian Joe. Without him and his workaround, I wouldn`t have been here now:)

Anything about me? Well, im well into my midlife crisis, and whether Linux is the solution or the cause, I guess time will tell. I`ve worked with computers for 30 years, mainly with hardware and repairs, and of course also software related issues, but only on various MS-OS. Fiddled a bit with html-coding and php, but nothing advanced. Then W8 came, and for my personal use I didn`t want to participate in an OS that looked like the teletubbies was on vacation in legoland, so then I started to experiment a little with an ooooooooooold laptop, and therefore searched for lightweight distros, and the first I tried was WattOS, which was fine.

The next one I tried was Peppermint, and I liked even better, and then I saw the famous #!-Disclaimer, and just had to try that, and felt instantly at home. Been there since, but of course multibooting and hopping between distros like crazy. So I`m new, but I`ve been trough a lot. My route is probably different than most. I didn` start out with Ubuntu or the big ones, but I went directly from Windows to openbox, which I`m happy that I did, because If I had started with Ubuntu, then I probably never would have discovered all the smaller exiting Debian-based distros.

Well, I guess that`s it. I`m a linux-noob, but relatively experienced for my short time in the Linux-world. You could say that I`m addicted. It`s only my two dogs that can get me away from the pc now and then. I don`t even watch television any more, and have no time for gaming. It`s linux, linux, and just linux..., and I don`t seem to get tired off it, like I`ve done with other all-consuming hobbies. My problem is that I never can do anything halfways. Either I`m commited, or I`m not:)

I read the topic on #!, and it was really interesting. As a newbie in #! I didn`t really know the story behind #!, nor Vastone`s background, and it made me even more interested in VSIDO. Downloading the ISO now. Wil not mess it up with Gnome3 as I initially intended. I think I`ll keep #! with a well configured and working openbox-session, and my own awesome Gnome 3 Session. In VSIDO I intend to do something different. Not sure what yet, but that`s whats exiting... I probably will use xfce, tint2 and openbox together, as I suppose it is now, but try to put my own twist in there somehow:)

Anyway, I`m looking forward to start vsidoing a little. It better be good , because I intend to replace Ubuntu with it, on my main laptop with ssd, and there`s only two spots in total... 120 GB split on two distros. It will be interesting tonight, because it`s an uefi install, and Ubuntu acts as the master-grub now, so VSIDO must take Ubuntu`s place in EFI, and detect Crunchbang and add an entry for it in EFI. I guess there is a lot that can go wrong, but in worst case, I just have to start from scratch. First install VSIDO, then Crunchbang.