mralext20 / linux-wbfs-manager

Automatically exported from code.google.com/p/linux-wbfs-manager
0 stars 0 forks source link

Ehancement: Read /dev/other_name_partitions #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Let your drive be /dev/anyname and not /dev/sd?? (e.g. with udev rules)
2. Try to choose it in the gtk interface
3.

What is the expected output? What do you see instead?
I want to choose it in the GUI, but I cannot choose it because it is not
listed.

What version of the product are you using? On what operating system?
latest svn (13.07.09), gentoo

Original issue reported on code.google.com by jbuec...@gmail.com on 13 Jul 2009 at 8:25

GoogleCodeExporter commented 9 years ago
I'm not sure how to fix this... is there any easy way to list all block devices?

Or maybe we should have a config file specifying the devices to list (the 
default
being /dev/sd*)?

Do you have any suggestions?

Original comment by ricardo.massaro@gmail.com on 14 Jul 2009 at 3:07

GoogleCodeExporter commented 9 years ago
Version 0.1.10 tries to solve this, but I have no way of testing on gentoo. 
(The way
it's solved is by reading devices names from /proc/partitions -- I'm not sure 
if it's
aware of udev).

Could you please test version 0.1.10 to see if it solves the problem?

Original comment by ricardo.massaro@gmail.com on 18 Jul 2009 at 5:55

GoogleCodeExporter commented 9 years ago
>/proc/partitions
the file exists on gentoo...

> I'm not sure if it's aware of udev
No, and that could be a problem: Since you only symlink the partitions with the 
udev
rules, it should be ok. 
But I renamed it: Then, (e.g) in /proc/partitions my usb-stick is listed as sdb,
sdb1,... but in /dev/... this files do not exist, but the names I gave the 
usbdrive
with udev...

>Could you please test version 0.1.10 to see if it solves the problem?
at the weekend 1.8.09 / 2.8.09. Till then I gave away my hdd...

Original comment by jbuec...@gmail.com on 21 Jul 2009 at 1:00

GoogleCodeExporter commented 9 years ago
>The way it's solved is by reading devices names from /proc/partitions

I think this was not a good idea. Now wether my symlinks nor my hdd-name is 
detected.
Symlinking my hdd was a good workaround for me. I think for special cases a 
config
file is a better solution.

Original comment by jbuec...@gmail.com on 2 Aug 2009 at 12:53