hi, there!
On Fri, 16 Apr 1999, Robert Watson wrote:
> We upgraded a crash machine from 3.1-RELEASE to 4.0-CURRENT from just
> before the EGCS switch was pulled. The machine is a Pentium 166 MMX
> overdrive. Prior to the upgrade, it correctly probed the Kensington KNE
> 2100 (something like th
> > No. make aout-to-elf builds a.out versions of everything first, then
> > uses them to build the elf versions.
>
> Correct. Older compilers would not be able to generate elf targets,
> so we have to update the compiler first.
Right. But the 2.x system should build the compiler (and bootstra
On 17-Apr-99 Brian Feldman wrote:
> Both sound drivers are broken with the new-bus code. My SB16, in the old
> driver, now gets recognized but sbxvi is never looked for. pcm0, the new
> driver, never initializes with the new code :(
>
> device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
>
The
Warner Losh wrote:
>
> In message <19990416202430.c70...@nuxi.com> "David O'Brien" writes:
> : Please excuse my ignorance, but why does make aout-to-elf require the
> : -CURRENT compiler to produce a.out binaries?
> :
> : make aout-to-elf moves a working set of a.out libraries to ---/lib/aout,
> :
Both sound drivers are broken with the new-bus code. My SB16, in the old
driver, now gets recognized but sbxvi is never looked for. pcm0, the new
driver, never initializes with the new code :(
device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
#controller snd0
#device sb0 at isa? port
> >> It doesn't have to. I have only one reference in my config:
> >>
> >> device da0 at scbus1 target 0 unit 0
I commented out my "device da0" and changed all my "disk"'s (16 of them
across two controlers) to "devices"'s and I was able to config and build
a kernel.
So the distin
In message <19990416202430.c70...@nuxi.com> "David O'Brien" writes:
: Please excuse my ignorance, but why does make aout-to-elf require the
: -CURRENT compiler to produce a.out binaries?
:
: make aout-to-elf moves a working set of a.out libraries to ---/lib/aout,
: so doesn't that cover the needs?
On Friday, 16 April 1999 at 20:06:08 -0700, David O'Brien wrote:
>>> device da0
> ..snip..
>>> diskda0 at scbus2 target 0
>
>> Err, perhaps it's because you've defined da0 twice?
>
> Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the
> config file has both
> > Does make aout-to-elf still purport to work from a 2.2.8R system to a
> > recent (like today's) current?
> After reading the UPDATING file, I realized just how silly a question
> this was :-). a.out make world is broken in -current with egcs.
Please excuse my ignorance, but why does make aou
On Fri, Apr 16, 1999 at 04:42:37PM +0930, Greg Lehey wrote:
> On Friday, 16 April 1999 at 0:54:32 -0600, Warner Losh wrote:
> > Does make aout-to-elf still purport to work from a 2.2.8R system to
> > a recent (like today's) current?
>
> I spent a week trying to upgrade from 3.0-CURRENT of about A
> > device da0
..snip..
> > diskda0 at scbus2 target 0
> Err, perhaps it's because you've defined da0 twice?
Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the
config file has both a da0 device (to get the generic SCSI disk code) and
disk (to wire it dow
On Fri, Apr 16, 1999 at 12:46:34PM -0400, Luoqi Chen wrote:
> By the way, if I turn off aliasing (set alias enable off), ftp works
> fine again.
With a week old current cvsupped at approx 0500 GMT on 11 April I see
similar behaviour - ftp seems fine with aliasing off, but often hangs
with aliasin
gt; with "unsubscribe freebsd-current" in the body of the message
>
Why not just download a kern.flp and mfsroot.flp from :
ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/
/3.1-19990416-STABLE/floppies/
'dd' (in linux) them to a disk or use:
ftp://ftp.freebsd.org/pub/
Do you have an empty /usr/X11R6/include? The Makefile assumes you have the
header files if the directory /usr/X11R6/include is present and tries to
build the X version of doscmd. This assumption may not be true though. I'll
change the Makefile to check for /usr/X11R6/include/X11/X.h instead. By the
Chris Csanady wrote:
>
> >As of a few minutes ago, a minimal set of changes to bring the so-called
> >'new-bus' functionality to the i386 kernel in -current.
>
> This seems to have broken disk wiring for me. Is there some necessary
> change in syntax that I am not aware of?
>
> I have the follo
In article you wrote:
> Daniel Eischen wrote:
>> John Polstra wrote:
>>
>>> My hunch is that it's not a fairness issue. It's just the fact that
>>> when you block in disk I/O, the whole process (all threads) blocks.
>>
>> That statement made me think that Modula-3 had it's own threading
>> supp
>As of a few minutes ago, a minimal set of changes to bring the so-called
>'new-bus' functionality to the i386 kernel in -current.
This seems to have broken disk wiring for me. Is there some necessary
change in syntax that I am not aware of?
I have the following scsi related stuff in my config
We upgraded a crash machine from 3.1-RELEASE to 4.0-CURRENT from just
before the EGCS switch was pulled. The machine is a Pentium 166 MMX
overdrive. Prior to the upgrade, it correctly probed the Kensington KNE
2100 (something like that) with the lnc driver as being at 0x300 irq 5
drq 6.
The wo
Hi, I was wondering. Does the new version of freeBSD support my
SMC-Ultra EtherEZ cable modem? If it does, I will throw away Linux and
convert. Thanks in advance
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Hi,
I've been trying to make buildworld on an aged Compaq DX2 (using newly-
supped CURRENT source) for about a week now, and (modulo the few egcs-looking
failures early on) I am now stuck with compilation failures in doscmd.
I have completely removed /usr/obj/* prior to starting, each time, and t
Thomas Dean wrote:
>
> I see the latest /etc/defaults/rc.conf will include either or both of
> /etc/rc.conf or /etc/rc.conf.local.
>
> I only want to have one.
>
> Which is going to stay with us the longest?
/etc/rc.conf, though rc.conf.local is not likely to go away. The
former is the "do your
I am running 4.0-current of April 12. 1999.
I just finished updating my ports after the change to egcs-2.91.66. I
know they were OK as they were, but, I wanted to eliminate all the gcc
compiled things. And, this was a good time.
I had to fix a couple of applications with bad code. Everything e
As of a few minutes ago, a minimal set of changes to bring the so-called
'new-bus' functionality to the i386 kernel in -current.
This is a complete, from the ground up, change in the way the system
boots and configures. For the most part, we've gone to a lot of trouble
to make it work the way it
I see the latest /etc/defaults/rc.conf will include either or both of
/etc/rc.conf or /etc/rc.conf.local.
I only want to have one.
Which is going to stay with us the longest?
tomdean
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the messag
Brian Somers wrote:
>
> Now I think I'm confused ;-} I haven't seen any changes to ftp
> I did the double lookup bit to all the stuff in libexec (including
> ftpd), but that shouldn't effect what's going on here. If the
> external NS record for Louqi's machine isn't supposed to be on that
>
NFS patch #3 ( for -current ) is now available. Again, I recommend waiting
until the weekend before seriously trying any of these patches and not
running them on any machine for which the loss of data would be a problem.
http://www.backplane.com/FreeBSD4/
The current patc
In message <19990416164237.n27...@lemis.com> Greg Lehey writes:
: I spent a week trying to upgrade from 3.0-CURRENT of about August last
: year to 4.0-CURRENT of the beginning of April. I finally gave up
: going the direct way and upgraded first to 3.1-STABLE and from there
: to 4.0-CURRENT. I ha
> Luoqi Chen wrote:
> >
> > Sorry, this is a legitimate ICMP packet: port unreacheable. It looks like
> > the ftp server (ftp.freebsd.org) was making an UDP query to DNS port on
> > the client (which happens to have a named server running, but that's just
> > for the internal network, external ip
Luoqi Chen wrote:
>
> Sorry, this is a legitimate ICMP packet: port unreacheable. It looks like
> the ftp server (ftp.freebsd.org) was making an UDP query to DNS port on
> the client (which happens to have a named server running, but that's just
> for the internal network, external ip address is s
> > Here's async log output from alias enabled ppp, while ftp was retransmitting
> > the PORT command packet:
> >
> > Async: 7e 3d c0 00 00 9d 21 45 00 00 38 13 42 00 00 ff
> > ^^
> > Async: 01 e3 a7 cf ca 49 aa d0 17 db 4e 03 03 a2 f8 00
^^
> > trying different configurations i have encountered the following
> >
> > 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang;
> > 2. ncftp3 from ports DOES NOT hang;
> > 3. netscape communicator 4 DOES NOT hang.
> >
> > so it seems that the problem is in native FreeBSD's ftp or
< said:
> DESCRIPTION
> This interface is obsoleted by rcmd(3). It is available from the compat-
> ibility library, libcompat.
>However, I don't see how rcmd() can be used to replace rexec()
> since rcmd() is a root/rresvport mechanism, as where rexec() is
> a .netrc mechanism.
D
Hi Bret,
I apologise for the outburst. I suppose the fact that I can't see a
problem on my box doesn't mean that no problem exists, and my tone was
uncalled for.
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Thu, 15 Apr 1999 22:18:08 MST, "Bret Ford" wrote:
>Let's continue this thread in capital letters. We might attract
>some attention! ;-)
Well done, you've attracted attention. I'm sitting here thinking you're
a moron.
I can ftp in and out of my machine without problems using a curre
My firewall is set with the open rule only---and I'm still getting the behavior
described below.
Bret Ford
> or you've got a firewall that doesn't allow active FTP :-)
>
>
> On Fri, 16 Apr 1999, Ilya Naumov wrote:
>
> >
> > trying different configurations i have encountered the following
>
>
> trying different configurations i have encountered the following
>
> 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang;
> 2. ncftp3 from ports DOES NOT hang;
> 3. netscape communicator 4 DOES NOT hang.
>
> so it seems that the problem is in native FreeBSD's ftp or a library
> trying different configurations i have encountered the following
>
> 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang;
> 2. ncftp3 from ports DOES NOT hang;
> 3. netscape communicator 4 DOES NOT hang.
>
> so it seems that the problem is in native FreeBSD's ftp or a library
> (
or you've got a firewall that doesn't allow active FTP :-)
On Fri, 16 Apr 1999, Ilya Naumov wrote:
>
> trying different configurations i have encountered the following
>
> 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang;
> 2. ncftp3 from ports DOES NOT hang;
> 3. netscape co
In message , Lowell Gilbert writes:
>Mikhail Teterin writes:
>
>> Sorry. I'm just repeating what Ladavac Marino wrote in
>> <55586e7391acd211b973c1100276179...@r-lmh-wi-100.corpnet.at>:
>>
>> LM: Please note that memory overcommit architectures are a
>> LM: rather common optimizatio
Mikhail Teterin writes:
> Sorry. I'm just repeating what Ladavac Marino wrote in
> <55586e7391acd211b973c1100276179...@r-lmh-wi-100.corpnet.at>:
>
> LM: Please note that memory overcommit architectures are a
> LM: rather common optimization; FreeBSD is one of them. They
> L
trying different configurations i have encountered the following
1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang;
2. ncftp3 from ports DOES NOT hang;
3. netscape communicator 4 DOES NOT hang.
so it seems that the problem is in native FreeBSD's ftp or a library
(libedit.so.2, l
In message , Snob Art Gen
re writes:
>On Thu, 15 Apr 1999, Don Lewis wrote:
>
>> SunOS 4 doesn't do memory overcommit.
>
>I get the impression from Vahalia's _UNIX Internals_ that this is true
>of SunOS 5 as well.
I know from experience that solaris 2.4 overcommits.
--
Poul-Henning Kamp
On Thu, 15 Apr 1999, Don Lewis wrote:
> SunOS 4 doesn't do memory overcommit.
I get the impression from Vahalia's _UNIX Internals_ that this is true
of SunOS 5 as well.
> This could be shaved down a bit if SunOS didn't require
> (swap > total VM) instead of (swap + RAM > total VM).
Again, from
ÐÔ , 16 ÁÐÒ 1999, Brian Somers ÎÁÐÉÓÁÌ:
> > I CAN'T FTP OUT FROM MY -CURRENT SYSTEM. I CAN FTP IN. SOMETHING
> > IS PROBABLY WRONG. I CAN LIST DIRECTORIES, USUALLY. 'GET' COMMANDS
> > HANG. I AM RUNNING -CURRENT FROM MORNING APR 13.
> Generally, if you don't get a response, it usually indica
[.]
>Let's continue this thread in capital letters. We might attract some
> attention! ;-)
>
> I CAN'T FTP OUT FROM MY -CURRENT SYSTEM. I CAN FTP IN. SOMETHING
> IS PROBABLY WRONG. I CAN LIST DIRECTORIES, USUALLY. 'GET' COMMANDS
> HANG. I AM RUNNING -CURRENT FROM MORNING APR 13.
>
On Fri, 16 Apr 1999, UCHIYAMA Yasushi wrote:
> | shouldn't be too hard though, but even then there are seriously non-trivial
> | differences in the tty, block/character devices, VM, networking, etc. Even
> | if the config interface was compatable it wouldn't ever be a 'drop in'
> | option, ev
| shouldn't be too hard though, but even then there are seriously non-trivial
| differences in the tty, block/character devices, VM, networking, etc. Even
| if the config interface was compatable it wouldn't ever be a 'drop in'
| option, even with 'newconfig'.
In strongly system-dependent par
> -Original Message-
> From: Matthew Dillon [SMTP:dil...@apollo.backplane.com]
> Sent: Thursday, April 15, 1999 9:38 PM
> To: Mikhail Teterin
> Cc: curr...@freebsd.org
> Subject: Re: swap on Irix (overcommiting, etc.)
>
> If some of you are wondering why some of us are saying
Matthew Dillon writes:
> To be blunt, the 'total VM' used by a system can run into the gigabytes
> while the actual real memory + swap allocation is 1/10 of that... or
Add another 1000% for stack autoextension... ;--)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscr
On Friday, 16 April 1999 at 0:54:32 -0600, Warner Losh wrote:
> Does make aout-to-elf still purport to work from a 2.2.8R system to
> a recent (like today's) current?
I spent a week trying to upgrade from 3.0-CURRENT of about August last
year to 4.0-CURRENT of the beginning of April. I finally g
50 matches
Mail list logo
