Re: [Leaf-devel] make.lrp

2002-03-20 Thread ssrat

On 19 Mar 02, at 16:02, Jacques Nilo wrote:

  I came across David's make.lrp. Assuming that dependencies are in order
  shouldn't I be able to just load this package into Bering and be able to use
  it as a development station. Any insight on this would be appreciated.

 If make.lrp was compiled against glibc 2.0 which is most probably the case
 there should not be any problem. Just give it a try :-)

It should have been done against glibc 2.0, so there shouldn't be 
any problem.  Of course, make isn't enough - but with gcc and 
automake and autoconf and all of the /usr/include headers and 
kernel headers and other include files and bison and flex and yacc, 
you should be okay :-)

My thoughts on creating make was that it's useful for so many 
OTHER things as well:

make diskimage
make backupimage

(who knows?)


___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Embedded Systems Conference

2002-03-16 Thread ssrat

Anyone see the (minature) write on Coyote in 2600?  Interesting - 
though odd that they wouldn't mention the Free versions (aside 
from LRP).



___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] CVS, Makefiles, and Sources

2002-01-23 Thread ssrat

This is shaping up to be very nice; I've got a directory for busybox and uClibc 
which contains:

* Makefile
* patches/ directory - Oxygen busybox has about 4-6

Then the makefile will download the appropriate version (using wget) and 
compile it using uClibc (as Oxygen does) - and create a busybox binary.

I've some more finalizing to do, but I think this may be just the way to go.  
Then the problem becomes:

* When working as a developer from CVS, one has to clean out all of the 
binary stuff before a commit.

Probably the best thing would be to use the makefile:

# make commit

..or similar...






___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Proposed CVS Structure

2001-05-03 Thread ssrat

On 3 May 2001, at 10:44, Ewald Wasscher wrote:

 [EMAIL PROTECTED] wrote:

  I wound up using whatever diffs [for ash that]
  Erik [Andersen] had.

 Fair enough. If you could send me the diff that converts the makefile to 
 gnu-make style I'd be thankful.

Everything should be in the Oxygen ISO; I had to clean out the ash 
source directory as I had several generations of ash, most 
uncompilable, several different diffs, etc.  The ash source on the 
CDROM should be clean, compile, and contain all the appropriate diffs.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Introducing myself

2001-05-01 Thread ssrat

On 30 Apr 2001, at 19:32, KP Kirchdörfer wrote:

 I've also an lrp package for dinosaurs available - rexx.lrp based on Ian
 Colliers REXX/imc.

I've seen REXX, but never got into coding it.  I've looked at it a
time or two; may even have some DOS versions.  If you like REXX, you
might like my copy of THE (The Hessling Editor) - a copy of the VAX
EDT editor which to my inexperienced mind looks a lot like SPF :-)

 I've learned a lot from David's Oxygen ideas, and used it wherever I was able
 to - with one exception: I'm not going to present a new LEAF developer, as he
 did yesterday. Congratulations to you and your family, David!

Thank you!  God has indeed blessed us

--
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Proposed CVS Structure

2001-05-01 Thread ssrat

On 1 May 2001, at 15:19, Ewald Wasscher wrote:

 Wouldn't it be a good idea to have a default way of building packages, 
 like Debian? With Debian you can cd into the upacked/patched source 
 directory and do a dpkg-buildpackage -b and voila! a binary package 
 appears after a while. So we could e.g. require that packages have a 
 LEAF.Makefile that automatically configures and builds a package, or a 
 leaf subdirectory like the debian subdirectory in Debian. Any comments?

With most source archives, you can cd into the unpacked source 
directory and do a make and voila! a binary package appears after a 
while :-)

What I had in mind was to do the same thing, but with patched sources 
- and thus then create a package at the same time.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Web Site DOWN

2001-04-29 Thread ssrat

On 23 Apr 2001, at 19:37, Mike Noyes wrote:

 Ewald Wasscher, 2001-04-23 20:22 +0200
 Mike Noyes wrote:
 Interesting. The German text is present on the SF home page again. At 
 least I think it's German.
 
 No, it's Dutch! (which is very similar to German)

