On Thu, Sep 07, 2000 at 08:15:29AM +0200, Bernie wrote:
> Steven wrote:
>
> >Why pick on Linux? DOS is the same.
>
> NO IT IS NOT! If the user types in an incorrect syntax the program should
> NEVER EVER screw anything up - it should exit gracefully (or atleast not
> make any changes and hang). This is exactly what I want to point out - the
> Linux world obviously have trouble grasping this (not based on what you are
> answering of course but on how the program does). Without these easy checks
> it will not be popular (since it is unsafe). Frankly I don't care much, but
> you as a Linux user (and FANatic <g>) should IMO. Or is Linux only meant
> for some people?
> DOS is safe in the sense that you can never screw anything up by typing
> something that isn't according to the syntax. That you as a user can format
> the HD and other things is something else entirely (you can destroy things
> if you want to but never by incorrect syntax).
>
> >If a user makes a
> >mistake in a command, he can get a distructive result.
>
> True, but this is about syntax not the meaning of that syntax. If the user
> happens to give a command that is allowed then it's the users fault.
>
Linux will not work with incorrect syntax either. I don't know a single
OS that works with incorrect syntax. Problems begin when a typo generates
a correct commando. In Linux the chance for this to happen is slightly
bigger as there are more commandos to pick from.
Next to that Linux implements much more security from ignorant users.
Because of the multi-user capabilities of Linux, normal users can't change
anything in the system but there own files. To do so the root password is
needed. So if you're little brother tries to code a virus, it's his files
that are in danger, not yours.
> >For example, if you carelessly hold down the shift key
> >while entering "del 8ball.com", you will delete every
> >com file in that directory. Try that in your root DOS
> >directory for some real fun.
>
> I will? I've never tried that, might I ask how that's going to happen?
> (And I can always undelete in DOS).
> Ok, here goes....
>
> C:\DOS\>DEL (BALL:COM
> No such file or directory
> C:\DOS\>DEL BALL:COM (using numeric 8)
> No such file or directory
> C:\DOS\>del 8ball.com (Shift-Enter)
> No such file or directory
>
> Perhaps you should start looking for viruses? Because DOS has never and
> will never act in the way you describe.
>
> Ok, you probably meant using a US keyboard, lets take a look (CTRL-ALT-F1):
> C:\DOS\>DEL *BALL>COM
> No such file or directory
>
I think he meant C:\DOS>del *ball.com
which would result in the deletion of all .com files.
> Sure we've all done it - but due to ourselves not due to a malfunctioning
> program (except Scandisk then but I have complained about that one before).
> undelete, unformat and a backup will fix those three.
>
Yet again what is the difference with Linux. The dd fsck-up is clearly a bug
or maybe a even a hardware problem. I just tried the command the way Steven
wrote, and for me it worked from the root-dir, and gracefully exited in all
other directorys, just the way it should be. My bootdisk worked fine.
I don't think this has anything to do with dd, but is either a bad floppy or
a bad day.
> >The incident which gave arise to this thread involved
> >dd (a low-level Linux command, similar in destructive
> >potential to the DOS debug command). Tell me, Bernie,
> >what would you say if a DOS newbie mangled debug and
> >crashed his CMOS ?
>
> If it was due to an error in Debug then Debug is incorrect, but if it was
> due to an error that the program couldn't be able to spot then it's the
> users fault.
Know there we are.
--
Casper Gielen mailto:[EMAIL PROTECTED]
--
It was a user's "club", ... in the sense of the "club" being
a large stick usefull for beating IBM about the head with.
Frank Wagner
