Nothing nailed down so-far...the whole enchalida is up for grabs! I'd
especially like to see a clean, extensible, understandable method for
setting up complex networking configurations static routes, since we're
Something like a meta-defninition that goes in the package (currently
Lynn wrote regarding the Mosquito distribution:
I have been busy looking at some CGI options myself lately. :)
soapboxPersonally, I think there's something fundamentally wrong with
managing a firewall/router through a web-based interface, but it seems that
I'm the only one who feels this
Dave,
I've noticed that the cdrom.cfg, smallnet.cfg, etc. configuration files on
the bootable cd are not in the root directory of the cdboot.ima image on the
CD.
Instead, they are inside the root.lrp, in /var/boot/config.
This is different from the standard floppy boot images, where the .cfg
You're seeing this error because the default configuration is linux -
which is for a floppy-based boot. The most recent CDROM should use
cdrom as the default config.
Ah. Thanks.
The default screen is the linux config screen. F1 will make the
cdrom/largenet/firewall/etc. options appear, and
Luis.F.Correia wrote:
When booting from a CD, the only floppy formats supported are 1.44
and 2.88.
Check which format Oxygen-CD is using and correct your config file.
Luis,
Thanks.
Just as a clarification, the CD-image I'm using is (currently dated Dec 17)
and at:
David, others, is there a reason for using syslinux instead of isolinux?
I'd say it's easier to use isolinux and forget about floppy images on
the CD.
FWIW,
ISOLinux worked great on the initial load, but there were some problems with
LINUXRC.
If I recall correctly, it seemed to want to mount
David Douthitt wrote:
Also, the Oxygen Bootable CDROM has been updated, but the 'largenet'
configuration is still SegFaulting at the end. Please help me find
out why It's very puzzling, as there is plenty of RAMdisk space
and other configurations work fine.
In case it is any help to
If people could bang away on the Oxygen development image, I'd
appreciate it. I'd like to hear from some testers before I release...
Finally got a chance to download (and test), so far looks good. The
config.lrp handling works nicely now. Thanks!
As an observation, /dev/boot seems to be a
On Tue, 4 Dec 2001, Charles Steinkuehler wrote:
snip
Yeah, I think it's pretty big, plus I believe most of these packages
require
openssl and other huge add-ons to run. The basics of public-key
cryptography, however, are pretty simple, so I think it'd be possible to
make a small (a few K,
Jack Coates [EMAIL PROTECTED] wrote:
And for this reason I'm thinking that versioning in the filename is a
convenient nice-to-have. If the version and author attributes are kept
on the web server that should be enough to enable accurate downloads,
though there are still troubleshooting issues.
Charles Steinkuehler wrote:
How do your fields compare against those stored by rpm deb?
A quick cruise over to debian and rpm.org produced this for me
(Sorry, Dave, if I'm speaking out of turn)
rpm debianDave
NamesourceName
Version Version
David Douthitt wrote:
I have a strong faith in the current format - even if we package up
newfangledsoftware 2.2.2 as a *.lrp with glibc 2.0, it'll still work
in that LRP 2.9.4 somebody's running.
If we add a new file (*.desc) to the /var/lib/lrpkg directory, the
package STILL works in
David Douthitt wrote:
About all that can be asked for is a comment-like tag that package
creators use to detail dependencies.
Agreed. That's what I was thinking of - comments for things the
maintainer knows of, with no guarantee that its accurate or comprehensive.
And I see what you mean
- Original Message -
From: arne @ loopback . org [EMAIL PROTECTED]
I would go a step further. make a minimal busybox only containing very
few
applets(tar,msh as shell,mount,ls,cat,...) And link it statically with
uClibc. This will result in a quite small binary and you don't need to
14 matches
Mail list logo
