Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2772 comp.os.386bsd.questions:15340
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!gatech!newsxfer.itd.umich.edu!zip.eecs.umich.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate
From: nate@bsd.coe.montana.edu (Nate Williams)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions
Subject: Re: [?!] So, is this a bug in the kernel execve() code?
Date: 20 Dec 1994 05:28:31 GMT
Organization: Montana State University, Bozeman Montana
Lines: 28
Message-ID: <3d5q1v$8cb@pdq.coe.montana.edu>
References: <D1351I.AM5@store.elvisti.kiev.ua>
NNTP-Posting-Host: bsd.coe.montana.edu
In article <D1351I.AM5@store.elvisti.kiev.ua>,
Andrew V. Stesin <stesin@elvisti.kiev.ua> wrote:
>Hi BSDers,
>
>as I wrote a few days ago, there was a strange thing noticed
>with FreeBSD-1.1.5R. Here is an (incorrect, I know! ;) program in C:
>
>int
>main (int ac, char **av)
>{
> return (execve("/bin/ls", av[1], 0));
>}
>
>anyway, given some command line parameters, this reboots the system
>immediately on our machine.
This problem was noticed and fixed in post 1.1.5. FreeBSD 2.0 has this
patch incorparated, and I believe there are patches on ref.tfs.com which
fix the 1.1.5 behavior. However, your best solution is to upgrade to
2.0, which I understand isn't always feasible.
Nate
--
nate@bsd.coe.montana.edu | FreeBSD dude and all around tech.
nate@cs.montana.edu | weenie.
work #: (406) 994-5980 | Unemployed, looking for permanant work in
home #: (406) 586-0579 | CS/EE field.