[PC-BSD Testing] pcbsd-snapshot-20120605 pc-mounttray test

[Ken Moore]

On 06/13/2012 11:44, user10508 at gmail.com wrote:
> After a fresh boot,
>
> test 1.
>
> The mounttray applet, on gnome-panel notification
> area was ended by clicking on the mounttray icon and then clicking
> on the close tray option on the popup item list.
>
> A pc-mounttray command was issued via terminal which produced the
> following:
>
> Begin terminal output:
>
> [colby at pcbsd-1403] ~% sudo pc-mounttray
> Locale: "en"
> pc-mounttray: starting up
> User detected: "colby"
> File manager detected: "openwith"
> Existing devices discovered:
>   -  "/dev/ada0s1"  ->   "SATA-Device-0" ,  "SATA:::FAT"
>   -  "/dev/ada0s2"  ->   "SATA-Device-1" ,  "SATA:::NTFS"
>   -  "/dev/ada0s3"  ->   "SATA-Device-2" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s4"  ->   "SATA-Device-3" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s5"  ->   "SATA-Device-4" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s6"  ->   "SATA-Device-5" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s7"  ->   "SATA-Device-6" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s8"  ->   "SATA-Device-7" ,  "SATA:::UNKNOWN"
>
> End terminal output.

Are these partitions (ada0s[3-8]) actual partitions with their own 
filesystems that you can mount? (I.E. is this something that you could 
mount and retrieve data from?) If not, I might need to tweak the 
detection algorithm to be a bit "smarter" about what it displays.

>
> A usb flash drive was inserted. A popup notification appeared
> indicating a new device had been connected and USB-Device-0 was added
> to the mounttray item list.
>
> The following new text appeared in the terminal window where the
> pc-mounttray command was issued:
>
> Begin additional terminal output:
>
> New device detected: "USB-Device-0" "/dev/da0s1" "USB:::FAT"
>
> End additional terminal output.
>
> In nautilus, at /media on the file system, a directory entry for
> USB-Device-0 was present. The directory was empty. There was no entry
> for /dev/da0s1.
The mount tray does not create/edit any directories in /media until you 
actually mount the device (and removes the directory when you unmount 
it). So if you want a clean test, you can make sure that there is 
nothing in /media before you startup/mount using the tray.
>
> I mounted /dev/da0s1 on /mnt via the following command:
>
> sudo mount -t msdos /dev/da0s1 /mnt

Did you try mounting the device using the actual tray? Any errors 
displayed when in the terminal then? (Simply click on the device name to 
mount/unmount it)

>
> The mount was successful with some system noise about -t msdos. All
> files and directories were present as expected on /mnt.
>
> Unmounting the file system via:
>
> sudo umount /mnt
>
> was uneventful.
>
>
> Test 2.
>
> In a terminal window I issued the following command:
>
> Begin command and command output:
>
> [colby at pcbsd-1403] ~% ps ax | grep pc-
> 1803 ??  I      0:00.54 /usr/local/bin/pc-systemupdatertray
> 1810 ??  I      0:00.01 sudo pc-nettray wlan0
> 2619 ??  S      0:02.99 pc-nettray wlan0
> 7795  0  S+     0:00.00 grep pc-
> [colby at pcbsd-1403] ~%
>
> End command and command output.
>
> In nautilus, /media had an empty directory for USB-Device-0
>
> I inserted a usb flash drive. The result was uneventful.
>
> I issued the following command in a terminal window:
>
> Begin command and command output:
>
>
> [colby at pcbsd-1403] ~% sudo pc-mounttray
> Locale: "en"
> pc-mounttray: starting up
> User detected: "colby"
> File manager detected: "openwith"
> Existing devices discovered:
>   -  "/dev/ada0s1"  ->   "SATA-Device-0" ,  "SATA:::FAT"
>   -  "/dev/ada0s2"  ->   "SATA-Device-1" ,  "SATA:::NTFS"
>   -  "/dev/ada0s3"  ->   "SATA-Device-2" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s4"  ->   "SATA-Device-3" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s5"  ->   "SATA-Device-4" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s6"  ->   "SATA-Device-5" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s7"  ->   "SATA-Device-6" ,  "SATA:::UNKNOWN"
>   -  "/dev/ada0s8"  ->   "SATA-Device-7" ,  "SATA:::UNKNOWN"
>   -  "/dev/da0"  ->   "USB-Device-0" ,  "USB:::UNKNOWN"
>
>
>
> End command and command output.
>
>
> "USB:::UNKNOWN" as per above is, I think, interesting.

Humm.... could you run "file -s /dev/da0" (or on another device if it 
says "UNKNOWN") and let me know what it says?

>
> In nautilus, /media still had an empty directory for USB-Device-0. /mnt
> was empty.
>
>
> Mounting /dev/da0s1 was uneventful, as above; /mnt directory contents
> were as above and unmounting as above, was uneventful.
>
> _______________________________________________
> Testing mailing list
> Testing at lists.pcbsd.org
> http://lists.pcbsd.org/mailman/listinfo/testing

I just finished updating how the devd detection works, so now it should 
work much faster and be more reliable. I also setup the program to also 
use glabel to try and determine the device name (if it has one), so more 
of the partitions/hard drives should be named properly now. If it still 
could not determine the device label/name, do you have a preference for 
the default naming convention? I just set it to "Partition-(device)" 
(Example: "Partition-ada0s1") instead of "SATA-Device-#" for now, but I 
can change that easily if you can think of something better.

Thanks for helping with this, it is really helpful to have others test 
this out to make sure that the algorithms are general enough to work on 
anyone's system.

-- 
~~ Ken Moore ~~
PC-BSD/iXsystems