> Why can't the PAO changes be committed to the main source tree? It would
> be nice if I could just install the latest version of FreeBSD from
> the Walnut Creek CD-ROM as is and have PCMCIA and APM support on my
Yes, it would be nice. To make a long story short (and emotionless)
there are integ
Why can't the PAO changes be committed to the main source tree? It would
be nice if I could just install the latest version of FreeBSD from
the Walnut Creek CD-ROM as is and have PCMCIA and APM support on my
laptop without always having to wait for Hosokawa.
I asked about this previously and rece
On Sat, 29 May 1999, Forrest Aldrich wrote:
> I'm still at 3.2; however, I wonder what plans there are (if any) to have
> pcmcia
> support in 4.x (like the 3com 3c574, etc). Might be a good idea to include
> a pcmcia floppy in the installation media (like Linux already has).
Someone has never di
I'm still at 3.2; however, I wonder what plans there are (if any) to have
pcmcia
support in 4.x (like the 3com 3c574, etc). Might be a good idea to include
a pcmcia floppy in the installation media (like Linux already has).
Thanks.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsub
On Sat, 29 May 1999, John Polstra wrote:
> In article ,
> Chuck Robey wrote:
>
> > I thought libgcc was being deprecated, isn't that so? That only
> > libstdc++ was going to be needed?
>
> No, I think you're confusing libgcc with libg++.
Yeah, guess you're right, I was. OK, thanks.
>
> Jo
In article ,
Chuck Robey wrote:
> I thought libgcc was being deprecated, isn't that so? That only
> libstdc++ was going to be needed?
No, I think you're confusing libgcc with libg++.
John
--
John Polstra j...@polstra.com
John D. Polstra & Co.
I've got an egcs related question here. If it wasn't for the linking,
this would be a ports question, but bear with me, you'll see.
Anyhow, I was trying to get sp to work, as I continue checking into xml
and xsl, so I used the /usr/ports/textproc/sp port. It dies in several
places, because it's
On Fri, May 28, 1999 at 02:44:58PM -0700, Jordan K. Hubbard wrote:
> A florida ISP recently donated a T3 connection and a beefy SMP box to
> us, so I took advantage of this to create another cvsup mirror which
> allows up to 32 connections. Folks are encouraged to use this site
> in preference to
On 29-May-99 Osokin Sergey wrote:
>
> Hello!
> pcm driver for SB 128 PCI in -current is broken...
># dmesg | more
> .
> es0: irq 5 at device 11.0 on pci0
> pcm0: using I/O space register mapping at 0xe800
>
>
> play, waveplay, wmsound dont' work correct.
> Does someone have any idea?
>
Mark Newton writes:
| I tried to upgrade my diskless router this afternoon to -current as
| cvsupped last night.
|
| I can't make it boot, though.
|
| It now panics with "Can't mount root" when I boot it. And yes, I have
| updated the kernel config for new-bus.
|
| I noticed the BOOTP stuff i
Hello!
pcm driver for SB 128 PCI in -current is broken...
# dmesg | more
.
es0: irq 5 at device 11.0 on pci0
pcm0: using I/O space register mapping at 0xe800
play, waveplay, wmsound dont' work correct.
Does someone have any idea?
And when it fixed?
Rgdz,
Osokin Sergey aka oZZ,
o...@etr
>>> JFYI - don't want us getting *too* complacent with -current now, do we? :-)
>>
>>Floating point exceptions are also broken, they always behave like
>>masked, even if you unmask some explicitly with fpsetmask().
>>
>>Even worse, a wrong result is returned if an exception had to be
>>thrown, whil
Dag-Erling Smorgrav writes:
> ENODEV from splash_bmp can also mean that no image is loaded, or that
> the image is invalid.
Specifically, splash_bmp will return ENODEV if one of the following
holds:
- no image is loaded
- the image data has a negative length (!)
- the first two bytes are not
In message <199905291221.waa28...@godzilla.zeta.org.au>, Bruce Evans writes:
>>Just found that savecore is broken in the same way. What is proper
>>procedure to fix it? I.e. is it must be fixed in the kernel, leaving
>>userland programs as is or in userland, leaving kernel as is?
>
>The kernel need
On Sat, 29 May 1999, Nicolai Petri wrote:
> Would it be possible and wise to implement a way to pass parameters to
> modules when they are loaded ?? Like "kldload if_olp -recv_debug" ?
Use sysctl for this.
--
| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| win..
>> JFYI - don't want us getting *too* complacent with -current now, do we? :-)
>
>Floating point exceptions are also broken, they always behave like
>masked, even if you unmask some explicitly with fpsetmask().
>
>Even worse, a wrong result is returned if an exception had to be
>thrown, while the r
>Just found that savecore is broken in the same way. What is proper
>procedure to fix it? I.e. is it must be fixed in the kernel, leaving
>userland programs as is or in userland, leaving kernel as is?
The kernel needs to maintain (or create as necessary for return by
sysctl()) udev_t versions of m
In <17751.927941...@zippy.cdrom.com>, Jordan K. Hubbard wrote:
[...]
> JFYI - don't want us getting *too* complacent with -current now, do we? :-)
Floating point exceptions are also broken, they always behave like
masked, even if you unmask some explicitly with fpsetmask().
Even worse, a wrong r
>I'm obviously missing something really stupid. Would anyone care to
>educate me about changes to diskless booting with NFS root filesystems
>since February 24?
rootdev is now correctly initialised to NODEV, but vfs_mountrootfs()
still uses NODEV to terminate the list of root devices to try.
Br
"Jordan K. Hubbard" writes:
> My only point was that you should make sure something is a certain way
> before you offer advice for dealing with its *current* behavior since,
> otherwise, that's just confusing to everyone. Either way, I don't
> think that *any* of the current sources, from libfetc
Ollivier Robert writes:
> According to Dag-Erling Smorgrav:
> > FTP servers which do not accept passive mode are, IMHO, broken. Their
> They're broken with respect to RFC-959, not only to your opinion :-)
No. Allowable responses to the PASV command include 227 (Entering
passive mode), 500 (Unreco
Mike Smith writes:
> > module_register_init: MOD_LOAD (splash_bmp, c028162c, 0) error 19
> That's what we needed to see. Error 19 is ENODEV; this means you
> either don't have VESA support compiled in, haven't loaded the VESA
> module, or your VESA BIOS doesn't support a mode that allows
> a 3
"Andrey A. Chernov" writes:
> Just check 'swapinfo' in recent -current, it shows "/dev/(null)" as swap
> device, it means that devinfo() call in kvm_getswapinfo() returns NULL,
> i.e. called with wrong argument which is swinfo.sw_dev
Other interesting swapinfo(8) behaviour:
root(yeshs-3)--# unam
Would it be possible and wise to implement a way to pass parameters to
modules when they are loaded ?? Like "kldload if_olp -recv_debug" ?
-
Nicolai Petri
n...@swamp.dk
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
24 matches
Mail list logo
