On Monday, 14th June 1999, "Jordan K. Hubbard" wrote:
>> 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;
On Mon, 14 Jun 1999, Jordan K. Hubbard wrote:
> > 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; wh
> 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 execute the targ
On Sunday, 13th June 1999, "Chuck Youse" wrote:
>Forgive my ignorance, but what exactly is meant by a "variant link", and
>what might one be used for?
Abused, not used. A number of incredibly dodgy things can be done with
symlinks that point here at one moment and there at another moment based
o
In message <199906101257.vaa16...@tasogare.imasy.or.jp> Mitsuru IWASAKI writes:
: apmd(8):
: http://home.jp.freebsd.org/~iwasaki/apm/19990610/apmd-usr.sbin.tar.gz
With the patched include files, this compiles and appears to work on
-current.
: 3.2-RELEASE kernel patch:
: http://home.jp.freebsd.or
> For the benefit of those of us who weren't at USENIX, can we please
> have a summary of what was discussed/decided?
Nothing was [deliberately] decided but much was discussed. As soon as
one of us lands back home in some reasonable state, a summary will be
posted. I've yet to do this myself and
In message <3765b7dc.e87ad...@wm28.csie.ncu.edu.tw> Ming-I Hsieh writes:
: Anyone can tell me why the ``sys/stat.h'' don't include ``sys/types''!
: It will cause some imcompatible between FreeBSD and some others UN*X.
Because it isn't supposed to.
STAT(2) FreeBSD System Calls Ma
In message Marc
Ramirez writes:
: Well, I'd like to add versioning, too, but _that's_ hard!
Versioning wouldn't be too hard to add to a filesystem. Name lookup
would be impacted. The act of creating a new version would just be
the creat(2) system call, or open with the O_CREAT bit set (and ma
Sorry about that everyone, I 'repl'ied to the wrong message.
> Ack, you may have opened up a can of worms here. I don't even think
> that nfs_namei() does the right thing when it returns an error... it
> doesn't look like it clears the ndp->ni_vp either in some error cases.
Who, me?
:
:On Mon, 14 Jun 1999, Matthew Dillon wrote:
:
:> Ack, you may have opened up a can of worms here. I don't even think
:
:I don't think it is fair to say he opened a can of worms. He found it, but
:it was clearly open to begin with. He had the misfortune to stumble across
:it. Since he h
On Mon, 14 Jun 1999, Matthew Dillon wrote:
> Ack, you may have opened up a can of worms here. I don't even think
I don't think it is fair to say he opened a can of worms. He found it, but
it was clearly open to begin with. He had the misfortune to stumble across
it. Since he has tracked
Jordan K. Hubbard wrote:
> Excellent. Let's assume then that all the core folk who are there,
> plus any committers who have an interest in the issue (since core has
> to listen to its developers' opinions too or we can no longer honestly
> claim to represent their interests), will be getting toge
On 15-Jun-99 Ming-I Hsieh wrote:
> Anyone can tell me why the ``sys/stat.h'' don't include ``sys/types''!
> It will cause some imcompatible between FreeBSD and some others UN*X.
Because you're supposed to know what you need when you use certain things..
As the stat(2) man page says, you need t
Anyone can tell me why the ``sys/stat.h'' don't include ``sys/types''!
It will cause some imcompatible between FreeBSD and some others UN*X.
Thanks!
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
>
> Any ideas on the following ?
>
> I am setting up a home/office network with NAT filtering gateway
>on a dual-NIC FreeBSD 3.2 box. No problem so far - I've set
>up several like this on 2.2.8 using natd.
>
> The new wrinkle is this: I need to connect to two ISPs
>(DSL & Cable
:
:>> What, to the reckoning of the resident populace, would happen if
:>> somebody were to rm a vnconfig'd swapfile while it was in use?
:> The system still has a reference to the file, even deleted,
:> so all you would be doing would be removing its directory
:> entry.
:
:And what happens when t
s...@iwl.net wrote:
>
> Any ideas on the following ?
>
> I am setting up a home/office network with NAT filtering gateway
>on a dual-NIC FreeBSD 3.2 box. No problem so far - I've set
>up several like this on 2.2.8 using natd.
>
> The new wrinkle is this: I need to connect to two IS
Oh man that routine is complex! I'm looking at it closely
and I think you are right, except I think you may have
introduced a minor bug in fixing the other bug. Here is the code and
the last bit of your modification for reference:
if (vap->va_size != -1) {
it was on a Purdue Dual Vax 11/780
much later DEC sold the 782 which was a
commercially produced version of the
Purdue Dual VAX 11/780 which was built
from one machine and a bunch of "spares".
George Goble produced the parts list to
order from DEC Spares to build your own.
several got built.
I have been looking at the code for UMAPfs... I am trying to understand
conceptually why it is so unstable... It looks straightforward enough as
simply passing the calls it receives on to the FS below it, almost like it
didn't exist at all. Why does this cause problems? Isn't the only differenc
Hi,
I've solved (I think) modules auth failures in pppd using PAM (compiled
with -DUSE_PAM). It's work after one modification:
--- ../pppd-orig/auth.c Sat Jun 20 15:02:08 1998
+++ auth.c Mon Jun 14 17:42:16 1999
@@ -867,7 +867,6 @@
*/
pam_error = pam_authenticate (pamh, PAM_SILENT);
*** nfs_serv.c Tue Jun 8 15:53:11 1999
--- /cs/crossd/nfs_serv.c Mon Jun 14 16:05:45 1999
***
*** 1343,1348
--- 1343,1349
fhandle_t *fhp;
u_quad_t frev, tempsize;
u_char cverf[NFSX_V3CREATEVERF];
+ int eexistdebug=0;
#ifndef nolint
I think I found the problem, and I have a pseudo-fix... (the machine nolonger
crashes).
This is a bleeding edge development, I have not had time to refine this code
any. The problem is that nfs_create for NFSv3 does not release the lock
for "vp" with a vput() before it exits. My crude "patch" fo
Chuck Youse wrote:
>
> Forgive my ignorance, but what exactly is meant by a "variant link", and
> what might one be used for?
A symlink that has a variable name embedded in it. It can be quite
useful at times; consider a symlink such as: /usr/local/bin/bash ->
/usr/local/{karch}/bin/bash, where
:> vn node, you will blow the system up when the system tries
:> to swap something in or out on that file.
:
:Is there any possibility of adding a reference count to the vn device
:so it can't be unconfigured if it's still referenced?
:
:Is there any possibility of implementing a compulsor
> I am still digging arround, but this is significantly above my head. It is
> great fun, and I wouldn't mind continuing except this is becoming a difficult
> issue. We have backed everything down to NFSv2, but existing mounts are
> difficult to get rid of.
It's a difficult issue no matter who y
Ok, now that I have hopefully gotten the criticial people's attention, I
will proceed with the details:
1: My test program can only reproduce this with NFSv3/UDP from a recently
patched Solaris system to a FreeBSD server. I have not tested older
Solaris patches, I suspect that they will not caus
Well, following up to my own post, 3 people have reported
no problems with softupdates on their SMP machines.
One was softupdates only
2 were softupdates and vimun together.
Thanks for everyones prompt replies.
Right, back to those PicoBSD commits.
Bye
Roger
To Unsubscribe: send mail to majord
Roger Hardiman wrote:
> Hi,
> I remember reading in the mailing lists how softupdates
> were unreliable on SMP 3.x and -current machines about 6-8 months
> ago.
>
> Is this all fixed now for SMP machines?
>
> I've been using softupdates on a uni-processor 3.2-stable machine
> and it works well.
I certainly hope they are working under SMP I am running
a 4-way Pentium-III xeon box using vinum and softupdates. so far it has
been a champ.
--
David Cross | email: cro...@cs.rpi.edu
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~cross
Hi,
I remember reading in the mailing lists how softupdates
were unreliable on SMP 3.x and -current machines about 6-8 months
ago.
Is this all fixed now for SMP machines?
I've been using softupdates on a uni-processor 3.2-stable machine
and it works well. I wanted to try it on my two
SMP machines
On Sun, 13 Jun 1999, Jordan K. Hubbard wrote:
> > Forgive my ignorance, but what exactly is meant by a "variant link", and
> > what might one be used for?
>
> Gee, it's refreshing to see someone other than myself bringing this
> subject up. :)
Well, I'd like to add versioning, too, but _that's_
On Sun, 13 Jun 1999, Chuck Youse wrote:
> Forgive my ignorance, but what exactly is meant by a "variant link", and
> what might one be used for?
In my fantasy world, a variant symlink is kind of a way of putting a
search path into a symbolic link, so that if you had an environment
variable E=a:b:
In reply:
> very fine-grain-locked systems often display convoying and
> are prone to priority inversion problems. coarse-grained
> systems exhibit all the granularity problems already described.
> (the first purdue dual-vax system plowed most of that ground)
Was this a VAX 11/782 or a later mach
Any ideas on the following ?
I am setting up a home/office network with NAT filtering gateway
on a dual-NIC FreeBSD 3.2 box. No problem so far - I've set
up several like this on 2.2.8 using natd.
The new wrinkle is this: I need to connect to two ISPs
(DSL & Cable Modem), ideally w
>> What, to the reckoning of the resident populace, would happen if
>> somebody were to rm a vnconfig'd swapfile while it was in use?
> The system still has a reference to the file, even deleted,
> so all you would be doing would be removing its directory
> entry.
And what happens when the system
Unknow User said:
> Quota crash my system after quotaoff followed by quotaon!
> I applied a patch (kern/8137), but it did not work!
> Can anybody explain how could i fix this problem.
> here goes the patch i applied:
[ patch deleted ]
I believe the currently accepted solution is to simply never
very fine-grain-locked systems often display convoying and
are prone to priority inversion problems. coarse-grained
systems exhibit all the granularity problems already described.
(the first purdue dual-vax system plowed most of that ground)
we published the best Unix SMP paper I've ever seen in
Matthew Dillon writes:
> :>A permanent vnode locking fix is many months away because core
> :>decided to ask Kirk to fix it, which was news to me at the time.
> :>However, I agree with the idea of having Kirk fix VNode locking.
> :
> : Actually, core did no such thing. Kirk told me a
Matthew Dillon writes:
> On the otherhand, if you *truncate* the file or unconfigure the
> vn node, you will blow the system up when the system tries
> to swap something in or out on that file.
Is there any possibility of adding a reference count to the vn device
so it can't be unconf
> -Original Message-
> From: Jordan K. Hubbard [SMTP:j...@zippy.cdrom.com]
> Sent: Monday, June 14, 1999 2:32 AM
> Cc: Chuck Youse; Marc Ramirez; hack...@freebsd.org
> Subject: Re: Variant symlinks [was Re: symlink question]
>
> > And have /usr/bin point to /binaries/i386/bin or /b
> -Original Message-
> From: John S. Dyson [SMTP:dy...@iquest.net]
> Sent: Saturday, June 12, 1999 6:58 PM
> To: w...@softweyr.com
> Cc: cro...@cs.rpi.edu; freebsd-hackers@FreeBSD.ORG
> Subject: Re: High syscall overhead?
>
> Think of it like this: since alot of desktops sit in i
:I noticed on a very high traffic'd webserver, I have just over 4000 sockets
:stuck in the TIME_WAIT state. Ideally, I want to "bend" the RFC a bit and
:close the descriptor before it hits that state, or, ignore the 2MSL wait
:when it enters that state.
:
:I take it there is no sysctl switch to
:> A permanent vnode locking fix is many months away because core
:> decided to ask Kirk to fix it, which was news to me at the time.
:> However, I agree with the idea of having Kirk fix VNode locking.
:
: Actually, core did no such thing. Kirk told me a month or so ago that he
:in
> -Original Message-
> From: Dag-Erling Smorgrav [SMTP:d...@flood.ping.uio.no]
> Sent: Sunday, June 13, 1999 6:02 PM
> To: Brian Feldman
> Cc: Dag-Erling Smorgrav; hack...@freebsd.org
> Subject: Re: select(2) breakage
>
[ML] To the previous posters:
the port range
unsubscribe freebsd-hackers
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
:What, to the reckoning of the resident populace, would happen if
:somebody were to rm a vnconfig'd swapfile while it was in use?
:
:Thanks,
:joelh
The system still has a reference to the file, even deleted,
so all you would be doing would be removing its directory
entry.
On the
47 matches
Mail list logo
