On January 15, 2002 08:37 pm, Rob Landley wrote:
On Tuesday 15 January 2002 03:25 pm, Russell King wrote:
On Tue, Jan 15, 2002 at 02:53:24PM -0500, Eric S. Raymond wrote:
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root
Daniel Phillips wrote:
I detect a slight lack of symmetry here, shouldn't it be make autoconfig?
Pardon me if this has been beaten to^W^W discussed above.
Yes. It should be make autoconfig, for symmterty reasons :-)
I called the files and the project autoconfigure, because
'autoconfig' is
On January 21, 2002 06:05 pm, Giacomo Catenazzi wrote:
Daniel Phillips wrote:
I detect a slight lack of symmetry here, shouldn't it be make
autoconfig? Pardon me if this has been beaten to^W^W discussed above.
Yes. It should be make autoconfig, for symmterty reasons :-)
I called
Ross Vandegrift [EMAIL PROTECTED]:
1) I noticed you've been pining the lists for EISA information. I don't
know a whole lot about EISA systems or anything, but I do have a 486 EISA
board and an EISA network card I'd be willing to send you if you wanted a
system to play around with. I don't
David Woodhouse [EMAIL PROTECTED]:
Hmmm, yes. I think I see at least two errors in that small selection, if I
understand it correctly.
Please help me correct them.
But as these are obviously behavioural changes, and
you've said you won't make behavioural changes in the first
David Woodhouse [EMAIL PROTECTED]:
Utter crap. CML2 makes them possible, and is a step in the right direction.
I'm not suggesting that you never make these changes - just that you do them
separately from the change in mechanism.
Sorry, it's *way* too late for that. In fact, it was already
Eric S. Raymond wrote:
Kai Henningsen [EMAIL PROTECTED]:
I think right now, the only halfway reasonable thing is to do what
ttyname() does: get the devide number off stat(/), and search it in /dev.
(Besides, you can figure out part of the answer - about as much as the
autoprober does
On Wed, Jan 16, 2002 at 11:38:40AM -0500, Ross Vandegrift wrote:
[snip]
I'm planning on trying this on a Debian testing box I have at work at some
point.
Just verified the same process works on Debian testing, as well as with
cml2-2.1.3.
Ross Vandegrift
[EMAIL PROTECTED]
Horst von Brand [EMAIL PROTECTED]:
Release 2.1.3: Tue Jan 15 14:41:45 EST 2002
* Resync with 2.4.18-pre3 and 2.5.2.
* It is now possible to declare explicit saveability predicates.
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the
Horst von Brand [EMAIL PROTECTED]:
Whatever happened to Do exactly as CML1 does; leave fixes and extensions
for later? If you put the kitchen sink into it, it _won't_ go into the
standard kernel.
If you stick to the CML1-equivalent facilities, you'll get almost
CML1-equivalent behavior. It's
Eric S. Raymond [EMAIL PROTECTED] said:
Horst von Brand [EMAIL PROTECTED]:
Release 2.1.3: Tue Jan 15 14:41:45 EST 2002
* Resync with 2.4.18-pre3 and 2.5.2.
* It is now possible to declare explicit saveability predicates.
* The `vitality' flag is gone from the language.
horst Whatever happened to Do exactly as CML1 does; leave fixes and extensions
horst for later? If you put the kitchen sink into it, it _won't_ go into the
horst standard kernel.
My opinions:
It's important that people who type make config or make oldconfig
or make menuconfig or make xconfig
Eric, the way you worded the change report it sounded to many of us as if
you were making the autoprober mandatory for detecting the root
filesystem.
That's why it spawned so many messages like this (including one from me
yesterday)
you should have added something in the changelog entry that
[EMAIL PROTECTED] said:
If you stick to the CML1-equivalent facilities, you'll get almost
CML1-equivalent behavior. It's almost partly because the hardware
symbols have more platform- and bus-type guards than they used to --
but mostly because I have not emulated the numerous CML1 bugs.
David Woodhouse [EMAIL PROTECTED]:
I'm concerned by the 'platform- and bus-type guards' to which you refer.
Could you give some examples where the behaviour has changed? Lots of
embedded non-x86, non-ISA boxen have ISA network chips glued in somehow,
for example. I hope you haven't
On Wednesday 16 January 2002 11:38 am, Ross Vandegrift wrote:
At this point the rules are compiled and a dialog box indicates that
Suppression has been turned off (press any key to continue). I hit any key
and am presented with the first menu.
Ah, I understand the bug.
That dialog
On Tue, Jan 15, 2002 at 02:53:24PM -0500, Eric S. Raymond wrote:
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root filesystem and forces
its symbol to Y.
This seems like a backwards step. What's the reasoning for
On Tue, 15 Jan 2002, Eric S. Raymond wrote:
The latest version is always available at http://www.tuxedo.org/~esr/cml2/.
Release 2.1.3: Tue Jan 15 14:41:45 EST 2002
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root
On Tue, 2002-01-15 at 14:53, Eric S. Raymond wrote:
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root filesystem and forces
its symbol to Y.
And when I compile a kernel for my Dreamcast? Or when I want to change
Nicolas Pitre [EMAIL PROTECTED]:
Release 2.1.3: Tue Jan 15 14:41:45 EST 2002
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root filesystem and forces
its symbol to Y.
What happens if you compile a kernel for another
On Tue, 15 Jan 2002, Eric S. Raymond wrote:
Nicolas Pitre [EMAIL PROTECTED]:
Release 2.1.3: Tue Jan 15 14:41:45 EST 2002
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root filesystem and forces
its symbol to Y.
On Tue, 15 Jan 2002, Eric S. Raymond wrote:
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root filesystem and forces
its symbol to Y.
can you override this autodetect? (it may not be valid if you are building
on one
[esr]
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the type of your root filesystem and forces
its symbol to Y.
[Russell King]
This seems like a backwards step. What's the reasoning for breaking
the ability to configure the kernel
On Tuesday 15 January 2002 03:41 pm, Nicolas Pitre wrote:
On Tue, 15 Jan 2002, Eric S. Raymond wrote:
Nicolas Pitre [EMAIL PROTECTED]:
Release 2.1.3: Tue Jan 15 14:41:45 EST 2002
* The `vitality' flag is gone from the language. Instead, the
autoprober detects the
On Tuesday 15 January 2002 03:24 pm, Eric S. Raymond wrote:
To invoke the autoconfigurator, you do one of two things:
`make autoconfigure'
This runs the autoconfigurator in standalone mode. This gives you
an entire configuration, ready to build with.
`make autoprobe
Rob Landley [EMAIL PROTECTED]:
Eric and I disagree on the behavior of make autoprobe. He likes the
concept of freezing symbols, which says if the autoprober detected a
configuration setting, the question shouldn't show up and give you the
opportunity to disagree. (Not confusing Aunt
[esr]
The version I just released does exactly that. Well, not exactly; it
actually looks at fstab -- /proc/mounts gives you '/dev/root' rather
than a physical device name in the root entry.
/etc/fstab is hardly guaranteed to be accurate either. The kernel
mounts the root device based on
27 matches
Mail list logo
