I think ISO-C is pretty clear here.
It would be wise to raise this on comp.std.c which is read by several
of the ISO C standard authors. Things that seem pretty clear often
turn out not to be...
-- Richard
___
[EMAIL PROTECTED] mailing list
Yeah... Think Sun2 systems
http://www.netbsd.org/Documentation/network/netboot/nd.html
Though it wasn't just for booting in the old days. On a diskless
workstation, your whole filesystem would be on nd. And it was a real
mistake to mount a writable partition on two machines, but nothing
Ok, GEOM Gate is ready for testing.
For those who don't know what it is, they can read README:
Aaargh! It's the return of nd(4) from SunOS.
(Sorry about that.)
-- Richard
___
[EMAIL PROTECTED] mailing list
That's because pccardc and pccardd aren't supported in NEWCARD.
Ok. It might be worth noting that in /etc/defaults/rc.conf, which still
has all the pccard_* variables with no suggestion that they don't work.
consider devd. It is somewhat incomplete in DP2, but complete enough
for this.
consider devd. It is somewhat incomplete in DP2, but complete enough
for this.
Thanks, I'll try it.
Is there any documentation for devd.conf? The man page is incomplete
(it only describes the syntax of comments, though admittedly it does
that in great detail) and there's no default
I now have DP2 running on my Vaio Z600 laptop, and I'm trying to get my
wireless ethernet running.
The cardbus is detected:
kernel: cbb0: RF5C475 PCI-CardBus Bridge at device 12.0 on pci0
kernel: cardbus0: CardBus bus on cbb0
kernel: pccard0: 16-bit PCCard bus on cbb0
But when it tries to
I'm trying to install DP2 on a Sony Vaio Z600TEK laptop, but it hangs
at Probing devices, please wait (this can take a while)
It's not completely hung, in that I can switch to the second console
and back. The last message there is
DEBUG: Add mapping for /dev/cuaa0 to sl0
and this is
Somewhere there should be a warning that the root partition needs to be
*much* bigger in 5.0 than in 4.x. It's gone from 40-something MB to
92 MB for a default install. It's really frustrating to install a
system and find that / is 104% full.
It looks as if even with 128 MB you're not going to
For those of us who scan the -current mailing list from time to time
but don't actually run current, is there a description somewhere of
what GEOM *is*?
-- Richard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
You are blowing this out of proportion and not actually reading
what people are proposing. So far, the comments are about
removing a.out support from the base compiler and offering
a.out binutils and gcc _as ports_.
That would be sufficient for my needs (a matching gdb would be useful
too,
GCC being able to produce a.out format binaries has nothing to do with
the ability of a Lisp or Prolog to compile to object files,
Correct.
and read such, whether said object files be a.out or ELF or COFF or PECOFF or
Mach-O or ...
False. As I said, I have systems that read a.out format
False. As I said, I have systems that read a.out format object files
and they would need to be ported to read ELF object files instead.
Furthermore, they write themselves out (after loading object files) in
a.out format, and would need to be ported to write themselves out
in ELF
yes binary support will remain.. if you need to generate new ones (?)
You say this as if no-one would want to do it, but I still use
programs (lisp and prolog compilers) that need to generate and read in
compiled .o files, and undump themselves after reading in such
files, and which are never
I think you're extremeley confused.
In what way? Or are you just being rude?
-- RIchard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Fatal error '_waitq_remove: Not in queue' at line 350 in file
/usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 0)
I get the same message with xine on -STABLE each time i use it.
I've had this problem for months if not years, in all recent releases
of FreeBSD. It's not
I wonder if there's any planned support for Alcatel Speed Touch PC (a ADSL
PCI card) I think there are some linuxdrivers but what could be needed for
FreeBSD support?
Contact the guys listed on http://www.xsproject.org/speedtouch/ (bottom of
the page).
That's the Speedtouch USB, not the
vfork(2) [...] The child code
between the fork() and subsequent exec() must be carefully written
because any changes to memory (including stack) or open files will
also be reflected in the parent.
Not open files: indeed, the main thing you typically want to do before
the exec() is opening,
PThe string pointed to by path1 shall be treated only as a character
Pstring and shall not be validated as a pathname.
I have heard on several occasions of peope using symlink(2) to
atomically store some small piece of information for locking purposes.
(Symlink was more reliably atomic
ufs:fd0a
set `df /` ; dev="/dev/$8"
How about something like
IFS=': '; set `df /`; IFS=' '
dev="/dev/$9"
-- Richard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
lineal velocity (and hence data rate) increases from the inside
(start) to the outside (end) of the disk.
And consequently any CD that isn't completely full will *always*
be slower than the quoted ("guaranteed not to exceed") rate.
-- Richard
To Unsubscribe: send mail to [EMAIL PROTECTED]
Origin = "AuthenticAMD" Id = 0x580 Stepping=0
You have one of the first K6-2s off the line. There were definite problems
with these, and as such, they were specially distinguished by having 66
printed on top.
I have a 0x580 which has had no problems at all. I'm pretty certain
it
Depends on your motherboard. Try to just disable UDMA66 first.
Thanks, that's what I did. It works fine (I'm using a SOYO 5EHM
motherboard with an AMD K6-2/200). Performance is excellent; bonnie
gives:
---Sequential Output ---Sequential Input-- --Random--
I'm about to install FreeBSD 3.2 on a machine with an IBM-DJNA-371350
(Deskstar 22GXP 13.5GB) drive. I see that on the -current mailing
list a few weeks ago you (phk) said:
Try disabling "ultra DMA" in the BIOS, that seems to have worked for
me on my IBM-DJNA-371800 drive.
Is that relevant for
People desperate for current functionality can wait, back port themselves or
run current. I have taken all three options in the past :-)
I agree. I have recently installed 3.1-STABLE on two machines, and in
each case the ethernet drivers (xl and lnc) had been broken since 3.1
(both are now
lnc0: Memory allocated above 16Mb limit
I've just committed a fix for this. It was caused by the change to the way
vm_page.c allocates memory
Is this fix going into stable? (I'm a little surprised that such a
change was considered appropriate for the stable branch in the first
place.)
--
Because Berkeley Unix has /always/ included a FORTRAN compiler.
Maybe we should put Franz Lisp back in.
bash-2.02$ uname -sr
FreeBSD 3.0-RELEASE
bash-2.02$ lisp
Franz Lisp, Opus 38.92
-
-- Richard
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in
26 matches
Mail list logo
