From tschaefe@paging.mot.com Tue Mar 24 16:12:08 1998 From: tschaefe@paging.mot.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] New Convert with a Question about RPMs Date: Tue, 24 Mar 1998 17:12:08 +0100 Message-ID: <6f8m0o$vci$1@Galois.suse.de> In-Reply-To: <[S.u.S.E. Linux] New Convert with a Question about RPMs> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3826427734145779775==" --===============3826427734145779775== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable FSSTD =3D File System Standard - there is a Linux file system standard, and a= ll the distributors say they're following it. FSSTD is essentially the guiding doc that specifies the location of every file on the system. No I don't know where it is .. probably need to browse http://w= ww.linux.org> or the Linux Journal site. For example to put "messages" into /var/adm/messages vs /var/log/messages. I'm not sure which is "right", I know of two distributors that say they're using FSSTD and they have messages in different locations.Slack puts the public ftp directory into /home/ftp. SuSE uses /usr/local/ftp. Slack had been putting apache into /var/lib/httpd, SuSE - hell I don't remember where it is. SAMBA wants /usr/local/samba, but I see it all over the map. Samba wants a /usr/local/samba/lib dir, SuSE is putting smb.conf it in /etc. And why would Slack pick /var/lib. To me, a /lib dir is a directory that has libraries. But I've seen a subtle unix tradition to re-define things and so a lib dir is for config files *sometimes*. And then you're supposed to just know that. It's stuff like that that makes simple installs take much longer than is necessary. Leaves you wondering where you should install new apps. Some sites stick to /usr/local, others hate /usr/local and want everything in /opt. Since Unix is rather religious about files and where they go, I am a bit disturbed by this. Although it would be nice to be able to collapse the entire os directory structure under a /linux root tree, just like Windows does with their \windows directory, with all of the os dirs under that, it will probably never happen since such a drastic change would cause major problems. Then you could create whatever apps directories you wanted to right off the root tree. That too wou= ld be politically incorrect. And one of the most confusing things about Unix is the convoluted directory structure. Just look at the mess that the weirdos at the XFree86 compound (I = say compound because it has to be some weird cult) came up with for X Windows. Y= ou have so many unnecessary and complicated links and double-secret-subnested directories as to make administration a mess. Whatever happend to just keeping things simple! -tks- Jim Hodgers wrote: > At 08:20 AM 3/24/98 -0500, you wrote: > > It might help us Newbies to explain just what "FSSTD" is... > Jim > ...Spider Veloce's forever... > > > > >Bodo, > > > >Is there a "FSSTD" flag in the rpm utility? If not then perhaps there shou= ld > >be, then rpm would have a builtin safety ... > > > > > >Bodo Bauer wrote: > > > >> We use RPM version 2.4.10 (S.u.S.E. Linux 5.1) and it's the same one > >> RedHat uses, we don't have a special rpm format. As long as the packages > >> don't contain any Redhat or Yggdrasil specials and they conform to > >> the FSSTD it should not be a problem to install them on S.u.S.E. linux. > > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e --===============3826427734145779775==--