Then there is Pennsylvania Dutch - which *IS* German (though of a 
dialect no longer spoken in Germany or anywhere outside of Amish 
and Old Order Mennonite and Hutterite settlements...)
-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread ssrat

On 25 Apr 2001, at 21:02, KP Kirchdörfer wrote:

 Is the only choice between Scylla (vi-mode) and Charybdis (wasting disk
 space)?

e3ws, e3vi, e3ne, e3em, et al, are just links to e3; in Oxygen you
need to be careful as the actual binary is e3.bin, with a shell
wrapper and all the links point to e3.bin.

Anyway, the lack or presence of backup files is a compile-time option
for e3; you can set it or not.  The vi emulation is built into e3, as
are the others.  The setting should be valid for all emulations.

--
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread ssrat

On 23 Apr 2001, at 19:47, Ewald Wasscher wrote:

 KP Kirchdörfer wrote:

  21-4updated busybox to version 0.51

  I'm running eigerstein with busybox 0.51 (and replaced most of the POSIXness
  links and other progs with busybox and tinylogin), but as long as we see the
  seg fault in 'busybox more' it's not ready for prime time - even if it's a
  beta version.

 How should I reproduce that error? I have no problems with segfaults so far.

This may be refering to a problem in Oxygen.  The problems were
solved with a recompile of glibc 2.0.7 from source.

  22-4add e3 (the pre 1.5 from oxygen) as the default editor

  Is this a version of e3, which don't make a backup of the original file?
  This feature of e3 is just wasting space, especially within lrcfg.

 I just checked and it doesn't seem to make a backup of an edited file.

This is a compile-time setting, to be set within the assembly source.
 The source comes with the option set to create backup files; I
always set the option not to create backups, and also to use vi as
the default editor (the option is normally set to use ws by default).

--
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Found my development platform.

2001-04-29 Thread ssrat

On 26 Apr 2001, at 19:34, Scott C. Best wrote:

   Forgive the off-topic moment of levity but...Oooo.
   
   http://www.jp.playstation.com/linux/image/main.jpg
 
   I can see it now...a Missle Command like interface to
 zap incoming packets of questionable origin...
   :^)

Someone (or two) somewhere adapted Doom to be used as a Linux 
sysadmin tool.  Processes were the enemy; important processes were 
hard to kill; and each enemy had a process number on it.

Nasty...

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] diskspace check

2001-04-29 Thread ssrat

On 27 Apr 2001, at 16:32, Jack Coates wrote:

 the annoying thing is that I don't see where it's getting called from --
 it's not in crontab, but I do know it's getting called because the ping
 check goes off about hourly.

Multicron is indeed in crontab, and is called as part of run-
parts - look at /etc/crontab.  The files in /etc/cron.daily 
/etc/cron.weekly etc. are called as appropriate; this then includes 
multicron-p (via links).

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Updating Eigerstein:progress

2001-04-29 Thread ssrat

On 30 Apr 2001, at 2:08, Ewald Wasscher wrote:

 [EMAIL PROTECTED] wrote:
 
  On 22 Apr 2001, at 14:34, Ewald Wasscher wrote:

  22-4TODO: update all binaries to the _latest_ versions available? Is
  this a good idea? That will probably use some additional diskspace

  Yes, definitely.  Fixes bugs and security problems.  I've heard lack 
  of updates classified as the number one security problem.
 
 Someone just had to give that as an answer.

Like me, eh?

 The only problem is that 
 some newer releases don't compile very easily with older 
 glibc/gcc/binutils.

I've found that the problems are actually minor in most cases: 
usually it is a missing pcap.h - most programs seem to think it's in 
the main include directory instead of pcap/pcap.h (sigh)...

A few programs seem to use updated glibc networking headers, but most 
things I've used don't have that problem.

 So do you think it will be sufficient to track e.g. 
 the latest debian security advisories or should all binaries in your 
 opinion really be the _latest_ versions?

I'd say they should be the *latest* versions - until you can't do it 
any longer with the older glibc.

I solved the problem by switching to glibc 2.1 - the bridge utils 
won't compile under glibc 2.0 any longer...

