Permissions on /root directory and /etc/mtree/BSD.root.dist
Hi All, I have one idea about permissions on /root directory and permissions on /root directory specified in the /etc/mtree/BSD.root.dist file. After finishing FreeBSD installating process permissions on /root directory are equal to 0755. Some administrators don't like these permissions for home dir of root and changed them to 0700, or to 0750, or to any other permissions. 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 mtree, which changes /root permissions to default value specified in the /etc/mtree/BSD.root.dist file. So, if administrator will not forgot about needed permissions on /root, then installworld will open /root directory for reading for everybody. I propose not to change permissions on /root directory in the /etc/mtree/BSD.root.dist file and leave them unchanged. Comments? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
undocumented wall(1) feature
Does anyone object to this?
Kris
Index: wall.c
===
RCS file: /mnt/ncvs/src/usr.bin/wall/wall.c,v
retrieving revision 1.19
diff -u -r1.19 wall.c
--- wall.c 2001/05/08 11:11:42 1.19
+++ wall.c 2001/09/06 10:06:06
@@ -71,8 +71,6 @@
static void usage(void);
char *ttymsg(struct iovec *, int, const char *, int);
-#defineIGNOREUSER sleeper
-
struct wallgroup {
struct wallgroup *next;
char*name;
@@ -140,8 +138,7 @@
iov.iov_len = mbufsize;
/* NOSTRICT */
while (fread((char *)utmp, sizeof(utmp), 1, fp) == 1) {
- if (!utmp.ut_name[0] ||
- !strncmp(utmp.ut_name, IGNOREUSER, sizeof(utmp.ut_name)))
+ if (!utmp.ut_name[0])
continue;
if (grouplist) {
strlcpy(username, utmp.ut_name, sizeof(utmp.ut_name));
PGP signature
Re: local changes to CVS tree
Also sprach Bernd Walter ([EMAIL PROTECTED]): How do people fix stuff in their local CVS tree and sync other FreeBSD changes with that? It's a CVSup FAQ: http://www.polstra.com/projects/freeware/CVSup/faq.html#canilocal Great, thanks. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
corrupted 'w' output
Hello, I updated from -current yesterday, ran make world; make kernel KERNCONF=X and went to bed. When I rebooted with fresh kernel this morning, I noticed something strange: vel@bugz:/usr/src # w 3:47PM up 5:38, 4 users, load averages: 0.00, 0.11, 0.08 USER TTY FROM LOGIN@ IDLE WHAT vel p0 kg.infotecs.ru 10:11AM 2 ssh -l vel bsx.ru vel p1 kg.infotecs.ru 10:22AM - w vel p2 kg.infotecs.ru 12:13PM 1:55 \M-[\M-!\^D\b (tcsh) vel p3 kg.infotecs.ru 12:53PM 2 \M-[\M-!\^D\b (tcsh) This only happens for terminals that are in a shell, when something else is running, output isn't corrupted. I think someone reported similar problem with 'ps' output. Regards, Eugene To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: undocumented wall(1) feature
On Thu, Sep 06, 2001 at 03:06:57AM -0700, Kris Kennaway wrote:
Does anyone object to this?
Just a bit of history. This has been added with this CSRG
commit:
: D 4.5 81/06/12 13:23:15 root 5 43/1/00129
: MRs:
: COMMENTS:
: I suppressed wall messages to the sleeper program
Not sure what does it mean. Perhaps, at that times,
the sleeper existed as a user process and was run
under the sleeper user.
Index: wall.c
===
RCS file: /mnt/ncvs/src/usr.bin/wall/wall.c,v
retrieving revision 1.19
diff -u -r1.19 wall.c
--- wall.c2001/05/08 11:11:42 1.19
+++ wall.c2001/09/06 10:06:06
@@ -71,8 +71,6 @@
static void usage(void);
char *ttymsg(struct iovec *, int, const char *, int);
-#define IGNOREUSER sleeper
-
struct wallgroup {
struct wallgroup *next;
char*name;
@@ -140,8 +138,7 @@
iov.iov_len = mbufsize;
/* NOSTRICT */
while (fread((char *)utmp, sizeof(utmp), 1, fp) == 1) {
- if (!utmp.ut_name[0] ||
- !strncmp(utmp.ut_name, IGNOREUSER, sizeof(utmp.ut_name)))
+ if (!utmp.ut_name[0])
continue;
if (grouplist) {
strlcpy(username, utmp.ut_name, sizeof(utmp.ut_name));
--
Ruslan Ermilov Oracle Developer/DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
RE: post 2.95.3 patches to test
All my previous test cases which used to break without sjlj patches are working with this patch correctly. I guess you might my results to your list of successes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Help with 3ware 3dm utility?????
Mike or anyone, I am having some difficulties getting 3dm for the 3ware escalade IDE raid card to work on FreeBSD 4.1 or 4.2 I am getting the following errors: twe0: command failed-aborted due to system command or reconfiguration twe0: TWETO_GET_PARAM failed for 0x40610x216 I can see that /dev/twe0 and /dev/twed0 exist when I look in the /dev directory. When I execute ps -auxw | grep 3dmd, I am getting mulitple 3dmd process spawning. root 259 0.0 0.3 620 412 p0 I 6:16PM 0:00.00 ./3dmd root 260 0.0 0.3 620 412 p0 I 6:16PM 0:00.03 ./3dmd root 261 0.0 0.4 636 436 p0 S 6:16PM 0:00.04 ./3dmd I'm not sure if I'm on the latest firmware version. If I'm not, how do I install the latest firmware version on to the card. FYI:(dmesg | grep twe0) twe0: 3ware Storage Controller port 0xefa0-0xefaf irq 11 at device 17.0 on pci0 twe0: 4 ports, Firmware FE6X 1.01.18.001, BIOS BEXX 1.06.00.001 twed0: TwinStor, Normal on twe0 Any tips or suggestions will be most grateful. Thanks, Steele.. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
DRI, XFree86-4.0.3 and -current.
Has anyone got patches for DRI under -current? Joe PGP signature
Re: proposed change to pci_pci.c
On Wed, Sep 05, 2001 at 06:37:28PM -0700, Mike Smith wrote: I'd be OK with this being done as a hack for now. I think the bridge code needs to be a bit kinder about allowing stupid things to be done if they're set up by the BIOS. I'd like to propose committing the following change which adds a new undocumented option in the spirit of PCI_ENABLE_IO_MODES. The new option (PCI_ALLOW_UNSUPPORTED_IO_RANGE) allows me to boot my old HP Omnibook 4150 while docked. Since I've seen a couple other people need this fix, I figure it would be more useful if they just had to add a line to their kernel config instead of editing the source files. Any objections? The pci_pci code actually needs some other changes done. Note the comment at line 267, If this is a 'default' allocation against this rid, we can't work out where it's coming from (we should actually never see these) so we just have to punt. The we should actually never see these part is not quite correct, since NEWCARD uses default allocation to automagically get an unused range from the pci bus. Then we have to tweak the window for the pcipci bridge to forward the new addresses if the window wasn't big enough. Not to mention, we still need to implement a way to request bus numbers properly... Bleah, hardware sucks. Give me a virtual machine. -Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: POSIX compatibility issue
I imagine Garrett and other standards-minded people have already seen this question, but I thought I'd echo it to the freebsd-standards mailing list. It's about a PR which makes a minor change to sys/types.h to solve some compile-time errors so that a program compiled with -D_POSIX_SOURCE currently gets if it references sys/socket.h. Seems like a plausible change to me, but I don't know enough about POSIX details to really know... At 11:22 PM -0700 9/5/01, Arun Sharma wrote: Can someone take a look at this PR ? http://www.freebsd.org/cgi/query-pr.cgi?pr=30317 It's necessary to fix compilation issues for a POSIX compliant Java VM, that uses sockets. There are similar open bug reports against NetBSD too, without any comments on why this change can not be made. -Arun -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: corrupted 'w' output
[Moved to -current, BCC'd to -hackers] Eugene L. Vorokov [EMAIL PROTECTED] writes: Hello, I updated from -current yesterday, ran make world; make kernel KERNCONF=X and went to bed. When I rebooted with fresh kernel this morning, I noticed something strange: vel@bugz:/usr/src # w 3:47PM up 5:38, 4 users, load averages: 0.00, 0.11, 0.08 USER TTY FROM LOGIN@ IDLE WHAT vel p0 kg.infotecs.ru 10:11AM 2 ssh -l vel bsx.ru vel p1 kg.infotecs.ru 10:22AM - w vel p2 kg.infotecs.ru 12:13PM 1:55 \M-[\M-!\^D\b (tcsh) vel p3 kg.infotecs.ru 12:53PM 2 \M-[\M-!\^D\b (tcsh) This only happens for terminals that are in a shell, when something else is running, output isn't corrupted. I think someone reported similar problem with 'ps' output. Regards, Eugene Those shell argv[0]'s are generated by login(1). I wonder if it was a recent commit to src/usr.bin/login/login.c that is causing it. Can you try locally backing out Rev. 1.68 (and Rev 1.36 of Makefile)? You will ofcourse have to relogin to see whether the w(1) output has changed. BTW, I can't reproduce this problem locally. Is there any special about your local configuration, particularly regarding PAM? Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Any plans to integrate gcc 3.0.1 ?
Fellow hackers Are there any plans to upgrade GCC to 3.0.1 in the near future ? Has anybody built the world with the GCC 3.0.1 ? If not, I might give it a try. I built the most recent version from the ports. Ciao, derweil, -- Carlo PS: I am asking this because I am not able to successfully bootstrap GNU Smalltalk with the JIT enabled, due to a GCC bug. I hope to be more successfull with the 'new' GCC. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: DRI, XFree86-4.0.3 and -current.
I have a page about the DRI for FreeBSD at http://gladstone.uoregon.edu/~eanholt/dri/. The current DRI CVS works on -stable. There is one compile error on -current that should be obvious to fix in the kernel modules, but I haven't uploaded patches as I haven't actually tested it yet (I'm still setting up my new -current installation). On Thursday 06 September 2001 10:57, Josef Karthauser wrote: Has anyone got patches for DRI under -current? Joe -- Eric Anholt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Permissions on /root directory and /etc/mtree/BSD.root.dist
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 mtree, which changes /root permissions to default value specified in the /etc/mtree/BSD.root.dist file. So, if administrator will not forgot about needed permissions on /root, then installworld will open /root directory for reading for everybody. I propose not to change permissions on /root directory in the /etc/mtree/BSD.root.dist file and leave them unchanged. Comments? There is a whole class of problems like this. For example, my installation of mutt doesn't work right if /var/mail is not mode 1777, but BSD.var.dist changes it to 755 every time I installworld. I think a more general solution might be in order. Perhaps some sort of local.dist that is processed after BSD.*.dist. As a workaround, I put chmod 1777 /var/mail in my rc.local script. I suggest you do something similar. -- Ben An art scene of delight I created this to be ... -- Sun Ra To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Posix Threading
John Baldwin wrote: If the intent is to have a pool of idle threads, ready to go when you get request traffic, and get around the latency, well, you'd do a lot better in the latency department if you went to a finite state automaton, instead of messing with threads. But if you insist, the best you are going to be able to get is use of a mutex, since a condition variable will result in a thundering herd problem. You will still have to eat the latency for the mutex trigger to the thread you give the work to, however (this is how I designed the work-to-do dispatcher in the Pathworks for VMS (NetWare) product for DEC and Novell). Most of what you say is ok, but this is wrong. condition variables do not mandate using a wakeup all strategy. There is such a thing as 'signal' instead of 'broadcast', which only wakes up one thread. My concern over recommending this would be that it is very implementation dependent as to which thread gets woken up. In Linux, it could result in a full context switch for it to be implemented by the threads system. Also I remembered something about a problem with the implementation from Draft 2, and as I said previously, I had no idea of the compliance level (this is from an experience with adapting the threads in the Standard Template Library, as distributed by the Moscow Supercomputing Center, to so correct static mutex initialization). In FreeBSD, you're certainly right, though it will maybe end up having the full context switch overhead (or even CPU selection overhead) once kernel threading via KSE is the norm (but in FreeBSD's implementation, you might be able to argue the same thing about mutex based triggers, if implemented such that the context is not passed off instead -- except that he wanted initial hibernation, and I don't think you could guarantee that with a mutex). FWIW, my implementation in VMS was based on DEC's MTS, which was a BLISS-based call conversion threading package, which I had to extend to have timers, and also had to add all the necessary synchorinization primitives. The basic implementation was made using ASTs with SYS$WAITEFLOR -- wait-event-flag-OR -- very similar to condition variables. The new condition variable primitive wasn't enough to give a guarantee the necessary semantics for the application (a port of Mentat Streams to VMS, in support of the SPX and IPX stacks used by NetWare), and I had to build real Mutex support on top of the primitives to get the packet MUX to do the correct thing. Anyway, there was really not enough information in his request, or my potentially outdated knowledge of pthreads on HP-UX for me to recommend condition variables with the wake one semantics. But again, your point is 100% valid for the FreeBSD release version out there, and I *DID* recommend that he switch his application to FreeBSD. ;-). PS: BLISS is ignorance... Regards, -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: DRI, XFree86-4.0.3 and -current.
On Thu, Sep 06, 2001 at 12:16:19PM -0700, Eric Anholt wrote: I have a page about the DRI for FreeBSD at http://gladstone.uoregon.edu/~eanholt/dri/. The current DRI CVS works on -stable. There is one compile error on -current that should be obvious to fix in the kernel modules, but I haven't uploaded patches as I haven't actually tested it yet (I'm still setting up my new -current installation). I had a look at that, but it wasn't too clear what I needed to do. I suspect that I'm expecting to checkout the DRI tree _over_ the top of the XFree86-4 tree but perhaps I don't need to do that. Additionally I'm using devfs on -current and I suspect that the r128.ko module doesn't DTRT WRTT. Joe PGP signature
Re: auto relaying for subdomains -- why?
Igor Podlesny wrote: Yes, I saw this info here: http://www.sendmail.org/m4/features.html#relay_mail_frombut most valuable part of my question was about the purpose or the idea behind this, cause it's not too clear to me why allowing relaying for domain FOO.BAR should allow relaying for SUB.FOO.BAR? I mentioned RFCs because I had a hope to find out the answer from it but still haven't yet... [EMAIL PROTECTED] [EMAIL PROTECTED] Whose account name at your customer's site are you going to intentionally render unintelligble, and force them to change their business cards and stationary? Alternately, why wouldn't they just say screw you, and set their masquerade features to make all the machines lie and say they were sending from the domain? What are you trying to accomplish by prohibiting some machines legitimately in a delegated subdomain (for which account and other authority has been vested in someone other than the main site administrator, such as a departmental administrator) from sending legitimate email? Why do you want them to have to jump through hoops in order to be able to send email which they will ultimately jump through the hoops -- and send through your relay anyway? What possible legitimate purpose is serves by letting [EMAIL PROTECTED] send email, but prohibiting [EMAIL PROTECTED] from sending mail? I suspect that you are more concerned with having only a single MAIL_HUB relaying email through you, rather than actually prohibiting people from using delegated subdomains. If so, then your problem is because you are trying to use the wrong tool to accomplish your task: do not use domain naming to try to control relaying, or people will simply spoof their source addresses, and relay an incredible amount of SPAM through your mail relays, since they will leak like a sieve. Also note: even if you prohibit outbound, you _can't_ do the same for inbound, without prohibiting delegation of subdomains. This would be like me insisting that you not use the email address [EMAIL PROTECTED], because at the top level, I will only allow relaying for poige@ru, since morning.ru is a delegation from ru. In other words, if you are trying to solve a problem, tell us the problem, don't ask us how to implement your proposed answer to a secret problem you won't share with us. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
KSE: mount_msdosfs works again !!
Dear KSE guinnea-pigsters The msdos partition mounts again under a KSE kernel. I applied the diff file straight from Julian's home page, dated -rw-r--r-- 1 carloother 2532518 Sep 6 18:14 thediff and its md5 check sum being. MD5 (thediff) = 867c031f8b3d4278c8bb58db03e020ab As usual, ccd, ncp and smbfs did not compile, but I don't use them. Interestingly, the newly build kernel detects my xl NIC, but the 'normal' kernel does not *shrug*. My next step is to build a KSE kernel with gcc 3.0.1; I know what You are going to say now: why increase complexity ? Don't worry, I won't post any damage detection based on unsing the new gcc. I am simply curious. Ciao, derweil, -- Carlo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: auto relaying for subdomains -- why?
Igor Podlesny wrote: Now it's all clear :) and I understand that it was just a way SENDMAIL's is configured. Another question could be why not to use syntax .foo.bar instead of foo.bar but I'm quite ready to call it a rhetorical one ;-)) (regexps are also there ;-) The virtusertable file syntax is such that: foo.bar predicate means relay for foo.bar, but not *.foo.bar, and: .foo.barpredicate means relay for *.foo.bar, but not foo.bar, and: foo.bar predicate .foo.barpredicate means relay for both foo.bar and *.foo.bar. The value of predicate depends on what you want to do with the email, and it is usually a tuple consisting of a mailer and a disposition suffix for that mailer, e.g.: foo.bar local:bob .foo.barsmtp:[EMAIL PROTECTED] means send all mail with an address in foo.bar to the POP3 mailbox on the local machine for the local user ``bob'', and send all mail for any delegates subdomains of foo.bar to the user ``tom'' with a mail account at another ISP named ``isp.com''. If you need to get this complicated, I suggest you read the sendmail FAQ, or buy a copy of the O'Reilly Sendmail book. P.P.S. I'm not quite sure should I start new thread or can remain within it with another question which is: What MTA software supports highly configurable relaying... One of the needed features is a support for using alternative mail routers (relays) in case when this MTA can't send a message by itself because of networks problem. Sendmail... this is handled by the SMART_HOST feature of sendmail. For example situation could be: MTA is on a network A which is temporarily cut off from it's uplink so it can't transfer mail by itself, but it has a connection (permanent or dial-up) to another mailer. Mail routing is via DNS. If you are on the other side of a dialup, you should mark the mailer expensive, set HoldExpensive to True, and then explicitly do the queue run in your link-up script, or, if you prefer, at intervals. Generally, what you want to do is a bad idea, since the best way to handle this if you have an unreliable permanent connection, is to simply use your other connection to contact the same list of MX's that it would have contacted anyway. Are there such MTAs which can be said if you can't send it by yourself (would be cool if additional parameters were some_time_period and failure_reason) then use that MTA (ip-addr) or that (another-ip)?. By IP address is a bad idea, though it could be done. I suspect in common case such system could easily lead to loops and have other drawbacks but in such simple configuration it seems all should work fine... Not really. But it will take you some amount of time to configure this correctly, and to get your back end infrastructure in place. I did this work for IBM Web Connections, and it took us 3 months to do the back end stuff, and 8 months to do all the client side stuff, so that it was all turn key. Basically, you are asking for a huge technology transfer, which generally runs most ISPs several hundreds of thousands of dollars to acquire. With the questions you are asking, you will probably need to buy or license it from someone. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: undocumented wall(1) feature
On Thu, Sep 06, 2001 at 04:08:54PM +0300, Ruslan Ermilov wrote: On Thu, Sep 06, 2001 at 03:06:57AM -0700, Kris Kennaway wrote: Does anyone object to this? Just a bit of history. This has been added with this CSRG commit: : D 4.5 81/06/12 13:23:15 root 5 43/1/00129 : MRs: : COMMENTS: : I suppressed wall messages to the sleeper program Not sure what does it mean. Perhaps, at that times, the sleeper existed as a user process and was run under the sleeper user. Bizarre :) Kris PGP signature
Re: DRI, XFree86-4.0.3 and -current.
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 dri.sourceforge.net. By the way no it doesn't work with devfs. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: KSE: mount_msdosfs works again !!
probably better in -current than hackers :-) hmm I can't think of a change that would have done that... I gotta get to smbfs and nwfs... On Thu, 6 Sep 2001, Carlo Dapor wrote: Dear KSE guinnea-pigsters The msdos partition mounts again under a KSE kernel. I applied the diff file straight from Julian's home page, dated -rw-r--r-- 1 carloother 2532518 Sep 6 18:14 thediff and its md5 check sum being. MD5 (thediff) = 867c031f8b3d4278c8bb58db03e020ab As usual, ccd, ncp and smbfs did not compile, but I don't use them. Interestingly, the newly build kernel detects my xl NIC, but the 'normal' kernel does not *shrug*. My next step is to build a KSE kernel with gcc 3.0.1; I know what You are going to say now: why increase complexity ? Don't worry, I won't post any damage detection based on unsing the new gcc. I am simply curious. Ciao, derweil, thanks for testing.. -- Carlo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
OT: firewire slugs available ?
In the near future I will be doing some research and development with IEEE 1394. Such that I will be requiring a _large_ number of firewire devices. It is not within my budget to purchase 63 x 4 cameras. So I was trying to think of the cheapest possible IEEE 1394 device - if worst comes to worse I could just buy 252 of those ... again, not very practicle. IEEE 1394 chipsets, however, are about $8.00 each. Has anyone seen IEEE 1394 slugs - devices that perform basic functionality (in terms of participating on the bus) but not much else ? (presumably, if these devices exist, they were developed for just this type of development) Comments and information appreciated. - John Kozubik - [EMAIL PROTECTED] - http://www.kozubik.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
NFS read cache and fcntl locking
Hi! I wonder how can userlevel process turn NFS-client's read cache off: Turn off attribute caching? Use fcntl lock triggering to invalidate the cache? Other way? Bye! P.S: The ac(reg|dir)(min|max) options of mount_nfs are not taking effect right now due to 4 missing lines in mount_nfs.c. I filled PR bin/30334 with a fix, so please somebody brave enough, take a look... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: DRI, XFree86-4.0.3 and -current.
On Thu, Sep 06, 2001 at 12:16:19PM -0700, Eric Anholt wrote: I have a page about the DRI for FreeBSD at http://gladstone.uoregon.edu/~eanholt/dri/. The current DRI CVS works on -stable. There is one compile error on -current that should be obvious to fix in the kernel modules, but I haven't uploaded patches as I haven't actually tested it yet (I'm still setting up my new -current installation). I'll test it for you with my AGP MOBILE M3 if you send me the bits and tell me where to install them ;). Joe PGP signature
