Slashdot Mirror

I'm working on a really cool project right now at work. It's a Mason/mod_perl-based front-end to RRDtool. Since its development directly benefits my employer, they have no problem letting me work on it. Once I get this thing into a state that is worth distributing, it will most likely be open-sourced.

The easiest way to get your project funded is to get a job at a place lets you do "project" work and is also open source-friendly like my employer. Chances are, if your project is cool, there is some commercial potential for it.

Good Luck!

Chris

Reading the install.txt file, I noticed that the source code for the Kernel is not included. (1) Why it is not in the distribution file? (2) How and where I can get it?

The source of the Kernel is made available under license from the ETH to people that propose a specific kernel-related project. For commercial use there is a small license fee per installed system. Please contact Prof. Gutknecht gutknecht@inf.ethz.ch in this regard.

Try MRTG, a nice tool for obtaining SNMP info. I use it for reporting utilization on my routers, others use it for modem usage, processor utilization, memory usage, uptime, basicly whatever you can get a MIB on. Also, freshmeat.net returns about 17 hits on a search for "SNMP". Google returns about 6206 hits on a search for SNMP from their www.google.com/linux page.
Some of it looks very usefull, of-course I have yet to do a search on Google that does not return good results.

You could get a wireless, solar-powered weather station for your roof. Then you could get some UNIX-based software and MRTG and put some graphs of your station online.

Half a decade ago I did some performance comparisions of different machines and compilers (available here).

The DEC C-Compiler was way faster than gcc (352ms compared to 464ms on a 21066-166).

All old numbers, but it gives a hint.

• have a look over at Walter Lord's excellent Ensoniq Audio PCI page

  http://www.netexcite.com/audiopci/inde x.html

• BTW: Walter offers the 8MB wavesets for Windows too.

  http://www.netexcite.com/audio pci/audiopcilinks.html

  How I wish that we could use this under Linux/FreeBSD - has anyone decoded the format?

• Then we got Michael Hyman's list of resources

  http://www.op.net/~mikeh/ensoniq.html

• The Linux driver from Thomas Sailer is here:

  http://www.ife.ee.ethz.ch/~sa iler/linux/pciaudio.html

• And on this daemonic site

  ftp://ftp.lf.net/pub/users/Joachi m.Kuebart/es1370

  Jochen Kuebart stores up his early FreeBSD driver (which is integrated in 4.0-CURRENT) and put specs online (they used to be on Ensoniq's site).

Another note:
The original Ensoniq Audio PCI seems to be closest compatible to the SB 128PCI, the PCI 64 uses a lower quality codec if remember right. ES1371 based cards might come with different codecs that comply to some Intel spec (you will notice when you read the specs).

And I saw reports about ES1373 based cards - but I have no clue how this differs to the ES1370, ES1371 - and heck, where is the ES1372? :-)

I hope this gives you something to go along.

MRTG is kinda a bear to work with for monitoring stuff other than a router, but it can be done. For an example you can check out my suso.org stats page. Look on the left side.

MRTG 2.x can be found at this page. It discusses using MRTG and provides a few hints for installation and use. It is not a substitute for reading the documentation that comes with the source which is distributed under the GPL.

Active development on MRTG 2.x (currently 2.7.4) has essentially stopped. There have been occasional patches and slight feature enhancements over the past year or two, but little active development.

The reason active delevopment stopped was the MRTG uses a very simplistic data storage mechanism. Whenever MRTG 2.x runs, it must reading in its entire data file and write it back out. While this works for small to medium numbers of interfaces (up to a few hundred), it starts to slow down dramatically and becomes unusable. The solution for this has been to divide up the load by using multiple instances of MRTG.

To resolve this, Tobi started working on a data storage tool he called the RRD Tool, the Round Robin Database. Using this tool, you can support several thousand intefaces. It is also distributed under the GPL as is everything he distributes. You can find more details about it at the above noted site or in the USENIX presentation he made.

While there is technically no "MRTG 3.0," several data collecting frontends are already in production use for Tobi's RRD Tool backend. The above mentioned cricket is one of them.

MRTG 2.x can be found at this page. It discusses using MRTG and provides a few hints for installation and use. It is not a substitute for reading the documentation that comes with the source which is distributed under the GPL.

