On Tue, Jun 15, 1999 at 08:59:59AM -0700, Arun Sharma wrote:
> While we're on the init topic, is there any strong feeling here about
> BSD /etc/rc* scripts Vs SysV ?
Yes, lots. The last round of discussion was covered in the freebsd-arch
mailing list, the archives should be enlightening.
N
--
pgpnad5Bmmg3c.pgp
Description: signed PGP message
adsha...@home.com wrote:
>>
>> Like sending a signal to the process providing the service ? The
>> problem with that approach is, the signal you send and the clean up
>> you do is non-standard for each service and having a standard
>> interface:
>>
>> /etc/rc.d/ stop|start|restart
>>
>> makes it
On Tue, 15 Jun 1999, Wayne Cuddy wrote:
> On my 2.2.7 system I have this directory:
> /usr/share/examples/drivers
>
> This is not on my 3.2S system. I have the 3.1 4 cd set can anyone tell me
> what I need to install in order get the drivers extracted from my 3.1 cd?
They are on cdrom2.
# cd
Wayne Cuddy wrote:
> They SysV way is more elegant and less error prone for bad typist.
... and has absolutely no way of encoding interdependencies between
services (or any concept of a "service" at all, other than as
after-the-fact hacks). What happens to your NFS services when
you do "/etc/
4.0-CURRENT: sys/pci/pcisupport.c:
955:/* VIA Technologies -- vendor 0x1106 &/
956:case 0x05861106: /* south bridge section */
957:return ("VIA 82C586 PCI-ISA bridge");
This is cute. Moo.
Daniel
--
dba...@cuckoo.com - Senior CuckooNet Consultant - http://www.cu
On my 2.2.7 system I have this directory:
/usr/share/examples/drivers
This is not on my 3.2S system. I have the 3.1 4 cd set can anyone tell me
what I need to install in order get the drivers extracted from my 3.1 cd?
Thanks,
Wayne
To Unsubscribe: send mail to majord...@freebsd.org
with "un
They SysV way is more elegant and less error prone for bad typist. Graphical
tools can be used to interface with these quite easily. It also also easy to
automate installations via installation mechanisms. I don't think I agree
that it is a bad idea because it is associated with SysV...
On 15
Arun Sharma wrote:
> Mark Newton writes:
> > Arun Sharma wrote:
> >
> > > While we're on the init topic, is there any strong feeling here about
> > > BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts
> > > is the ability to start and stop any service that I like.
> >
Mark Newton writes:
> Arun Sharma wrote:
>
> > While we're on the init topic, is there any strong feeling here about
> > BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts
> > is the ability to start and stop any service that I like.
>
> That's fine -- there are lots of way
On 16-Jun-99 Justin C. Walker wrote:
> I'm not sure this is relevant, but the loopback address should
> *not* be fed to ARP. That's attached to the loopback interface
> (lo0), and shouldn't be seen on any wire. Could be your config is
> seriously fouled up.
Yes, but how :)
The loo
On 16-Jun-99 John Baldwin wrote:
> Whoops.. just ifconfig de0. Have you tried using the interface? We use
> for a lab I help run, and 'arp -a' on the clients does not show an entry for
> the local de0 card they have installed, but they work fine regardless. Do
> have a route for 127.0.0.1 i
Bleh. More fragility. VOP_*() routines, lookup(), and namei() leave
garbage pointers in nameidata and returned-vnode structures when they
return an error. They really ought to NULL-out those garbage pointers.
It's on my list to fix. It makes it difficult for the NFS code to ke
Christopher Sedore writes:
> I bought a one-for-all remote that I drove from FreeBSD just in the last
> year or two. You might try www.smarthome.com. I bought the remote,
> cable, and docs for how to use it for under US $100. They also have
> RS232 learning IR devices for $180. Expensive, but I
> From: John Baldwin
> Date: 1999-06-15 16:23:24 -0700
> To: "Daniel J. O'Connor"
> Subject: RE: DHCP, arp and de0
> Cc: freebsd-hackers@FreeBSD.ORG
> In-reply-to:
> X-Priority: 3 (Normal)
> Delivered-to: freebsd-hackers@freebsd.org
> X-Mailer: XFMail 1.3 [p0] on FreeBSD
> X-Loop: FreeBSD.ORG
>
On 16-Jun-99 Daniel O'Connor wrote:
>
> On 15-Jun-99 John Baldwin wrote:
>> Are you using the built-in dhcp client (/sbin/dhclient)? If so, what does
>> output look like during boot up? What does 'ifconfig -i de0' show? Also,
>> you have a lease in /var/db/dhcp.leases?
>
> I am using /sbin
I bought a one-for-all remote that I drove from FreeBSD just in the last
year or two. You might try www.smarthome.com. I bought the remote,
cable, and docs for how to use it for under US $100. They also have
RS232 learning IR devices for $180. Expensive, but I wasn't willing to
do the electroni
Josef Karthauser writes:
>
> I've got a phototransistor plugged into my DTR line on the serial
> port. Is there any working software for FreeBSD for utilising this?
> (I want to never lose a remote control again!)
Oh My Goodness! I don't know whether to laugh or cry.
Can somebody get me started
On 15-Jun-99 John Baldwin wrote:
> Are you using the built-in dhcp client (/sbin/dhclient)? If so, what does
> output look like during boot up? What does 'ifconfig -i de0' show? Also,
> you have a lease in /var/db/dhcp.leases?
I am using /sbin/dhclient de0 to get a lease, and the config fil
Arun Sharma wrote:
> While we're on the init topic, is there any strong feeling here about
> BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts
> is the ability to start and stop any service that I like.
That's fine -- there are lots of ways to start and stop any service you
:Hmm... that is a bit long for us... 3 weeks, 21 days at 1.7 day/panic =
:0.59 Panic/Day == 21 (day) * 0.59(day/panic) [remeber to check your units ;]
:...
:David Cross | email: cro...@cs.rpi.edu
I'll have patches on my site in a few days. I just meant time ti
On 13-Jun-99 Daniel J. O'Connor wrote:
> Hi,
> I have tried getting my system to use DHCP on my local network, but I'm
> having
> trouble.
> If I don't use DHCP everything works fine, but if I use DHCP I get the
> following messages appearing in my log file when I use ESD, and try and ping
> my LA
> The differences between -current and -stable for nfs_serv.c and nfs_subs.c
> are relatively minor. Once we've life tested the hell out of it in
> current, it should be easy to MFC into stable. Maybe 3 weeks total.
Hmm... that is a bit long for us... 3 weeks, 21 days at 1.7 day/pan
:Way to go! I was hoping this would happen... it is the miracle of Open Source.
:I am a bit sad that I'm not doing any of the stuff now though :(, you guys
:are just too gosh darn quick.
:
:Seriously though... when are we likely to see this stuff hit -STABLE? I would
:like to to dig through your
> :Umm, okay but I'm a little confused about how the zfree I'm adding to
> :nfs_nget falls under this. Am I being really stupid here?
>
> it's unrelated. I was starting a new thread.
>
> I have finished fixing up nfs_serv.c and am now testing it. Most of
> the procedures require
:Umm, okay but I'm a little confused about how the zfree I'm adding to
:nfs_nget falls under this. Am I being really stupid here?
it's unrelated. I was starting a new thread.
I have finished fixing up nfs_serv.c and am now testing it. Most of
the procedures required significant
talk to terry on this topic :-)
He has a set of patches that straighten all this out
julian
On Tue, 15 Jun 1999, Matthew Dillon wrote:
> This is totally screwed up: The rules used to determine whether
> a path component buffer ( struct componentname, sys/namei.h ) is freed
> by a
Umm, okay but I'm a little confused about how the zfree I'm adding to
nfs_nget falls under this. Am I being really stupid here?
On Tue, 15 Jun 1999, Matthew Dillon wrote:
> This is totally screwed up: The rules used to determine whether
> a path component buffer ( struct component
>Is the 82559 ethernet controller supported under Freebsd 3.2?
Yes.
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
To Unsubscribe: send mail to majord...@freebsd.org
Is the 82559 ethernet controller supported under Freebsd 3.2?
Dennis
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
This is totally screwed up: The rules used to determine whether
a path component buffer ( struct componentname, sys/namei.h ) is freed
by a VOP routine or not are idiotic.
As far as I can tell, the rule is:
* if no error is returned free the path component buffer, but onl
you can also find samples in /usr/share/examples/drivers. These may be
slightly broken in 4.x
On Wed, 16 Jun 1999, Greg Lehey wrote:
> [moved to -hackers; this is more appropriate there]
>
> On Tuesday, 15 June 1999 at 20:51:59 +0300, garret.wh...@nokia.com wrote:
> >
> > Hi All!
> >
> > I'm l
[moved to -hackers; this is more appropriate there]
On Tuesday, 15 June 1999 at 20:51:59 +0300, garret.wh...@nokia.com wrote:
>
> Hi All!
>
> I'm looking to write device drivers for FreeBSD. To this end, I'm searching
> for a Driver-Kernel interface reference manual for FreeBSD (ordinary BSD
> sh
On Tue, 15 Jun 1999, Mike Smith wrote:
> Peter is sic transit mundi at the moment, having missed his original
> flight back from Usenix. This probably calls for another committer
> (eg. one of the Matts...)
Hmm, a choice of 1 out of 1 unless I missed somthing
Peter is sick in transit to mun
> The problem is that peter is not releasing the nfs_node_hash_lock
> when he goes to retry, creating a deadlock with himself.
>
> Peter, looks like a quick fix & commit to me, I'd say just go ahead
> and do it.
Peter is sic transit mundi at the moment, having missed his origi
The actual code of interest is:
FreeBSD:
* $Id: nfs_node.c,v 1.28.2.1 1999/06/07 00:04:05 peter Exp $
or
* $Id: nfs_node.c,v 1.29 1999/06/05 05:26:36 peter Exp $
...
/*
* Insert the nfsnode in the hash queue for its new file handle
*/
for (np2 = nhpp->lh_first
In message <199906151750.caa23...@tasogare.imasy.or.jp> Mitsuru IWASAKI writes:
: Thanks a lot for your testing.
: I'm preparing -current NotePC for testing this.
You are most welcome. I'm glad that I could be of assistance. I've
wanted something like this for a long time, but never found the ti
On Tue, Jun 15, 1999 at 08:07:02PM +0200, Sheldon Hearn wrote:
>
>
> On Tue, 15 Jun 1999 20:05:10 +0200, Guido van Rooij wrote:
>
> > And when you fix that, the wrapper stuff gets invoked for every
> > packet...
>
> Even worse than I anticipated. :-)
>
> So then we just note in the manpage tha
Yes, I looked at it. It's also true that we both (OpenBSD/FreeBSD) have a
small memory leak too in this case.
NetBSD has none of the problems.
-matt
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
patch adds support for the Linksys 10/100 PCMCIA card
if you have a NE2000 type card which is supported by if_ed.c, please
apply this patch and provide feedback. it work wonderfully for me,
but i have only two cards that use this driver.there are a wide
variety of cards that use the if_ed.c
On Tue, 15 Jun 1999 20:07:02 +0200, Sheldon Hearn wrote:
> So then we just note in the manpage that only TCP-based services are
> wrapped?
And don't even _think_ about telling me that the phrase "Support is
provided for TCP Wrappers" doesn't say anything about UDP. ;-)
Ciao,
Sheldon.
To Unsu
On Tue, Jun 15, 1999 at 10:37:18AM -0700, Matthew Dillon wrote:
>
> Sounds good to me! If someone on -hackers has easy access to the OpenBSD
> source, it would be nice if he could check whether the OpenBSD code
> has the same problem and notify the OpenBSD folks if it does.
they dont
On Tue, 15 Jun 1999 20:05:10 +0200, Guido van Rooij wrote:
> And when you fix that, the wrapper stuff gets invoked for every
> packet...
Even worse than I anticipated. :-)
So then we just note in the manpage that only TCP-based services are
wrapped?
Ciao,
Sheldon.
To Unsubscribe: send mail
On Tue, Jun 15, 1999 at 08:01:55PM +0200, Sheldon Hearn wrote:
>
> Hi folks,
>
> The patches on PR 12097 that deal with fixing inetd's handling of
> tcp_wrapper support do _not_ enable wrapping of UDP services. David
> Malone and I are busy working on a patch for doing so, but I have a
> question
Hi folks,
The patches on PR 12097 that deal with fixing inetd's handling of
tcp_wrapper support do _not_ enable wrapping of UDP services. David
Malone and I are busy working on a patch for doing so, but I have a
question that I probably should have asked when we started.
Is there any point in wr
Thanks a lot for your testing.
I'm preparing -current NotePC for testing this.
imp> I've applied the patches to my -current system. I had to apply two by
imp> hand, and then it just compiled and appeared to work with no ill
imp> effects on my desktop.
It should :)
I heard that 3.2-RELEASE kerne
> :>
> :> Heh, I just realized how funny that first statement was :-)
> :
> :
> :Yup, that's my take too waking up any waiters to re-contend seemed
> :correct to do too
> :...
> :
> :If peter doesn't respond by this afternoon, I'll commit it. I've tried it
> :on -current so far.
>
>
:>
:> Heh, I just realized how funny that first statement was :-)
:
:
:Yup, that's my take too waking up any waiters to re-contend seemed
:correct to do too
:...
:
:If peter doesn't respond by this afternoon, I'll commit it. I've tried it
:on -current so far.
Sounds good to me!
> :
>
> The problem is that peter is not releasing the nfs_node_hash_lock
> when he goes to retry, creating a deadlock with himself.
>
> Peter, looks like a quick fix & commit to me, I'd say just go ahead
> and do it.
>
> Heh, I just realized how funny that first stateme
In article <10710.928404...@peewee>
j...@zippy.cdrom.com writes:
>> 1. Put pccardd on the mfsroot floppy and add a few things to
>>sysinstall (this may already be done by his patches, I haven't
>>had time to check) which enable its use during installation.
I've ported PC-card boot.flp to
:> for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) {
:> if (mntp != NFSTOV(np)->v_mount || np2->n_fhsize != fhsize ||
:> bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize))
:> continue;
:> vrele(vp);
:>
> for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) {
> if (mntp != NFSTOV(np)->v_mount || np2->n_fhsize != fhsize ||
> bcmp((caddr_t)fhp, (caddr_t)np2->n_fhp, fhsize))
> continue;
> vrele(vp);
>
Closer examination shows the possible problem:
Rev 1.29 added:
/*
* Insert the nfsnode in the hash queue for its new file handle
*/
for (np2 = nhpp->lh_first; np2 != 0; np2 = np2->n_hash.le_next) {
if (mntp != NFSTOV(np)->v_mount || np2->n_fhsize
Arun Sharma said:
> "James E. Housley" writes:
>
> > Just for my infomation. What is the difference between "Inactive" and
> > "Free" memory. Right now top says I have 157M Inact and 3260K Free.
>
> Inactive means the page contains valid data belonging to some file,
> but is not mapped into an
Umm, recently I've noticed for both 3.2 && 4.0 that NFS seems to get
wedged on a directory that is mounted from a Solaris 2.6 (unpatched)
server- but this seems to only happen if the local mount point is a
directory just off of root.
The scenario is, e.g.:
bird:/export/home on /home
bird:/spac
On Tue, Jun 15, 1999 at 07:51:54AM -0400, Bill Fumerola wrote:
> On Tue, 15 Jun 1999, Ruslan Ermilov wrote:
>
> > While the -core is busy to review/approve this patch,
> > I would like to know your opinion. What do you think
> > of it?
>
> The sysv init should probably be off by default.
>
Sure
On Tue, Jun 15, 1999 at 08:54:23AM -0700, Arun Sharma wrote:
> "James E. Housley" writes:
>
> > Just for my infomation. What is the difference between "Inactive" and
> > "Free" memory. Right now top says I have 157M Inact and 3260K Free.
>
> Inactive means the page contains valid data belongin
On Tue, 15 Jun 1999, Ruslan Ermilov wrote:
> While the -core is busy to review/approve this patch,
> I would like to know your opinion. What do you think
> of it?
The sysv init should probably be off by default.
- bill fumerola - bi...@chc-chimes.com - BF1560 - computer horizons corp -
- ph:(80
While we're on the init topic, is there any strong feeling here about
BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts
is the ability to start and stop any service that I like.
-Arun
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers
"James E. Housley" writes:
> Just for my infomation. What is the difference between "Inactive" and
> "Free" memory. Right now top says I have 157M Inact and 3260K Free.
Inactive means the page contains valid data belonging to some file,
but is not mapped into any address space. Free means, the
Hi, hackers!
While the -core is busy to review/approve this patch,
I would like to know your opinion. What do you think
of it?
Thanks,
--
Ruslan Ermilov Sysadmin and DBA of the
r...@ucb.crimea.ua United Commercial Bank,
r...@freebsd.orgFreeBSD committer,
+380.652.
"David E. Cross" writes:
> That is my interpretation of the code. It would *seem* to just pass the
> call off to the next FS layer as if the VFS system of the kernel had done it
> directly Conceptually I must be missing something.
Umm, umapfs rewrites the owner/group of vnodes if I'm not mi
>> I have been looking at the code for UMAPfs... I am trying to understand
>> conceptually why it is so unstable...
>
>You're looking in the wrong place. It's unstable because of
>infrastructure problems which require fairly substantial amounts of
>work to correct.
>
>DES
I guess that is what I a
"David E. Cross" writes:
> I have been looking at the code for UMAPfs... I am trying to understand
> conceptually why it is so unstable...
You're looking in the wrong place. It's unstable because of
infrastructure problems which require fairly substantial amounts of
work to correct.
DES
--
Dag
I've yesterday tried to get kernel dumps to work and failed (and instead
just fixed the bug I was looking for :-).
The manpage for dumpon seems to be out of date. Adding
dump on wd0s2b
to the KERNEL config file, gives me a syntax error in that line.
And adding the dumpdev to rc.conf
Just for my infomation. What is the difference between "Inactive" and
"Free" memory. Right now top says I have 157M Inact and 3260K Free.
Jim
--
James E. HousleyPGP: 1024/03983B4D
System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13
Pager: page...
> -Original Message-
> From: Tommy Hallgren [SMTP:thallg...@yahoo.com]
> Sent: Tuesday, June 15, 1999 1:23 PM
> To: Mike Smith; hack...@freebsd.org
> Subject: Re: ZD labs test update
>
> Isn't 16MB/s quite bad for this kind of system?
>
[ML] Figuring in the SCSI overhead,
--- Mike Smith wrote:
> We'd previously encountered problems with the Infortrend controller not
> at all liking the other disks we'd tried to talk to; a collection of
> Cheetahs with IBM and Compaq firmware simply wouldn't work. This time
> we had better luck with real Seagate firmware, and th
> > symlinks have caused me grief (Pyramid OSx) and never joy. I hope it fails
> > yet again to appear in FreeBSD. Just think of the new security holes for a
> > start.
>
> Name one, please. You can currently point a symlink anyplace you
> like; whether the user has permission to *read* or exec
On Thu, Jun 10, 1999 at 02:16:57PM +0100, Roger Hardiman wrote:
> Hi,
>
> Several people have asked my recently about supporting the AverMedia
> remote control and the FlyVideo Remote Control units for their
> Bt848/Bt878 TV cards.
>
> Well, I finally got a reply from AverMedia and after checking
dil...@apollo.backplane.com (Matthew Dillon) writes:
> However, if the inside of the first conditional generates an error, the vp
> may be vput twice. What I recommend is this for the last bit:
That can't happen (the attributes are straight from VATTR_NULL along
that path) - if it could
dsche...@enteract.com (David Scheidt) writes:
> First try: Suppose foo depends on /usr/local/etc/foo.conf.
> /usr/local/etc is a link to /usr/local/${ARCH}/etc. User does
> export $ARCH=../../home/user, so /usr/local/etc/foo.conf is now in
> their home directory. Depending on how poorly writte
:Who, me? Open a can of worms? ;)
Heh!
:> We are going to have to instrument the code - basically means NULLing
:> out ni_vp and any local vnode pointer when the vnode in question is
:> released so we can keep track of it and putting KASSERT()s in strategic
:> places. nfs_n
m...@servo.ccr.org (Mike O'Dell) writes:
> very fine-grain-locked systems often display convoying and
> are prone to priority inversion problems. coarse-grained
Priority inversion problems are design flaws. Depending on the type
of locks, they may not even be possible. Spin locks held for shor
Straight back from Usenix, I've returned to ZD labs to continue with
the benchmarking attempt we started the week before last. Just to
remind everyone, this is the standard Samba-and-Apache runaround with
the addition of Zeus to the mix in order to get a feel for its relative
performance. Th
75 matches
Mail list logo