Ironic that Matthew (the fellow who did Materhorn) was the 
bridgeutils maintainer, and has now left it stagnate until someone 
else picked it up.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] diskspace check

2001-04-29 Thread ssrat

On 30 Apr 2001, at 0:41, Mike Noyes wrote:

 [EMAIL PROTECTED], 2001-04-29 16:16 -0500
 On 27 Apr 2001, at 17:25, Mike Noyes wrote:

   He recommends 18M for
   Oxygen though, and I don't know if this fixes the performance
   slowdown.
 
 Oxygen can run in 16M; I've done it many times.
 
 Oxygen does contain, in many default configurations, a separate
 partition for /var/log.
 
 David,
 Do we need to change this page then?
 http://leaf.sourceforge.net/content.php?menu=9page_id=6

I don't have web access at the house, but perhaps we should change 
that.  16M is tight; I think I even got it to work in 12M.  However, 
this is considered tiny by Oxygen standards; I computed the space 
by: RAMdisk-1 + RAMdisk-2 + RAMdisk-3 + 6M for Linux = space.  
However, all of the free RAMdisk space is used for working memory, so 
in practice, if the RAMdisk is never full you can operate in less.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] A little less mail, a little less Oxygen development....

2001-04-29 Thread ssrat

There is a new baby in the house so I'm not going to be doing a 
lot in the next week or so...

Andrew James was born 22 April 2001 at 7:25 am, and was 9 lbs. 4 oz. 
(ask your wives if that's big :-)

Current outstanding development concerns:

* Both Oxygen versions (glibc 2.0.7 and 2.1.3) have problems with 
insmod: the kernel in both is a kernel with the bridge patches 
installed and compressed with UPX.


-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] A little less mail, a little less Oxygen development....

2001-04-29 Thread ssrat

On 30 Apr 2001, at 5:29, Dale Long wrote:

 On Sun, 29 Apr 2001 [EMAIL PROTECTED] wrote:
   Ooph! I don't have to. Is there a infant blue ox in the back yard
   as well? 
  
  No blue oxes :-) but his older brother was 10 lbs. 2 oz. at birth :-)
 
 How long was the labour for both of them? Ouch.

Labor for Simon Andrew was about 12 hours; however, with Andrew James 
labor was in 4 hours.  Want to see a bunch of nurses and doctors 
materialize from out of nowhere?  Have a pregnant woman in labor say 
I've gotta PUSH!!  :-)

Andrew came in about three pushes :O came so fast that he wound up 
bruised a bit, but none the worse for the wear.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Secure Logging

2001-02-20 Thread ssrat

On 20 Feb 2001, at 17:03, Mike Noyes wrote:

 Secure Logging Over a Network
 http://interactive.linuxjournal.com/Magazines/LJ74/3913.html

You have to be authenticated to go here.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Secure Logging

2001-02-20 Thread ssrat

On 20 Feb 2001, at 12:53, Sergey Kozhedub wrote:

 The compromise is to use a separate storage device/partition for
 log files when needed. 

This is what Oxygen does by default - /var/log is a separate volume 
of a user-definable size (I think the default was 2M).

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] bootstrapping signed packages

2001-02-20 Thread ssrat

On 20 Feb 2001, at 22:38, Mark Seiden wrote:

 i'm about to switch to oxygen, which i've built on 2.2.18 (i
 hope...) for our beta test. 

Thanks for using Oxygen!

 when (not if) you run out of room on a single floppy, which
 contains "trustworthy" software, how to download additional .lrps
 in a trustworthy way? 

I'm not sure what you mean but read on.

Are you aware that you can download *.LRP files during the boot 
process from an HTTP (web) server, from an FTP server, from a TFTP 
server, or even from a GOPHER server?  This is Oxygen specific, 
however.

 so we're thinking of including on the floppy a public key
 corresponding with the private key used to sign each package (some
 sort of certificate), and checking each package as it's
 downloaded. 

This requires something to handle the keys - presumably, pgp - which 
doesn't yet exist in a package.

 this means using md5 or sha1 hashes with the signatures kept on
 the floppy won't work (as we'll have to update the signatures each
 time we update a package). 

 does the apkg format allow for signed content?

