To me this very much sounds like feature creap. The less options, the
better, no one is looking at them anyway. Who says you are doing a
build on ufs anyway?
It might be something for a FAQ though (if there is one) or for the
handbook.
Just my 0.01 BEF.
Nick
> >The following patch to /u
> Hi,
>
>The following patch to /usr/src/release/Makefile allows the
> specification of the variable FASTCLEAN, which instead of doing
> a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of
> course, this is only useful if your CHROOTDIR location is a
> separate mount point (which min
John Polstra wrote:
>
> If/when you change the size of jmp_buf, please remember to increment
> __FreeBSD_version in "src/sys/sys/param.h". This is likely to break
> the Modula-3 threads support (CVSup), and I'll need a way to deal with
> that.
Good one. jmp_buf has indeed changed. Consider it d
On Wed, 8 Sep 1999, Jordan K. Hubbard wrote:
>
> No offense, but this is really pretty ugly for something that I'd
> anticipate to be a *major* edge case. I've been building releases for
> years, for example, and I've yet to build one on a filesystem all by
> itself. I usually just cast around
>The following patch to /usr/src/release/Makefile allows the
> specification of the variable FASTCLEAN, which instead of doing
> a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of
> course, this is only useful if your CHROOTDIR location is a
> separate mount point (which mine is: /sn
Hi,
The following patch to /usr/src/release/Makefile allows the
specification of the variable FASTCLEAN, which instead of doing
a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of
course, this is only useful if your CHROOTDIR location is a
separate mount point (which mine is: /snap).
After upgrading my test machine (2x PPro, CS4236B chip) to current, I decided
to upgrade my main machine (K6-200, AWE-64 pnp). The newpcm code recognised
both DMA channels and seems to be properly configured.
Thanks to all.
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1
Just a quick note,
inside the netscape ldap library, there is a header file called potable.h, in it
there is the following snippet:
/*
* for connect() -- must we block signals when calling connect()? This
* is necessary on some buggy UNIXes.
*/
#if !defined(LDAP_CONNECT_MUST_NOT_BE_INTERRUPTED
>
> BTW: will the new shim solve the issue that on my tecra8000 the PCI:PCIC
> controller gets an shared interupt with other PCI controllers which I can not
> use with the former pccard code.
huh?
my tecra8000 works great with a linksys 10/100 pcmcia card.
my problem is
After comments from Phk and Matt..
Particularly I'm looking for someone with a ccd and knowledge of it to
look at these patches, (not big) and see if they do anything of interest..
The theory is to inherrit the blocksizes of the underlying devices up to
the ccd device. I don't have a ccd array
Matthew Reimer wrote:
> Maybe the code is trying to bind the local side of the socket to port
> 0x5B? If so, then it could be proved by running Netscape as root.
No, 0x5B is the LDAP_CONNECT_ERROR hex value. As I pointed out in the truss earlier a
SIGALRM happens that causes connect() to return
Maybe the code is trying to bind the local side of the socket to port
0x5B? If so, then it could be proved by running Netscape as root.
Matt
Amancio Hasty wrote:
>
> Don't know what the problem is with netscape.
>
> I can search the ldap server with openldap's ldapsearch tool:
>
> /usr/local/
Don't know what the problem is with netscape.
I can search the ldap server with openldap's ldapsearch tool:
/usr/local/openldap/bin/ldapsearch -h ldap.infospace.com -b "c=US" "cn=Amancio*"
And what do you know I am listed there 8)
cn=Amancio Hasty+ [EMAIL PROTECTED]; c=US; o=Amancio Hasty Jr
If/when you change the size of jmp_buf, please remember to increment
__FreeBSD_version in "src/sys/sys/param.h". This is likely to break
the Modula-3 threads support (CVSup), and I'll need a way to deal with
that.
No, I can't just use sizeof. The Modula-3 threads package is written
in (duh) Mod
Amancio Hasty wrote:
> Hi,
>
> I can't connect to the default ldap servers;however, on my win98 box I can connect
> to the InfoSpace ldap server. I have a local ldap server here and I can connect
> to it using netscape with no problem.
>
> Try it : rah.star-gate.com port 389
>
> --
>
> Amancio
Hi,
I can't connect to the default ldap servers;however, on my win98 box I can connect
to the InfoSpace ldap server. I have a local ldap server here and I can connect
to it using netscape with no problem.
Try it : rah.star-gate.com port 389
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsu
Amancio Hasty wrote:
> click on "Communicator" -> AddressBook , then on your ldap server:
>
> Fill in :
>
> Description: User Friendly name for your ldap server
> LDAP Server: ldap's hostname
> Server Root: your server root
> Port Number : the port number where your ldap server is listening to
click on "Communicator" -> AddressBook , then on your ldap server:
Fill in :
Description: User Friendly name for your ldap server
LDAP Server: ldap's hostname
Server Root: your server root
Port Number : the port number where your ldap server is listening to
>From the address book window you
Hi,
Has anyone had any luck using communicator with a LDAP server? Both
communicator 4.5 and 4.61 fails to connect to any LDAP server that I
have tried. It appears that the connect() gets interrupted and not
restarted. This happens both under current and 3.0.
Lars
To Unsubscribe: send mail
yeah, thanks.
- Original Message -
From: Mike Smith <[EMAIL PROTECTED]>
To: Tomer Weller <[EMAIL PROTECTED]>
Cc: Current <[EMAIL PROTECTED]>; Questions <[EMAIL PROTECTED]>
Sent: Wednesday, September 08, 1999 8:34 PM
Subject: Re: weird Xfree86 Issue
> > I can only start my Xfree when ppp
>I have 'make release' up to the point where it fails building
> the PCCARD kernel. It needs to have the miibus0 controller added.
> A patch is attached.. Would someone please commit this?
What a coincidence! I just fixed this!
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.o
Hi,
I have 'make release' up to the point where it fails building
the PCCARD kernel. It needs to have the miibus0 controller added.
A patch is attached.. Would someone please commit this?
Thanks,
john
ps: I'm still having problems with the size of the fixit floppy, but
currently I've sim
> I can only start my Xfree when ppp is up and running, is that a known problem ?
It's known that your DNS setup is busted, yes.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EMAIL PROTECTED]
I can only start my Xfree when ppp is up and running, is that a known problem ?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, Sep 08, 1999 at 08:01:59AM -0700, Peter Wemm wrote:
> peter 1999/09/08 08:01:59 PDT
>
> Modified files:
> sys/pci if_dm.c if_rl.c if_sf.c if_sis.c if_ste.c
> if_tl.c if_wb.c if_xl.c
> Log:
> Add a pointer to "controller miibus0" for
> pcm0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on
> isa0
>
> If dmesg from sb0 would help I could get it.. Anything else I could help
> with in making "device pcm0" work without params? or is that pnp only?
Yes, that is for pnp-only.
--
we are but packets in the internet of life
To Un
On Wed, 08 Sep 1999 16:53:37 +0300, Maxim Sobolev wrote:
> Why you can't be happy with "device pcm0 at isa? port 0x220 irq 5 drq
> 1 flags 0x15" if it works?
I think Adam's just trying to make sure that he hasn't done something
silly which is preventing him from using a more graceful configura
Adam McDougall wrote:
> I thought I'd try kicking sb0 out of my kernel and try pcm for a change,
> but I cannot get it to work with simply "device pcm0". My sb16 is not pnp,
> and adding controller pnp0 did not help. With just device pcm0, the
> kernel mentions nothing of pcm at all. sb0 worked
Kenneth Culver wrote:
> > Not only does the sio device give me trouble, since I don't use it I took
> > it out, and rebuilt the kernel. Immediately upon reboot, I got a kernel
> > panic. It went like this:
> >
> > Copyright (c) 1992-1999 The FreeBSD Project.
> > Copyright (c) 1982, 1986, 1989, 19
> Not only does the sio device give me trouble, since I don't use it I took
> it out, and rebuilt the kernel. Immediately upon reboot, I got a kernel
> panic. It went like this:
>
> Copyright (c) 1992-1999 The FreeBSD Project.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of
Not only does the sio device give me trouble, since I don't use it I took
it out, and rebuilt the kernel. Immediately upon reboot, I got a kernel
panic. It went like this:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University
I thought I'd try kicking sb0 out of my kernel and try pcm for a change,
but I cannot get it to work with simply "device pcm0". My sb16 is not pnp,
and adding controller pnp0 did not help. With just device pcm0, the
kernel mentions nothing of pcm at all. sb0 worked fine with:
controller sn
> Was the card recognised as pcm1 before? You probably need to go to /dev
> and type:
> sh MAKEDEV snd0
indeed, that was the problem.
randy
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Some "large footprint" changes have been made to the CVS tree and should
be nearly finished. In a nutshell:
- $Id$ and all other traditional rcs keywords are now preserved and
no longer touched by our tools.
- $FreeBSD$ is expanded as an alias for $CVSHeader$ (like $Header$ but
with the CVSROO
It seems Soren Schmidt wrote:
> It seems Doug Rabson wrote:
> > >
> > > Hmm, I'm also having a hell of a time here, on closer inspection it
> > > turns out that my problem is that the kernel allways finds an ed0
> > > device allthough none is present. I have both an ed0 & an ep0 device
> > > in m
On Wed, 8 Sep 1999, Matthew N. Dodd wrote:
> On Wed, 8 Sep 1999, Soren Schmidt wrote:
> > Hmm, I'm also having a hell of a time here, on closer inspection it
> > turns out that my problem is that the kernel allways finds an ed0
> > device allthough none is present. I have both an ed0 & an ep0 dev
It seems Doug Rabson wrote:
> >
> > Hmm, I'm also having a hell of a time here, on closer inspection it
> > turns out that my problem is that the kernel allways finds an ed0
> > device allthough none is present. I have both an ed0 & an ep0 device
> > in my config as I use both type of cards. So m
On Tue, 7 Sep 1999, Warner Losh wrote:
...
> Fix the resource allocation error. :-) That's really the only way
> that you'll be able to fix it.
Hmm.
Why should just upgrading the kernel and not changing the configuration/hardware
give me an resource conflict?
BTW: will the new shim solve the iss
On Wed, 8 Sep 1999, Soren Schmidt wrote:
> It seems Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Michael
>Reifenberger writes:
> > : if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
> >
> > The ep driver works in -current.
> >
> > : The message from pccard
39 matches
Mail list logo
