Mike Noyes wrote:
>
> 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 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.
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