Really, it's not a "apkg" format but the *.lrp format - and it's just 
a *.tar.gz file.

Having said that, one of the things on my list of "ToDos" is to 
change apkg to generate *.md5 for every file in the package for 
checking purposes.  This would mean:

* When loading, the files would be checked using a list of files and 
md5sums in pkg.md5

* When saving, this pkg.md5 file would be created on the fly and 
saved.

The main problem to date has been that not all things put in a *.lrp 
are files - often they are directories, which cannot have a *.md5 sum 
taken.

As a matter of record, I might note that Oxygen now comes with md5sum 
loaded.  The challenge is this:

Given an input of:

/some/dir
/some/wild*
/some/file2
/some/dir2/file*
/some/dir2/dir*

Generate an output containing an md5sum of all files

I've taken a quick stab at it - once I get busybox updated, it should 
be nicer - the newest version contains support for find -type and 
find -mtime ...and even find -perm ...

Should be easier (easy?) to do using find -type f ...

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] md5 checksums in packages

2001-02-20 Thread ssrat

Well, that'll teach me to open my mouth :-)

I've gotten preliminary *.md5 file checksumming put into Oxygen's 
package handling system.  The files are included in the packages in 
the path of: /var/lib/lrpkg/pkg.md5 and are created during the 
package creation process automatically.

These package files are checked when "apkg -v pkg" is used, and 
also are checked during installation.  In both cases, the checksum 
for pkg.md5 is skipped; after all, what IS the checksum for a file 
being created while checksumming?  That's like trying to put a key 
signature on a key signature on a key signature...

The only package handled differently is root.lrp, since the root.list 
file doesn't really contain files to include but permits the system 
to catch files that are NOT included.  You really don't want to 
checksum the entire system - not yet anyway.  This also hints at the 
fact that the "exclude" files are NOT checked during md5sums; 
anything listed in pkg.list is checksummed, even if it is contained 
in a pkg.exclude ...  I'll have to think about that...

I guess the next thing is to create a mini-tripwire :-) using 
md5sums.  Hmmm

find / | md5sum  sys.md5sum

...hmmm

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] bootstrapping signed packages

2001-02-20 Thread ssrat

On 21 Feb 2001, at 1:31, [EMAIL PROTECTED] wrote:

 On Tue, Feb 20, 2001 at 05:05:52PM -0600, [EMAIL PROTECTED] scribbled:
  Having said that, one of the things on my list of "ToDos" is to 
  change apkg to generate *.md5 for every file in the package for 
  checking purposes.  This would mean:
 
 Every file? That's a hell of a lot of md5suming. Would not a
 single md5sum of all the files suffice?

It's not that bad.  Most packages don't have that many files.

 But, why would you want to md5sum a directory?

I didn't say I wanted to.

 Why not md5sum the concatenation of all files in the dir, or even
 of all the md5sums of all the files in the dir? 

That's the idea: generate md5sums for all files in the directory.  
However

 If your challenge is to step through the list, using each line as an
 argument for md5sum, I can help, with a method Charles devised when I
 asked for help doing something similar for mp3s... :)

Actually, I've gotten something working, but I think it's sort of 
kludgey.  Here is a more concise description of the possible input to 
md5sum:

directory
wildcard-directory
file
wildcard-file

...so - which one is it?  This has to be massaged for md5sum... also, 
a directory needs to be recursed into - I don't think my current 
checksumming does this.

Another problem is that the ENTIRE path needs to be generated; this 
is also problematic...

Let me think; this is what I need:

directory: find $(fullpath $1) ! -type d
wildcard-directory: find `echo $(fullpath $1)` ! -type d
file: echo $(fullpath $1)
wildcard-file: echo $(fullpath $1)

hmmm or something like that.

 Does your busybox find support -exec?

No.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Ladybug kernel and modules posted

2001-02-19 Thread ssrat

On 17 Feb 2001, at 18:33, Jack Coates wrote:

 The tree is 2.2.18 based and the kernel is compiling to 413002 bytes.

Not bad! ...

 Patches are:
 linux_brfw_2.2.17.diff

