*BSD News Article 68444


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!cancer.vividnet.com!hunter.premier.net!bofh.dot!news.mathworks.com!newsfeed.internetmci.com!howland.reston.ans.net!blackbush.xlink.net!rz.uni-karlsruhe.de!news.uni-stuttgart.de!news.rhrz.uni-bonn.de!saph2.physik.uni-bonn.de!juengst
From: juengst@saph1.physik.uni-bonn.de (Henry G. Juengst)
Newsgroups: comp.unix.misc,comp.unix.bsd.misc
Subject: Re: How to delete files within C programs
Date: 13 May 1996 18:52:59 GMT
Organization: Institut fuer Strahlen- und Kernphysik
Lines: 70
Sender: juengst@saph2.physik.uni-bonn.de (Henry G. Juengst)
Distribution: world
Message-ID: <4n80eb$oo4@news.rhrz.uni-bonn.de>
References: <Oum-El-Kheir.Benkahla-3004961724540001@mac-ugm-3.imag.fr> <4mv2r7$ld3@news.rhrz.uni-bonn.de> <4mvsjp$nhn@web.nmti.com> <4n5cer$33m@news.rhrz.uni-bonn.de> <4n7mse$o34@web.nmti.com>
Reply-To: juengst@saph1.physik.uni-bonn.de
NNTP-Posting-Host: saph1.physik.uni-bonn.de
Xref: euryale.cc.adfa.oz.au comp.unix.misc:22710 comp.unix.bsd.misc:1039


In article <4n7mse$o34@web.nmti.com>, peter@nmti.com (Peter da Silva) writes:
>> >Or let's look at VMS. How to you remove a print job again? I can't
>> >keep track of whether it's DELETE QUEUE/JOB or DELETE /QUEUE or DELETE
>> >JOB. It wouldn't surprise me to find it's now SET JOB/NOPRINT. Half the
>> >commands in VMS are hidden under SET somewhere, including their remote
>> >terminal program (SET HOST).
>
>> Especially for you (quoted VMS help, callable via 'HELP'):
>
>> DELETE [...]
>
>That is, if you already know that the command to cancel a print job is
>"delete", which is at *least* as counterintuitive as "unlink" to delete
>a file (hint to DEC, try "cancel").

You wrote "How to you remove a print job again?" Other people say "how
to delete a print job". There is no real difference. This was just another
example where you tried to show how bad VMS is. Well, I think 'lprm' and
'cancel' are nice examples which show the two typical problems of unix:
First, there are different commands on different unixes and second, these
commands (at least 'lprm') are cryptical. This was your example. I think
we don't need to discuss the POSIX standard for this case, too...

>
>If you don't already know what you're looking for VMS HELP is a joke.

You know that you can call VMS HELP without any parameter and get the
top level of commands. You will find DELETE and PRINT immediatly.

>
>> Peter, if you have fundamental problems with VMS concepts I recommend
>> not to start a discussion about it (perhaps in comp.os.vms).
>
>Henry, if you have a fundamental problem with UNIX, I recommend you don't
>start flaming it in comp.unix. And if you do, then expect your own ox to be
>gored. It's your discussion. You started it. Take responsibility for the
>consequences of your own actions.

Perhaps you should discuss about unix next time if someone talkes about
unix. Your first response had nothing to do with the problem. It does not
help if anybody shows a problem and another one says that this is also true
anywhere else.

>
>UNIX doesn't have a monopoly on obscure commands, and it at least provides

Correct.

>decent cross-references from one part of a subsystem to another so if you
>know the command to print a file you can find the command to cancel the print

If you know the command to print...

>job in the same section of the online documentation.
>
>-- 
>Peter da Silva    (NIC: PJD2)      `-_-'             1601 Industrial Boulevard
>Bailey Network Management           'U`             Sugar Land, TX  77487-5013
>+1 713 274 5180         "Har du kramat din varg idag?"                     USA
>Bailey pays for my technical expertise.        My opinions probably scare them

Henry

--
juengst@saph1.physik.uni-bonn.de         [131.220.161.1]  (Internet)
omni:.de.uni-bonn.physik.saph1::juengst                   (DECnet/OSI, phase V)
saph1::juengst                           [26.358]         (DECnet, phase IV)

Any opinions in this mail are my own.