Nothing like trial and error, but cone on, let's not have have each person individually reinvent the wheel. Many man hours are wasted trying to figure out how the most basic commands work by experimentation, when it would be so easy to just make a clear explanation of them in the documentation. Some examples of the command line would be most helpful. While Linux, in general is not for the faint of heart, the doccumentation for this particular set of tools is overly cryptic. I, for one, am not a programmer and can't "read the source code". Not that that should be necessary for anyone not refining it anyway. With a good explanation of the cammands and variables, those man hours could be spent working on innovative ways to impliment these wonderful tools, rather than trying to figure out which end goes up. I have spent days trying to do the most basic things with these new tools that I accomplished in hours with 2.2.x, and have made some progress but it does not have to be so difficult. The Linux project is a wonderful thing! Millons of people from all over the world, working together and sharing their knowledge and ideas. And creating a first rate OS in the process. Linux is gaining more and more support every day. I believe that it will soon find it's place in the commonwealth that it is so deserving of, but for that to happen it's features must be accessable to users other than the Elete. Finally, the power is in the right place. In the hands of the users. Let's try and get along. We are all on the same team. ----- Original Message ----- From: "Ramin Alidousti" <ramin@xxxxxx> To: <lartc@xxxxxxxxxxxxxxx> Sent: Wednesday, June 13, 2001 4:49 PM Subject: Re: Re: [LARTC] How to use tc to limit bandwidth of a special IP in LAN > On Thu, Jun 14, 2001 at 01:02:19AM +0200, Wingtung.Leung wrote: > > > First, the best way to learn things is to try it. If you think that's a > > I'm not opposed to trying. But just think how much time you'd waste if you had > to start from nowhere with apache/sendmail/bash/netfilter and many many other > applications. Of course you have the source and can figure out what they do > by going through the code line by line, but that's not the point. > > Why do you think that your "GNU/Linux" has "Linux Documentation Project"???? > > > waste of time, you shouldn't be using GNU/Linux in the first place, but > > consider a commercial boxed Cisco router or something alike. > > Actually, one of the reasons that I don't like the commercial products like > cisco is that you get: > > Command Comment > ------- ------- > ip cef enables cef > no ip cef disables cef > > but what the heck is cef in the first place? > > Most of the Linux applications have an excellent documentation. iproute2 is > an exception. > > > And secondly, the best and most accurate documentation: the source code. > > Every detail is explained there. > > I'm glad that it's not coded in machine language... > > > No offence. > > non taken. > > > A handle is just a tool or way to hold something, in this case a pointer > > or reference to the previously constructed class. > > > > (Please don't CC me, I'm already subscribed to the list.) > > I'd expected more from an academicus as yourself. They used to have many > courses like "formele specificaties". Did they remove them from the programs? > > Ramin > > _______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/ >
