System V standard vs. BSD standard -> where to find?

System V standard vs. BSD standard -> where to find?

Post by Thomas Schulze-Velmed » Sun, 03 Jan 1999 04:00:00



Hello alltogether :-)

I would like to know the differnces between the System V.4 "standard"
and the BSD "standard"
I know a few things (e.g. different bootup-techniques) but where can I
find all
differnences. e.g. where can I read what's to do, to have a System V.4 -
complaint un*x?

thanx in advance!

Regards

Thomas SV

 
 
 

System V standard vs. BSD standard -> where to find?

Post by Victor Wagn » Mon, 04 Jan 1999 04:00:00


: Hello alltogether :-)

: I would like to know the differnces between the System V.4 "standard"
: and the BSD "standard"
: I know a few things (e.g. different bootup-techniques) but where can I
: find all
: differnences. e.g. where can I read what's to do, to have a System V.4 -
: complaint un*x?

But why?

Really, I think that it is impossible to convert linux into 100% System
V.4 complaint system. At least it have no AT&T originated code in
kernel. It is possible however, and even desirable, to make fully POSIX
complaint system. POSIX standard was mainly SysV based. But don't forget
that there are a lot of useful things which are originated in Berkley.
And Linux tries to get best of both worlds.

: thanx in advance!

: Regards

: Thomas SV
--
--------------------------------------------------------
I have tin news and pine mail...


 
 
 

System V standard vs. BSD standard -> where to find?

Post by Thomas Schulze-Velmed » Mon, 11 Jan 1999 04:00:00


Hi Victor,

Quote:> Really, I think that it is impossible to convert linux into 100% System
> V.4 complaint system.

I don't want to convert anything!
I just want to know the differences! (more or less COMPLETE)
For myself, I prefer the BSD-style, anyway.

Thanks in advance

Regards

Thomas

 
 
 

System V standard vs. BSD standard -> where to find?

Post by Roland Latou » Mon, 11 Jan 1999 04:00:00



> > Really, I think that it is impossible to convert linux into 100% System
> > V.4 complaint system.
> I don't want to convert anything!
> I just want to know the differences! (more or less COMPLETE)
> For myself, I prefer the BSD-style, anyway.

I'll give it a try. No guarantees on completeness, though.
1)Under BSD, you can be in multiple groups at once.
  Under SysV, you can be in multiple groups, but only one at a time.
  Look for 'chgrp' command, and see output of 'id'.
2)different printspoolers: BSD is more network-aware
  SysV is based on shell scripts
3)different process scheduler:
  BSD process scheduler tries to be more 'fair' under college-student
  conditions. SysV scheduler is IMHO more performance-oriented.
4)BSD has disk quotas, for dealing with college-student conditions.
5)Different /etc/init and different startup scripts:
  SysV init uses /etc/inittab to run scripts in different directories
  for different runlevels, with S* and K* to start/stop processes.
  SysV also uses /etc/inittab to run its gettys
  BSD runs gettys from /etc/gettytab. SysV uses /etc/gettydefs for
  control of those gettys.

I'm sure I missed something, and all the linux releases I've seen are a
blend, trying to get the best of both worlds. Some of this may be
influenced by POSIX.

Does that help?
--
  Roland Latour  Slackware3.4 & PPP     http://home.cdsnet.net/~rolandl

 
 
 

1. LCSDNYR 2001 -> standards, standards, standards

[snip - a call for standardisation]

I completely agree, but I don't think Linux is going the wrong way (yet).

As always, tarballs (./configure, make, su -c 'make install') stay (oh yes
they will). Package-like installing (cfr deb, rpm, jbl, ...) goes the
right way: easy, user-friendly and without any hassle. I don't think it's
necessary to evolve to one package. Each type of packaging has it
advantages and disadvantages. It's a choice, a mindgame if you will. Some
people like the deb-packages since they are extremely easy to install.
Some others want rpm, since the availability of those files is enormous.
Some people stay with the tarballs.

I don't think Linux is going the wrong way.

With packages without any hassle. With tarballs you should look at the
Makefile before 'make install'-ing and search for 'make uninstall'. If
that's available (and correctly programmed), there isn't any other hassle.

This could be one point of discussion (tarballs - uninstalling software),
but I don't know enough about tarballs (I only use them if I can't find
any rpm-files for it) so I'd better shut up :-/

Again, with packages no troubles. Tarballs are also without any hassle,
since upgrading is very simpel. Configuration-files stay (thus not the way
M$ handled things, i.e. registry), binaries get upgraded, libraries are
... how do they say it... renewed? I mean, a newer version of library
doesn't overwrite things (f.i. libsmpg-2.0-3.so.2), only has a greater
version-number (f.i. libsmpg-2.1-1.so.2). And ldconfig makes sure programs
use the right library...

/etc/*.conf, $HOME/.*rc, ... I think Linux (and most unix-like OS'ses) are
doing a great job on that. They are easy to back-up, easy to modify
(manually AND with scripts/tools), ...

--
 SwifT

2. Protocol Switch Table protosw.h

3. "Standard Journaled File System" vs "Large File Enabled Journaled File System"

4. tcsh's vi command line mode: How to Change Word Delimiter

5. System V/BSD standards?

6. Out of ideas's Mod dependencies in 2.1.131

7. redirecting standard output and standard error

8. Upgrading to 3.1 ?

9. standard out and standard error

10. differentiate between standard output and standard error?

11. standard out and standard error questions

12. capturing standard error info but not standard out

13. No standard GUI, but standard metaphors!