Seeing as it's ME using the boxes in question, I'd prefer not to have to 
find out I forgot a step in setting up my user accounts when I'm on site 
at a customer.  I know other ways to resolve the problem too, but seeing 
as I rebuild my laptop/workstation on a regular basis, I'd rather 
minimize the maintenance where possible.  ESPECIALLY seeing as the drive 
in question is a FAT32 drive - which doesn't have security capabilities. 
  If/when I want the security (which is usually the case), I'll connect 
my ext3 formatted drive(s).  :)

Adding my user account to the haldaemon group shouldn't be bypassing the 
file access security - just allowing my user to use the mounted devices. 
  (I'll have to dig into just what the haldaemon group allows though...)

I see what you are saying about the flexibility vs defaults.  And I know 
I'm playing both sides here - I want it easy, but I also know how easy 
it is to solve the underlying problem with a little CLI magic.  But put 
this in the hands of joe novice user and you'll hear comments like "I 
tried Ubuntu, but it wouldn't let me write to my external drive. 
Windows did, so I switched back.  Ubuntu just isn't for me."  I know, 
for you and I, this is lame, but it's also the way things are.

But this is now transitioning into a philosophical debate.  You and I 
know we can go in circles on this type of topic for hours... So I'm 
going to opt out now.. :)

Good idea re the template though....

Shawn


Gustin Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Modify the new user templates then.  Sheesh.  First people complain
> about their OS not being flexible enough, then they complain that the
> defaults are not exactly the way the want.
> 
> I for one don't want the behaviour you want.  Full read write access to
> removable devices by default?  My users are lucky they get keyboards and
> mice :)
> 
> <sarcasm>
> It sound like what you really want is a mac.  It does a handful of task
> like this real well.
> </sarcasm>
> 
> Shawn wrote:
> | haldaemon did the trick.  The plugdev was already setup as a secondary
> | group - needed to add haldaemon.  logged out, then in, and was able to
> | create a directory.
> |
> | But my main complaint still stands.  This is not "low maintenance".  It
> | means that for every box I may use, or every user that I set up on those
> | boxes, I also need to add the haldaemon group.  This is still better
> | than having to mess with file ownership/permissions though.  So it's a
> | step in the right direction.
> |
> | (I think I'm getting lazy in my old age - I just don't want to have to
> | fight an OS to make it do what I think it should be doing by default... :)
> |
> | Shawn
> |
> | Neil Bower wrote:
> |> On Wednesday 23 January 2008 22:33, Neil Bower wrote:
> |>
> |> Or try group "haldaemon". Same disclaimer.
> |>
> |> Cheers!
> |>
> |> Neil B.
> |>
> |>> Hey Shawn,
> |>>
> |>> Have you added "plugdev" as a secondary group to your account? This
> is a
> |> stab
> |>> in the dark and assuming that you are using the GUI to manage the users.
> |>>
> |>> Cheers!
> |>>
> |>> Neil
> |>>
> |>> On Wednesday 23 January 2008 21:59, Shawn wrote:
> |>>> I've seen this now on two different systems, so know it's a Ubuntu
> |>>> thing, and not a "shawn" thing...
> |>>>
> |>>> Plugging an external USB drive enclosure into the box.  Ubuntu detects
> |>>> the drive and asks what I want to do with it - so I open the
> folder.  I
> |>>> can read the contents, but cannot modify/write to the drive.  The
> |>>> mounted drive is a FAT32 drive.
> |>>>
> |>>> Fist impression says just change the ownership on the mount point.
> |>>> Except that even as root I'm being told I can't.  So I look at doing a
> |>>> chmod on the mount directory and no joy there either (sometimes).
> |>>>
> |>>> So my question is, what am I missing?  Is there a group I can add my
> |>>> user too to get permission to these drives?  Is there a simpler way?
> |>>>
> |>>> I *know* I can make this work by going to the command line and doing a
> |>>> manual mount, or adjusting permissions/ownership, or tweaking the udev
> |>>> rules, etc.  But the idea is that these drives should just be "plug
> and
> |>>> play", without having to fuss with em.
> |>>>
> |>>> Any tips are appreciated.
> |>>>
> |>>> Shawn
> |>
> |> _______________________________________________
> |> clug-talk mailing list
> |> [email protected]
> |> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> |> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> |> **Please remove these lines when replying
> |
> | _______________________________________________
> | clug-talk mailing list
> | [email protected]
> | http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> | Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> | **Please remove these lines when replying
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFHmIM/wRXgH3rKGfMRAkpwAKCh4FJTIqkG9NMKRDl8WQnxrRWlLwCfdR0N
> TXlL7sD16IKlkEbE1yan+zY=
> =xUNr
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
  • [clug... Shawn
    • ... Neil Bower
      • ... Neil Bower
        • ... Shawn
          • ... Gustin Johnson
            • ... Shawn
          • ... Gary Z. (If forwarding, PLEASE delete address from body of e-mail!)
            • ... Gustin Johnson
    • ... Gustin Johnson

Reply via email to