Do you have the bridgex or whatever it was compiled to an *.lrp?

 linux-2.2.17-ow1.diff

This is now at linux-2.2.18-ow4 

 patch-int-2.2.18.3

Is the crypto really available to release in the U.S.?  Or is it 
still a dangerous thing?  I asked on a mailing list a while back and 
got ZERO responses - so I removed my Oxygen kernel with crypto 
support.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Ladybug kernel and modules posted

2001-02-19 Thread ssrat

On 19 Feb 2001, at 15:58, Mike Sensney wrote:

 At 07:03 AM 02/19/2001 -0800, Jack Coates wrote:
 
 On Mon, 19 Feb 2001 [EMAIL PROTECTED] wrote:
   Is the crypto really available to release in the U.S.?  Or is it
   still a dangerous thing?  I asked on a mailing list a while back and
   got ZERO responses - so I removed my Oxygen kernel with crypto
   support.
 
 I think it's okay if you put a disclaimer on, which is something I forgot
 to do. Off to sourceforge...
 
 Check out Charles' page toward the bottom in the section titled
 Cryptographic Software. http://lrp.steinkuehler.net

Can we put this onto the SourceForge web site and put up some 
precompiled crypto kernels?  Also, what is required to post images 
using crypto kernels?

Anyone actually using (or have used) crypto kernels?

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] Crypto

2001-02-19 Thread ssrat

On 19 Feb 2001, at 17:02, Jack Coates wrote:

 that could be very handy for service images, but router/fw images
 are not likely to have a need (except for VPN which AFAIK doesn't
 use kerneli.org stuff). 

Possibly true.  However, crypto does enhance security.  My main 
purpose is to expand flexibility and so on; for the crypto kernel it 
would be useful for accessing crypto filesystems on a hard drive, 
especially if the full Linux distribution on the hard drive does NOT 
support crypto file systems (TOP SECURITY!).

It could also be used for hard drives, providing a fully encrypted 
(nonbootable) filesystem - provides physical security if the hard 
drive is removed.

It could also be used to render any swap space useless if someone 
decides to go wandering through the swap file/partition.  This was 
recently suggested in one of the security forums I'm a part of - you 
encrypt the swap space each time you use it; when the drive is 
removed the swap space is jibberish - no more scanning swap for 
passwords :-)  NOTE: this is apparently only possible under the patch 
for Linux 2.4.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Ladybug kernel and modules posted

2001-02-19 Thread ssrat

On 19 Feb 2001, at 18:39, Mike Noyes wrote:

 I stand corrected. You want that content linked from our home
 page. Correct?

Ray Olszewski said:

 Trying to connect to the URL you list above results in --
 
 Not Found
 
 The requested URL /pub/oxygen/ was not found on this server.
 
 Apache/1.3.14 Server at leaf.sourceforge.net Port 80
 
 Since this differs in a fairly basic way from Charles' URL, I suspect
 a miscommunication somewhere between you and Mike.

I get a valid page both from http://leaf.sourceforge.net/pub/oxygen/ 
and from the LEAF home page.  It all works for me... what's the 
difference between what I did and what you did?
 
 You and Charles would still have your individual directories.
 Charles will still be able to mirror his content to the /cstein
 directory. The new eigerstein and oxygen web directories will
 be placed in CVS so everyone can update the content. This should
 reduce/eliminate the need for you and Charles to do web
 maintenance. 

This looks pretty good to me!

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Device files in /tmp

2001-02-17 Thread ssrat

On 17 Feb 2001, at 6:49, Jack Coates wrote:

 I'd be inclined to stick to your existing system -- it seems sick
 and wrong to put device files in /tmp and I don't understand what
 they'd be doing there instead of /dev. There may well be a good
 reason (permissions? why not chmod the /dev entry?) but until one
 comes forward... 

I noticed too, that /tmp defaults to being built into / which 
includes /dev; thus unless /tmp is separated out it can have device 
files created in it.

Is THIS a bad thing?

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] CDROM booting

2001-02-16 Thread ssrat

I've been getting an Oxygen-based booting CDROM ready, but have hit a 
snag, and I don't know how to tackle it.

