I was just wondering about the caveat in that access(2) man page
that says that access is a potential security hole and should
never be used, and the fact that ipfw calls it on line 2435.
I seem to recall a discussion about this a few months ago, but
I don't really remember the details... and
In local.freebsd-hackers, you wrote:
On Thu, Sep 06, 2001 at 12:16:19PM -0700, Eric Anholt wrote:
I have a page about the DRI for FreeBSD at=20
http://gladstone.uoregon.edu/~eanholt/dri/. The current DRI CVS works on=
I had a look at that, but it wasn't too clear what I needed to do. I
Chad David [EMAIL PROTECTED] wrote:
I was just wondering about the caveat in that access(2) man page
that says that access is a potential security hole and should
never be used, and the fact that ipfw calls it on line 2435.
I seem to recall a discussion about this a few months ago, but
I
Hello Freebsd
I have used FreeBsd For several Months including using
linux and unix for about 5 Years. I have studied
Information Technology and Programming for two years.
I have came to the point where i believe i could help
in building Freebsd.
Could you please send me some information about
On Fri, Sep 07, 2001 at 11:53:16AM +0100, Philip Taylor wrote:
Hello Freebsd
I have used FreeBsd For several Months including using
linux and unix for about 5 Years. I have studied
Information Technology and Programming for two years.
I have came to the point where i believe i could help
On Thu, Sep 06, 2001 at 10:45:51PM +0200, Olivier Houchard wrote:
Josef Karthauser wrote:
Has anyone got patches for DRI under -current?
Joe
I made an ugly patch so that the drm, gamma and tdfx kernel modules
compile under current. I submitted it to DRI, so you may find it at
Submissions are due this afternoon. Please submit by e-mail ASAP. We're
currently substantially behind prior months -- this is in some ways
expected due to various people on summer vacations in the Northern
Hemisphere, but it would be nice to get things a bit more fleshed up. In
particular,
On Thu, Sep 06, 2001 at 08:23:34PM +0100, void wrote:
On Thu, Sep 06, 2001 at 10:30:08AM +0400, Andrey Simonenko wrote:
0700 mode restricts other users from reading /root directory.
When root wants to upgrade system he/she run make buildworld,
make installworld. But installworld calls
On Fri, Sep 07, 2001 at 10:34:29AM -0400, Robert Watson wrote:
Project: (name here -- required field)
URL: (URL, if any, here -- omit field if none)
Contact: (name and e-mail address of one or more contact points --
required field)
Project: Documentation Project
URL:
Philip Taylor wrote:
Hello Freebsd
I have used FreeBsd For several Months including using
linux and unix for about 5 Years. I have studied
Information Technology and Programming for two years.
I have came to the point where i believe i could help
in building Freebsd.
Could you please
Robert Watson wrote:
Submissions are due this afternoon. Please submit by e-mail ASAP. We're
currently substantially behind prior months -- this is in some ways
expected due to various people on summer vacations in the Northern
Hemisphere, but it would be nice to get things a bit more
On Fri, 7 Sep 2001, Terry Lambert wrote:
Robert Watson wrote:
Submissions are due this afternoon. Please submit by e-mail ASAP. We're
currently substantially behind prior months -- this is in some ways
expected due to various people on summer vacations in the Northern
Hemisphere,
On Fri, 7 Sep 2001, Terry Lambert wrote:
This might not be keeping with the philosophy, though, since most of us
do not trust -current enough to do our PhD Thesis, Master's Project, or
business work on it, and tend to create derivative works of -stable,
instead...
It should be noted, of
Hi,
Could anybody give me some info about 'how to compile the FreeBSD source
code' and run.
Any pointers to useful links will also suffice.
thanks a lot
ashley
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
On Fri, Sep 07, 2001 at 03:23:31PM -0400, Ashley Thomas wrote:
Hi,
Could anybody give me some info about 'how to compile the FreeBSD source
code' and run.
Any pointers to useful links will also suffice.
first, this isn't the proper mailing list for this type of question.
[EMAIL PROTECTED]
status on merging of features to -stable, the release process, etc. At
one point, Jordan was spitting out a FreeBSD news letter once in a while.
Dunno if we'll ever see it again, but I thought that was a good idea, and
was part of the impetus for exploring a monthly electronic report.
I use BUF_STRATEGY() in a kernel module to read a sector on a device like
/dev/ad0s3g. The biowait() routine after BUF_STRATEGY() gives me errors
like EALREADY and EPERM from time to time. I find out that these errors
occur after I already wrote the same device by another program. If I wait
a
Assuming it is in /usr/src (where it gets put by default)
cd /usr/src
make
or
cd /usr/src/
make buildworld
make installworld
or
cd /usr/src/usr.bin/yourfavouriteutility
make depend
make
maek install
If you do not hav ethe source, see the many places in th online handbook
that tell you
On Fri, Sep 07, 2001 at 12:53:48PM -0700, Jordan Hubbard wrote:
status on merging of features to -stable, the release process, etc. At
one point, Jordan was spitting out a FreeBSD news letter once in a while.
Dunno if we'll ever see it again, but I thought that was a good idea, and
was
Oops, I'll have to clarify that. No, you don't need to keep an XFree86-4
tree around at all. Just get the X-DRI tree from sourceforge, and install it
over your XFree86-4 install.
I have both XFree and X-DRI CVS trees (downloading the 90MB or whatever per
X release just isn't going to happen
Ok,
So this represents my most significant effort to date to fix something
in C. It took me far too long to identify where the one line fix needed
to go and even longer to figure out how to do it in C.
Here's the problem that this fixes:
When using pkg_add -r to add multiple packages
(i.e.
On Fri, Sep 07, 2001 at 03:04:16PM -0700, Bill Swingle wrote:
- strlcpy(packagesite, , sizeof(packagesite));
Chris Costello recommended that I do this like this instead:
packagesite[0] = '\0'
Which seems to make sense since it lacks the overhead of strlcpy. Is
there a right way to
If memory serves me right, Bill Swingle wrote:
Chris Costello recommended that I do this like this instead:
packagesite[0] =3D '\0'
Which seems to make sense since it lacks the overhead of strlcpy. Is
there a right way to do this?
Although I haven't seen the context for this line (other
On Friday, September 07, 2001, Leo Bicknell wrote:
I think Chris's version is right, although if you're writing a
security app, or just want to be overly paranoid in general
you could use:
bzero((void *)packagesite, sizeof(packagesite));
That's unnecessary unless you know you're going
On Fri, Sep 07, 2001 at 05:46:26PM -0500, Chris Costello wrote:
bzero((void *)packagesite, sizeof(packagesite));
That's unnecessary unless you know you're going to be reading
data from that string starting somewhere other than
packagesite[0];. And the `void *' cast is unnecessary, as
On Fri, Sep 07, 2001 at 03:04:16PM -0700, Bill Swingle wrote:
So this represents my most significant effort to date to fix something
in C. It took me far too long to identify where the one line fix needed
to go and even longer to figure out how to do it in C.
Here's the problem that this
On Fri, Sep 07, 2001 at 01:54:06PM -0700, Eric Anholt wrote:
I'm working on making it so we can have an official port of the DRI -- you'll
install the XFree86-4.x port (which would install X, the dri modules, libGL,
libGLU, etc.), then go to graphics/drm-kmod and install that, and you'll be
On Fri, Sep 07, 2001 at 03:04:16PM -0700, Bill Swingle wrote:
Anyway, it's an easy fix but my real question is, is this the correct
way to destroy the value of a variable in C? Here's my patch:
--- src/usr.sbin/pkg_install/add/main.c Fri Sep 7 15:02:17 2001
+++
On Fri, Sep 07, 2001 at 04:22:43PM -0700, David O'Brien wrote:
This was introduced in rev 1.38:
and replace a big if..then..else construct
to determine the package download directory with a lookup table.
I am very tempted to back this part out. This better implimentation
has
In message [EMAIL PROTECTED], Chris Costello writes:
On Tuesday, September 04, 2001, Maxim Sobolev wrote:
Content-Description: ASCII C program text
Index: coda/coda.h
===
RCS file: /home/ncvs/src/sys/coda/coda.h,v
retrieving
On Saturday, September 08, 2001, Poul-Henning Kamp wrote:
No actually not, I want something short and predictable like
VT_CODA.
How about my second suggestion: making v_tag point to
mp-mnt_stat.f_fstypename, or a copy thereof?
--
On Tuesday, September 04, 2001, Maxim Sobolev wrote:
Content-Description: ASCII C program text
Index: coda/coda.h
===
RCS file: /home/ncvs/src/sys/coda/coda.h,v
retrieving revision 1.9
diff -d -u -r1.9 coda.h
--- coda/coda.h
On Friday, September 07, 2001, Chris Costello wrote:
But is it necessary that you really use those defines? The
idea is not to use them globally. Perhaps getnewvnode() should
get the string from `mp-mnt_stat.f_mntfromname', instead...
^
Vladimir A. Jakovenko wrote:
Terry, I clearly understand all your explanations. Yes, we are living in
real life and there is a lot of programms with bad design.
But all what I want is possibility to receive UDP packets with
corresponding dst IP and port by more than one process on a single
On Mon, Sep 03, 2001 at 11:48:02PM -0700, Terry Lambert wrote:
Vladimir A. Jakovenko wrote:
Hello!
According to UNPv1 SO_REUSEPORT on UDP sockets can be used to bind more than
one socket to the same port (even with same source ip address). But quick
look on /sys/netinet/udp_usrreq.c
35 matches
Mail list logo
