In message [EMAIL PROTECTED], Matthew
Jacob writes:
I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3
'da' disks that were found.
The only real problem is that it won't see the partitions made for
'dangerously dedicated' 'da' disks. What's the plan for addressing
In message [EMAIL PROTECTED], Matthew
Jacob writes:
On Mon, 28 Aug 2000, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Matthew
Jacob writes:
I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3
'da' disks that were found.
The only real problem is that
What names do you usually access your disks by ? Just da0a etc ?
da0{a,b,c,d} and so on..
You should be able to find those as well with the clone stuff...
Nope. Weren't there.
I booted up once. I had 3 disks- none with a FreeBSD label. The
contents of /dev for da disks was
Brooks Davis writes:
On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote:
Doing 'make install' without /boot/device.hints is failed,
saying "You must set up a /boot/device.hints file first."
Is this right?
You should read cvs-all. There was a commit by Peter which forces
In message [EMAIL PROTECTED], Matthew
Jacob writes:
What names do you usually access your disks by ? Just da0a etc ?
da0{a,b,c,d} and so on..
You should be able to find those as well with the clone stuff...
Nope. Weren't there.
I booted up once. I had 3 disks- none with a FreeBSD
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from shooting yourself in the foot?
cvs-all is not appropriate. I am
James Johnson writes:
The method of building and installing a kernel to me seems a bit off.. Both
the buildworld and installworld targets default to GENERIC, yet GENERIC is a
file checked into the -CURRENT CVS repository.. Any changes to this file
will get blown away if whenever you update
On Sun, 27 Aug 2000 21:35:26 +0200, Poul-Henning Kamp wrote:
Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init
will mount devfs on /dev automatically.
Out of curiosity, what's the motivation behind this decision? Why don't
you allow defvs to be mounted on an arbitrary
In message [EMAIL PROTECTED], Sheldon Hearn writes:
On Sun, 27 Aug 2000 21:35:26 +0200, Poul-Henning Kamp wrote:
Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init
will mount devfs on /dev automatically.
Out of curiosity, what's the motivation behind this decision? Why
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from shooting yourself in the foot?
Actually,
I did just notice something.. why would I have sc0/sc1 and
vga0/vga1? Or is that just because of the 'options SC_PIXEL_MODE'
that I have?
Jason DiCioccio - IBM Global Services - [EMAIL PROTECTED] - www.ibm.com
Systems Admin - Open Domain Server - [EMAIL PROTECTED] -
Donn Miller writes:
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from shooting yourself in the
Although binary distribution would be easier, I suspect that many of us
would prefer to build everything locally. That is one of the unique
features of FreeBSD, even if it is time consuming.
On Sat, Aug 27, 2000 , Gary Kline wrote:
BTW, I have some ideas how this entire issue of
-current from Aug, 22, cd9660 image file mounted via vn reports this:
Aug 28 13:45:51 counter /kernel: unexpected vn driver lock: 0xccf008c0: type VREG,
usecount 2, writecount 1, refcount 452, flags (VOBJBUF)
Aug 28 13:45:51 counter /kernel: tag VT_UFS, ino 357635, on dev #da/6 (13, 6) lock
I should haven mentioned that this is a SMP machine (i440BX P-III 550
dual) and is running vmware.
-current from Aug, 22, cd9660 image file mounted via vn reports this:
Aug 28 13:45:51 counter /kernel: unexpected vn driver lock: 0xccf008c0: type VREG,
usecount 2, writecount 1, refcount 452,
-On [2827 23:05], Soren Schmidt ([EMAIL PROTECTED]) wrote:
Well, this wouldn't have happend without Jeroen (asmodai) having
good contacts at HighPoint, so I thank him for making this
possible.
No problem.
It's all team work anyways, I couldn't write the driver. ;)
Hopefully Highpoint will
Mike Meyer wrote:
Donn Miller writes:
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from
Maxim Sobolev writes:
Mike Meyer wrote:
Donn Miller writes:
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having
Up until this weekend, I was able to use the staroffice52 port with
little problem (I had installed it earlier without benefit of the port
and it worked fine.) I did a 5.0-current kernel rebuild on
Thursday with
sources current on that day and things were fine. When I rebuilt my
kernel
Mike Meyer wrote:
Will the system fail to boot if there isn't an empty device.hints
file?
No, it will boot, but some devices (like keyboard, console etc) would not work.
That's clearly not true - I just removed an empty /boot/device.hints
and rebooted, and all those things work fine.
Maxim Sobolev writes:
Mike Meyer wrote:
Will the system fail to boot if there isn't an empty device.hints
file?
No, it will boot, but some devices (like keyboard, console etc) would not work.
That's clearly not true - I just removed an empty /boot/device.hints
and rebooted, and
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Brad Knowles wrote:
At 7:36 PM + 2000/8/28, Alex Zepeda wrote:
Perhaps in a rush to get started, I've compiled and
been using a SMP kernel even before the second processor arrives. This
has worked fine, however I've gotten some rather weird hangs and
Hi Poul-Henning,
I've been having trouble with ps(1) printing invalid controlling
terminal names for processes connected to psuedo-terminals.
This only seems to be a problem for DEVFS-enabled systems.
The output that makes it look like things are broken is this:
$ ps -t p7
PID TT STAT
On Mon, 28 Aug 2000, Matthew Jacob wrote:
On Mon, 28 Aug 2000, Poul-Henning Kamp wrote:
Have you tried accessing them directly, for instance:
ls -l /dev/da0s2e
or whatever their names are ?
Sure. They're not there. A reboot still just has da0[c], da1[c], and
da2[c] show
Hi Poul-Henning,
I've been having trouble with ps(1) printing invalid controlling
terminal names for processes connected to psuedo-terminals.
This only seems to be a problem for DEVFS-enabled systems.
Yes, devname(3) need to learn a few things. It's actually always
been a problem if you
In message [EMAIL PROTECTED], Bruce Ev
ans writes:
Sure. They're not there. A reboot still just has da0[c], da1[c], and
da2[c] show up.
That's more than show up on i386's :-). After booting with -s, only
the whole disk devices and the root device show up. Devices for slices
and partitions
That's more than show up on i386's :-). After booting with -s, only
the whole disk devices and the root device show up. Devices for slices
and partitions slices only show up when they are opened or stat'ed.
This bug is normally mostly hidden by opening most partitions to mount
them.
Hmm.
Ahh...,
I tried to summarize my opinion.
If you find any misunderstandings of me, please correct them.
*** What's happen if there's no /boot/device.hints?
case A kernel has no built-in hints
... some devices would not work, system would stall!
You can tell whole hints to the kernel
"Yevmenkin, Maksim N, CSCIO" wrote:
[snip]
same here :( i got original Sun CD with StartOffice 5.1a and tried to
install it. it failed. i used
# make WITH_CDROM=yes USE_CDROM=yes install
and everything was fine, but then i got exactly the same error.
XFree86-3.3.6 and
On Mon, Aug 28, 2000 at 03:19:15AM -0500, Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from
On Mon, Aug 28, 2000 at 08:24:50AM -0500, Mike Meyer wrote:
Well, yeah, I'd expect that. I'm still trying to figure out what
*good* failing to compile unless there's an empty /boot/device.hints
The kernel does not fail to *BUILD*. ``make install'' is what fails. I
agree that the requirement
John Baldwin writes:
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Sat Aug 26 11:14:35 GMT 2000)
/kernel text=0x2432ca zf_read: fill error
elf_loadexec: archsw.readin failed
Your floppy is bad. Try a different one.
Not necessarily. This also happens if you try to
In message [EMAIL PROTECTED] Tony
Fleisher writes:
: Just a suggestion, but isn't this the type of thing that
: should be added to UPDATING?
Quoting from the UPDATING file:
...
2825:
/boot/device.hints is now required for installkernel to
succeed.
...
2612:
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: I do read cvs-all, and I missed it. Not did I find device.hints in the
: relevant Makefiles. Can you provide a pointer to details on how
: /boot/device.hints is used in the build process, or how having an
: empty one keeps you from
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: I do read cvs-all, and I missed it. Not did I find device.hints in the
: relevant Makefiles. Can you provide a pointer to details on how
: /boot/device.hints is used in the build process, or how having an
: empty one keeps you from
In message [EMAIL PROTECTED] Mike Meyer writes:
: Will the system fail to boot if there isn't an empty device.hints
: file?
If the kernel doesn't have a hints file compiled into it, then you
will have problems. However, you may not have a video console. I've
been able to boot my laptop with a
On Mon, Aug 28, 2000 at 10:23:34AM -0700, Archie Cobbs wrote:
John Baldwin writes:
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Sat Aug 26 11:14:35 GMT 2000)
/kernel text=0x2432ca zf_read: fill error
elf_loadexec: archsw.readin failed
Your floppy is bad.
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: In my opinion, people making major changes that require something in
: UPDATING, should coordinate with you *before* the commit. Only 5 or
: 6 brain cells are needed for this- I sure wish some of my fellow
: committers weren't such skinflints
John Baldwin writes:
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Sat Aug 26 11:14:35 GMT 2000)
/kernel text=0x2432ca zf_read: fill error
elf_loadexec: archsw.readin failed
Your floppy is bad. Try a different one.
Not necessarily. This also happens if
Mike Smith writes:
/kernel text=0x2432ca zf_read: fill error
elf_loadexec: archsw.readin failed
Your floppy is bad. Try a different one.
Not necessarily. This also happens if you try to boot boot.flp
instead of kern.flp.
Only if you've been silly enough to only put
On Sun, 27 Aug 2000, David Malone wrote:
[...]
(This is why the flag I was talking about in the other mail
would be useful for spotting other cases where the storage
may be writable, even if it's not a cluster).
Thoughts:
1) The mbuf should be marked read-only explicitly with
[ note: trimming -current from the CC: list ]
Bosko Milekic writes:
1)The mbuf should be marked read-only explicitly with a single
additional M_FLAG.
#define M_RDONLY0x0x2000
2)The flag should be ORed in in MEXT_ADD_REF() only if the ref_cnt is
equal to or
In message [EMAIL PROTECTED] Mike Meyer writes:
: Maxim Sobolev writes:
: Mike Meyer wrote:
:
: Donn Miller writes:
:Mike Meyer wrote:
: I do read cvs-all, and I missed it. Not did I find device.hints in the
: relevant Makefiles. Can you provide a pointer to details on how
:
On Mon, Aug 28, 2000 at 03:46:20PM +0200, Brad Knowles wrote:
Personally, I'm astonished that an SMP kernel will actually boot
and run on a uniprocessor machine.
Grr, still getting used to mutt, and I didn't reply to the list. Yes, I'm
using an SMP board, and waiting on the arrival of
On Monday, 28 August 2000 at 8:24:50 -0500, Mike Meyer wrote:
Maxim Sobolev writes:
Mike Meyer wrote:
Will the system fail to boot if there isn't an empty device.hints
file?
No, it will boot, but some devices (like keyboard, console etc) would not work.
That's clearly not true - I just
On Tue, Aug 29, 2000 at 10:25:26AM +0930, Greg Lehey wrote:
At the very least, there appears to be confusion about how to use the
hints. I can see two conflicting views here:
1. You must have a /boot/device.hints file, but it may be empty.
This is minimally correct. I.e. that's what the
In article [EMAIL PROTECTED],
Brian Fundakowski Feldman [EMAIL PROTECTED] wrote:
Woops, I have the KASSERT bungled up. Please change
KASSERT(to *hiwat uip != NULL,
to
KASSERT(to = *hiwat || uip != NULL,
It seems to be fixed now. I've had a script pounding on it all
48 matches
Mail list logo
