
|
[openbeos]
||
[Date Prev]
[10-2004 Date Index]
[Date Next]
||
[Thread Prev]
[10-2004 Thread Index]
[Thread Next]
[openbeos] Re: B_USER_DATA_DIRECTORY?
- From: "Mikael Jansson" <tic_khr@xxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Fri, 01 Oct 2004 12:58:39 GMT
> > Think people may have read the top bit and skipped the
> > rest...that's
> > what I did anyway (sorry!)
> >
> > On the "home" issue, I never really understood what it was for
> > (coming
> > from windows without ever going thru anything vaguely unixy). After
> > using BeOS for a while, I decided it was where programs decided to
> > put
> > stuff, where config stuff went, etc. In fact, I created a /boot/
> > Files
> > folder just so I could put things in there myself and feel like it
> > was
> > a folder I actually owned for all of my stuff. "My Documents" isn't
> > such a bad idea.
> >
> Except you are not supposed to put anything in /boot
> on multiuser systems you're not supposed to touch anything that's not
> contained in your $HOME, and you don't have permission to do so.
> that's what the home folder is, it's the root of what *you* own.
>
That's semantics; the problem was that he didn't know that $HOME was
actually where you store your documents.
We clearly need to emphasize how to use the folders in the boot volume.
apps for applications, beos for read-only system stuff, etc.
After reading Simon's comment, I actually think it's not such a bad
idea to rename /boot/home (or rather $HOME, for multi-user
environments) to something more unambigiously(sp?) indicating that this
is where the user's data goes.
--
Mikael Jansson
http://mikael.jansson.be
|

|