I think you'd do better addressing questions about wolverine to the wolverine
list.
--
Cheers
John Summerfield
http://www2.ami.com.au/ for OS/2 & linux information.
Configuration, networking, combined IBM ftpsites index.
Microsoft's most solid OS: http://www.geocities.com/rcwoolley/
Note: mai
> > "TP" == Thornton Prime <[EMAIL PROTECTED]> writes:
>
> TP> I find building one machine by hand, then using mkkickstart to build a
> TP> new kickstart file works best for me.
>
> I was hoping there is an easier way. It's too easy to miss something.
> Surely Red Hat must have something up
I'm trying to bring up the beta on a machine whose only disk is behind a
3w-6800 card, all in one big (538GB) RAID 5 set. The card has been updated
to the latest BIOS. When formatting the filesystems, I get large numbers
of card resets and the following errors on the screen:
3w-: tw_scsi_eh
On 27 Mar 2001, Jason L Tibbitts III wrote:
> Me <[EMAIL PROTECTED]> writes:
>
> TP> I find building one machine by hand, then using mkkickstart to build a
> TP> new kickstart file works best for me.
>
> I was hoping there is an easier way. It's too easy to miss something.
> Surely Red Hat must
> "TP" == Thornton Prime <[EMAIL PROTECTED]> writes:
TP> I find building one machine by hand, then using mkkickstart to build a
TP> new kickstart file works best for me.
I was hoping there is an easier way. It's too easy to miss something.
Surely Red Hat must have something up its sleeve; a
On 27 Mar 2001, Jason L Tibbitts III wrote:
> I have a standard setup where I just stick a kickstart floppy in a machine
> and boot it to get a complete installation. Now I want to update my ks.cfg
> file for the 7.1 beta.
I find building one machine by hand, then using mkkickstart to build a
I have a standard setup where I just stick a kickstart floppy in a machine
and boot it to get a complete installation. Now I want to update my ks.cfg
file for the 7.1 beta.
My problem is that I have this long list of packages to install, some of
which have been renamed or subsumed into other pac
[EMAIL PROTECTED] said:
> Furthermore, RH7 apps will not be compatible with ohter Linuxes, so
> if you build your app on RH7 and ship it to a user who's not using
> RH7, the app will act funny, since the target system ABI is not
> compatible.
I'm a bit doubtful that gcc will cause this kind of
[EMAIL PROTECTED] said:
> This only applies for C++, where there is no standard ABI and haven't
> been - _for C, it is binary compatible_.
>
To me, "binary compatibility" has always meant something a little different.
On OS/2, DOS, Windows* one has a choice of C and C++ compilers. Shared
l
