public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Preparing a shared USB stick
Date: Thu, 02 Jan 2014 23:44:00 +0000	[thread overview]
Message-ID: <52C5F9C0.5070101@fuuzetsu.co.uk> (raw)
In-Reply-To: <CAPi0psvFOhdJ0WokoN6F+1TrPcjEMoDVCZqzTuTWSnxkZyP8hQ@mail.gmail.com>

On 02/01/14 23:02, Chris Stankevitz wrote:
> Hello,
>
> Please consider a USB "stick" that is unformatted but is to be used by
> multiple people/machines.  Ideally your instructions will work for all
> people/os/WM, but if necessary please assume that everyone is running
> gnome under linux

Well, if it ideally should work across multiple operating systems,
you're probably stuck with FAT32 or similar due to Windows.

> 1. How should I prepare this device so that it can be plugged into any
> machine and will be writable by anyone?  I suspect the answer will
> involve words like fdisk, mkfs.xxx, mkdir/mount, chmod/chown.  I'm
> most interested in the chmod/chown part.

If you go with FAT, there's no notion of ownership (I believe) so it's
not a problem. If you don't, I still don't think chmod/chown matters
as long as the user has the permissions to write to the stick when
mounted on their own machine. I might be wrong though!

> 2. How can I prepare the device so that files/directories added by
> people in the future will continue to be writable by anyone?

Likewise, I think they'll be able to as long as they have the
permission to write to the mounted stick _on their own machine_.

> 3. How can I ensure that all files will appear to have the same owner;
> or, if this is not important, can you explain why it should not be a
> problem.

I think it's not a problem, at least not with FAT.

> And of course if you can refer me to a document that explains this I'm
> happy to read it.
>
> Thank you,
>
> Chris
>

I'm not an expert but hopefully this helps to at least steer you in
the right direction. I used multiple USB sticks across multiple
machines across multiple systems in the past and I never had any
ownership concerns that you do. The only issues were if one of the
systems couldn't read the file format used.

--
Mateusz K.


  reply	other threads:[~2014-01-02 23:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 23:02 [gentoo-user] Preparing a shared USB stick Chris Stankevitz
2014-01-02 23:44 ` Mateusz Kowalczyk [this message]
2014-01-03  2:31   ` Francisco Ares
2014-01-03  9:16     ` Neil Bothwick
2014-01-04 23:32       ` Chris Stankevitz
2014-01-03  6:45 ` Alan McKinnon
2014-01-03 18:47   ` [gentoo-user] " James
2014-01-04 23:31   ` [gentoo-user] " Chris Stankevitz
2014-01-04 23:44     ` Alan McKinnon
2014-01-05  0:42       ` [gentoo-user] " walt
2014-01-05  1:21         ` Alan McKinnon
2014-01-05 21:26           ` walt
2014-01-05 21:55             ` Alan McKinnon
2014-01-05 21:50           ` walt
2014-01-05 21:59             ` Alan McKinnon
2014-01-05  5:15       ` [gentoo-user] " Chris Stankevitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52C5F9C0.5070101@fuuzetsu.co.uk \
    --to=fuuzetsu@fuuzetsu.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox