Re: [Leaf-user] Bering and DOC2000
At 2002-02-16 22:52 -0500, Patrick Nixon wrote: I'm relatively new at the whole development, unusual requirements thing, so while I am confident about compiling a kernel and whatnot, getting it t boot properly is shaky ground for me. Pat, Have you read Developer Guide? http://leaf.sourceforge.net/pub/doc/guide/developer.rtf Also, look at the developer FAQs in sec13. http://leaf.sourceforge.net/content.php?menu=1105page_id=19 -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf.sourceforge.net/content.php?menu=1000page_id=4 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Jacques Nilo wrote: I am :-). It takes some time to reach Europe :-) :-) Bering is a miniature Linux OS that lives entirely on a 1.68 MB diskette, and it's purpose is to act as a router/firewall that connects two networks, filtering the content to protect the internal network. Bering is based upon a tried and true router/firewall called Dachstein (version rc2), created by Charles St[ei][ie]nk[ue][eu]l[h]er, sigh. The Bering firewall uses iptables for the firewall rules and Linux kernel 2.4.x as the base OS. Running Bering on an old Pentium with 32 MB of RAM is like using one of those Linksys or DLink router-firewalls, except that Bering is much more powerful, capable, and extensible. I'll buy that description if there is no copyright attach to it. Everything I post to the internet, by it's nature, can't be copyrighted, because the internet is the essence of free exchange. Just because I arranged a series of 1's and 0's in an interesting pattern does not give me the right to claim that I am the only one who can do so. But that's a whole 'nother thread for a differernt newsgroup :-o In other words, you're welcome to it without restriction. The problem I noticed with it right after I hit send was that it didn't mention Shorewall, a fundamental aspect of making it a router/firewall. So maybe the line would need to say: upon a tried and true router called Dachstein rc2, created by Charles S_ and upon the Shorewall firewall by Tom Eastep. Some news about Bering beta-4 about to be released: the initial loading of modules from boot/lib/modules now works properly ifupdown has been fixed and do not use ifconfig and route anymore (only ip) latest shorewall to be included Should be ready for testing tomorrow I would like to include in the doc two paragraphs about: Booting Bering from an hard disk This varies a lot with the syslinux version used and the available tools to prepare the hard drive. If you have a stable set of tools like mkdosfs, syslinux, and the like, then this wouldn't be too hard. David made a lot of these tools into .lrp packages. I'll mess around with them some more. But I've syslinuxed an IDE drive and still had remenants from System Commander in the master boot block that screwed with booting to the syslinux boot: prompt. So it's never a piece of cake, especially with syslinux going through so many revisions. I'll see if anyone knows the best version so far. Booting Bering from DOC From an M-Systems Disk On Chip? Any volunteer ? Next on the list: ipsec Cheers Jacques ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Since I see you are using MTD, would you be able to make your image available to others? If you need space to host it, I'll find someplace to put it. For some reason it seems like I'm pushing the envelope of Leaf by wanting to use PCMCIA Wireless Cards and a DOC2000 ;) Thanks! --Patrick On Fri, 8 Feb 2002, Bao C. Ha wrote: Hi guys, I have been able to bring the Jacques Nilo's Bering Leaf distribution up on a Disck-On-Chip (DOC2000) based system. I am using the Beta 2 since there seems to be problems with modify the Beta 3 floppy image. Following is the summary of changes to make it happens. (1) The DOC2000 has one partition. It is used as an ext3 filesystem. The content of the floppy image is put on the DOC's partition. (2) Grub. I am using grub to boot up from DOC. Following is the /boot/grub/menu.lst file. default 0 timeout 5 title=Linux with video card and keyboard kernel (dc0,0)/linux ramdisk_size=1536 init=/linuxrc \ root=/dev/ram0 boot=/dev/nftla1,ext3 LRP=root,etc,local,\ modules,pump,keyboard,shorwall,dnscache,weblet,dhcpd,ppp,\ pppoe,log,libz,sshd,sshkey,ssh,sftp initrd (dc0,0)/initrd.lrp Notes: - The kernel command is all on one line. - There is no PKGPATH. That will hang the DOC2000. Mtd devices can't be mounted at multiple points at the same time. (3) Loading required modules at boot time. The /boot/etc/modules is changed to load the following modules: (the order is very important to detect nftl on DOC2000) mtdcore docecc doc2000 docprobe nftl mtdchar mtdblock jbd ext3 There is probably no need to load mtdchar and mtdblock. Both the jbd and ext3 modules can be replaced by another fs module, like ext2, if ext2 file system is to be used for the DOC2000. These modules are also downloaded into the /boot/lib/modules directory (4) Add the following to the /var/lib/lrpkg/root.dev.mk file to create the /dev/nftla devices. #DOC nftl makedevs nftla b 93 0 0 8 s null 21 makedevs nftlb b 93 16 0 8 s null 21 That is all! Thanks. Bao ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
At 2002-02-16 08:21 -0500, Patrick Nixon wrote: Since I see you are using MTD, would you be able to make your image available to others? If you need space to host it, I'll find someplace to put it. Patrick, The LEAF Bering release has mtd modules. http://leaf.sourceforge.net/devel/jnilo/leaffw.html http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/drivers/mtd/ For some reason it seems like I'm pushing the envelope of Leaf by wanting to use PCMCIA Wireless Cards and a DOC2000 ;) Yes. We're working to make this easier. -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf.sourceforge.net/content.php?menu=1000page_id=4 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Are there any special procedures for me to boot off the DOC? rdev it and that's it? --Pat On Sat, 16 Feb 2002, Mike Noyes wrote: At 2002-02-16 08:21 -0500, Patrick Nixon wrote: Since I see you are using MTD, would you be able to make your image available to others? If you need space to host it, I'll find someplace to put it. Patrick, The LEAF Bering release has mtd modules. http://leaf.sourceforge.net/devel/jnilo/leaffw.html http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/drivers/mtd/ For some reason it seems like I'm pushing the envelope of Leaf by wanting to use PCMCIA Wireless Cards and a DOC2000 ;) Yes. We're working to make this easier. -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf.sourceforge.net/content.php?menu=1000page_id=4 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
At 2002-02-16 09:37 -0500, Patrick Nixon wrote: Are there any special procedures for me to boot off the DOC? rdev it and that's it? Pat, I don't know the exact procedure you need to follow. You may be the first person to try the mtd support in Bering. I'm sorry I was unable to help you further. Maybe someone else has some information that will help you. On Sat, 16 Feb 2002, Mike Noyes wrote: The LEAF Bering release has mtd modules. http://leaf.sourceforge.net/devel/jnilo/leaffw.html http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/drivers/mtd/ -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf.sourceforge.net/content.php?menu=1000page_id=4 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Bering and DOC2000
Since I see you are using MTD, would you be able to make your image available to others? If you need space to host it, I'll find someplace to put it. I don't have a floppy image. I took the Bering beta 2 image and dump everything on it to my DOC2000. All of the kernel stuff is actually in Jacques's web space, http://leaf.sourceforge.net/devel/jnilo/latest/. But, you can just build your own kernel and use it instead. Jacques has a kernel config file that can be used as a template. I have to build my own, since I could not get the IDE driver to work properly. Plus, Jacques' kernel has not been patched to work with Freeswan. The only tricky part is to rebuild the initrd image: initrd.lrp, to include the mtd device drivers. Let me know and I will send mine. Thanks. Bao ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Bao C. Ha wrote: you can just build your own kernel and use it instead. Jacques has a kernel config file that can be used as a template. I have to build my own, since I could not get the IDE driver to work properly. So the ide driver is not compiled into the kernel and you couldn't load something like ide.o in initrd.lrp? Ok. The only tricky part is to rebuild the initrd image: initrd.lrp, to include the mtd device drivers. Is there an mtd.o? Is that the only .o module that needs to be loaded specially for the DOC, assuming the ide support is compiled into the kernel? Curious, Matthew ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Bering and DOC2000
you can just build your own kernel and use it instead. Jacques has a kernel config file that can be used as a template. I have to build my own, since I could not get the IDE driver to work properly. So the ide driver is not compiled into the kernel and you couldn't load something like ide.o in initrd.lrp? Since we don't use modprobe, the ide modules: ide-mod.o ide-mod-probe.o, ide-disk.o, ... have to be loaded at the right sequence. I did it and get it to work with my kernel, but not Jacques' one. I did not pursue any further once I got it to work. The only tricky part is to rebuild the initrd image: initrd.lrp, to include the mtd device drivers. Is there an mtd.o? There is no mtd.o, but a collection of mtd drivers: mtd-core.o, docecc.o, doc2000.o, docprobe.o, and nftl.o, to support DOC2000. Is that the only .o module that needs to be loaded specially for the DOC, assuming the ide support is compiled into the kernel? You don't need ide support to be built-in into the kernel. I have been playing with two systems: one with DOC2000 and one with a small IDE disk. On the DOC2000 system, I don't need ide at all. Again, the problem is that we don't use modprobe. The mtd or ide drivers have to be loaded in the right sequence for them to detect the hardware and work properly. Since they are required during bootup, they have to be loaded from the initrd image. Bao ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
I don't know if JN is reading this thread, but it'd be nice if the above link would go a bit further in the What is Bering description. To say it is basically an enhanced Dachstein doesn't tell the new person what Bering is if they don't know what Dachstein is. I think the answer would want to include something like: I am :-). It takes some time to reach Europe :-) Bering is a miniature Linux OS that lives entirely on a 1.68 MB diskette, and it's purpose is to act as a router/firewall that connects two networks, filtering the content to protect the internal network. Bering is based upon a tried and true router/firewall called Dachstein (version rc2), created by Charles St[ei][ie]nk[ue][eu]l[h]er, sigh. The Bering firewall uses iptables for the firewall rules and Linux kernel 2.4.x as the base OS. Running Bering on an old Pentium with 32 MB of RAM is like using one of those Linksys or DLink router-firewalls, except that Bering is much more powerful, capable, and extensible. I'll buy that description if there is no copyright attach to it. Some news about Bering beta-4 about to be released: the initial loading of modules from boot/lib/modules now works properly ifupdown has been fixed and do not use ifconfig and route anymore (only ip) latest shorewall to be included Should be ready for testing tomorrow I would like to include in the doc two paragraphs about: Booting Bering from an hard disk Booting Bering from DOC Any volunteer ? Next on the list: ipsec Cheers Jacques ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Pat, I don't know the exact procedure you need to follow. You may be the first person to try the mtd support in Bering. I'm just going to fire off some thoughts, perhaps not the correct answer :) I thought Charles laid it out pretty well in his hard disk howto and the cdrom howto boot instructions. Even though the directions refer to booting from a different device, the fundamental parts remain true, imo: 0) Need to be able to prove you can access the DOC device from a running LEAF system, thereby defining the modules that needed to be loaded to talk to it. Make note of IRQ's and addresses for comparison later. Using something I recall as Mullenstein (John Mullen did it I think), I have successfully booted and loaded using the M-Systems doc.o However, due to the license of M-systems driver, it can't be redistributed (or at least that's my understanding.) I've even compiled my own version of the kernel. Bering is based off 2.4.x which has MTD support directly in the kernel. Which shouldn't be too big of a problem to test except that my system with the DOC doesn't have a floppy so it's a rather time consuming process to try different sets of files. (I know, poor me ;) I'm relatively new at the whole development, unusual requirements thing, so while I am confident about compiling a kernel and whatnot, getting it t boot properly is shaky ground for me. 1) Need those modules that made the DOC work loaded for the kernel during the bootstraping initrd process (put them in /var/lib/modules?). So the idea is to take the working image from step (0) and burn a new diskette making sure that... 2) syslinux.cfg points to the boot device and the DOC modules get loaded during boot. Isn't that the big picture? If so, I'd like to hear about this fellow's configuration in level (0), and then move on. A big factor with these PC Cards and Compact Flash Cards is that they don't normally get an irq assignment by the PCI bios, or something like that, during POST, the way the other devices do. Johan and a few others are hashing through the details of what it takes to force a mass storage card to the correct IRQ and base address, or at least to reserve those settings for the device to take when it's driver loads. The issue is with the CardBus bridge and the CF bridge, which buffer data to the PCI bus and have to handle recognizing the different PC Cards during hot-swap operations. Maybe CF Cards with True IDE emulation would work easier. The LEAF Bering release has mtd modules. http://leaf.sourceforge.net/devel/jnilo/leaffw.html I don't know if JN is reading this thread, but it'd be nice if the above link would go a bit further in the What is Bering description. To say it is basically an enhanced Dachstein doesn't tell the new person what Bering is if they don't know what Dachstein is. I think the answer would want to include something like: Bering is a miniature Linux OS that lives entirely on a 1.68 MB diskette, and it's purpose is to act as a router/firewall that connects two networks, filtering the content to protect the internal network. Bering is based upon a tried and true router/firewall called Dachstein (version rc2), created by Charles St[ei][ie]nk[ue][eu]l[h]er, sigh. The Bering firewall uses iptables for the firewall rules and Linux kernel 2.4.x as the base OS. Running Bering on an old Pentium with 32 MB of RAM is like using one of those Linksys or DLink router-firewalls, except that Bering is much more powerful, capable, and extensible. If I don't hear from him, I'll suggest that in another thread. Good Luck, Matthew ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Bering and DOC2000
Hi guys, I have been able to bring the Jacques Nilo's Bering Leaf distribution up on a Disck-On-Chip (DOC2000) based system. I am using the Beta 2 since there seems to be problems with modify the Beta 3 floppy image. Following is the summary of changes to make it happens. (1) The DOC2000 has one partition. It is used as an ext3 filesystem. The content of the floppy image is put on the DOC's partition. (2) Grub. I am using grub to boot up from DOC. Following is the /boot/grub/menu.lst file. default 0 timeout 5 title=Linux with video card and keyboard kernel (dc0,0)/linux ramdisk_size=1536 init=/linuxrc \ root=/dev/ram0 boot=/dev/nftla1,ext3 LRP=root,etc,local,\ modules,pump,keyboard,shorwall,dnscache,weblet,dhcpd,ppp,\ pppoe,log,libz,sshd,sshkey,ssh,sftp initrd (dc0,0)/initrd.lrp Notes: - The kernel command is all on one line. - There is no PKGPATH. That will hang the DOC2000. Mtd devices can't be mounted at multiple points at the same time. (3) Loading required modules at boot time. The /boot/etc/modules is changed to load the following modules: (the order is very important to detect nftl on DOC2000) mtdcore docecc doc2000 docprobe nftl mtdchar mtdblock jbd ext3 There is probably no need to load mtdchar and mtdblock. Both the jbd and ext3 modules can be replaced by another fs module, like ext2, if ext2 file system is to be used for the DOC2000. These modules are also downloaded into the /boot/lib/modules directory (4) Add the following to the /var/lib/lrpkg/root.dev.mk file to create the /dev/nftla devices. #DOC nftl makedevs nftla b 93 0 0 8 s null 21 makedevs nftlb b 93 16 0 8 s null 21 That is all! Thanks. Bao ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user