Hey guys ... Certainly you can ask, pidsley, and what you say does make sense.
Bit of History:
When I came from W2K to Linux (Ubuntu) I had problems even getting a data partition I could use. So I went about doing what I could - searching and asking. I was angry that "I" couldn't mount (at first) partitions I created, and when I finally could I couldn't read/write to them. At that time I had 3 IDE HDD's here and could not use anything but my / & /home combined 30GB partition on hda1, that really pissed me off. Over 50% of hda1 I could not access let alone the other two HDD's that I couldn't even see.
to continue
My /media/5 will be accessible, as user, by all distros - except the No-GUI whenever it goes in.
At one time I had 12 partitions here, and no external HDD so my backups went to their own partition. At least I have an Ext USB HDD to take care of that problem, it only gets plugged in when it's needed. It use to get mounted as soon as it was plugged in, now for some reason I have to physically mount it, I'll get that changed again -when I get time to research how. No, I'm not asking. :)
I hit that problem again with this change, and it has been so long ago that I forgot how to get them to be mine. Now they are empty, they are mine, if I need them they are set up.
When I use the first two partitions for "darkside", media/6 & 7, I will set them up properly in disk-manager and unmount them. But I'll know I can mount them if I want.
Then when a 'test' distro goes in the same process will take place, set them up with disk-man and then unmount them.
The final 16GB partition will be a NO-GUI install when the time comes, and get the same treatment, but it will have everything on the one partition.
None of the above will have access to this system (1 & 2). As long as this works, my wife is happy.
This way - if I want to store something on them until the time comes to put a disto there I can - it's my option.
machinebacon
Code: Select all
26 Aug 13 | 23:34:09 ~
$ ser udisks
p gir1.2-udisks-2.0 - GObject based library to access udisks2 - introspection data
i A libudisks2-0 - GObject based library to access udisks2
p libudisks2-dev - GObject based library to access udisks2 - development files
p udisks - storage media interface
p udisks-doc - storage media interface - documentation
p udisks-glue - simple automount daemon with support for user-defined actions
i A udisks2 - D-BUS service to access and manipulate storage devices
p udisks2-doc - udisks2 documentation
26 Aug 13 | 23:34:29 ~
$ udisks2
bash: udisks2: command not found
26 Aug 13 | 23:34:44 ~
$ sudo udisks2
sudo: udisks2: command not found
26 Aug 13 | 23:34:50 ~
$
Never realized I had that installed ... and it's not working ... I'm guessing on this system I need udisks not udisks2 that BBQ uses. (that's going in tomorrow, hopefully, with darkside)
Update
udisks - installed and works ... tomorrow I read the man page. Looks like it's more powerful than disk-manager, that would be nice - set up some aliases & dump disk-manager.
I am THE resident noob, hands down no discussion. ... and
I wear my soap on a rope.