When the CD boots, it uses a disk image - I'm using a 2.88M floppy 
image.  syslinux comes up, and linux and root.lrp are loaded and run 
fine.

The problem is once /linuxrc takes over, it uses the boot= parameter 
to read the first set of packages.  This should, I would think, refer 
to the 2.88M floppy image in memory; however, how do I refer to this 
image?

/dev/fd0u1680 doesn't work (it's not a 1.68M anyway); /dev/fd0u2880 
doesn't work either - presumably, because both refer to the physical 
disk drive, not an in-memory image.

I know it can be done somehow but how?

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] CDROM booting

2001-02-16 Thread ssrat

On 16 Feb 2001, at 14:37, Charles Steinkuehler wrote:

 Note the 'automount' part of linuxrc will find the CD-ROM if
 there's no floppy in the drive, and use that as boot by default. 

Oh?  How does that go?  I don't remember seeing it in LRP 2.9.7, and 
anyway, if it was, I'm sure I removed it.

 The linuxrc script should probably be changed to automatically
 find a CD-ROM drive (ie try mounting /dev/hd? with -t iso9660 until
 something works) and make a symlink to /dev/cdrom for CD-ROM
 booting distributions (another thing to get to
 one-of-these-days). 

Good idea now how do you determine if iosfs.o is loaded (as 
module or in the kernel)?  The proconfig patch would be nice here but 
that hasn't been updated either for 2.2 OR 2.4 since June of last 
year.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] Loading from a PATH (not just a device)

2001-02-16 Thread ssrat

Example: Loading packages not from /dev/fd0, but from a directory on 
the floppy.  I was thinking of this syntax:

PKGPATH=/dev/fd0(pkgs):msdos

or

PKGPATH=/dev/hdc(pkgs/net):iso9660

and so on.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] Device files in /tmp

2001-02-16 Thread ssrat

I'm reconsidering the mount restriction I have for /tmp, which 
amounts to the fact that /tmp is mounted with the nodev option - 
preventing device files from being created.

The reason I'm reconsidering is because it would seem that pdnsd also 
creates device files there.  If I were to do this, I would create a 
separate /tmp (no more folding /tmp into the / volume) and mounting 
it without the nodev option.

Is this a reasonable way to go?  Are there other programs that will 
want to create device files in /tmp?

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Question about Syslinux v.1.52

2001-02-15 Thread ssrat

On 15 Feb 2001, at 3:45, Kenneth Hadley wrote:

 I finally got around to testing syslinux v1.52 today and it
 appears mister Anvin (syslinux's creator) has fixed the bugs that
 where causing mayhem for LRP Kernels Can anyone else confirm the
 fact that the new syslinux v.1.52 works for them? AND am I going
 nuts when its seams to load the kernel MUCH quicker now? 

I don't know if it loads quicker, but I've been using syslinux 1.52 
in Oxygen development for a couple of weeks or so - seems to work 
just fine.

 My test bed machine (that used to fail with any version of syslinux
 higher than v.1.48 but works with v.1.52) is a Cyrix-266MX 

This surprises me - I've never had any problem with 1.49 - nor heard 
of any.  Oxygen's been using 1.49 for some time.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Pardon me while I shoot myself. =)

2001-02-15 Thread ssrat

On 15 Feb 2001, at 9:09, George Metz wrote:

 What a week and a half.

I'll say!

 So if you're still with me to this point, the reason I was away
 was that I was down for a week and a half due to a misconfigured
 syslinux.cfg file and a NIC that doesn't like to work right unless
 it's running at 100BaseTX. 

Ouch!

Welcome back - we missed you!

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Intresting Question.............

2001-02-15 Thread ssrat

On 15 Feb 2001, at 4:07, Kenneth Hadley wrote:

 I'm not sure how many on this list are aware how I was able to get PPPoE to
 run correctly under Eigerstein and why I would like to come up with a
 cleaner solution

 Basically the main problem under PPPoE was getting the interface to come up
 before the firewall rules are in place [...]

 Method 1
 /init.d/pppoe file
 Have a pppoe script in /init.d/ that runs the adsl-start command and then
 a svi network ipfilter reload which if I understand correctly will reload
 the firewall rules...

Almost... but this invites an infinite loop.  Why not just create 
/etc/init.d/pppoe and order it in the startup process so that it runs 
before the firewall rules?

Look at the other files in /etc/init.d and see how they use 
RCDLINKS= and add one of these lines to /etc/init.d/pppoe so that 
pppoe is ordered after the network is loaded but before the firewall.

Also, make sure that the script understands parameters:

start: start PPPoE
stop: stop PPPoE
restart if needed: stop, pause if needed, start
nothing: usage

The other files in /etc/init.d should help you understand this better.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] Compiling Linux 2.2 for QoS support

