On Mon, Jun 26, 2000 at 09:25:37PM +0200, Guido van Rooij wrote:
>
> How about adding a hint to the hint driver itself. E.g.
>
> SYNOPSIS
> device isa
> device ata
> hint "hintsfile"# see hint(4)
I don't think this is enough. If I botch my hints file enough (and
lets
On Sat, Jun 24, 2000 at 06:32:47PM -0500, Mike Pritchard wrote:
>
> SYNOPSIS
> device isa
> device ata0 at isa? port IO_WD1 irq 14
> device ata1 at isa? port IO_WD2 irq 15
>
>
> Should this become:
>
> SYNOPSIS
> device isa
> device ata
> hint.ata.0.at="isa"
> hint.
Michael Wlliams wrote:
>
> I'm catching up on email, sorry if this was answered... are you talking
> OBP/Forth
> on Suns? Try
> ok sifting foo
> to get a list of words with foo in them (kinda like grep foo). Try
> ok see foo
> to see the details of the word (if you get forth this will help.)
>
>
On Sun, 25 Jun 2000 17:27:28 +0900, "Daniel C. Sobral" wrote:
> This definitely needs some work. I'm not sure the hints syntax will
> change much, if at all. OTOH, I don't know how to approach this. In
> other words, suggestions (and specially patches) are welcome.
Actually, I think that this
I'm catching up on email, sorry if this was answered... are you talking
OBP/Forth
on Suns? Try
ok sifting foo
to get a list of words with foo in them (kinda like grep foo). Try
ok see foo
to see the details of the word (if you get forth this will help.)
If you're not doing forth/obp... my apologi
Mike Pritchard wrote:
>
> I just noticed that this change has now made a lot of the section 4
> man pages out of date.
>
> What is the best way to represent these changes in the man pages?
> A good example is ata(4). Currently it reads like this:
>
> SYNOPSIS
> device isa
> device ata0
On Tue, Jun 13, 2000 at 04:18:29PM -0700, Peter Wemm wrote:
> change *ALL* "device foo0 at isa? port blah etc" to "device foo" - see
> GENERIC for examples. All the 'at ? port ?' stuff is handled by
> the new /boot/device.hints
> See GENERIC - if you use a static limited device (eg: fe, aha,
Andrzej Bialecki wrote:
>
> That's fine. However, this practically makes using /boot/loader
> mandatory. I still wonder if having some in-kernel interpreter wouldn't
> give us more choice, with exactly the same functionality. Of course, it
> would have to be run before any probing starts...
If y
In message <[EMAIL PROTECTED]> Andrzej Bialecki
writes:
: That's fine. However, this practically makes using /boot/loader
: mandatory. I still wonder if having some in-kernel interpreter wouldn't
: give us more choice, with exactly the same functionality. Of course, it
: would have to be run befo
On Wed, 21 Jun 2000, Daniel C. Sobral wrote:
> Andrzej Bialecki wrote:
> >
> > This thread is long, so maybe I missed something.. Can we have the *.hints
> > file loadable as a module of some special type (like kernel.conf), and
> > searched for during configuration like userconfig did?
>
> Fun
Andrzej Bialecki wrote:
>
> This thread is long, so maybe I missed something.. Can we have the *.hints
> file loadable as a module of some special type (like kernel.conf), and
> searched for during configuration like userconfig did?
Funny you got no reply.
This is not necessary. If you copy sai
On Fri, 16 Jun 2000, Peter Wemm wrote:
> Chia-liang Kao wrote:
> > Hi,
> >
> > Is there anyway to put the device.hint stuff into kernel nevertheless?
> > My diskless box fetches the kernel would know nothing about things reside
> > in device.hint.
>
> That is what the hints directive is for.
>
On 13-Jun-00 Peter Wemm wrote:
> *** CAUTION IS REQUIRED ***!
>
> FYI, an intrusive commit has been done that requires careful attention. If
> you ignore this or mess it up, it can burn your house down, shoot your dog,
> close your bank accounts, report you to the IRS, or maybe even something
>
Chia-liang Kao wrote:
> Hi,
>
> Is there anyway to put the device.hint stuff into kernel nevertheless?
> My diskless box fetches the kernel would know nothing about things reside
> in device.hint.
That is what the hints directive is for.
you could create a file "diskless.hints" and add the line
Hi,
Is there anyway to put the device.hint stuff into kernel nevertheless?
My diskless box fetches the kernel would know nothing about things reside
in device.hint.
Cheers,
CLK
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > Uh, 'help' doesn't give you a list of commands I believe.
>
> Damn, it doesn't either. 'help' is the same as 'help help'.
>
> Suggestions for a better replacement for ? 'commands'?
Just change unadorned help to say 'help help' to get a list.
To Unsubscribe: send mail to [EMAIL PROTECT
> Uh, 'help' doesn't give you a list of commands I believe.
According to loader(8) it means:
? Same as ``help index''.
I did not try yet if that one works correctly.
Regards,
Marc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body o
> Uh, 'help' doesn't give you a list of commands I believe.
Damn, it doesn't either. 'help' is the same as 'help help'.
Suggestions for a better replacement for ? 'commands'?
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself,
Uh, 'help' doesn't give you a list of commands I believe.
On Thu, 15 Jun 2000, Mike Smith wrote:
> > On 15 Jun, Marc van Woerkom wrote:
> >
> > > 3. in the boot loader I miss the list of commands,
> > >? (i hope this was the command) just yields a number
> >
> > I also see this.
>
> Th
> On 15 Jun, Marc van Woerkom wrote:
>
> > 3. in the boot loader I miss the list of commands,
> >? (i hope this was the command) just yields a number
>
> I also see this.
The use of ? was a bad idea, since it's special to Forth. Use 'help'
instead.
--
\\ Give a man a fish, and you feed
> 4. I thought I put just the sym driver in the kernel, why do I
>see ncr? (see next item)
Now it is back to using sym.
Possibly some configuration mistake by me.
Regards,
Marc
PS Here is the diff..
-FreeBSD 5.0-CURRENT #15: Thu Jun 15 00:25:51 CEST 2000
+FreeBSD 5.0-CURRENT #16:
On 15 Jun, Maxim Sobolev wrote:
>> c) is much more interesting: With the new kernel my syscons scrolling
>> stopped working. However, this could also be jake's fault, I'll ask
>> him.
>
> Still works like a charm here. Maybe problem is elsewhere?
I have the same problem as Alexander, nut it onl
On 15 Jun, Marc van Woerkom wrote:
> 3. in the boot loader I miss the list of commands,
>? (i hope this was the command) just yields a number
I also see this.
> 5. Here are the dmesg differences between the February and the new
>kernel. Could you explain the unassigned resources messag
Another way to reboot the system is
vidcontrol 80x50
Regards,
Marc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Alexander Langer wrote:
> c) is much more interesting: With the new kernel my syscons scrolling
> stopped working. However, this could also be jake's fault, I'll ask
> him.
Still works like a charm here. Maybe problem is elsewhere?
-Maxim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
Hi!
I was able to build and boot, starting from a February -CURRENT but there
are some oddities.
1. I had to disable linux emulation, as it caused system hangup
Yes I followed the hint on rebranding from src/UPDATING
2. My system seems to have a problem with fsck
I had to use the old Feb
Hello Peter!
I just have things running. I see that the kernel boots _much_ faster
now. I don't know, if you wanted that or if this is a nice
side-effect.
However, a few comments, which might be of interest. Some of those are
probably planned by you already.
a) the device.hints file: It will pr
Peter Wemm wrote:
>
> The only change in /boot is /boot/defaults/loader.conf:
>
> diff -r1.26 -r1.27
> 24c24
> < loader_conf_files="/boot/loader.conf /boot/loader.conf.local"
> ---
> > loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local"
>
> ie: /boot/device.hints is
At 01:20 AM 6/14/2000 -0700, Peter Wemm wrote:
>Peter Wemm wrote:
>
>> # update /boot/loader.conf
>> cd src/sys/boot; make obj depend all install
>
>Of course, it would be just my luck that there is a loader bug right now,
>and this command will throw you into the fire. ;-( If your loader
>compla
Peter Wemm wrote:
> # update /boot/loader.conf
> cd src/sys/boot; make obj depend all install
Of course, it would be just my luck that there is a loader bug right now,
and this command will throw you into the fire. ;-( If your loader
complains about not being version 0.3+ or later and aborting,
Matthew Jacob wrote:
>
> > # I cannot stress this enough: **SAVE A WORKING /kernel**
> > cp /kernel /kernel.works
>
> Save a working /modules and /boot as well.
Which is always good advice, but I can clarify the effect on these...
The only change in /boot is /boot/defaults/loader.conf:
diff
> # I cannot stress this enough: **SAVE A WORKING /kernel**
> cp /kernel /kernel.works
Save a working /modules and /boot as well.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
*** CAUTION IS REQUIRED ***!
FYI, an intrusive commit has been done that requires careful attention. If
you ignore this or mess it up, it can burn your house down, shoot your dog,
close your bank accounts, report you to the IRS, or maybe even something
bad.
An old version 51 config(8) will (
33 matches
Mail list logo
