On 05/21/2017 03:25 AM, Michael Milliman wrote:
On 05/21/2017 05:09 AM, Jimmy Johnson wrote:
On 05/21/2017 12:57 AM, Pascal Hambourg wrote:
Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :
No, you should NOT have deleted the partition, now your partition table
is messed up.
Bullshit. This is just a Gnome error.
Unless you are deleting the last partition your partition table is going
to be messed up. I hope you enjoy your B.S. You can workaround by using
UUID, but personally I do not care for a messed up partition table.
I also call B.S. on this response. The OPs problem has absolutely
nothing to do with the partition table or the UUIDs of the various
partitions. If it did, the system would not have gotten to the point of
starting GNOME. Adding, deleting and resizing partitions, using the
appropriate tools, is relatively save in the modern era. I have, on
many occasions over the years deleted and re-arranged the partitions on
my system to accommodate changing needs and have had no problems whatsoever.
Michael what I'm saying is if you have sda1,sda2,sda3, partitions and
you delete sda2 partition, sda3 becomes sda2 and if you make a new
partition, even in the same unused space it will become sda3. So, in the
end the drive will read sda1,sda3,sda2 and personally I can't live like
that, I have to many systems to tend too. But as it's been mentioned you
can use UUID if your fstab and that reminds me, if you delete or format
a partition the UUID will change, #blkid will give you the UUID's. I
hear your argument, but I say back-up and start over, do it right.
--
Jimmy Johnson
Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15
Registered Linux User #380263
