04-14-2015, 06:25 AM
Hello gold-finger,
I think we are in agreement now, judging from both our experiences. The gparted method, by firstly creating a fat32 WITH nominal persistence space AND naming the ext2 part AFTER, seems to do the trick.
I agree that the system appears to get confused with 2 instances of casper-rw and lack of space in the fat32 part to initially set it all up. Proof of this, is my success a short while ago, in resurrecting an old 8gb Silicon Power stick that was giving me all sorts of trouble, including hanging and running slow.This was always a slow stick when new, but it is now quite snappy and useful.
So the lesson here for the time being, is to avoid using gparted to resize partitions, only use it to create them.
Having mentioned the triple unetbootin menus previously, I've now noticed that this new stick is now booting only one instance of the unetbootin menu before the feather logo, so that's a win. This might have something to do with our discussion on unetbootin thinking there are two systems/partitions.
If the stick is plugged into a computer, the file manager will open up two notifications, one being the system and the other the casper-rw partition. Now that the creation of the stick is slightly different, regards the building sequence, unetbootin may have stabilised itself to recognise just one OS. I'm only guessing, though, but I'll take it.
With regard to the stick types, I'm using those tiny Sandisk Cruzer Fit sticks. They are most reliable and available up to 64Gb in size (in fact, I think they now come in 128Gb, but might be wrong on that). They are about 5mm in size, so are perfect to permanently leave inserted and run linux as a live or installed system. They don't poke out the side and my users love them as they can be left in, whilst in transit. A bit dearer than others, though!
Just before I sign off, LL2.4 is supposed to support Bluetooth, but it still does not work. I need to install the PPA and use cschramm's fix to get it working. Maybe my definition of "supports" is incorrect. I expect it to mean OTB, but sadly not the case. At least there is a way to enable it. Have you found this to be the case.
Cheers for now and thanks again!
I think we are in agreement now, judging from both our experiences. The gparted method, by firstly creating a fat32 WITH nominal persistence space AND naming the ext2 part AFTER, seems to do the trick.
I agree that the system appears to get confused with 2 instances of casper-rw and lack of space in the fat32 part to initially set it all up. Proof of this, is my success a short while ago, in resurrecting an old 8gb Silicon Power stick that was giving me all sorts of trouble, including hanging and running slow.This was always a slow stick when new, but it is now quite snappy and useful.
So the lesson here for the time being, is to avoid using gparted to resize partitions, only use it to create them.
Having mentioned the triple unetbootin menus previously, I've now noticed that this new stick is now booting only one instance of the unetbootin menu before the feather logo, so that's a win. This might have something to do with our discussion on unetbootin thinking there are two systems/partitions.
If the stick is plugged into a computer, the file manager will open up two notifications, one being the system and the other the casper-rw partition. Now that the creation of the stick is slightly different, regards the building sequence, unetbootin may have stabilised itself to recognise just one OS. I'm only guessing, though, but I'll take it.
With regard to the stick types, I'm using those tiny Sandisk Cruzer Fit sticks. They are most reliable and available up to 64Gb in size (in fact, I think they now come in 128Gb, but might be wrong on that). They are about 5mm in size, so are perfect to permanently leave inserted and run linux as a live or installed system. They don't poke out the side and my users love them as they can be left in, whilst in transit. A bit dearer than others, though!
Just before I sign off, LL2.4 is supposed to support Bluetooth, but it still does not work. I need to install the PPA and use cschramm's fix to get it working. Maybe my definition of "supports" is incorrect. I expect it to mean OTB, but sadly not the case. At least there is a way to enable it. Have you found this to be the case.
Cheers for now and thanks again!