> I'm not going to bother tearing apart your reply.
>
> You obviously have -no- idea what the current state of the PnP system in
> FreeBSD is.
Me neither. I would have appreciated a brief discussion of how the PnP
system deals with the sort of problem Mr. Larson describes.
> If the FreeBSD ke
>At 11:11 AM 4/3/00 +0200, you wrote:
>Moral of the story. It is plain untrue that Windows sees all hardware in
>a straightfoward way. One may need to fiddle very much with BIOS settings
>and it is very long and guesswork, involving a lot of reboots. It is much
>easier to use tools such as pnpdum
As I recall, Matthew N. Dodd wrote:
> On Sat, 25 Mar 2000, Chad R. Larson wrote:
>> This makes me wary. One of the reasons I like UNIX is the assumption
>> implicit in its organization that the users might actually know what
>> they're doing.
>
> This has nothing to do with UNIX.
Sorry for the
> This makes me wary. One of the reasons I like UNIX is the
> assumptions implicit in its organization that the users might
> actually know what they're doing.
>
> Every time Microsoft and the PC industry have tried to remove the
> responsibility and control from the users (EISA--no jumpers,
>
On Thu, 23 Mar 2000, Mitsuru IWASAKI wrote:
> Sorry, I don't have null-modem cable or 3c5x9cfg.exe or DOS here, but
> I did some hacks. By follwing patch made referring to 3-STABLE code,
> system was passed ep probe/attach routine with correct mac address and
> stopped /etc/rc.network in userland
Hi,
> > Grrr, It's too difficult because I can't do anything after the messsage
> > even etner DDB or pause screen and back scrolling...
>
> Use the serial console.
Sorry, I don't have null-modem cable or 3c5x9cfg.exe or DOS here, but
I did some hacks. By follwing patch made referring to 3-STA
