Hi, I noticed that IPFW as a built in kernel options quietly doesn't
seem to work,
no compile errors, but the resultant kernel passes evrything and does
not appear
to contain ipfw funtionality.
ipfw -a l returns
ipfw: getsockopt(IP_FW_GET): Protocol not available.
kldload ipfw and it all works f
I'm as excited as anyone to see progress, especially if it means the
ability to modularize the kernel and load various drivers on demand. But,
alas, it seems this whole thing was rushed horribly.
The first thing I noticed was the panic I got, in atkbd_isa_intr, which
has since been fixed.
But on
From: Motomichi Matsuzaki
Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs.
Date: Sun, 18 Apr 1999 13:55:58 +0900
Message-ID: <19990418135558w.mz...@e-mail.ne.jp>
mzaki> If the routines can refer the users' environment 'LC_CTYPE',
mzaki> it is fine idea. But it can't, I suppose.
I
On Sun, 18 Apr 1999, Motomichi Matsuzaki wrote:
>
> From: "Daniel C. Sobral"
> >
> > I'm concerned about the possible size of GENERIC with this code.
> > Remember, it has to fit in the install floppy. (Well, not really,
> > with loader, but I'm not the one who is getting killed because of a
> >
From: "Daniel C. Sobral"
> Luoqi Chen wrote:
> >
> > > I've add UNICODE support to the Joliet patch.
> > >
> > > It contains few charsets now, but to add other charsets is very easy.
> > > Currently, iso8859-1 and euc-jp is included.
> > >
> > Cool! I think NTFS and VFATFS could use this code to
Can anyone tell me if I can get freebsd 3.1 running on a compaq
pressario 1675 - I'm worried about the pcmcia controller being
recognized (and my xircom re-100btx working). Thanks.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the messa
> -Original Message-
> From: Robert Watson [mailto:rob...@cyrus.watson.org]
> Sent: 17 April 1999 01:16
> To: freebsd-current@freebsd.org
> Subject: lnc0: broke for us between 3.1 and 4.0?
>
> After upgrading to -current, the probe failed as follows
> (when config was
> used on the GEN
On Sat, Apr 17, 1999 at 12:38:25PM -0700, Annelise Anderson wrote:
>
> I think it was, thanks. I changed the order of the nameservers
> in resolv.conf and it no longer happens. :)
What about setting up a caching DNS server on your machine ?
You could configure forwarders.
options {
dire
> I have one problem, though. During the kernel boot:
>
> isa_dmainit(2, 1024) failed
>
> And, of course, any access to something that needs isa
> dma (e.g. floppy) panics. It's a large-memory machine (1G).
> I was under the impression that this was supposed to be fixed
>
Let us not forget that much of the newconfig work can be used with
newconfig shims in the newbus scheme.
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Sun, 18 Apr 1999, Daniel C. Sobral wrote:
> Brian Feldman wrote:
> >
> > > IPFW works for me...but I'm loading the KLD.
> >
> > I like having my ipfw rules there BEFORE anything happens, hence before
> > rc(5).
>
> klds can be loaded by the loader. Hence, before /kernel.
Thanks for ruining
After the latest new-bus changes in FreeBSD-current a kernel configured
with ISDN support and PnP does not compile anymore. The following patch
fixed the problem for me, at least the kernel compiles and runs. I don't
have a PnP ISDN card (only a non-PnP one), but I do have PnP enabled in my
kernel
> I would ask people to STOP DOING THIS. Do not harass or ridicule someone
> for not being fluent in english! Now, it is sorely true that someone wil
Let me just reinforce this statement. It truly does no good at all
and, speaking as a former non-speaker-of-the-native-language when I
li
Annelise Anderson wrote:
> When I log in to my -current machine (April 13 sources) it takes a
> minute or two after the password is entered before the shell prompt
> comes up:
>
> FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0)
>
> login: xanne
> Password:
> []<--cursor just stays here for a while
Brian Feldman wrote:
>
> > IPFW works for me...but I'm loading the KLD.
>
> I like having my ipfw rules there BEFORE anything happens, hence before
> rc(5).
klds can be loaded by the loader. Hence, before /kernel.
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.
Hello Matthew,
Saturday, April 17, 1999, 9:07:51 PM, you wrote:
>> I am getting problems similar to those outlined above. I don't run
>> natd, either, but I do
>> have a firewall enabled. (open rule) I've had to 'put' files rather than
>> 'get' them, since my
>> last build/installworld.
On Sat, 17 Apr 1999, Soren Schmidt wrote:
> It seems Annelise Anderson wrote:
> > When I log in to my -current machine (April 13 sources) it takes a
> > minute or two after the password is entered before the shell prompt
> > comes up:
> >
> > FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0)
> >
>
Luoqi Chen wrote:
>
> > I've add UNICODE support to the Joliet patch.
> >
> > It contains few charsets now, but to add other charsets is very easy.
> > Currently, iso8859-1 and euc-jp is included.
> >
> > Mixture of Joliet/RockRidge Extension is also available, however untested.
> >
> Cool! I thin
It seems Annelise Anderson wrote:
> When I log in to my -current machine (April 13 sources) it takes a
> minute or two after the password is entered before the shell prompt
> comes up:
>
> FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0)
>
> login: xanne
> Password:
> []<--cursor just stays here for
OK!
> There is an option for this which is documented in LINT, MSGBUF_SIZE.
Thanks for letting me know!
> Could you try this patch which should make it see your PCI-ISA bridge:
Well, I'm more than pleased to say IT DID!! Everything is working now!
I'm typing this using the new kernel.
Thank you
:
:> Is this formal decision of core team ? I feel a huge despair, as a
:> member of newconfig project
:
:This was a core team decision, but I really do hope we can still
:figure out some way of working together on a final hybrid of the best
:ideas from both projects since this honestly wasn
On Sat, 17 Apr 1999, Jake Burkholder wrote:
> > Hmm, you might like to try this patch and see what happens, there is
> > a missing old driver wrapper for the pcm stuff. As a result, it's not
> > getting run from the isa probe. Regarding the other driver, I'm not
> > sure what's going on there as
On Sat, 17 Apr 1999, Jose Gabriel Marcelino wrote:
>
>
> On Sat, 17 Apr 1999, Doug Rabson wrote:
>
> > I think we aren't picking up the PCI-ISA bridge chip which means that the
> > isa bus didn't get probed. Could you do a verbose boot (boot -v) of your
> > *old* kernel and post the resulting
When I log in to my -current machine (April 13 sources) it takes a
minute or two after the password is entered before the shell prompt
comes up:
FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0)
login: xanne
Password:
[]<--cursor just stays here for a while
This is on a LAN; it works fine at the cons
Oh, btw, you did break sbxvi. Look carefully at the #if which surrounds it ;)
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _
> Hmm, you might like to try this patch and see what happens, there is
> a missing old driver wrapper for the pcm stuff. As a result, it's not
> getting run from the isa probe. Regarding the other driver, I'm not
> sure what's going on there as the hooks appear to be present.
Right on, that patc
On Sat, 17 Apr 1999, Doug Rabson wrote:
> I think we aren't picking up the PCI-ISA bridge chip which means that the
> isa bus didn't get probed. Could you do a verbose boot (boot -v) of your
> *old* kernel and post the resulting dmesg.
Ok. Here it is. This is the biggest I could get.
I had so
Matthew Thyer wrote:
> Whats the posibility of having another process for the display ?
To be blunt, the probability is epsilon. I simply am not interested
in spending time to make the silly GUI perform better when I could
instead work on making the package transfer files faster.
BTW, have you t
On Sun, 18 Apr 1999, Peter Wemm wrote:
> Brian Feldman wrote:
> > On Sat, 17 Apr 1999, Peter Wemm wrote:
> > > Chris Piazza wrote:
> > > > On 17-Apr-99 Brian Feldman wrote:
> > > > > Both sound drivers are broken with the new-bus code. My SB16, in the
> > > > > ol
> d
> > > > > driver, now ge
> -Original Message-
> From: Robert Watson [mailto:rob...@cyrus.watson.org]
> Sent: 17 April 1999 01:16
> To: freebsd-current@freebsd.org
> Subject: lnc0: broke for us between 3.1 and 4.0?
>
>
>
> We upgraded a crash machine from 3.1-RELEASE to 4.0-CURRENT from just
> before the EGCS swi
Replying to myself...
You'd have to be able to specify the absolute maximum memory use for
a process to ensure you'd still kill run-aways (These would go first!
regardless of the other rules maybe).
Matthew Thyer wrote:
>
> There is obviously a problem when all swap is exhausted.
>
> The only s
There is obviously a problem when all swap is exhausted.
The only solution is to allow the additional memory *use* to succeed AND
to warn the sysadmin that ALL virtual memory has been exhausted.
The only way to do this is to be able to allocate extra virtual memory.
I'd vote for a system that wou
On Sat, 17 Apr 1999, Peter Wemm wrote:
> For what it's worth, PnP has for the most part not been changed under
> new-bus and is using the old mechanisms. The only significant risk is that
> the attach code doesn't like what I've done with the emulation of
> isa_device->id_id for "unit numbers".
> Is this formal decision of core team ? I feel a huge despair, as a
> member of newconfig project
This was a core team decision, but I really do hope we can still
figure out some way of working together on a final hybrid of the best
ideas from both projects since this honestly wasn't done w
Brian Feldman wrote:
> On Sat, 17 Apr 1999, Peter Wemm wrote:
> > Chris Piazza wrote:
> > > On 17-Apr-99 Brian Feldman wrote:
> > > > Both sound drivers are broken with the new-bus code. My SB16, in the ol
d
> > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the ne
w
>
On Sat, 17 Apr 1999, Brian Feldman wrote:
> On Sat, 17 Apr 1999, Peter Wemm wrote:
>
> > Chris Piazza wrote:
> > > 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.
On Sat, 17 Apr 1999, Jose Gabriel J Marcelino wrote:
>
>
> > [..]
> >
> > This sounds a bit like it might be fixed by Bruce:
> > RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v
> >
> > revision 1.2
> > date: 1999/04/17 09:56:35; author: bde; state: Exp; line
Whats the posibility of having another process for the display ?
Naturally this would only be forked if the DISPLAY env is set and the
user didnt refuse GUI mode.
John Polstra wrote:
>
> Thomas Schuerger wrote:
>
> > cvsup is mostly based on disk (and network) I/O, so there shouldn't
> > be a p
On Sat, 17 Apr 1999, Peter Wemm wrote:
> Chris Piazza wrote:
> > 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
In message <199904170528.oaa05...@chandra.eatell.msr.prug.or.jp>, NAKAGAWA
Yoshihisa writes:
>> 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.
>
>Is this formal decision of core team ? I feel a huge despair, as a
> [..]
>
> This sounds a bit like it might be fixed by Bruce:
> RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v
>
> revision 1.2
> date: 1999/04/17 09:56:35; author: bde; state: Exp; lines: +2 -2
> Can you check if you have this update?
I have just checked
How many of you are using RealTek network cards ?
They are crap in my experience (under any OS).
Bret Ford wrote:
>
> >
> > Wednesday, April 14, 1999, 10:25:11 AM, you wrote:
> >
> > >>I am getting problems similar to those outlined above. I don't run
> > >> natd, either, but I do
> > >> h
Jose Gabriel Marcelino wrote:
>
> Hi,
>
> I'm getting kernel panics during boot with the latest
> kernel built today using new-bus.
> This broke both my custom kernel and today's GENERIC (with all the needed
> updates) on my machine. Booting with the old kernel works fine.
>
> From what I can s
> 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.
Is this formal decision of core team ? I feel a huge despair, as a
member of newconfig project
--
NAKAGAWA, Yoshihisa
y-nak...@nwsl.mesh.ad.jp
Hi,
I'm getting kernel panics during boot with the latest
kernel built today using new-bus.
This broke both my custom kernel and today's GENERIC (with all the needed
updates) on my machine. Booting with the old kernel works fine.
> Hey!
>
> I've add UNICODE support to the Joliet patch.
>
> It contains few charsets now, but to add other charsets is very easy.
> Currently, iso8859-1 and euc-jp is included.
>
> Mixture of Joliet/RockRidge Extension is also available, however untested.
>
Cool! I think NTFS and VFATFS could
Matthew Thyer wrote:
> I've found that I need to disable my secondary IDE controller with
> the version 5 and 6 of the new ATAPI drivers.
Just as a thought.. Is your kernel.debug leftover from an earlier build?
Perhaps that's why it works and the current ones do not...
Cheers,
-Peter
To Unsub
I've found that I need to disable my secondary IDE controller with
the version 5 and 6 of the new ATAPI drivers.
It's probably something to do with Ultra DMA support as I have an Ultra DMA
6.48 GB IBM drive on my IDE controller 0 (master) and a Ultra DMA Mitsubishi
32 spin CD-ROM drive as slave on
>Chris Piazza wrote:
>> 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? p
> It's a shame since that can be quite useful on machines where disk space is
> tight, but I have no idea how hard it will be to get working again.
Use "gzexe" - the old fashioned way of doing things. If anyone does
actually want it fixed, on a minimum, man send-pr .. I don't see anything
related
Maxim Sobolev writes:
> If seems that 4.0-current (make world & kernel as of yesterday) can't
> execute ELF gzip'ed binaries with following symptoms:
It never could, AFAIK.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe
On Sat, 17 Apr 1999, Maxim Sobolev wrote:
> If seems that 4.0-current (make world & kernel as of yesterday) can't
> execute ELF gzip'ed binaries with following symptoms:
I enquired about this a few months ago (but didn't hear anything in reply). As
far as I've been able to work out, the facility
Hey!
I've add UNICODE support to the Joliet patch.
It contains few charsets now, but to add other charsets is very easy.
Currently, iso8859-1 and euc-jp is included.
Mixture of Joliet/RockRidge Extension is also available, however untested.
How to use:
1. Pick up the patch from the URL.
On Fri, Apr 16, 1999 at 09:45:29PM -0400, Luoqi Chen wrote:
> Do you have an empty /usr/X11R6/include?
Ah, yes I do. Thanks for that :)
> 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 m
According to Peter Wemm:
> As a special warning: The APIC_IO interrupt management could be a little
> wonky on systems that require the special mptable fixups. If you have
> warnings about broken mptables, or additional interrupts being wired,
> hold back until it's been checked.
Seems to work fi
According to David E . O'Brien:
> 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 down).
I've never defined da* twice in oldconfig-style config. You're not supposed
to do that I
I have one problem, though. During the kernel boot:
isa_dmainit(2, 1024) failed
And, of course, any access to something that needs isa
dma (e.g. floppy) panics. It's a large-memory machine (1G).
I was under the impression that this was supposed to be fixed
in the vm
Chris Piazza wrote:
> 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
Hi All,
If seems that 4.0-current (make world & kernel as of yesterday) can't
execute ELF gzip'ed binaries with following symptoms:
sh-2.02# cp /bin/sh ./
sh-2.02# gzip sh
sh-2.02# ls -l
total 177
-rw-r--r-- 1 root wheel 43 Apr 17 09:58 Report
-r-xr-xr-x 1 root wheel 170093 Apr 17 09:5
59 matches
Mail list logo
