jes. Thats what I was seeing.
Bug or feature of what part?
Could the executor be enhanced to avoid this behaviour.
(Why is "file" smarter than the executor)?
Does the executor rely on assumtions whereas "file" just compare bytes?

Michael Reifenberger - IT, UNIX, R/3-Basis
Pers: [EMAIL PROTECTED]  Webspace: http://www.reifenberger.com

> -----Urspr> üngliche Nachricht-----
> Von:  Mike Smith [SMTP:[EMAIL PROTECTED]]
> Gesendet am:  Freitag, 3. November 2000 12:57
> An:   Reifenberger Michael
> Betreff:      Re: unwanteed halt & powerdown under -current (linuxerator?) 
> > Hi,
> > >> Hi,
> > >> executing /compat/linux/bin/rpm issues a halt and powerdown under -current
> > >> an my TECRA8000.
> > >> Is it just me?
> > >
> > >No.  You don't have the Linux module loaded.  There's a Linux system call 
> > >which (alarmingly) maps to shutdown-and-poweroff if run as a FreeBSD 
> > >binary.
> > Not really. See my previous mail.
> > It seems that a SYSV4 Syscall maps to the evil call.
> Unless you had the SVR4 module loaded, it would still have been run as a 
> FreeBSD binary, which would give you exactly the same behaviour.
> -- 
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also.  But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view.  [Dr. Fritz Todt]
>            V I C T O R Y   N O T   V E N G E A N C E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to