In message , attila writes:
>
>I just noticed the date on this discussion was two months ago;
>so I referenced the code in kern_prot.c which indicates no
>decision was made on this item
>
>was another solution implemented?
It is on my machine here, It has just been preempted by
Hi folks,
Can anyone using /etc/pccard_ether with a DHCP implementation _other_
than the one we have in the base system (isc-dhcp2) feed back on the
diffs supplied in PR 10566, viewable at
http://www.freebsd.org/cgi-bin/query-pr.cgi?pr=10566
Thanks,
Sheldon.
To Unsubscribe: send mail
On Thu, 25 Mar 1999, Ben Smithurst wrote:
> Kris Kennaway wrote:
>
> > Has anyone else been seeing this? What kind of information would help to
> > narrow the problem down?
>
> This has happened a few times on my -stable box, though not very
> often. It just happened a few minutes ago, I wasn't
Hello,
Does current i4b support LZS/STAC compression? My ISP just enabled it
on their ISDN ports, I'd like to use it.
Or is compression not necessary in the kernel driver, but in the
userspace programs (ppp, pppd). When I grep through ppp sources I do
see STAC mentioned somewhere.
--
Peter Mut
I just noticed the date on this discussion was two months ago;
so I referenced the code in kern_prot.c which indicates no
decision was made on this item
was another solution implemented?
actually, in a more deliberate consideration of the implications
of changing the
On Fri, 26 Mar 1999 09:06:06 +0900, "Daniel C. Sobral" wrote:
> Last I checked, rc.conf.site was referenced in defaults/rc.conf. Has
> this changed?
Check again. :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the messag
Mike Smith wrote:
>
> > As a result I'm not able to create a
> > site-wide rc.conf file and rdist it to multiple machines, configured
> > identically except for having distinct own host names. I think some
> > very basic information identifying a host should be kept in its own
> > place:
>
> You
> The current rc.conf system doesn't seem to allow for separating out host
> identity from host configuration.
Just to squash this; yes, it does.
> As a result I'm not able to create a
> site-wide rc.conf file and rdist it to multiple machines, configured
> identically except for having distinct
add my vote for 3.1
chroot() has always been a little less than JAIL if the user
so constrained expects/requires access to virtually anything.
__
go not unto usenet for advice, for the inhabitants thereof wil
On 25-Mar-99 Rahul Dhesi wrote:
> The current rc.conf system doesn't seem to allow for separating out host
> identity from host configuration. As a result I'm not able to create a
> site-wide rc.conf file and rdist it to multiple machines, configured
> identically except for having distinct own h
Sorry to reply to my own email, but there is an error.
On Thu, Mar 25, 1999 at 11:00:28AM -0800, David O'Brien wrote:
> In /etc/rc.conf have the typical
>
> network_interfaces="lo0 fxp0"
>
> line, but don't have a
>
> ifconfig_fxp0=""
>
> this will cause ``/etc/rc.network'' to ru
> I think some very basic information identifying a host should be kept
> in its own place:
>
>host name and ip address for each network interface
>
> And I like the way SunOS does it: The file hostname. contains the
> machine's host name, where is the name of the network interface.
In /et
There was another report of a similar problem on -hackers. Removing
the 'pseudo-device splash' seemed to fix things. You might also try the
patches in this thread.
http://www.freebsd.org/cgi/getmsg.cgi?fetch=715663+0+archive/1999/freebsd-hackers/19990307.freebsd-hackers
Nathan
Ben Smithurst
In article <199903170258.saa01...@implode.root.com>,
David Greenman wrote:
>A much better solution would be for someone to spend the time to
> implement the needed VM frobbing of modifying, at BSDI binary exec-time,
> the ps_strings address constant in the binary's crt0 that is causing the
>
Peter Jeremy writes:
> I'm running -current from a couple of weeks ago. I recently re-compiled
> XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't
> work with X11, though it does work inside an Xterm. My old aout emacs
> still works (with old aout libraries - the re-compil
Kris Kennaway wrote:
> Has anyone else been seeing this? What kind of information would help to
> narrow the problem down?
This has happened a few times on my -stable box, though not very
often. It just happened a few minutes ago, I wasn't doing anything on
the machine, I wasn't even logged in. N
On Thu, 25 Mar 1999 08:41:22 PST, Rahul Dhesi wrote:
> The current rc.conf system doesn't seem to allow for separating out host
> identity from host configuration.
Use /etc/rc.conf for host configuration and /etc/rc.conf.local for host
identity. Or whatever.
Ciao,
Sheldon.
To Unsubscribe: se
On Thu, 25 Mar 1999 17:30:18 +0100, Blaz Zupan wrote:
> If you had taken at look at the PR yourself, you'd notice that it was ME,
> who submited that PR :)
I did take a look at it, that's how I know about it. You don't seriously
expect me to notice the name of each originator for each PR I look
The current rc.conf system doesn't seem to allow for separating out host
identity from host configuration. As a result I'm not able to create a
site-wide rc.conf file and rdist it to multiple machines, configured
identically except for having distinct own host names. I think some
very basic infor
> Have a look at the PR database, specifically at ports/10710. I haven't
> checked it out myself. Perhaps you'd like to try it out and send
> feedback to the freebsd-ports mailing list, which is a much more
> appropriate list through which to address this sort of issue.
If you had taken at look at
I'm running a RealTek ethernet card in a 486dx4-100 machine and am having some
problems. Firstly, doing an ls on a nfs mounted directory exported from the
RealTek machine hangs. According to tcpdump it is receiving the readdir
packets. Secondly, it will hange solidly when acting as the receiver
On Sun, 14 Mar 1999 17:22:42 +0100, Blaz Zupan wrote:
> We don't even have a Postfix port. Has anybody created a port or should I
> go ahead and have a look at it?
Hi Blaz,
Have a look at the PR database, specifically at ports/10710. I haven't
checked it out myself. Perhaps you'd like to try i
i have problems with sio and i read in the man something about dca(4), is it a
replacement ? does it work well ? is it included with 4.0-CURRENT ? please reply
Hi folks,
I've gotten myself confused. Am I correct in thinking that dg's recent
hike on KVA size allows for MAXUSERS > 64 without odd lock-ups?
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
24 matches
Mail list logo
