Some patches are on the LRP ftp sites or mirrors. Linux kernel on ftp.kernel.org or mirrors. Alan Cox's pre patches on Alan's site.
Most packages based on Debian, www.debian.org. Current release: slink
v1.9.0 was the last libc5 version. All later versions are now libc6 (glibc) based. If you have something that you can not recompile for libc6, you can add the libc5 library if you have enough room. Both libc6 and libc5 can co exist. (see also, what distr to use to make packages)
Some people can offer commercial support. If you want to be added to the list, send mail to the FAQ maintainer. Currently you may try Dave or Paul
ftp.psychosis.com/linux/linux-router-devel/
See the above question. You would also want to put some X clients on the system, specificlly netscape. That is NEVER going to fit on a single floppy. Also running eveything out of the ram disk may not be feesable as well. Setting up a large (say 32MB) ramdisk could be done, but the down side will mean quite a long boot time to load everything into it. On the upside once it's booted performance would be GREAT! Something like this would require an LS-120 or ZIP. A SCSI ZIP would work quite well if you want to run right off of that as opposed to the ram disk approach. Of course you could always use a harddrive. Then why not go to a full distribution? Maybe you should. LRP is still much simpler to deal with. Less to maintain. Less to break. It's up to you to pick the best tool for the job.
Why not? I've had some one ask this before, and it's certainly feasable, though whether an X server and all the required files will fit on a normal floppy is questionable. Either way you should be able to make a standard package that can add all this.
Generally, no. Once the disk (boot medium) is prepared it is FULLY self contained and can be backed-up on to itself. Most any OS can be used to build a disk. The archives are in tar-gzip format and can be pulled apart by most any OS. It should also be possible to rebuild the archives on any OS that supports Unix file permissions.
It sure helps, but again generally no. What you do need is a firm understanding of the Unix way of doing things, the TCP/IP stack, and how sh scripts work. This is not to say you're lost if you don't. LRP has a menuing system that easily gets to most of the files you need to change, and comments in those files to support you further. As these systems mature the required learning curve will decrease.
The boot medium contains a linux kernel, generic root archive, and package archives of addtional features to be merged with the rest of the root at boot time (such as PPP, snmp, RADIUS support, etc). When the disk is booted these archives are uncompressed and extracted into a ramdrive (/dev/ram0) then the ramdrive is mounted as root. The entire system runs solid state from ram.
Any changes made to the root must be backed up to the boot medium, or they will be lost after a reboot. The procedure to back up is menu based, and if need be, can be automated to take place at regular intervals.
debin blah
LRP has no entity you can pay. We suggest you make your contribution to either the FSF or to Debian. Active contributors have also never declined a full expenses paid vacation to a land of choice......
The Linux Router Project (LRP) is a networking centric mini-distribution of Linux. It is small enough to fit on a single 1.44MB floppy disk, and makes building and maitaining routers, terminal servers, and typically embedded networking system next to trivial.
Some known examples are:
Dave uses it for an ISP modem pool (psychosis.com?)
Bret uses it to upload digital maps every 5 minutes, from a solar-powered, spread spectrum radio connected LRP box. See http://water.gbasin.net especially http://water.gbasin.net/1.html
Feel free to tell us your most exotic LRP machine.
I know of some, here are the links. Feel free to add to it. also see the "Commercial support for LRP" link
Private IP space
Anyone on the routing RFC's ?
Depends on the program
routed: ? gated: ? zebra: http://www.zebra.org/
(Paul: this obviously needs someone :)
NET3 MULTIPLE-ETHERNET
Make a nice list of commonly used port numbers with possibly links to the products (eg realaudio etc) Meanwhile, checkout /etc/services
Nope, there are alternatives. See: muLinux