2001-02-14 Thread ssrat

I'm compiling a raft of Linux kernels based on 2.2.18 for release; 
one of these was to include QoS support.  I started delving into the 
options, and experienced a white-out from the blizzard of options 
available :-)

Can someone enlighten me as to the best options to use for QoS and 
why and what it is all the options mean?

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] Read-only Linux IDE drivers?

2001-02-13 Thread ssrat

Has anyone ever done this?  It seems like this would be a good way to 
include IDE into the kernel in an embedded application, so as to 
provide the utmost security.  Hardware solutions appear to be non-
existant, and software solutions either allow write access, or 
disallow access altogether.

If one modified the IDE driver to be read-only, then either installed 
it into the kernel or as a module, would that not be better?  If it 
was a module, then you could remove read AND write access by removing 
the module and erasing it.

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] LDAP chown to dummy

2001-02-09 Thread ssrat

On 9 Feb 2001, at 14:39, Mike Noyes wrote:

 Thanks! I just verified that this works. I should have tried the archive 
 switch before.

Don't you need the -R switch to recurse?

 $ cd /home/groups/leaf/htdocs
 $ mv yourname ..
 $ cp -a ../yourname .
 $ rm -rf ../yourname
 $ cd /home/groups/ftp/pub/leaf/devel
 $ mv yourname ..
 $ cp -a ../yourname .
 $ rm -rf ../yourname

How about this?

#!/bin/ksh

HTTP_HOME=/home/groups/leaf
FTP_HOME=/home/groups/ftp/pub/leaf/devel

tag () {
   cd $1
   [ ! -f $2 ]  exit 1
   mv $2 ..
   cp -a ../$2 .  rm -rf ../$2
   }

tag $HTTP_HOME $1 || echo http: err!
tag $FTP_HOME $1 || echo ftp: err!

makes a nice program to put in somewhere...

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] Where IS everybody?

2001-02-06 Thread ssrat

On 6 Feb 2001, at 6:00, Steven Peck wrote:

 I know Jeff is in Davis, [California..]

 Mike's in the [San Francisco, California...] area.
 
 Charles is out in the midwest [...]

Western Kansas, I thought.  Kansas City?

 and Rick out on the East coast?

Where?

 Oh, I'm in Sacramento, CA

Ray's in Palo Alto.  Jack said San Jose.  I'm in Madison, Wisconsin 
(an Alternative to Reality :-)

Lest anyone forget Pedro's domain says Portugal, doesn't it?  
Where are you, Pedro?

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Linux-friendly Embedded SBCs

2001-01-18 Thread ssrat

On 18 Jan 2001, at 19:05, Scott C. Best wrote:

 Heya. It'd be worthwhile, I think, for one of our more board-minded
 LEAF'rs to suggest just such an SBC which we could use as a
 'development target'. Not that we won't be putting it into desktop
 x86's as well, of course, but I was told by a VP at BigIronCompany
 yesterday that "no one can build a $100 gateway". Hmmm... 

How hard would it be to use a SBC in a PC (connecting through 
the ISA bus) to design a SBC LEAF then extract it, box it, and run 
it?  Would be something else!

I was thinking again about chips - the Linux creator (Linux) was 
involved in the development of the Transmeta chip, and also the 
FORTH creator (Charles Moore) developed not one but several 
chips.  What would it be like to compile Linux for the Novix chip or 
another FORTH chip?  Hmmm.

Everybody knows that FORTH is better than C anyway ;)
duck and run!

 Love those sort of challenges. :)

Da!

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel