On Wed, 1 Sep 1999, [iso-8859-1] Gr�goire Colbert wrote:
> Axalon Bloodstone wrote:
> >
> > On Wed, 1 Sep 1999, [iso-8859-1] Gr�goire Colbert wrote:
> > >
> > > PLEASE, make sure that the infamous PUMP has been replaced with DHCPCD
> > > before you begin to burn Mdk61... I know I've already asked you a zillion
> > > times, but please understand that using pump by default is a SERIOUS problem
> > > for people who use cable-modems.
> >
> > pump worked fine here, before the modem roasted atleast. I'll ask the tech
> > what they have at the headend here in denver for a dhcp server, when he
> > gets here..
>
> Listen : I really don't care about what your techie in Denver will say. It
> seems that you are completely missing what is the problem.
Fine don't care don't listen, for those that do it's Nt4 sp3
> The FACT is that you have two programs in Cooker that basically do the same
> thing :
> - one is called "pump"
> - the other is called "dhcpcd"
So? Pick any one general task, and i'm sure theres atleast two programs in
the distribution that will achieve the results. Remeber it's all about
choice.
> Those programs are used when you want to get an IP adress from the server of
> your provider, using a cable-modem and the DHCP protocol. YOU DON'T CHOOSE
> YOUR CABLE PROVIDER. THERE IS ONLY ONE IN THE TOWN. If he is running NT on
> his servers, and you are running Mdk60 which use the "pump" program to get
> the IP, and that it fails 50% of the time, what can you do? Nothing. Just
> tell the problem on cooker mailing list and say that dhcpcd is working much
> better. Then you wait for an official patch. 1 month. 2 months.
Actualy I am nt limited to one cable provider, thats called a monoploy and
against the law. In particular my state sub funds the little guys, to keep
them afloat here. Not to mention the two Microwave cable providers.
> One day, you decide to do the patch yourself. You try it during 3 days. You
> don't have any problem : it works perfectly. You decide to send your patch
> to the cooker list. You think that people will greet you for helping. But
> no. No answer. Well, you think that they just don't have the time. You wait.
> 1 week away. Still no answer. Then you complain again, because you feel that
> nobody cares of your problem, and that the next Mandrake will be shipped
> with a bug that you corrected.
Are we on the same mailing list? Both me and Bernhard have stated that
we've done this ateast once each and that the changes got lost.
> And then, at least, an answer. One guy explains you that he doesn't have the
> problem personnally. So he doesn't care at all. In fact, this is just like
> there is no problem. "Everything >/dev/null".
Never said i didn't care. I stated that mine was working, and that I would
try to gleen some info from the tech.
> Listen, Axalon : "pump" is **NOT** DHCP compliant, and MANY PEOPLE have
> problems with it. Pump works for you? Very fine. Do you consider that this
> is a sufficient reason to let it as the default DHCP client in the next
> Mandrake? Don't you think that DHCPCD could work just as fine for you, just
> as it worked in Mandrake 5.1, 5.2, and 5.3 ?
It's not? Erik, care to comment?
Don't really know, how dhcpcd worked in 5.1 5.2 5.3 or 6.0, dhcp is for
lazy admins by lazy admins, and they should all be hung right along side
the guy that birthed bill gates.
Now personal beliefs out of the. Yes it should work out of the box, and it
should work well out of the box. We wouldn't have provided both with only
one functional, i've once again patched initscripts (Loose em again i'll
hunt you down and beat you, and remeber i fly really cheap so don't think
you safe over in europe =P )
> If this is what you think, then there is probably a job for you at
> Microsoft.
Sorry i'm over qualified i can tie my own shoes.
> Gregus
>
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
