[openbeos] Re: Distribution/Upgrade Mechanism Question
- From: "David J. Lowe" <DaveLowe@xxxxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Mon, 1 Apr 2002 09:17:54 -0600
I've heard the earlier, pre-v5, cards were supported... My personal edition
of r5, updated to 5.0.3, has only two entries for nics, a 3com one, and an
isa ne200 (200, 2000? don't remember at this point, but do know that it
doesn't work).
-----Original Message-----
From: openbeos-bounce@xxxxxxxxxxxxx
[mailto:openbeos-bounce@xxxxxxxxxxxxx]On Behalf Of john 'soco' robinson
Sent: Monday, April 01, 2002 9:19 AM
To: openbeos@xxxxxxxxxxxxx
Subject: [openbeos] Re: Distribution/Upgrade Mechanism Question
i thought there was tulip support already with all the appropriate
updates to R5 (ie 5.0.3) or am i think about Bone?
-soco
----- Original Message -----
From: "David J. Lowe" <DaveLowe@xxxxxxxxxxxx>
To: <openbeos@xxxxxxxxxxxxx>
Sent: Monday, April 01, 2002 5:10 PM
Subject: [openbeos] Re: Distribution/Upgrade Mechanism Question
> It uses the Linux Tulip driver (ftp://ftp.scyld.com/pub/network/tulip.c,
> this link given at the LinkSys site).
>
> I've looked at the driver, but at this point looking is all I can do (my
> career has been spent in visual c++/mfc and vb, so driver development is
> beyond me at the moment, particularly when porting from one unknown Linux
to
> one (currently) unknown BeOS/OpenBeOS).
>
>
>
> -----Original Message-----
> From: openbeos-bounce@xxxxxxxxxxxxx
> [mailto:openbeos-bounce@xxxxxxxxxxxxx]On Behalf Of David Reid
> Sent: Monday, April 01, 2002 8:53 AM
> To: openbeos@xxxxxxxxxxxxx
> Subject: [openbeos] Re: Distribution/Upgrade Mechanism Question
>
>
> What's it based on? Or, if you run it with unix/linux, what does it call
it?
>
> david
>
> ----- Original Message -----
> From: "David J. Lowe" <DaveLowe@xxxxxxxxxxxx>
> To: <openbeos@xxxxxxxxxxxxx>
> Sent: Monday, April 01, 2002 3:44 PM
> Subject: [openbeos] Re: Distribution/Upgrade Mechanism Question
>
>
> > Linksys LNE100TX(v5) Fast Ethernet Adapter
> >
> >
> >
> > -----Original Message-----
> > From: openbeos-bounce@xxxxxxxxxxxxx
> > [mailto:openbeos-bounce@xxxxxxxxxxxxx]On Behalf Of David Reid
> > Sent: Monday, April 01, 2002 8:44 AM
> > To: openbeos@xxxxxxxxxxxxx
> > Subject: [openbeos] Re: Distribution/Upgrade Mechanism Question
> >
> >
> > What card is it?
> >
> > david
> >
> > ----- Original Message -----
> > From: "David J. Lowe" <DaveLowe@xxxxxxxxxxxx>
> > To: <openbeos@xxxxxxxxxxxxx>
> > Sent: Monday, April 01, 2002 3:36 PM
> > Subject: [openbeos] Distribution/Upgrade Mechanism Question
> >
> >
> > > Hello, I'm very new here, and hopefully this question has already been
> > > answered (and if it has, could you point me to it?)...
> > >
> > > Has there been any thought towards system upgrades to the initial
public
> > > release (non-beta)? If there are fixes to various parts, will people
> have
> > > to physically check a particular web-site to determine if they need an
> > > upgrade/fix? Or will there be an update manager that can accurately
> > > determine what various systems/servers a particular box has and query
> some
> > > central repository for any potential fixes?
> > >
> > > I think this is a pretty important consideration for end-users. I
feel
> > they
> > > want to simply use their system and have it "heal" itself as the
> > > weeks/months/years progress (and strongly feel that the last thing
they
> > want
> > > to worry about is whether or not their box is secure, flaky, etc, and
> they
> > > certainly don't want to worry about library conflicts, etc.).
> > >
> > > Anyways, hello all, and keep up the good work! Hopefully some day
I'll
> > have
> > > the time to contribute to OpenBeOS (which will occur probably right
> around
> > > the time BeOS recognizes my nic card :-) ).
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
Other related posts:
