My original question was:-
___________________________________________________________________________
When booting genvmunix and running doconfig, the following message
appears after
*** PERFORMING KERNEL BUILD ***
ERROR: could not make special device files!!
Why would this occur?
In the KERNEL OPTION SELECTION section, kernel option 13 is selected
(all of the above).
After the kernel option selection, the following messages are seen:-
/usr/sbin/autopush: Can't push requested modules on STREAM for entry 39
/usr/sbin/autopush: Device (6,-1) already configured
cp: /tmp/CONDOR_LATEST: No such file or directory
(CONDOR_LATEST is the kernel name.)
This has previously worked.
Digital asked whether LAT was installed (which it was) and then stated that thiswas not a known problem and thus suggested that a basic kernel file was built
from a vanilla config file using the sizer utility then to build the kernel
incrementally and hence determine which option it fails on.
Does anyone know what the problem is and hence a quicker solution?
-----------------------------------------------------------------------------
The solution:-
The problem was caused by a rogue version of sizer (a shell script) in
/sbin. Removing this caused everything to work again.
Thanks to all who replied, but particularly to
<tpb_at_zk3.dec.com> (Dr. Tom Blinn)
with whom I corresponded.
******************************************************************************
--------------
| | David Clapperton
__ -------------- __ __ Systems Programmer
|__|__ |__| |__| |__| |__| |__| Information Resource Services
|__| __ __ __ __ __ University of Westminster
|__| |__| |__| |__| |__| 115 New Cavendish Street
__ __ __ London
\/ \/ \/ E-mail: davidc_at_westminster.ac.uk
******************************************************************************
Received on Thu Aug 01 1996 - 12:23:23 NZST