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--