On Fri, 30 Mar 2001, Scott C. Best wrote:
Am having trouble with normal grep options in
eigerstein 2.2.16. Anyone else seen this? Getting error
messages like "sed: can't read foo..." for simple
things like:
grep -v foo /etc/passwd
Huh? sed with greap? Any thoughts on
Pi:
Woof!
That's terribly annoying.
So...forgive my non-sed'ness, but what would be the
equiv of, say: "grep -v -i FOO /etc/passwd" ?
Thanks again
-Scott, thinking about grep.lrp...
On Fri, 30 Mar 2001, Pim van Riezen wrote:
On Fri, 30 Mar 2001, Scott C.
On Fri, 30 Mar 2001, Scott C. Best wrote:
Pi:
Woof!
That's terribly annoying.
I agree, it just always seemed to annoy me personally at times where
taking a better look at it was not an option.
So...forgive my non-sed'ness, but what would be the
equiv of, say: "grep -v -i
George Metz wrote:
Perfect example is a feature I found while compiling a 2.4.2 kernel for my
SuSE server last night. It's an option that I don't ever recall seeing in
any of the kernels, that stores the kernel's configuration in the kernel
image itself - at a cost of 1-4k of size - so that
Mike Noyes, 2001-03-28 10:20 -0800
Everyone,
I'd like us to start using the SF Tracker to handle package submissions.
Comments?
Note: I don't know if it's necessary to tarball/zip them before uploading.
Everyone,
PatchManager: I checked last night, and the Patch Manager handles binary
files
Charles Steinkuehler wrote:
The chroot thing is a one-time deal to build a root image on the HDD. The
part you're missing is I'm running LRP WITHOUT a ramdisk, more like
conventional linux...hopefully I won't be burned at the stake.
A Now I understand. Jeff was so gentle about it
"Scott C. Best" wrote:
[...] what would be the
equiv of, say: "grep -v -i FOO /etc/passwd" ?
sed '/[Ff][Oo][Oo]/d' /etc/passwd
Pi said:
grep -v didn't even work in the old LRP2.9.8 release. Always had to hack
around it by using sed -e "s/foo//" instead of grep -v "foo".
Busybox 0.50
Pim van Riezen wrote:
The "-i" I'm not sure about, I tend to not use regexpes all that oftenly
either.
-i is case-insensitivity.
Being a regular vi nut, I use regexps all the time. It's gotten so
bad I'm constantly having to check which regexps are allowed by which
utility (vi, sed, grep
Mike Noyes wrote:
CVS: I would like us to use CVS for packages (.lrp). I added a binary
wrapper this morning for .lrp. I'd like some feedback on possible directory
structures. I think it should look something like this:
packages -+
+ /boot -+
|+ /eigerstein
David Douthitt, 2001-03-30 07:26 -0600
The CDROM I have has (in part) the following breakdown:
src --+-- base ...like busybox, ctar, tftp, ...
|
+-- pkgs --+-- net
|
+-- sys
|
+-- ...et al...
David,
Are all
The key to making this happen is getting a linuxrc that's smart (or
flexible) enough to deal with whatever is required. The other missing
piece
is a way to communicate with the CD-ROM boot scripts.
That would be syslinux.cfg; what is needed (sounds like) is a way to
shift the entire
David, does Oxygen have any reason it would be different from other
LRPs, or should somebody give this guy the standard answer?
I'm not sure what the standard answer would be.
However, the use of the ram disks is hardcoded in linuxrc, and
/etc/fstab; the kernel is probably the biggest
On Fri, Mar 30, 2001 at 06:49:48AM -0600, David Douthitt scribbled:
This wouldn't be the "proconfig" patch would it? With this patch, you
can type "cat /proc/config" and it will give you a list of features
set, in the form of a Config file for the running kernel.
Fairly neat, if not much
Charles Steinkuehler wrote:
Um... not quite. You are talking about bootable CDROMs with a
configuration disk; I am talking about booting from floppy disk and
using the CDROM as a data disk. Your ideas are much more
revolutionary than mine.
Actually, I want both to work. My CD-ROM
David Douthitt, 2001-03-30 08:32 -0600
Mike Noyes wrote:
David,
Are all the files in this src directory text, or are there binary
files too?
The src directory is basically a snapshot of my build directories; so
all have *.o files, as well as *diff files and so on. In some cases
there are
David Douthitt, 2001-03-30 09:09 -0600
If you like. I'm not sure what you mean by "binary wrappers for .o
and tar.gz" ...?
Everyone,
This should explain how CVS handles binary files. It'll also explain why I
need to add binary file wrappers.
9. Handling binary files
Mike Noyes wrote:
David Douthitt, 2001-03-30 09:09 -0600
Mike Noyes wrote:
David,
It looks like you have an oxygen tree that's almost ready for import
into CVS. I can add binary wrappers for .o and tar.gz. This should
allow you to import your src tree as oxygen. Did I miss
David Douthitt, 2001-03-30 09:23 -0600
Mike Noyes wrote:
David,
I'm talking about an import of the src tree from the CD into CVS. Are
you talking about importing the compiled output, or am I confused
again?
Let me see if I understand this right:
* What I have now is "working
I have to go with David here and I think it deserves a mention.
You are coordinating work on an Open Source project. You have been driving
force and crucial to installing and maintaining the website (you then found
a better solution and made it happen :getting help counts), coordinating and
Here here!!
I second all of that. Mike, you are a major driving force that
most projects don't have, and that we're _very_ lucky to have.
I'm good for another reference letter.
On Fri, Mar 30, 2001 at 11:26:20AM -0800, Steven Peck scribbled:
I have to go with David here and I think it
George Metz wrote:
On Fri, 30 Mar 2001, David Douthitt wrote:
This wouldn't be the "proconfig" patch would it? With this patch, you
can type "cat /proc/config" and it will give you a list of features
set, in the form of a Config file for the running kernel.
Fairly neat, if not
This weekend, the forecast calls for a 30 percent chance of
lrp.c0wz.com and/or lrp.steinkuehler.net downtime, as both
myself and Charles may be working on new servers for our
respective sites.
Additionally, mine's gone a little flaky on me, so even if
I don't replace the server, it could see
On Fri, Mar 30, 2001 at 09:03:15PM -0500, George Metz scribbled:
It would appear from discussion here and a search that proconfig was
folded into 2.4; in any case, the most recent versions at the web site
are:
I couldn't find it in menuconfig, nor by a recursive, case
insensitive
On Sat, 31 Mar 2001 [EMAIL PROTECTED] wrote:
Well, if you look at the top quote, the suggestion was that it
has been folded into the main kernel tree; and I don't use
slack-provided kernels, I download plain kernels from
kernel.org...not that I think slack patches their kernels
anyhow. ;)
David Douthitt, 2001-03-30 11:11 -0600
Mike Noyes wrote:
David Douthitt, 2001-03-30 09:50 -0600
...what you have after this is done is a source code directory that
could, in theory, be compiled straight away to create a usable LRP
binary.
That sounds great!
Ok, I just added
25 matches
Mail list logo
