From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6C1FF.35B9DF1D" Date: Thu, 17 Aug 2006 15:15:26 +0200 Message-ID: From: To: <9fans@cse.psu.edu> Subject: [9fans] dir tree Qs Topicbox-Message-UUID: a1acc24c-ead1-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. ------_=_NextPart_001_01C6C1FF.35B9DF1D Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable hi, =20 why do we have=20 =20 /386 /bin /lib /rc =20 ... but: =20 /$home /bin /386 /rc =20 ?? =20 also, =20 /lib, /sys/lib, and /$cpuname/lib is confusing... would welcome some explanation underneath a tree structure, best on wiki (I would like to get some idea on how to structure my /$home dir.... =20 thanks, best, ++pac. =20 ------_=_NextPart_001_01C6C1FF.35B9DF1D Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable

hi,

why do we have =

/386

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = /bin

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = /lib

/rc

…

but:

/$home

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = /bin

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0 /386

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0 /rc

also,

/lib, /sys/lib, and /$cpuname/lib is = confusing…

would welcome some explanation underneath a = tree structure, best on wiki

(I would like to get some idea on how to = structure my /$home dir….

thanks, best,

++pac.

------_=_NextPart_001_01C6C1FF.35B9DF1D-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <83f9126caeae638a3c28b472ec9a7d57@quanstro.net> From: erik quanstrom Date: Thu, 17 Aug 2006 08:53:34 -0500 To: 9fans@cse.psu.edu Subject: Re: [9fans] dir tree Qs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a1e2617c-ead1-11e9-9d60-3106f5b1d025 you make some good points. i noticed that glenda has that directory structure last night. i think it would make more sense to have $home/rc/bin and $home/$cputype/^(bin lib) in one's home directory. the difference between /$cputype/lib and (/lib and /sys/lib) is that /$cputype/lib stuff depends on the $cputype. it's actual system libraries. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <14ec7b180608170708t17e9b47bi35fa28f7dfa20a18@mail.gmail.com> Date: Thu, 17 Aug 2006 08:08:12 -0600 From: "andrey mirtchovski" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: [9fans] dir tree Qs In-Reply-To: <83f9126caeae638a3c28b472ec9a7d57@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <83f9126caeae638a3c28b472ec9a7d57@quanstro.net> Topicbox-Message-UUID: a1e95e32-ead1-11e9-9d60-3106f5b1d025 /386 contains much more than just binaries, while $home/bin/386 contains only that: binaries. i think the rationale was that having a directory for each architecture back when 386 wasn't the dominant one would clutter $home. we rarely spend any time in / after all. besides, Plan 9 shouldn't expose the architecture to the user right at the front line: what the current arch is was not meant to be something we ought to care about. i could be wrong, of course. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <010b16eca074d6f280559da640c69e60@quanstro.net> From: erik quanstrom Date: Thu, 17 Aug 2006 09:33:28 -0500 To: 9fans@cse.psu.edu Subject: Re: Re: [9fans] dir tree Qs In-Reply-To: <14ec7b180608170708t17e9b47bi35fa28f7dfa20a18@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a1f9b49e-ead1-11e9-9d60-3106f5b1d025 why would one never keep a library in one's home directory? keeping the structure the same would make it easier to bind $home/$cputype before/after /$cputype. $0.02 - erik On Thu Aug 17 09:08:52 CDT 2006, mirtchovski@gmail.com wrote: > /386 contains much more than just binaries, while $home/bin/386 > contains only that: binaries. > > i think the rationale was that having a directory for each > architecture back when 386 wasn't the dominant one would clutter > $home. we rarely spend any time in / after all. besides, Plan 9 > shouldn't expose the architecture to the user right at the front line: > what the current arch is was not meant to be something we ought to > care about. > > i could be wrong, of course. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <8230c3f5af1ea828cb4163dc9756cddc@vitanuova.com> Date: Thu, 17 Aug 2006 15:57:13 +0100 From: rog@vitanuova.com To: 9fans@cse.psu.edu Subject: Re: Re: [9fans] dir tree Qs In-Reply-To: <010b16eca074d6f280559da640c69e60@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a2018192-ead1-11e9-9d60-3106f5b1d025 i've wondered in the past why this difference. on balance i prefer the way it's done in $home, as the set of objtypes is open-ended, so it results in a somewhat less cluttered home directory - it's easy to remove all binaries, for example, without knowing the name of all objtypes (quick aside: i wish there was a constant pattern that would match all c compiler intermediate object files...) maybe the real reason why it's done differently in / is that there's already a /bin, and it is assumed to contain only binaries for the current objtype, which having (for instance) /bin/m68k would violate. one could have had (for instance) /arch/bin/386, /arch/lib/386, ... but would it have been worth it? From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Thu, 17 Aug 2006 12:05:14 -0400 From: jmk@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: Re: [9fans] dir tree Qs In-Reply-To: <8230c3f5af1ea828cb4163dc9756cddc@vitanuova.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a20dc61e-ead1-11e9-9d60-3106f5b1d025 you'll be wanting dotfiles next. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <7d3530220608170908w243103f0h32d46f558b3710ef@mail.gmail.com> Date: Thu, 17 Aug 2006 09:08:44 -0700 From: "John Floren" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: [9fans] dir tree Qs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8230c3f5af1ea828cb4163dc9756cddc@vitanuova.com> Topicbox-Message-UUID: a2197f9a-ead1-11e9-9d60-3106f5b1d025 On 8/17/06, jmk@plan9.bell-labs.com wrote: > you'll be wanting dotfiles next. > .rcrc muhahahaha John -- "The first thing we do, let's kill all the lawyers" -- Shakespeare, Henry VI From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: erik quanstrom Date: Thu, 17 Aug 2006 11:10:58 -0500 To: 9fans@cse.psu.edu Subject: Re: Re: [9fans] dir tree Qs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: a21dac1e-ead1-11e9-9d60-3106f5b1d025 hey, that's a good idea! i shudda thunkofit. =E2=98=BA - erik > you'll be wanting dotfiles next. From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 17 Aug 2006 19:05:23 +0200 To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: [9fans] dir tree Qs From: csant Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: User-Agent: Opera Mail/9.02 (Linux) Topicbox-Message-UUID: a2284b38-ead1-11e9-9d60-3106f5b1d025 Speaking of file structures - I have (in vane) tried to find some doc on what the rationale behind /mnt vs /n is (or rather: what exactly goes in /n ?). I *think* I know what the difference is, but I wanted to find some documentation on it. Anybody'd have apointer, please? (or a quick answer?) :) /c From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <14ec7b180608171008l7eee1d2ci83460dd22c30456e@mail.gmail.com> Date: Thu, 17 Aug 2006 11:08:26 -0600 From: "andrey mirtchovski" To: csant , "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: Re: [9fans] dir tree Qs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: Topicbox-Message-UUID: a23accb8-ead1-11e9-9d60-3106f5b1d025 /n is remote servers. /mnt/is local. On 8/17/06, csant wrote: > Speaking of file structures - I have (in vane) tried to find some doc on > what the rationale behind /mnt vs /n is (or rather: what exactly goes in > /n ?). I *think* I know what the difference is, but I wanted to find some > documentation on it. Anybody'd have apointer, please? (or a quick answer?) > :) > > /c > From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4adb44c7e3b1bd960c949703fcd7b082@vitanuova.com> Date: Thu, 17 Aug 2006 18:10:54 +0100 From: rog@vitanuova.com To: 9fans@cse.psu.edu Subject: Re: Re: Re: [9fans] dir tree Qs In-Reply-To: <14ec7b180608171008l7eee1d2ci83460dd22c30456e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a24a2280-ead1-11e9-9d60-3106f5b1d025 > /n is remote servers. /mnt/is local. /mnt/term ? From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <44E4A5EF.7060709@lanl.gov> Date: Thu, 17 Aug 2006 11:22:55 -0600 From: Ronald G Minnich User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] dir tree Qs References: <4adb44c7e3b1bd960c949703fcd7b082@vitanuova.com> In-Reply-To: <4adb44c7e3b1bd960c949703fcd7b082@vitanuova.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a2545f34-ead1-11e9-9d60-3106f5b1d025 rog@vitanuova.com wrote: >>/n is remote servers. /mnt/is local. > > > /mnt/term ? yeah, I think that is a tenuous claim (/mnt vs. /n) I always figured it was that stuff in /mnt was supposed to be in /mnt, otherwise if it was in /n, it was supposed to be in /n? ron From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <912ce27c52ab8df208513643c7e54193@quanstro.net> From: erik quanstrom Date: Thu, 17 Aug 2006 12:28:53 -0500 To: 9fans@cse.psu.edu Subject: Re: [9fans] dir tree Qs In-Reply-To: <44E4A5EF.7060709@lanl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a25c0f36-ead1-11e9-9d60-3106f5b1d025 not to throw a monkey wrench in your taxonomy, but what about /mail/fs? - erik On Thu Aug 17 12:26:41 CDT 2006, rminnich@lanl.gov wrote: > rog@vitanuova.com wrote: > >>/n is remote servers. /mnt/is local. > > > > > > /mnt/term ? > > yeah, I think that is a tenuous claim (/mnt vs. /n) > > I always figured it was that stuff in /mnt was supposed to be in /mnt, > otherwise if it was in /n, it was supposed to be in /n? > > ron From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <68a47ea683ad5f1a0c4ed9df19b3e627@9netics.com> To: 9fans@cse.psu.edu Subject: Re: Re: Re: [9fans] dir tree Qs Date: Thu, 17 Aug 2006 10:34:11 -0700 From: Skip Tavakkolian <9nut@9netics.com> In-Reply-To: <4adb44c7e3b1bd960c949703fcd7b082@vitanuova.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a266ec4e-ead1-11e9-9d60-3106f5b1d025 >> /n is remote servers. /mnt/is local. > > /mnt/term ? /n for ephemeral and /mnt for eternal? From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 17 Aug 2006 19:38:47 +0200 To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] dir tree Qs From: csant Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <4adb44c7e3b1bd960c949703fcd7b082@vitanuova.com> <44E4A5EF.7060709@lanl.gov> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <44E4A5EF.7060709@lanl.gov> User-Agent: Opera Mail/9.02 (Linux) Topicbox-Message-UUID: a26e47e6-ead1-11e9-9d60-3106f5b1d025 > rog@vitanuova.com wrote: >>> /n is remote servers. /mnt/is local. >> /mnt/term ? > > yeah, I think that is a tenuous claim (/mnt vs. /n) > > I always figured it was that stuff in /mnt was supposed to be in /mnt, > otherwise if it was in /n, it was supposed to be in /n? /n/dump is yet another one confusing me. If /mnt stands for "mount", what does /n stand for? /c From mboxrd@z Thu Jan 1 00:00:00 1970 To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: Re: [9fans] dir tree Qs From: csant Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <68a47ea683ad5f1a0c4ed9df19b3e627@9netics.com> Content-Transfer-Encoding: 7bit Date: Thu, 17 Aug 2006 19:39:51 +0200 Message-ID: In-Reply-To: <68a47ea683ad5f1a0c4ed9df19b3e627@9netics.com> User-Agent: Opera Mail/9.02 (Linux) Topicbox-Message-UUID: a2726ea2-ead1-11e9-9d60-3106f5b1d025 > /n for ephemeral and /mnt for eternal? like in /n/dump ? From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: erik quanstrom Date: Thu, 17 Aug 2006 12:41:26 -0500 To: csant@csant.info, 9fans@cse.psu.edu Subject: Re: [9fans] dir tree Qs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Cc: Topicbox-Message-UUID: a28ef4aa-ead1-11e9-9d60-3106f5b1d025 i think it's a holdover from research unix. "network." - erik On Thu Aug 17 12:39:22 CDT 2006, csant@csant.info wrote: > > rog@vitanuova.com wrote: > >>> /n is remote servers. /mnt/is local. > >> /mnt/term ? > > > > yeah, I think that is a tenuous claim (/mnt vs. /n) > > > > I always figured it was that stuff in /mnt was supposed to be in /mnt, > > otherwise if it was in /n, it was supposed to be in /n? > > /n/dump > is yet another one confusing me. If /mnt stands for "mount", what does /n > stand for? > /c From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <67ad5fd401b4add3e05ff9e4d525db40@9netics.com> To: csant@csant.info, 9fans@cse.psu.edu Subject: Re: Re: Re: [9fans] dir tree Qs Date: Thu, 17 Aug 2006 10:42:30 -0700 From: Skip Tavakkolian <9nut@9netics.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Cc: Topicbox-Message-UUID: a2b0f168-ead1-11e9-9d60-3106f5b1d025 >> /n for ephemeral and /mnt for eternal? > like in /n/dump ? /n for one and /mnt for all? From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: Re: Re: [9fans] dir tree Qs Date: Thu, 17 Aug 2006 10:44:40 -0700 From: Skip Tavakkolian <9nut@9netics.com> In-Reply-To: <67ad5fd401b4add3e05ff9e4d525db40@9netics.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a2b52c4c-ead1-11e9-9d60-3106f5b1d025 >>> /n for ephemeral and /mnt for eternal? >> like in /n/dump ? > > /n for one and /mnt for all? also, in my world, /n has mntgen and /mnt doesn't. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <0e16b31d6bdd819c6e2df755028243eb@vitanuova.com> Date: Thu, 17 Aug 2006 18:44:46 +0100 From: rog@vitanuova.com To: csant@csant.info, 9fans@cse.psu.edu Subject: Re: [9fans] dir tree Qs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Cc: Topicbox-Message-UUID: a2bd22bc-ead1-11e9-9d60-3106f5b1d025 > is yet another one confusing me. If /mnt stands for "mount", what does /n > stand for? actually, the main distinction seems to be that /n holds filesystems that contain regular files, and /mnt has service interfaces. personally i wouldn't mind losing /mnt - /n is so much easier to type. From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <4adb44c7e3b1bd960c949703fcd7b082@vitanuova.com> References: <4adb44c7e3b1bd960c949703fcd7b082@vitanuova.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9CE026D9-867A-4638-95AB-91D905351C4B@lanl.gov> Content-Transfer-Encoding: 7bit From: andrey mirtchovski Subject: Re: [9fans] dir tree Qs Date: Thu, 17 Aug 2006 11:45:19 -0600 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: a2b964ce-ead1-11e9-9d60-3106f5b1d025 On Aug 17, 2006, at 11:10 AM, rog@vitanuova.com wrote: >> /n is remote servers. /mnt/is local. > > /mnt/term ? obviously a mistake :) From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: Re: [9fans] dir tree Qs From: Charles Forsyth Date: Thu, 17 Aug 2006 19:17:29 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a2d8d688-ead1-11e9-9d60-3106f5b1d025 > /n ?). I *think* I know what the difference is, but I wanted to find some > documentation on it. Anybody'd have apointer, please? (or a quick answer?) namespace(4) has a stab at it, including answering (however briefly) quite a few of the questions people have asked so far. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Thu, 17 Aug 2006 11:40:46 -0700 From: "Russ Cox" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: [9fans] dir tree Qs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Topicbox-Message-UUID: a2dcdd14-ead1-11e9-9d60-3106f5b1d025 Why look in man pages when the answer's already known not to be in the wiki? Russ From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Thu, 17 Aug 2006 15:56:45 -0300 From: "=?ISO-8859-1?Q?Iruat=E3_Souza?=" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] dir tree Qs In-Reply-To: <0e16b31d6bdd819c6e2df755028243eb@vitanuova.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <0e16b31d6bdd819c6e2df755028243eb@vitanuova.com> Topicbox-Message-UUID: a2e1885a-ead1-11e9-9d60-3106f5b1d025 2006/8/17, rog@vitanuova.com : > > is yet another one confusing me. If /mnt stands for "mount", what does /n > > stand for? > > actually, the main distinction seems to be that /n holds filesystems > that contain regular files, and /mnt has service interfaces. > > personally i wouldn't mind losing /mnt - /n is so much easier to type. > i don't know if that's too silly of me, but having this separation with this semantics (regular files vs service interfaces) doesn't goes against the idea that in plan9 one wouldn't have to differentiate between types of files unless he/she wishes so? From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <0b8a3f246291f2ea2597b61df48d80aa@terzarima.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] dir tree Qs From: Charles Forsyth Date: Thu, 17 Aug 2006 20:29:51 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a2e984ba-ead1-11e9-9d60-3106f5b1d025 > i don't know if that's too silly of me, but having this separation > with this semantics (regular files vs service interfaces) doesn't goes > against the idea that in plan9 one wouldn't have to differentiate > between types of files unless he/she wishes so? there are several different types of files, and a few significant conventions, so that /net is not interchangeable with /mnt, say. put another way, things under /net deliberately present a particular interface so that ndb/cs and dial will function, regardless of what the names actually mean (ip vs datakit for instance). if you try dialling things in /mnt, you're bound to be disappointed. what plan 9 says is that to access anything, ultimately you open a name, read/write, close. it doesn't say that you don't differentiate between files, and what you read and write will differ for /dev/draw as against /net/tcp From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Thu, 17 Aug 2006 16:42:24 -0300 From: "=?ISO-8859-1?Q?Iruat=E3_Souza?=" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] dir tree Qs In-Reply-To: <0b8a3f246291f2ea2597b61df48d80aa@terzarima.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <0b8a3f246291f2ea2597b61df48d80aa@terzarima.net> Topicbox-Message-UUID: a2efa80e-ead1-11e9-9d60-3106f5b1d025 2006/8/17, Charles Forsyth : > > i don't know if that's too silly of me, but having this separation > > with this semantics (regular files vs service interfaces) doesn't goes > > against the idea that in plan9 one wouldn't have to differentiate > > between types of files unless he/she wishes so? > > there are several different types of files, and > a few significant conventions, > so that /net is not interchangeable with /mnt, say. > put another way, things under /net deliberately present a > particular interface so that ndb/cs and dial will function, > regardless of what the names actually mean (ip vs datakit for instance). > if you try dialling things in /mnt, you're bound to be disappointed. > > what plan 9 says is that to access anything, ultimately you > open a name, read/write, close. > it doesn't say that you don't differentiate between files, > and what you read and write will differ for /dev/draw as against > /net/tcp > > that really explains the point to me :] thanks charles. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Thu, 17 Aug 2006 21:07:45 +0100 From: rog@vitanuova.com To: 9fans@cse.psu.edu Subject: Re: [9fans] dir tree Qs In-Reply-To: <0b8a3f246291f2ea2597b61df48d80aa@terzarima.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a30aaa28-ead1-11e9-9d60-3106f5b1d025 > if you try dialling things in /mnt, you're bound to be disappointed. mind you i've used /mnt/term/net/tcp!machine!port before now... From mboxrd@z Thu Jan 1 00:00:00 1970 To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: [9fans] dir tree Qs From: csant Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: Content-Transfer-Encoding: 7bit Date: Thu, 17 Aug 2006 22:54:04 +0200 Message-ID: In-Reply-To: User-Agent: Opera Mail/9.02 (Linux) Topicbox-Message-UUID: a3147b8e-ead1-11e9-9d60-3106f5b1d025 > namespace(4) has a stab at it, including answering (however briefly) > quite a few of the questions people have asked so far. Oh - nice, thank you. I somehow missed that one. /c From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Subject: RE: [9fans] dir tree Qs Date: Tue, 29 Aug 2006 06:27:37 +0200 Message-ID: In-Reply-To: <83f9126caeae638a3c28b472ec9a7d57@quanstro.net> From: To: <9fans@cse.psu.edu> Topicbox-Message-UUID: a98c60bc-ead1-11e9-9d60-3106f5b1d025 I decided to adhere to namespace (4) dir structure in my home dir, thus, the mkfiles in /n/sources/contrib/pac/* will hopefully reflect = this change. thanksd for all the points, best, ++pac