cc -O -pipe -DINET6 -c
/usr/src/usr.sbin/rtadvd/rtadvd.c/usr/src/usr.sbin/rtadvd/rtadvd.c:64:
dump.h: No such file or directory*** Error code 1
Stop in /usr/src/usr.sbin/rtadvd.
during the mkdep, I get:
../../kern/kern_linker.c:49: linker_if.h: No such file or directory
../../kern/link_aout.c:45: linker_if.h: No such file or directory
../../kern/link_elf.c:55: linker_if.h: No such file or directory
mkdep: compile failed
*** Error code 1
Stop in /usr/src/sys/compile/MONI
I normally wouldn't recommend it. But the same situation with a different (not to be
mentioned) OS happened to me.
After hours of being frustrated, I decided the scsi controller went south. A cow-orker
told me to LL the drive,
and voila, magic. These were IBM LVD 10kRPM drives, brand spankin new
Why not? The drives are empty LVD Drives, nothing bad'll happen.
I mean, it may very well be sysinstall being massively out of sync, but it shouldn't
hurt to LL the drives.
-eric
Mike Smith wrote:
> > Try low-levelling the drives. The behavior sounds similar to what I had a long
>time ago, l
Yep.
-eric
Forrest Aldrich wrote:
> Interesting point... these ARE new drives that were put in today.
>
> I presume you mean to use the BIOS scsi utility?
>
> _F
>
> At 06:16 PM 3/22/00 -0800, Eric Sabban wrote:
> >Try low-levelling the drives. The behavior sou
Try low-levelling the drives. The behavior sounds similar to what I had a long time
ago, low level formatting them fixed the problem.
-eric
Forrest Aldrich wrote:
> Since this is a fairly current issue, I'm posting this appropriately.
>
> I have a DELL server that has hooked up to it a PowerVa