Active development on MRTG 2.x (currently 2.7.4) has essentially stopped. There have been occasional patches and slight feature enhancements over the past year or two, but little active development.

The reason active delevopment stopped was the MRTG uses a very simplistic data storage mechanism. Whenever MRTG 2.x runs, it must reading in its entire data file and write it back out. While this works for small to medium numbers of interfaces (up to a few hundred), it starts to slow down dramatically and becomes unusable. The solution for this has been to divide up the load by using multiple instances of MRTG.

To resolve this, Tobi started working on a data storage tool he called the RRD Tool, the Round Robin Database. Using this tool, you can support several thousand intefaces. It is also distributed under the GPL as is everything he distributes. You can find more details about it at the above noted site or in the USENIX presentation he made.

While there is technically no "MRTG 3.0," several data collecting frontends are already in production use for Tobi's RRD Tool backend. The above mentioned cricket is one of them.

MRTG 2.x can be found at this page. It discusses using MRTG and provides a few hints for installation and use. It is not a substitute for reading the documentation that comes with the source which is distributed under the GPL.

Active development on MRTG 2.x (currently 2.7.4) has essentially stopped. There have been occasional patches and slight feature enhancements over the past year or two, but little active development.

The reason active delevopment stopped was the MRTG uses a very simplistic data storage mechanism. Whenever MRTG 2.x runs, it must reading in its entire data file and write it back out. While this works for small to medium numbers of interfaces (up to a few hundred), it starts to slow down dramatically and becomes unusable. The solution for this has been to divide up the load by using multiple instances of MRTG.

To resolve this, Tobi started working on a data storage tool he called the RRD Tool, the Round Robin Database. Using this tool, you can support several thousand intefaces. It is also distributed under the GPL as is everything he distributes. You can find more details about it at the above noted site or in the USENIX presentation he made.

While there is technically no "MRTG 3.0," several data collecting frontends are already in production use for Tobi's RRD Tool backend. The above mentioned cricket is one of them.

MRTG 2.x can be found at this page. It discusses using MRTG and provides a few hints for installation and use. It is not a substitute for reading the documentation that comes with the source which is distributed under the GPL.

Active development on MRTG 2.x (currently 2.7.4) has essentially stopped. There have been occasional patches and slight feature enhancements over the past year or two, but little active development.

The reason active delevopment stopped was the MRTG uses a very simplistic data storage mechanism. Whenever MRTG 2.x runs, it must reading in its entire data file and write it back out. While this works for small to medium numbers of interfaces (up to a few hundred), it starts to slow down dramatically and becomes unusable. The solution for this has been to divide up the load by using multiple instances of MRTG.

To resolve this, Tobi started working on a data storage tool he called the RRD Tool, the Round Robin Database. Using this tool, you can support several thousand intefaces. It is also distributed under the GPL as is everything he distributes. You can find more details about it at the above noted site or in the USENIX presentation he made.

While there is technically no "MRTG 3.0," several data collecting frontends are already in production use for Tobi's RRD Tool backend. The above mentioned cricket is one of them.

Note that Cricket is not a direct replacement for MRTG; it is a frontend for RRDtool, which is maintained by Tobi Oetiker as the "successor" to MRTG.

RRDtool manages the storage and retrieval of time-series data in an intelligent way, making it easy to write programs that manipulate such data. There are at least two frontends to it (including Cricket) that perform data collection and presentation functions. Hopefully there will be many other applications that make use of RRDtool.

Of course, you can read about all that on the
web page for RRDtool.

Cricket and RRDtool together pretty much give you the current functionality of MRTG, with a much better configuration scheme and a more extensible framework.

It looks rather like he uses MRTG ( Multi Router Traffic Grapher). It's a tool for tracking router usage.

I like his weekly graph. Older data is on the right, and you can see normal traffic (green is in, blue is out) and compare to the slashdot effect beginning mid-Thursday.

I'm pretty sure that the drivers included are the OSS Lite with some additions. Linux drivers for PCI soundcards seems to be the source of my AudioPCI drivers, not OSS.
Time flies like an arrow;