Re: making /usr/share/mk apps PREFIX-independant???
On Fri, 21 Dec 2001 09:30:30 +0200, Ruslan Ermilov wrote:
I'm against PREFIX in share/mk files. Instead, just setting
DESTDIR=${PREFIX} should (almost) be enough.
I agree. See ports/mail/popd/Makefile for an example of a port that
uses a pure bsd.prog.mk-driven Makefile for ${PREFIX}-sensitive
installation.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
RE: tx driver problem.
Try doubling maxusers. Its easy, and it might make a difference. Done - but got no reasonable result :-( after or while the problem is happening, try a 'netstat -m' It's quite long-lasting (this state takes several minutes till cvs co finishes - though it should be done in say 20 seconds under normal conditions). So during the state it looks like this (after doubling maxusers): bash-2.05# netstat -m 18/32/6144 mbufs in use (current/peak/max): 17 mbufs allocated to data 1 mbufs allocated to packet headers 16/28/1536 mbuf clusters in use (current/peak/max) 64 Kbytes allocated to network (1% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Petr Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 2 Institute of Compt. Science 10200 Praha, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: [EMAIL PROTECTED] phone: +420-5-41512278 e-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: making /usr/share/mk apps PREFIX-independant???
On Fri, Dec 21, 2001 at 10:49:13AM +0200, Sheldon Hearn wrote:
On Fri, 21 Dec 2001 09:30:30 +0200, Ruslan Ermilov wrote:
I'm against PREFIX in share/mk files. Instead, just setting
DESTDIR=${PREFIX} should (almost) be enough.
I agree. See ports/mail/popd/Makefile for an example of a port that
uses a pure bsd.prog.mk-driven Makefile for ${PREFIX}-sensitive
installation.
Doesn't it strike anyone as being a bit, well, icky, that we have to do
this for software developed on this platform, using this platform's
standard infrastructure for defining Makefiles?
Perhaps just a USES_BSD_MK=yes flag to wrap this for other ports as
well (I'm thinking specifically of the scr* stuff I wrote, but there may
be others).
N
--
FreeBSD: The Power to Serve http://www.freebsd.org/
FreeBSD Documentation Project http://www.freebsd.org/docproj/
--- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 ---
msg30350/pgp0.pgp
Description: PGP signature
Re: making /usr/share/mk apps PREFIX-independant???
On Fri, 21 Dec 2001 10:06:58 GMT, Nik Clayton wrote: Perhaps just a USES_BSD_MK=yes flag to wrap this for other ports as well (I'm thinking specifically of the scr* stuff I wrote, but there may be others). That sounds like a good idea. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Another filesystem test program
On Thu, Dec 20, 2001 at 11:40:22PM -0800, Hiten Pandya wrote: src/tools/regression :) Jordan committed fsx there a day or so ago. can it be used for any type of filesystem? I was wondering if it would be useful for the JFS port I am doing. Download it, and take a look at the source Hiten. I'm sure that you'll see ways that it can be adapted. Joe msg30352/pgp0.pgp Description: PGP signature
Re: Another filesystem test program
: http://apollo.backplane.com/FreeBSD/fsstress-1.00.tgz : : ports/regression ? : : This would be really nifty, it could be a depot for various test : programs, unless of course we want it to be in src/ ? : :src/tools/regression :) Jordan committed fsx there a day or so ago. : :-- : :John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ I'll throw it in there tomorrow. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: making /usr/share/mk apps PREFIX-independant???
On Fri, Dec 21, 2001 at 10:06:58AM +, Nik Clayton wrote:
On Fri, Dec 21, 2001 at 10:49:13AM +0200, Sheldon Hearn wrote:
On Fri, 21 Dec 2001 09:30:30 +0200, Ruslan Ermilov wrote:
I'm against PREFIX in share/mk files. Instead, just setting
DESTDIR=${PREFIX} should (almost) be enough.
I agree. See ports/mail/popd/Makefile for an example of a port that
uses a pure bsd.prog.mk-driven Makefile for ${PREFIX}-sensitive
installation.
Doesn't it strike anyone as being a bit, well, icky, that we have to do
this for software developed on this platform, using this platform's
standard infrastructure for defining Makefiles?
Perhaps just a USES_BSD_MK=yes flag to wrap this for other ports as
well (I'm thinking specifically of the scr* stuff I wrote, but there may
be others).
You don't listen. :-)
Just adding PREFIX won't solve anything, as you still need to supply the
correct BINDIR (which is, for the main src/ tree makefiles, initialized
by the root Makefile.inc in each subtree), and provide the correct MANDIR,
LIBDIR, etc.
In the port I maintain (ports/net/tcpmssd), the main program's Makefile
looks like this:
: PROG= tcpmssd
: PREFIX?=/usr/local
: BINDIR= ${PREFIX}/bin
: MAN8= tcpmssd.8
: MANDIR= ${PREFIX}/man/man
:
: .include bsd.prog.mk
If you modify it to look like this (that's the goal?):
: PROG= tcpmssd
: MAN8= tcpmssd.8
:
: .include bsd.prog.mk
You still need to supply BINDIR and MANDIR somehow.
The following worked for my port flawlessly, but it's a
prototype only, and the complete version should cover all
bsd.own.mk defines:
--- bsd.port.mk~Wed Nov 28 07:00:36 2001
+++ bsd.port.mk Fri Dec 21 12:58:53 2001
@@ -1158,6 +1158,10 @@
MAKE_ENV+= ${INSTALL_MACROS}
SCRIPTS_ENV+= ${INSTALL_MACROS}
+.if defined(USE_BSD_MAKE)
+MAKE_ENV+= BINDIR=${PREFIX}/bin MANDIR=${PREFIX}/man/man
+.endif
+
# The user can override the NO_PACKAGE by specifying this from
# the make command line
.if defined(FORCE_PACKAGE)
This should work for both /usr/local and /usr/X11R6 prefixes.
I don't pretend that this solution is ideal, as a port may
need different BINDIR settings for its different parts. I
have given a little thinking to this, just to demonstrate
that the fixes should go into ports/Mk, not into the base
.mk files.
Cheers,
--
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: making /usr/share/mk apps PREFIX-independant???
On Fri, Dec 21, 2001 at 01:16:41PM +0200, Ruslan Ermilov wrote: You don't listen. :-) snip I don't pretend that this solution is ideal, as a port may need different BINDIR settings for its different parts. I have given a little thinking to this, just to demonstrate that the fixes should go into ports/Mk, not into the base .mk files. That's what I meant. We're in violent agreement :-) N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- msg30355/pgp0.pgp Description: PGP signature
how to mirror gnats db?
hi all, I wanted to ask, how I could mirror the gnats database to my own system. I have cvsup. I am very sorry if this is the wrong list to ask this question. thanks, regards, =Hiten =[EMAIL PROTECTED] = SSH Fingerprint: 1024 45:a5:9c:f2:fb:07:da:70:18:02:0b:f3:63:f1:7a:a6 [EMAIL PROTECTED] __ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sk_buff on FreeBSD
On Thursday 20 December 2001 23:31, Pedro F. Giffuni wrote: I have started proting some network protocols (ax.25 for ham) from linux,... Hmm..I recall we had code for that but it was removed ages ago (in the 2.x era). I suggest you look for the relevant code in NetBSD. The linux code has 0 change of getting committed to FreeBSD due to the GPL poison pill. Pedro. Follow up to my last message. Try taking a look at ftp://ftp.ucsd.edu/hamradio/packet/tcpip/bsd/ There are a couple of programs you could start with real easy. Also check out the sun directory. GB -- GB Clark II | Roaming FreeBSD Admin [EMAIL PROTECTED] | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sk_buff on FreeBSD
On Thursday 20 December 2001 23:31, Pedro F. Giffuni wrote: I have started proting some network protocols (ax.25 for ham) from linux,... Hmm..I recall we had code for that but it was removed ages ago (in the 2.x era). I suggest you look for the relevant code in NetBSD. The linux code has 0 change of getting committed to FreeBSD due to the GPL poison pill. Pedro. Hi, You might look into modifing the userland PPP to do ax.25 instead. There is plenty of non-GPL code out there showing how to do ax.25. GB -- GB Clark II - N5VMF| Roaming FreeBSD Admin [EMAIL PROTECTED] | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: how to mirror gnats db?
On Fri, Dec 21, 2001 at 04:54:43AM -0800, Hiten Pandya wrote: hi all, I wanted to ask, how I could mirror the gnats database to my own system. I have cvsup. /usr/share/examples/cvsup/gnats-supfile -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sk_buff on FreeBSD
On Friday 21 December 2001 01:06 am, GB Clark II wrote: On Thursday 20 December 2001 23:31, Pedro F. Giffuni wrote: I have started proting some network protocols (ax.25 for ham) from linux,... Hmm..I recall we had code for that but it was removed ages ago (in the 2.x era). I suggest you look for the relevant code in NetBSD. The linux code has 0 change of getting committed to FreeBSD due to the GPL poison pill. Pedro. Hi, You might look into modifing the userland PPP to do ax.25 instead. There is plenty of non-GPL code out there showing how to do ax.25. GB I've been using Phil Karnes' 'net' stuff for about 10 years now. It is the predecessor to the JNOS and TNOS code. It does ax25, net/rom and IP over a tnc with a kiss rom and runs in userland. I also hacked it to run with a BBS using IPC. The code is unencumbered and if you're interested, I'll put it out for download. I haven't compiled it since 2.x days, and I think it may need some tweeking to compile on 4.x. (I seem to recall getting some error messages the last time I tried). The BBS is available also. If you want it, I'll have to get it together to make a tarball. -Jim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
firewire driver
Hi all! I've patched the fwohci driver from the DVTS suite (http://www.sfc.wide.ad.jp/DVTS/) to do the memory allocation for the card on it's own in the case BIOS is too lazy to do it (my case). Patch is in the attachement. I'd like to thank Warner Losh for his help with this problem and for his PCCBB code in the -CURRENT. My patch runs for me on FreeBSD 4.4. So if somebody is interested, here you are... With best regards and best wishes for the year 2002, Petr Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 2 Institute of Compt. Science 10200 Praha, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: [EMAIL PROTECTED] phone: +420-5-41512278 e-mail: [EMAIL PROTECTED] fwohci.diff Description: Binary data
Re: userland program panics freebsd 4.3
- Original Message - From: Paul Halliday [EMAIL PROTECTED] To: Kris Kennaway [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 20, 2001 10:08 PM Subject: Re: userland program panics freebsd 4.3 On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: I'm not aware of any services that broke between 4.3 and 4.4. Care to elaborate? scan through freebsd-questions, freebsd-mobile and freebsd-ports That's completely non-helpful. I read -questions and -ports, and don't recall complaints of massive breakage in 4.4. Perhaps you'd care to be more specific so we can actually address the problems, if they exist? Because there are dozens or even hundreds of kernel bugs fixed since 4.3, so there's a very good chance yours was one of them. I guess I forgot a couple of things: #1, this IS a free operating system and noone is being paid to fix my problems #2, you probably get a lot of 'its broke please fix it' posts to these newsgroups #3, when I am frustrated I get a little testy. I would like to thank those who have assisted me in trying to find this problem and fix it. Nick Hilliard for his original pointer to FBSD handbook and the dumpdev section. Matthew Dillon for his offer to look at the vmcore (I know someone asked for more information, but beyond the gdb kernel traces and the description of the hardware, I don't think posting a 256MB core here would be a good idea) I also forgot that those of you who do try to help fix problems might also get frustrated at the lack of information given during the initial posts. Sorry, I did the best I could. I described the hardware and the environment and thought I pointed to the section in the kernel that had the problem. I was hoping that the given environment would trigger some suggestions, other than going to a new version. I like FBSD, It is faster and easier to use than Linux (for my application). I like the ports section. It is very easy to use, easy to update, and it contains most of what I would need. FBSD has been very stable except for this one thing. I expect that eventually we will find why it is happening and find some small, obscure 'feature' in the os that is causing this. It will get fixed quickly and help future generations of FBSD users who aren't so lucky as to be able to reproduce the panic at will. Again, I thank those who helped, even those who I did not mention and when I find the problem, I will post the resolution. -- Michael Scheidell Secnap Network Security, LLC [EMAIL PROTECTED] 1+(561) 368-9561 See updated IT Security News at http://www.fdma.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Sale on Toner Cartridges!!
D J Printing Corporation 2564 Cochise Drive Acworth, GA 30102 770-974-8228 [EMAIL PROTECTED] --LASER, FAX AND COPIER PRINTER TONER CARTRIDGES-- *WE ACCEPT GOVERNMENT, SCHOOL AND UNIVERSITY PURCHASE ORDERS* **WE NOW CARRY HP4500/4550 COLOR LASERJET CARTRIDGES!!** ***FREE SHIPPING WITH ANY ORDER OF $200 OR MORE!!!*** APPLE LASER WRITER SELECT 300/310/360 $60 LASER WRITER PRO 600/630 OR 16/600$60 LASER WRITER 300/320 OR 4/600 $45 LASER WRITER LS/NT/NTR/SC $50 LASER WRITER 2NT/2NTX/2SC/2F/2G $50 LASER WRITER 12/640$60 HEWLETT PACKARD LASERJET SERIES 1200 (C7115A) $40 LASERJET SERIES 4100X/4100A (C8061A/X)$99 LASERJET SERIES 1100/1100A (C4092A) $40 LASERJET SERIES 2100/SE/XI/M/TN (C4096A) $70 LASERJET SERIES 2/2D/3/3D (92295A)$43 LASERJET SERIES 2P/2P+/3P (92275A)$55 LASERJET SERIES 3SI/4SI (92291A)$75 LASERJET SERIES 4/4M/4+/4M+/5/5M/5N (92298A/X)$55 LASERJET SERIES 4L/4ML/4P/4MP (92274A)$40 LASERJET SERIES 4000/T/N/TN (C4127A/X-H YLD) $70 LASERJET SERIES 4V/4MV (C3900A) $80 LASERJET SERIES 5000 (C4129X)$95 LASERJET SERIES 5L/6L (C3906A)$39 LASERJET SERIES 5P/5MP/6P/6MP (C3903A)$50 LASERJET SERIES 5SI/5SI MX/5SI MOPIER/8000(C3909A/X) $80 LASERJET SERIES 8100/N/DN ((C4182X) $100 HEWLETT PACKARD COLOR LASERJET COLOR LASERJET SERIES 4500/4550 BLACK (C4191A) $55 COLOR LASERJET SERIES 4500/4550 CYAN (C4192A) $85 COLOR LASERJET SERIES 4500/4550 MAGENTA (C4193A) $85 COLOR LASERJET SERIES 4500/4550 YELLOW (C4194A) $85 COLOR LASERJET SERIES 4500/4550 DRUM UNIT (C4195A) $55 HEWLETT PACKARD LASERFAX LASERFAX 500/700, FX1 $50 LASERFAX 5000/7000, FX2 $65 LASERFAX FX3 $60 LASERFAX FX4 $65 LEXMARK E312L, E310 (13T0101) $75 OPTRA 4019, 4029 HIGH YIELD $130 OPTRA R, 4039, 4049 HIGH YIELD$125 OPTRA S, 4059 HIGH YIELD $135 OPTRA N $100 EPSON LASER TONER EPL-7000/7500/8000$95 EPL-1000/1500 $95 EPSON INK JET STYLUS COLOR 440/640/740/760/860 (COLOR) $20 STYLUS COLOR 740/760/860 (BLACK) $20 CANON LBP-430 $45 LBP-460/465 $55 LBP-8 II $50 LBP-LX$54 LBP-NX$90 LBP-AX$49 LBP-EX$59 LBP-SX$49 LBP-BX$90 LBP-PX$49 LBP-WX$90 LBP-VX$59 CANON FAX L700 THRU L790 (FX1)$55 CANON FAX L5000 THRU L7500 (FX2) $65 CANON LASERCLASS 4000/4500/300 (FX3) $60 CANON LASERCLASS 8500 THRU 9800 (FX4) $65 CANON COPIERS PC 1/2/3/6/6RE/7/8/11/12/65 (A30) $69 PC 210 THRU 780 (E40/E31) $80 PC 300/400 (E20/E16) $80 NEC SERIES 2 LASER MODEL 90/95$100 SUPERSCRIPT 860 $115 ***FREE SHIPPING WITH ANY ORDER OF $200 OR MORE!!!*** PLEASE NOTE: * ALL OF OUR PRICES ARE IN US DOLLARS * WE SHIP UPS GROUND. ADD $6.50 FOR SHIPPING AND HANDLING * WE ACCEPT ALL MAJOR CREDIT CARDS OR COD ORDERS. * COD CHECK ORDERS ADD $3.50 TO YOUR SHIPPING COST. * OUR STANDARD MERCHANDISE REPLACEMENT POLICY IS NET 90 DAYS. * WE DO NOT SELL TO RESELLERS OR BUY FROM DISTRIBUTERS. * WE DO NOT CARRY: BROTHER, MINOLTA, KYOSERA, PANASONIC, XEROX, FUJITSU,
RE: tx driver
Hi! Sorry, for late intervention... Your dmesg shows that this is SMC9432TX_1 card, and I've never hold such one in heands :( Though I saw the SMC9432FTX, and it use the same PHY. So: 1) ``pciconf -l'' and ``ifconfig tx0'' output, please 2) Could you upgrade to 4.4 or later? There were few changes. Particullary, the true AC101 PHY support. You may try to fetch miibus.ko and if_tx.ko binaries from 4.4 system, if you don't want to upgrade whole system. I hope it will work. 3) Can you look at the card's and switch's leds when you have the performance problems? The main question is if the card loose the link or there is really no problems with the link? 4) Does ifconfig output about media selected conforms the leds and reality? Bye! On Thu, 20 Dec 2001, Petr Holub wrote: You should send a kernel config to the list. It might be mbuf starvtion, but that doesn't sound like a driver specific problem. OK. dmesg from boot -v and kernel config is in the attachement. Thanks, Petr Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 2 Institute of Compt. Science 10200 Praha, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: [EMAIL PROTECTED] phone: +420-5-41512278 e-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: userland program panics freebsd 4.3
Kris Kennaway wrote: On Thu, Dec 20, 2001 at 09:10:14AM -0500, Michael Scheidell wrote: I doubt hardware related I can get it to do it on two seperate boxes. OK, then you need to get more details as explained. My gut reaction tells me that this is either a kernel stack overflow or out of KVM. The kernel stack overflow problem was fixed in 4.4-STABLE some time back (change UPAGES from 2 to 3 in the kernel) so that the kernel stack changes from 4.5K to 8.5K. The other possibility is that he's configured the kernel so big (maxusers too high etc) and he's running out of KVM. No tuning information was supplied (kernel configs, any sysctl/tunable changes etc). I'd be interested to know what this says: # gdb -k /kernel /dev/mem (kgdb) print ((struct vm_map *)kernel_map)-size Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: userland program panics freebsd 4.3
Kris Kennaway wrote: On Thu, Dec 20, 2001 at 09:10:14AM -0500, Michael Scheidell wrote: I doubt hardware related I can get it to do it on two seperate boxes. OK, then you need to get more details as explained. My gut reaction tells me that this is either a kernel stack overflow or out of KVM. The kernel stack overflow problem was fixed in 4.4-STABLE some time back (change UPAGES from 2 to 3 in the kernel) so that the kernel stack changes from 4.5K to 8.5K. Ok, 'fixed', thats good, makes me want to try the 4.4 kernel, or could I tune 4.3 kernel to a 8.5k stack? The other possibility is that he's configured the kernel so big (maxusers too high etc) and he's running out of KVM. No tuning information was supplied (kernel configs, any sysctl/tunable changes etc). maxusers 128, guess I could fiddle with vm,kernfiles, etc, but that was easyest way, the 'one' processes (user) can spawn 32*20 individual processes, each one open several files (yes, I uses ulimits on it) limits -C nessusd Resource limits for class nessusd: cputime infinity secs filesize 131072 kb datasize-cur65536 kb stacksize-cur 32768 kb coredumpsize-cur0 kb memoryuse-cur 65536 kb memorylocked-cur65536 kb maxprocesses 64 openfiles 256 sbsize infinity bytes nothing twiddled in sysctl, but in order to get apache to run, did: options PMAP_SHPGPERPROC=300 (sorry, If I didn't post it here, did both (maxusers and PMAP_) on comp.unix.bsd.freebsd.misc group already) I'd be interested to know what this says: # gdb -k /kernel /dev/mem (kgdb) print ((struct vm_map *)kernel_map)-size print ((struct vm_map *)kernel_map)-size $1 = 247824384 -- Michael Scheidell Secnap Network Security, LLC [EMAIL PROTECTED] 1+(561) 368-9561 See updated IT Security News at http://www.fdma.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: userland program panics freebsd 4.3
On Thu, Dec 20, 2001 at 07:14:08PM -0800, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 09:08:36PM -0600, Paul Halliday wrote: On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: I'm not aware of any services that broke between 4.3 and 4.4. Care to elaborate? scan through freebsd-questions, freebsd-mobile and freebsd-ports That's completely non-helpful. I read -questions and -ports, and don't recall complaints of massive breakage in 4.4. Perhaps you'd care to be more specific so we can actually address the problems, if they exist? My soundcard on my lappy has been broken since 4.4. And to be brutally honest, it's really starting to piss me off. Which PR contains your bug report? I couldn't see one. I'm not Paul Halliday, but I do have an ignored soundcard PR: kern/31445. I made the PR, mentioned it on multimedia, posted a patch a couple days later (to the PR), and even got someone to say he'd tried it and it had helped him. That correspondance is also attached to the PR. The PR is still open and unchanged since 29 Oct 2001. Soundcard behavior is unmodified on the box I reported it on as of a CVSup earlier this week. What did *I* do wrong? msg30368/pgp0.pgp Description: PGP signature
Re: userland program panics freebsd 4.3
On Fri, Dec 21, 2001 at 12:51:38PM -0500, Michael Scheidell wrote: My gut reaction tells me that this is either a kernel stack overflow or out of KVM. The kernel stack overflow problem was fixed in 4.4-STABLE some time back (change UPAGES from 2 to 3 in the kernel) so that the kernel stack changes from 4.5K to 8.5K. Ok, 'fixed', thats good, makes me want to try the 4.4 kernel, or could I tune 4.3 kernel to a 8.5k stack? This one is easy - edit /usr/src/sys/i386/include/param.h and change UPAGES from 2 to 3 (or even 5 if you like). I got Bruce to add an errata about this... David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Renaming root to something else ?
Here's question oozing with newbieness, but I'm still convinced this is the correct list. Does this code from src/sbin/init/init.c preclude renaming of the root account ? /* * Establish an initial user so that programs running * single user do not freak out and die (like passwd). */ if (setlogin(root) 0) warning(setlogin() failed: %m); If so, wouldn't it be an idea to call getpwnam on uid 0 ? I don't even know C all that well, so flame on if this is obvious, but if you could indicate why at the same time it would be nice ;) Thanks, Ceri -- keep a mild groove on To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Another filesystem test program
:We ought to add a standard way of running the tests expected to pass, :maybe a script in the subdirs ./regress pass that runs the tests :expected to pass and exits 0 if they do. : :The scheduling tests I put in don't even compile on :-current because MAP_INHERIT is non-standard and now gone from mman.h :(MAP_INHERIT should be protected by a POSIXY feature test in 4.X mman.h, :something to do after the release). The tests don't work on -current :(still do on 4.x), with oodles of extra context switches, but that's :another story. : :Peter : :-- :Peter Dufault ([EMAIL PROTECTED]) Realtime development, Machine control, MAP_INHERIT never worked as advertised, so we removed it. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Adding si_fd to struct __siginfo ...
Hi, One of my tasks is to add oplock support to FreeBSD so that we (Panasas) can allow correct caching of files by Windows clients in the presence of NFS clients using the same files. We have a preliminary implementation, based on the Linux implementation, but it is a gross hack because there is no way for the kernel, when it delivers a signal, to indicate the fd that caused delivery of the signal. Linux and Solaris have an fd field in struct siginfo_t which allows the kernel to indicate, for signals relating to files, to indicate which fd the signal relates to. I notice that in FreeBSD struct siginfo_t seems to have int __spare__[7]; and would like to use one of those spare fields as si_fd. While I can do that in our code base, if I want to contribute the OpLock code it would be useful if the FreeBSD community finds this change agreeable. Are there any counter suggestions or any big objections? -- Richard Sharpe, [EMAIL PROTECTED], LPIC-1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sendmail + auth + ssl + freebsd
Leo Bicknell wrote: If no one else has figured this mess out, I'll do it and write a page for the handbook. If someone else has, please clue me in, and if necessary I'll still write that handbook page. :-) It would be very nice if it was simple to make FreeBSD sendmail SSL and authenticate against the password file. Authentication is not against the password file. The normal mechanism for use of SMTP AUTH uses a shared secret vi a SASL challenege/response. SASL requires that the password be in clear text, so that the transformation on the host using the NONCE can be repeated on the client with the shared secret, without the secret ever going over the wire in cleartext. The program you are looking for is saslpasswd. You will have to maintain a local passwd file, seperate from the UNIX passwd file, for each of your mail clients. My personal approach was to use an LDAP directory, and limit the password using precalculation of a partial nonce. In any case, without the saslpasswd file, you will not be offered the AUTH extension on the SMTP connection (Say EHLO domain, and it will tell you what it supports or not). The most commonly deployed method is MD5 digest (this is what Netscape uses). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Looking for a sysctl logger
I'm looking for a program that can interrogate the sysctl mechanism and dump the data out for use by rrd or some other thing. I have something that does this now for acpi battery info (I feed the data into rrd for analysis), but I was hoping for something more general purpose. And no, I don't want to write it in perl : -) I'm trying to make it low impact, hence c. I don't mind doing it myself, but I'd rather use an existing wheel. -- Robert Sexton - [EMAIL PROTECTED], Cincinnati OH, USA To walk or take transit is a public act which makes the street a safer component of community. To drive is a private act which makes the street into a utility - Peter Calthorpe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Adding si_fd to struct __siginfo ...
* Richard Sharpe [EMAIL PROTECTED] [011221 15:11] wrote: Hi, One of my tasks is to add oplock support to FreeBSD so that we (Panasas) can allow correct caching of files by Windows clients in the presence of NFS clients using the same files. We have a preliminary implementation, based on the Linux implementation, but it is a gross hack because there is no way for the kernel, when it delivers a signal, to indicate the fd that caused delivery of the signal. Linux and Solaris have an fd field in struct siginfo_t which allows the kernel to indicate, for signals relating to files, to indicate which fd the signal relates to. I notice that in FreeBSD struct siginfo_t seems to have int __spare__[7]; and would like to use one of those spare fields as si_fd. While I can do that in our code base, if I want to contribute the OpLock code it would be useful if the FreeBSD community finds this change agreeable. Are there any counter suggestions or any big objections? There was already a big mess of a discussion about how this would be much better done via kqueue than with realtime signals. I guess if you can get a working implementation that is compatible with the existing interfaces it would work, however it's a _much_ better idea to use kqueue to deliver this sort of notification. And yes, it has been discussed in the lists already. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: userland program panics freebsd 4.3
- Original Message - From: David Malone [EMAIL PROTECTED] To: Michael Scheidell [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, December 21, 2001 1:18 PM Subject: Re: userland program panics freebsd 4.3 On Fri, Dec 21, 2001 at 12:51:38PM -0500, Michael Scheidell wrote: My gut reaction tells me that this is either a kernel stack overflow or out of KVM. The kernel stack overflow problem was fixed in 4.4-STABLE some time back (change UPAGES from 2 to 3 in the kernel) so that the kernel stack changes from 4.5K to 8.5K. This one is easy - edit /usr/src/sys/i386/include/param.h and change UPAGES from 2 to 3 (or even 5 if you like). I got Bruce to add an errata about this... I did this, and instead of crashing in 15 ins, its still running after 3 hours. I will rerun tests and report back. Thanks for the suggestion (now, if I cvsup RELENG_4_3 do I get the OLD param.h?) -- Michael Scheidell Secnap Network Security, LLC [EMAIL PROTECTED] 1+(561) 368-9561 See updated IT Security News at http://www.fdma.com/ David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Adding si_fd to struct __siginfo ...
Alfred Perlstein wrote: * Richard Sharpe [EMAIL PROTECTED] [011221 15:11] wrote: Hi, One of my tasks is to add oplock support to FreeBSD so that we (Panasas) can allow correct caching of files by Windows clients in the presence of NFS clients using the same files. We have a preliminary implementation, based on the Linux implementation, but it is a gross hack because there is no way for the kernel, when it delivers a signal, to indicate the fd that caused delivery of the signal. Linux and Solaris have an fd field in struct siginfo_t which allows the kernel to indicate, for signals relating to files, to indicate which fd the signal relates to. I notice that in FreeBSD struct siginfo_t seems to have int __spare__[7]; and would like to use one of those spare fields as si_fd. While I can do that in our code base, if I want to contribute the OpLock code it would be useful if the FreeBSD community finds this change agreeable. Are there any counter suggestions or any big objections? There was already a big mess of a discussion about how this would be much better done via kqueue than with realtime signals. I guess if you can get a working implementation that is compatible with the existing interfaces it would work, however it's a _much_ better idea to use kqueue to deliver this sort of notification. And yes, it has been discussed in the lists already. OK, I will go and look at the discussion ... -- Richard Sharpe, [EMAIL PROTECTED], LPIC-1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sendmail + auth + ssl + freebsd
On Wed, 19 Dec 2001, Leo Bicknell wrote: After searching the archives and looking at the source, I find myself more confused. I've been asked to set up sendmail + ssl + SMTP auth on a FreeBSD host. A quick strings on the sendmail binary shows a number of SSL functions, so I'm thinking the SSL bits are in there, but I'm not quite sure how to take advantage of them. Issuing AUTH to a stock -STABLE sendmail gets command unrecognized though, so I don't think that is there. Do you have this in /etc/make.conf? # Add SMTP AUTH support to Sendmail SENDMAIL_CFLAGS+= -I/usr/local/include/sasl -DSASL -D_FFR_UNSAFE_SASL SENDMAIL_LDFLAGS+= -L/usr/local/lib SENDMAIL_LDADD+=-lsasl In sendmail.mc: TRUST_AUTH_MECH(`PLAIN LOGIN DIGEST-MD5 CRAM-MD5')dnl define(`confAUTH_MECHANISMS',`PLAIN LOGIN DIGEST-MD5 CRAM-MD5')dnl define(`confDONT_BLAME_SENDMAIL',`GroupReadableSASLFile')dnl in /usr/local/lib/sasl/Sendmail.conf: pwcheck_method: shadow This will at least give you AUTH. (I think you need to install ports/security/cyrus-sasl to make it work, but I'm not sure). If no one else has figured this mess out, I'll do it and write a page for the handbook. If someone else has, please clue me in, and if necessary I'll still write that handbook page. :-) It would be very nice if it was simple to make FreeBSD sendmail SSL and authenticate against the password file. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Another crash with fsx?
Hey, Could someone test the following: # mdconfig -a -t malloc -s 4m -u 0 # disklabel -r -w md0 auto # newfs /dev/md0c # tunefs -n enable /dev/md0c # mount /dev/md0c /mnt ( the above is directly copied from `man mdconfig') # cd /mnt # ~/fsx test.file On my machine this produces a hard freeze, I have to hold the power button on the case for several seconds to get a reboot. I found something else when I discovered the above behavior. If you try and start X while a background fsck is working the machine will lock up and then reboot of its own accord. I'm going to test without setting softupdates now. # uname -a FreeBSD gallium 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Fri Dec 21 22:06:00 GMT 2001 dominic@gallium:/usr/obj/usr/src/sys/GALLIUM i386 I can provide any other information you need on request. -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Another crash with fsx?
On Saturday 22 December 2001 2:44 am, Dominic Marks wrote: snip/ I'm going to test without setting softupdates now. Okay. This only happens when softupdates is enabled. snip/ -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
shutdown -p sometimes doesn't...
[replies sent directly to me may timeout and bounce, since I'm not online as often as I should be, but I'll check the list archives] Servus I have a machine here with a power manglement BIOS that allows me to enable automatic power-on at a scheduled time. Kewl, eh? Normally (when above feature is disabled) `shutdown -p' will power-off the machine, since I've enabled APM in rc.conf, which is well and good. However, if I happen to have made no other changes than to enable power-on in the BIOS, `shutdown -p' is no different from an ordinary reboot. The machine goes through all the motions of poweroff, but instead reboots. I tried adding debuggery to see if I could figure out if enabling power-on made any noticeable difference to the kernel, but all looked the same. Now, I've just installed NetBSD on the same machine, and I've used windows as well, which had no problems with poweroff whether or not I enabled auto-poweron. I figured doze was probably doing something weird, but when the NetBSD `poweroff' command succeeded in powering off the machine immediately after FreeBSD `shutdown -p' caused a reboot, I got disturbed. I tried looking at the NetBSD source k0dez to see if it somehow was poking at the BIOS somewhat differently or something, but I couldn't see anything obvious as to why it works when FreeBSD fails. Would anyone care to take a stab at fixing this, or offer insight as to why enabling powerup automagically would be enough to make the FreeBSD shutdown -p poweroff calls fail? I'm mystified thanks barry bouwsma To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Adding si_fd to struct __siginfo ...
Richard Sharpe [EMAIL PROTECTED] writes: There was already a big mess of a discussion about how this would be much better done via kqueue than with realtime signals. I guess if you can get a working implementation that is compatible with the existing interfaces it would work, however it's a _much_ better idea to use kqueue to deliver this sort of notification. And yes, it has been discussed in the lists already. OK, I will go and look at the discussion ... Unfortunately this discussion mistakenly took place on a FreeBSD mailing list intended for administrative-only issues, so it isn't publicly available on our end. Luckily, a Samba mailing list was on the CC line. You should be able to find it on the [EMAIL PROTECTED] archives circa September 2001. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Adding si_fd to struct __siginfo ...
Mike Barcroft wrote: Richard Sharpe [EMAIL PROTECTED] writes: There was already a big mess of a discussion about how this would be much better done via kqueue than with realtime signals. I guess if you can get a working implementation that is compatible with the existing interfaces it would work, however it's a _much_ better idea to use kqueue to deliver this sort of notification. Well, it turns out that there are two problems with what I suggested: 1, signals are lossy, in that if multiple signals occur, only one might be delivered; and 2, there is no place to store any signal-related information in the kernel, in any case. So, it seems like kqueue is really the only game in town, but I will need an appropriate filter, and it would be nice if I could get some sort of async notification that there were events ready to be processed, as I really don't want to rewrite Samba completely, just to support kqueue ... Hmmm, perhaps the approach should be to signal that leases/oplocks have been broken, but provide the details via kqueue. And yes, it has been discussed in the lists already. OK, I will go and look at the discussion ... Unfortunately this discussion mistakenly took place on a FreeBSD mailing list intended for administrative-only issues, so it isn't publicly available on our end. Luckily, a Samba mailing list was on the CC line. You should be able to find it on the [EMAIL PROTECTED] archives circa September 2001. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Richard Sharpe, [EMAIL PROTECTED], LPIC-1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
