🚀 go-pugleaf

In article 37C@dscomsa.desy.de, hallam@zeus02.desy.de (Phill Hallam-Baker) writes:
>
>Bugs they still need to fix:-
>
>	1) Online manual still designed with aim of minimizing disk space rather than
>providing information.

Try out Sun's Answerbook technology (will take up over 200MB of disk if you install
the whole thing), with hyper-text links throughout, a great search facility, etc.

>	2) No help facility.

Almost every vendor now has a help viewer pop-up in their windows environment. For
Suns, just hit the Help key (if you haven't disable it) while in Openwindows.

>	3) No standardized user firendly shell.

What's a user-friendly shell? There sure are plenty to choose from, take your pick from
sh, csh, ksh, tcsh, bash, etc.

>	4) Command qualifiers hard coded into applications making multilanguage
>customization impossible.

Take a look at Solaris 2.1 -- it has extensive I18N (internationalization) support
at both the O/S and the programmer's levels.

>	5) Requires expensive expert to have a chance of any security.

Sun's CMW (shipping in volume as of 12/17/92) only needs a regular admin and a
security officer (who is required for any secure facility anyhow), and is being
evaluated for the DISA CMW (B2+ security).

>	6) File system limited to sequential file, forcing applications to create their
>own file system on top of the UNIX one, thus preventing any standardization or
>application independent optimization.

Almost every Unix implementation now has many optimizations built-in, such as write
clustering, SCSI tag-queuing, etc.  You can also create holey files.  Striping (both
via h/w and s/w) is abundantly available.  What type of file I/O are you complaining
about the lack of?

>Phill Hallam-Baker

-Phil Morris