Re: kvm questions
Vlad GALU [EMAIL PROTECTED] writes: Hello. I am trying to write a monitoring program which makes use of the kvm interface. procfs is significantly less evil, if you can get the information you require from it. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc bug? Openoffice port impossibel to compile on 4.8
Wes Peters [EMAIL PROTECTED] writes: On Thursday 29 May 2003 00:12, Dag-Erling Smorgrav wrote: May I remind you that KR-style declarations have been deprecated for the last 14 years? Funny, the last time I looked at a C language specification they were still supported. 6.11.5 Function definitions [#1] The use of function definitions with separate parameter identifier and declaration lists (not prototype-format parameter type and identifier declarators) is an obsolescent feature. and obsolescent feature is defined as follows in the introduction: [#2] Certain features are obsolescent, which means that they may be considered for withdrawal in future revisions of this International Standard. They are retained because of their widespread use, but their use in new implementations (for implementation features) or new programs (for language [6.11] or library features [7.26]) is discouraged. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc bug? Openoffice port impossibel to compile on 4.8
Valentin Nechayev [EMAIL PROTECTED] writes: Essential words are understriked. I can't imagine how it can be read as unsupported. I didn't use the word unsupported, I said deprecated. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc bug? Openoffice port impossibel to compile on 4.8
Wes Peters [EMAIL PROTECTED] writes:
GCC 3.2 is broken by design. It insists, amongst other stupidities, on
type-checking arguments using old style declarations like:
int foo(bar)
char *bar;
{}
rendering most UNIX software from before 1996 uncompilable.
have you tried -traditional?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3 IDE devices on Promise card + FreeBSD == not possible?
Pete [EMAIL PROTECTED] writes: atacontrol create mirror ad6 ad7 This is starting to _really_ confuse me. Does FreeBSD have two software RAID systems? Yes (vinum and raidframe) Is there something built into the ATA controller drivers that can do software RAID too? It looks that way from that atacontrol and ata man pages. No, but atacontrol knows how to configure hardware RAID controllers such as your Promise FastTrack. Where does Vinum fit in here or is Vinum extraneous now? Vinum is a volume manager with RAID functionality. Is Vinum just a front-end to the ata system? No, it's completely device independent. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: booting from Promise tx2000: FIXED
Len Conrad [EMAIL PROTECTED] writes: while waiting for Soeren Schmidt to get the Promise SX4000 driver done! I was under the impression that the SX4000 and SX6000 were already supported? I know that phk has an SX6000 which he says works fine. OTOH, it's possible that this hasn't percolated down to -STABLE yet. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging a repeating panic that does not produce a dump
Mike Tancsa [EMAIL PROTECTED] writes: It only happens when periodic runs, but it on occasion skips a day. Eg. yesterday it did not do it. It only started happening post Jan28th. I can brutalize the server with repeated buildworlds (-j2 through 8) and it is always successful. Its only on periodic that it dies and find is always the process running. Its only with SMP as well on this 'oldish' machine Hmm, it would be great to know what process was running when it crashed. Unfortunately, I don't know how to do that post-KSE... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: arc4random() range
[EMAIL PROTECTED] writes: Well, I'm right in principle but wrong in current practice, at the very least make it: #define arc4random31() (arc4random() RAND_MAX) or rather #define arc4random31() (arc4random() % (RAND_MAX + 1)) to avoid relying on RAND_MAX being one less than a power of two. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: arc4random() range
Peter Jeremy [EMAIL PROTECTED] writes: In any case, doesn't the name imply that it's 31-bits... Yes, it's a bad name. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging a repeating panic that does not produce a dump
Mike Tancsa [EMAIL PROTECTED] writes: Fatal trap 12: page fault while in kernel mode mp_lock = 0002; cpuid = 0; lapic.id = 0100 fault virtual address = 0xc6efa8e8 Hmm, different fault address this time. (kgdb) up 6 #6 0xc0174830 in makedev (x=28, y=160) at /usr/src/sys/kern/kern_conf.c:207 These numbers look perfectly valid (cuaia0). The only explanation I can think of is some kind of race, or some kind of corruption. Hopefully somebody more clued than myself will be able to figure it out. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging a repeating panic that does not produce a dump
Mike Tancsa [EMAIL PROTECTED] writes: I am seeing a repeatable panic with a 4.x SMP machine (not when in uni mode). It never produces a crash dump, but always panics when periodic runs. Hmm, it doesn't even seem to *try* to dump... are you sure you have configured a dump device? instruction pointer = 0x8:0xc0174830 This is the address of the instruction which caused the fault. You can run nm(1) on your kernel to find out where in the kernel that is, e.g.: # nm /kernel | grep \^c0174 | sort this should give you a list of maybe a dozen symbols; the one you want is the last one in the list that has a lower address than c0174830. How do you build your kernels - 'make buildkernel' or manually? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging a repeating panic that does not produce a dump
Mike Tancsa [EMAIL PROTECTED] writes:
ns4# nm /kernel | grep \^c0174 | sort
[...]
c01747d4 T makedev
c01748f4 T freedev
This is it (makedev)
Does this actually show the location ?
ns4# gdb -k kernel.debug
[...]
(kgdb) list *0xc0174830
0xc0174830 is in makedev (/usr/src/sys/kern/kern_conf.c:208).
203 if (x == umajor(NOUDEV) y == uminor(NOUDEV))
204 Debugger(makedev of NOUDEV);
205 udev = (x 8) | y;
206 hash = udev % DEVT_HASH;
207 LIST_FOREACH(si, dev_hash[hash], si_hash) {
208 if (si-si_udev == udev)
209 return (si);
210 }
211 if (stashed = DEVT_STASH) {
212 MALLOC(si, struct specinfo *, sizeof(*si), M_DEVT,
(kgdb)
Yep. Looks like si is garbage:
fault virtual address = 0x211e6d36
is most likely the value of si at the time of the crash. It's nowhere
near kernel memory (which starts at 0xc000).
If / when you get a dump, show me the backtrace and the value of x, y
and udev (as reported by gdb operating on the recovered core)
How do you build your kernels - 'make buildkernel' or manually?
Always make buildkernel. I have a debug kernel built as well
(makeoptions DEBUG=-g)
That's what I wanted to know.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: debugging a repeating panic that does not produce a dump
Mike Tancsa [EMAIL PROTECTED] writes: Thank you very much, I will do so as soon as I get the dump. BTW, could the act of giving the wrong params to dumpon cause the crash ? No, it wouldn't. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: dynamic hints
Peter Wemm [EMAIL PROTECTED] writes: Yes, sort-of. kenv(8) can change the strings. But I suspect it is too late for something like isa since I think it would have done a pass at boot to create the attachment nodes. But as configuration knobs for drivers that want to examine a string directly via getenv() etc, those would not be too late. It wouldn't be too late for loadable modules... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: OpenPAM and OSVERSION
Sergey Matveychuk [EMAIL PROTECTED] writes: What is OSVERSION num right after OpenPAM implemented? What problem are you trying to solve? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: OpenPAM and OSVERSION
Sergey Matveychuk [EMAIL PROTECTED] writes: What is OSVERSION num right after OpenPAM implemented? What problem are you trying to solve? security/pam-* ports. I'v fiexed pam-mysql for this time. It's works for me. I'm working for PR. If you've fixed it in a way which requires knowing whether the system runs Linux-PAM or OpenPAM, you've fixed it wrong. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: OpenPAM and OSVERSION
Sergey Matveychuk [EMAIL PROTECTED] writes: If you've fixed it in a way which requires knowing whether the system runs Linux-PAM or OpenPAM, you've fixed it wrong. OK. Why? Because most PAM problems in ports are bugs in the ports themselves, which Linux-PAM just happens to tolerate and OpenPAM doesn't. In other words, it should be possible to find a solution to the problem which works equally well for Linux-PAM and OpenPAM, without the need to know which is which. And as a last resort, you can make OpenPAM- specific code conditional on the _OPENPAM preprocessor symbol. What fix will be a right one? I can't tell you unless you show me what you believe needs fixing. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: OpenPAM and OSVERSION
Sergey Matveychuk [EMAIL PROTECTED] writes: What a right way escape from PAM_CONV_AGAIN/PAM_TRY_AGAIN and relate code from LINUX_PAM? Shoot the module author for using it, and Andrew Morgan (Linux-PAM author) for inventing it. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Some security questions.
Julian Elischer [EMAIL PROTECTED] writes: 1/ Command logging. We're thinking that a hacked version of the shell that logs commands may do what they want, but personally I think that if you are going to log things then you really want to PROPERLY do it, and log the EXEC commands along with the arguments. (sadmin et al. doesn't give arguments, and neither does ktrace) Yes, we can do that in the sense that it can be implemented if there's a demand for it, but I don't think any existing code can do it. 2/ they want to disable a login if it fails 'n' sequential logins anywhere in the system. i.e. 2 on one machine followed by another on another machine. Yes we can do that with a smart PAM module. I can immagine using pam_radius, and hacking a radius server to track login fails.. Anyone have any better ideas? Maybe a pam_module specially written? (h) PAM has a mechanism which allows for arbitrary named objects to be stored for the duration of a PAM transaction, along with a destructor which is called when the object is released (either explicitly or when the transaction ends). You could write a PAM module which stores an object in the authenticate phase, then modifies its contents in the setcred phase (which only occurs if authentication was successful). The destructor would register success or failure in a database depending on whether the object was modified before release. The exact nature of that database is not important. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Help with understanding process state, context switching andsignals
Andrey Simonenko [EMAIL PROTECTED] writes: In short: I need to stop (suspend) some process from the kernel, when that process is in user mode and get information about its general-purpose registers, its VM structures, etc. Have you looked at ptrace(2)? That's what gdb(1) uses. You can get additional information about memory maps etc. from procfs. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: End-Of-Life announcement for M-Systems DiskOnChip driver(fla).
David Yeske [EMAIL PROTECTED] writes: I still use this. Users will not suddenly quit using hardware that works, they will start using a different OS that works with it, or they will be stuck trying to continue to support an old version of FreeBSD because it works with it. Read the announcement again. FreeBSD 5.x will still have DoC support, which means you have at least two years to grow tired of it before we stop putting out 5.x releases. By that time you will hopefully have realised it is a dead-end technology and switched to something that works. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: replacing GNU grep with UNIX grep.
Sergey Babkin [EMAIL PROTECTED] writes: Also the GNU grep has a lot more options, the most interesting of them being -r. Unfortunately, GNU grep's -r option is broken (it does not handle symnlinks correctly). Try textproc/freegrep from ports instead. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Modifying mergemaster behavior
Doug Barton [EMAIL PROTECTED] writes: On Tue, 28 Jan 2003, Garance A Drosihn wrote: Well for one thing, if a given file has a lot of changes, then I would like mergemaster to skip over the initial one-line change that only tells me how some comment now has a new version-number in it. This is an oft-requested feature, but I'm not sure how best to implement it. Look up the -I option in the diff(1) man page. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Modifying mergemaster behavior
Doug Barton [EMAIL PROTECTED] writes: I didn't say I don't know HOW to implement it, I said I didn't know how BEST to implement it. You snipped the part of my e-mail where I explained the issues. I don't see the problem, you don't need to run diff twice... no more than you already do (any reason why you don't use cmp instead of diff on line 815?) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: USB support for new HP printers?
John Nielsen [EMAIL PROTECTED] writes: Hi, John. The LaserJet 1200 advertises several alternate settings for the printer-class interface: 7/1/3 (for IEEE 1284.4 packets, the new and different USB interface you mentioned), 7/1/2 (bidirectional raw print data), and 7/1/1 (unidirectional raw print data). If you can somehow convince the ulpt driver to bind to 7/1/2 or 7/1/1 rather than just blindly binding to the first alternate setting it finds, then that should be all you need. Interesting. I wonder if the same applies to the OfficeJet. I have a d145, and while FreeBSD recognizes it just fine, and attaches it as a ulpt device, it fails to print (the process that tries to write to /dev/ulpt0 just hangs). I'll see if I can figure out a way to force the ulpt driver to bind to 7/1/2. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: USB support for new HP printers?
The attached patch allows me to print to my HP OfficeJet by making
ulpt0 use the bidirectional interface (7/1/2) instead of the IEEE1284
interface (7/1/3). I haven't had time to set up CUPS yet, but simply
catting a text file do /dev/ulpt0 works fine, while previously it
would just hang.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
Index: sys/dev/usb/ulpt.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ulpt.c,v
retrieving revision 1.50
diff -u -r1.50 ulpt.c
--- sys/dev/usb/ulpt.c 30 Oct 2002 01:18:58 - 1.50
+++ sys/dev/usb/ulpt.c 4 Dec 2002 23:33:39 -
@@ -236,8 +236,7 @@
id-bInterfaceNumber == ifcd-bInterfaceNumber) {
if (id-bInterfaceClass == UICLASS_PRINTER
id-bInterfaceSubClass == UISUBCLASS_PRINTER
- (id-bInterfaceProtocol == UIPROTO_PRINTER_BI ||
- id-bInterfaceProtocol == UIPROTO_PRINTER_1284))
+ id-bInterfaceProtocol == UIPROTO_PRINTER_BI)
goto found;
altno++;
}
Re: Increasing KVM
Ian Campbell [EMAIL PROTECTED] writes: How exactly would I go about increasing KVM? Read the FAQ. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Accessing memory below 1 MB
[EMAIL PROTECTED] writes:
I'm writing some graphics code (just for fun) and I need legal access to
the memory addresses below 1 mb.
You can't access the framebuffer directly in FreeBSD like you can in
DOS. Take a look at libvgl ('man vgl').
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: kern/40003: Panic on boot w/4.6-stable
Charles Sprickman [EMAIL PROTECTED] writes:
(kgdb) up 11
#11 0xc013e8a5 in ad_attach (atadev=0xc075b650) at ../../dev/ata/ata-disk.c:124
124 adp-heads = atadev-param-heads;
(kgdb) p adp
$2 = (struct ad_softc *) 0x68c040
(kgdb) p atadev
$3 = (struct ata_device *) 0xc075b650
(kgdb) p *adp
Cannot access memory at address 0x68c040.
(kgdb) p *atadev
$4 = {channel = 0xc075b600, unit = 16, name = 0xc04503b0 ad1, param = 0x0,
driver = 0x0, flags = 0, mode = 0, cmd = 0, result = 0x0}
ad_attach() is trying to dereference atadev-param, which is NULL.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: kern/40003: Panic on boot w/4.6-stable
Charles Sprickman [EMAIL PROTECTED] writes: On 28 Jul 2002, Dag-Erling Smorgrav wrote: ad_attach() is trying to dereference atadev-param, which is NULL. Is there any other info I can provide? I'll drive, you steer. :) No, this is Søren's cup of tea, which is why I Cc:ed him. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: allocating memory
Stephen Montgomery-Smith [EMAIL PROTECTED] writes:
I have access to a rather large computer (3GB of RAM) and I would like
to write a program to access most of this memory. I find that I am
unable to malloc more than about 0.5 GB of memory, even if I do it in
small increments. Now I am trying mmap, and this lets me get to about
2.5 GB of memory (again I ask for the memory in small increments). What
is it that causes these limitations?
man limits, and see MAX{DSIZ,SSIZ} in NOTES.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: Is gethostbyname2() reentrant?
Peter Haight [EMAIL PROTECTED] writes: If I link with libc_r can I use gethostbyname2() at the same time in two different threads? Use getaddrinfo() instead. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: /usr/include/netinet/in.h
Ian [EMAIL PROTECTED] writes: The general rule is including includes from includes is bad. Okay, it's time to point out that these are opinions, not rules, and differing opinions exist. POSIX disagrees with you. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Erm, since everyone managed to HIJACK my sshd thread! ;)
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -hackers is not the appropriate forum for code review. The patch is incorrect and should be backed out. Never mind, I did it myself. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: jail in 4.5-RELEASE: setrlimit() and blocked processes
John Kozubik [EMAIL PROTECTED] writes: You can solve this problem by removing the setrlimit() call in postfix, with the following patch: s/solve/work around/ The correct *solution* would be to fix setrlimit(). DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: procfs issue.
Alfred Perlstein [EMAIL PROTECTED] writes: It looks like the following delta (submitted by Tim J. Robbins) may fix it: It looks correct to me, please commit (unless John has any objections?) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 'rm' incompatibility with Posix.2
Bogdan TARU [EMAIL PROTECTED] writes: I have attached a patch for the 'rm' untility, which strips the trailing slash(es) from the path (according to Posix.2). But I think there are many other utilities which need to be patched (e.g. cp, mv). Please don't. This functionality is extremely useful. Consider this: des@des ~% mkdir foo des@des ~% touch foo/bar des@des ~% ln -s foo baz des@des ~% ls -l baz lrwxr-xr-x 1 des des 3 Apr 10 16:15 baz - foo des@des ~% ls -l baz/ total 0 -rw-r--r-- 1 des des 0 Apr 10 16:15 bar and the same scenario on Solaris: des@sex ~% mkdir foo des@sex ~% touch foo/bar des@sex ~% ln -s foo baz des@sex ~% ls -l baz lrwxrwxrwx 1 des des3 Apr 10 16:16 baz - foo/ des@sex ~% ls -l baz/ lrwxrwxrwx 1 des des3 Apr 10 16:16 baz/ - foo/ [scream and curse] des@sex ~% cd baz des@sex ~/baz% ls -l total 0 -rw--- 1 des des0 Apr 10 16:16 bar In my humble opinion, Solaris (and every other *nix) is broken in this respect, and *BSD is correct. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 'rm' incompatibility with Posix.2
Bogdan TARU [EMAIL PROTECTED] writes: On 10 Apr 2002, Dag-Erling Smorgrav wrote: In my humble opinion, Solaris (and every other *nix) is broken in this respect, and *BSD is correct. Except for OpenBDS. No NetBDS machine available, maybe some of you could try it on one as well? I don't know of any OpenBDS or NetBDS, but NetBSD has the same semantics as FreeBSD: des@rc4 ~% mkdir foo des@rc4 ~% touch foo/bar des@rc4 ~% ln -s foo baz des@rc4 ~% ls -l baz lrwxr-xr-x 1 des des 3 Apr 10 16:41 baz@ - foo des@rc4 ~% ls -l baz/ total 0 -rw-r--r-- 1 des des 0 Apr 10 16:41 bar DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 'rm' incompatibility with Posix.2
Bogdan TARU [EMAIL PROTECTED] writes: Could you also try the NetBDS's 'rm'? If it does work like FreeBDS, than I really don't know what to believe anymore. It doesn't, actually, it removes the symlink rather than the directory it points at. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Four misc. questions related to jail usage
Patrick Thomas [EMAIL PROTECTED] writes: No, procfs is pretty much useless these days (except for truss). In 4.5, won't `ps` (and perhaps other apps) not work for people in a jail if their jail does not have a proc file system mounted in their /proc ? Only 'ps -e'. Everything else will work just fine. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Four misc. questions related to jail usage
Patrick Thomas [EMAIL PROTECTED] writes: 1. Does each jail need to have its own proc filesystem mounted? No, procfs is pretty much useless these days (except for truss). 2. Does kern.maxproc scale in a linear fashion with maxusers ? The default value for kern.maxproc is 20 + 16 * maxusers. 4. Why is it that some linux utilities, run inside a jail, get the hostname of the host machine, and not the hostname of the jail itself? It's a bug. It was fixed recently (in the last few days) in -CURRENT. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Make's ongoing effort to get his PR's closed...
Mike Meyer [EMAIL PROTECTED] writes: In my ongoing attempt to get my PR's closed, here's the list again. They are listed roughly in the order of difficulty. Please send this to [EMAIL PROTECTED] DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: in-kernel HTTP Server for FreeBSD?
Hiten Pandya [EMAIL PROTECTED] writes: Is there any In-Kernel HTTP Server for FreeBSD, like there is kHTTPD for Linux? God forbid! Lots of hack value, sure, but not something you'd seriously consider for production use. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: in-kernel HTTP Server for FreeBSD?
Thomas Hurst [EMAIL PROTECTED] writes: Don't functions like FreeBSD's zero-copy sendfile() provide similar performance benefits without the massive security issues? sendfile() isn't zero-copy, it's just two-less-copies. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: in-kernel HTTP Server for FreeBSD?
Roy Sigurd Karlsbakk [EMAIL PROTECTED] writes: well .. So let's turn the question upside-down, and ask Is there a web server or -accelerator for FreeBSD with similar performance as with khttpd or Tux? Have you tried thttpd or boa? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: in-kernel HTTP Server for FreeBSD?
Roy Sigurd Karlsbakk [EMAIL PROTECTED] writes: sendfile() isn't zero-copy, it's just two-less-copies. zero-copy means zero copy-operations within memory To an MCSE, maybe. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: in-kernel HTTP Server for FreeBSD?
Roy Sigurd Karlsbakk [EMAIL PROTECTED] writes: sendfile() isn't zero-copy, it's just two-less-copies. zero-copy means zero copy-operations within memory To an MCSE, maybe. strange ... [...] So what would you call direct DMA from the disk controller to the network adapter? Minus-one-copy? And even in the sendfile(2) case, data sometimes *is* copied in-core to satisfy alignment requirements etc. Stop using buzzwords just because they give you a woody. (and yes, even a Dr. Scient can be mistaken. Papers don't make you smart, you know - though I wouldn't expect someone who brags about being an MCSE and MCNE to understand that) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: in-kernel HTTP Server for FreeBSD?
Roy Sigurd Karlsbakk [EMAIL PROTECTED] writes: er.. So - if you certify within a product, you'll probably become dumber? Getting an MCSE or an MCNE doesn't necessarily make one dumb - though some might ask if one couldn't find anything better to do with one's (employer's) time and money. Believing that it's worth more than the paper it's printed on, however, and bragging about it in an open-source forum, raises serious questions about one's intellectual acumen. Now, a CCNE, on the other hand... DES (neither of the above) -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
OpenPAM Caliopsis + integration patches
OpenPAM Caliopsis and accompanying FreeBSD integration patches are now available from URL:http://openpam.sourceforge.net/. A fully patched tree is also available from the p4 depot, under //depot/user/des/pam/. Please see the release notes and change log for information about known and resolved issues. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ptrace and SIGTRAP problem
Zhihui Zhang [EMAIL PROTECTED] writes: The following small program demonstrates that a parent process can write into the data space of its child by ptrace(). If the parent waits for the child to exit, there is no problem. However, if the parent does not do so, the child will get a SIGTRAP signal and core dumps. Can anyone give me a clue how this is the case? Thanks! The parent must either detach from the child, or wait for it to terminate. See ptrace(2). DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ptrace and SIGTRAP problem
Zhihui Zhang [EMAIL PROTECTED] writes: - PT_CONTINUE + waitpid() works fine, the trace program prints out values. This is expected behaviour. - PT_CONTINUE alone does not work but no core-dump caused by SIGTRAP - PT_DETACH + waitpid() does not work and core-dump - PT_DETACH alone does not work and core-dump. These three cases are unexpected. I'll have to dig some more into this, but I'm afraid I won't have time until some time next week. Who is sending the SIGRAP (5) signal? execve(2) in kern_exec.c posts SIGTRAP if the process has debugging turned on (which it does as a result of PT_TRACE_ME). DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ptrace and SIGTRAP problem
Zhihui Zhang [EMAIL PROTECTED] writes: On 9 Feb 2002, Dag-Erling Smorgrav wrote: execve(2) in kern_exec.c posts SIGTRAP if the process has debugging turned on (which it does as a result of PT_TRACE_ME). This is one time thing. It will be catched by the first wait() call in the parent process. Yes. Subsequent SIGTRAPs normally indicate that syscall tracing is enabled (see /sys/i386/i386/trap.c) but I don't think that's the case here. I'll try to figure out what's happening when I find time. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: New feutures...........
Rafter Man [EMAIL PROTECTED] writes: 2. I hope that in the furture the FreeBSD developers will rewrite the system in C++. You need to have your head examined. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: New vhost bugs.FreeBSD.org
Maxime Henrion [EMAIL PROTECTED] writes: The recently added cvsweb.FreeBSD.org vhost makes me think we could also have one pointing to the PR database (/cgi/query-pr-summary.cgi), for example, bugs.FreeBSD.org as the subject of this mail suggests. Yes, please. DES (Bugmeister) -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel hacker task: Floppy driver mode handling.
Poul-Henning Kamp [EMAIL PROTECTED] writes: There exists a patch for adding a mode to our floppy driver to add DEC RX50 media handling. Clearly a job for Jessem, don't you think? :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: what is PSEUDOFS?
Hiten Pandya [EMAIL PROTECTED] writes: i know what DEVFS is... after the lecture at the BSDCon 2001 Europe by phk Well, the author of pseudofs was there too, and did mention it in his lightning talk right before Jordan's MacOS X presentation. You could have asked him there :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Bugmeister discussion list
Doug Barton [EMAIL PROTECTED] writes: On 22 Nov 2001, Dag-Erling Smorgrav wrote: I've set up a [EMAIL PROTECTED] mailing list Any reason this can't/shouldn't be a freebsd.org mailing list? Mostly because setting up a freebsd.org mailing list takes time and I wasn't willing to wait. There will eventually be a bugbusters@ list once I get a bugbuster team organized. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Bugmeister discussion list
[apologies to those who receive multiple copies of this message] I've set up a [EMAIL PROTECTED] mailing list with the following charter: Discussions pertaining to the FreeBSD PR system. The purpose of this list is to serve as an informal forum for discussing policies and mechanisms for PR handling in the context of the FreeBSD Project. To subscribe, send the usual magic incantations to [EMAIL PROTECTED] DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Bugmeister discussion list
Gary Jennejohn [EMAIL PROTECTED] writes: This seems like a fatal name for the list considering what buggers means. I know perfectly well what it means. I did say the list was informal, didn't I? :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Unix Philosophers Please!
Bernd Walter [EMAIL PROTECTED] writes: In short: The data is tranfered into the kernel and dropped there. The data is never transferred into the kernel. There is no copyin() or uiomove() there. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: forwarding
Martin Vana [EMAIL PROTECTED] writes: The problem is when I try to retrive any files from users. Than DC tryies to establish direct connection to user on ports from 410-415. How could I somehow 'catch' this request (SYN_SENT foo.foobar.com 41x) and forward it through ssh tunnel and back? You can't. Don't limit yourself to just one box, I also have another FreeBsd machine ready to serve. Is the other box outside the firewall? In that case, set up PPP on both boxen (see /usr/share/examples/ppp/ppp.conf.sample) and run PPP over SSH. On the inside box, set up a single static route to the outside box and let PPP take care of the default route. The outside box should run natd or ipnat unless you have a spare IP address you can use for the PPP link. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: buildworld breakage during make depend at usr.bin/kdump
Eugene L. Vorokov [EMAIL PROTECTED] writes: Uhmz ? Your shell is broken. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Unix Philosophers Please!
Nicpon, John [EMAIL PROTECTED] writes: Please specifically define where data goes that is sent to /dev/null It goes into a special data sink in the CPU where it is converted to heat which is vented through the heatsink / fan assembly. This is why CPU cooling is increasingly important; as people get used to faster processors, they become careless with their data and more and more of it ends up in /dev/null, overheating their CPUs. If you delete /dev/null (which effectively disables the CPU data sink) your CPU may run cooler but your system will quickly become constipated with all that excess data and start to behave erratically. If you have a fast network connection you can cool down your CPU by reading data out of /dev/random and sending it off somewhere; however you run the risk of overheating your network connection and / or angering your ISP, as most of the data will end up getting converted to heat by their equipment, but they generally have good cooling, so if you don't overdo it you should be OK. I hope this answers your question. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: buildworld breakage during make depend at usr.bin/kdump
Guido van Rooij [EMAIL PROTECTED] writes: May I aks which shell you are using? Zsh. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: truss vs ktrace
Arun Sharma [EMAIL PROTECTED] writes: Another advantage of truss is that the output is online and interactive. ktrace requires you to use kdump to view the trace. I certainly wouldn't call truss interactive. As for online, see the -l command-line option to kdump. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: truss vs ktrace
Robert Watson [EMAIL PROTECTED] writes: There are a fair number of differences, but from my perspective, one of the primary ones is that truss relies on procfs, Truss could be easily be rewritten to use ptrace() instead of procfs. It'd be a lot slower though, because ptrace() can only return one int at a time from process memory whereas with /proc/pid/mem you can read as much as you want in one go. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: New rc.d init script roadmap
Gordon Tetlow [EMAIL PROTECTED] writes: M1 (Patch included) Setup infrastructure Make rcorder compile Your rcorder patch is incorrect. FreeBSD lacks a prototype for fparseln(). It so happens that it doesn't make any difference on any of the platforms FreeBSD supports (because our ints and pointers are the same size), but that's no reason not to do things right. Also, I don't see the point in munging the Makefile like you do - I think we can live with having a Makefile that's slightly (and trivially) different from NetBSD's. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: New rc.d init script roadmap
Gordon Tetlow [EMAIL PROTECTED] writes: Actually, fparseln() is defined in libutil.h (per the man page). I don't have my current box available (power outage at home), but if you could look over it, it should work. Ah, that's right - I couldn't find the right header, I should have simply looked at the libutil Makefile. Thanks! DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: New rc.d init script roadmap
John Baldwin [EMAIL PROTECTED] writes: Huh? Int on alpha is 32, and pointer is 64. I thought we were ILP64 on 64-bit archs, but you're right. And I ought to know better... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: New rc.d init script roadmap
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
Your rcorder patch is incorrect.
Here's a correct patch. Does anybody mind if I commit this and
connect rcorder(8) to the build?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
Index: Makefile
===
RCS file: /home/ncvs/src/sbin/rcorder/Makefile,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 Makefile
--- Makefile 16 Jun 2001 07:16:14 - 1.1.1.1
+++ Makefile 18 Oct 2001 19:44:57 -
@@ -3,11 +3,12 @@
PROG= rcorder
SRCS= ealloc.c hash.c rcorder.c
MAN= rcorder.8
+WARNS?= 2
LDADD+= -lutil
DPADD+= ${LIBUTIL}
# XXX hack for make's hash.[ch]
-CPPFLAGS+= -DORDER
+CFLAGS+= -DORDER
.include bsd.prog.mk
Index: rcorder.c
===
RCS file: /home/ncvs/src/sbin/rcorder/rcorder.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 rcorder.c
--- rcorder.c 16 Jun 2001 07:16:14 - 1.1.1.1
+++ rcorder.c 18 Oct 2001 19:45:27 -
@@ -41,7 +41,11 @@
#include stdlib.h
#include string.h
#include unistd.h
+#if defined(__NetBSD__)
#include util.h
+#else
+char *fparseln(FILE *, size_t *, size_t *, const char[3], int);
+#endif
#include ealloc.h
#include sprite.h
Re: My contributions to the close a PR campaign
Seth Kingsley [EMAIL PROTECTED] writes: Why not remove it after using it to restore the mixer state? It would only exist to survive a reboot. You'd have to reset everything manually after a crash. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: fastforwarding?
Wes Peters [EMAIL PROTECTED] writes: The description there isn't very forthcoming. fastforwarding caches the results of a route lookup for destination addresses that are not on the local machine, and uses the cached route to short-circuit the normal (relatively slow) route lookup process. The packet flows directly from one layer2 input routine directly to the opposing layer2 output routine without traversing the IP layer. And more importantly, without traversing ipfw or ipfilter. In other words, don't use this on a firewall. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: What happens to a connection between a select and accept...
Sean Chittenden [EMAIL PROTECTED] writes: It is possible to select(2) a socket for the purposes of doing an accept() by selecting it for read. This simply means that select(2) will consider a listen socket readable when there's at least one incoming connection in that socket's listen queue. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of encryption hardware support in FreeBSD
Soren Kristensen [EMAIL PROTECTED] writes: As I now has prototypes avaliable of low cost PCI and MiniPCI boards, moving to production in a couple of weeks, I would like to check up on the work, as I would really like to see FreeBSD support. The boards are now supported in OpenBSD 2.9. OK, so if I understand correctly, the encryption hardware in question offers a high-speed hardware implementation of the encryption algorithms used by IPSec, so it's a matter of a) having support code that interfaces with the hardware, possibly with a device interface to allow userland apps access to the encryption hardware and b) making our (well, KAME's) IPSec code use that instead of doing the encryption in software. Is that it, or did I misunderstand something? Now, if you want FreeBSD support for your hardware, all you have to do is find a willing developer whistles innocently, send him a sample board (or preferably two, for a full circuit, but one will do) with complete documentation and any additional resources you are willing and able to provide, and then wait a bit. Simply asking for someone to port the OpenBSD driver will not do - OpenBSD and FreeBSD are not very similar at the kernel level, and as others have stated before in a different context, driver source does not constitute adequate documentation. It helps, but it's neither sufficient nor necessary. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of encryption hardware support in FreeBSD
Karsten W. Rohrbach [EMAIL PROTECTED] writes: i think ipsec crypto abstraction into hardware is one side of the medal, but the other side -- to be polished first -- ist getting openssl onto the iron. What you're basically trying to say is that you want a userland interface to the crypto hardware, so that OpenSSL can take advatange of it if it's present? as i said, there is a 3.x freebsd driver, would this help? i am not into writing drivers ;-) Allow me to repeat myself: driver source does not constitute adequate documentation. It helps, but it's neither sufficient nor necessary. A 3.x driver *could* be ported forward to 4.x and 5.x, but the required changes are not trivial (newbus, SMPng...) and you'd still need sample boards for testing and debugging, and docs for reference when you don't understand what the existing driver is trying to do. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of encryption hardware support in FreeBSD
Karsten W. Rohrbach [EMAIL PROTECTED] writes: yup, exactly. to me it seems to be a major problem to get some unified api out of openssl adressing fucnctions on the hardware -- i simply do not know how other crypto chipsets do it, i just investigated the rainbow board. they got a patch against openssl 0.9.5 i think, that glues in the driver calls instead of standard lib functions. Can you dig out this patch for me? It would be a big win if the userland interface to Soren's hardware were compatible with Rainbow's driver. yes yes yes ;-) you are perfectly right here. i just wanrted to mention that there is an _existant_ driver and patch against the openssl lib, also some test programs to look if the driver works, for freebsd 3.x. This would be useful for ensuring compatibility with Rainbow's stuff, especially if, as you say, they have a 4.1 version out now. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of encryption hardware support in FreeBSD
Soren Kristensen [EMAIL PROTECTED] writes: SSL is for secure web access, and the main need is for Public Key generating. This don't really have anything to do with the IP stack. Afaik, OpenSSL is more like a extension to the web server software. Try 'man openssl', or just 'openssl -help'. You'll be surprised... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: What happens to a connection between a select and accept...
Sean Chittenden [EMAIL PROTECTED] writes: Quick question. Anyone know how gracefully the kernel handles a socket connection that is killed by the client between a select and accept call? I don't expect any problems, but I know there was a race condition in Linux that caused all kinds of nasty bugs and problems. There was one in FreeBSD too. It's been fixed; accept(2) will return -1 and set errno to ECONNABORTED, which you'd know if you'd RTFM. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
Andy [EMAIL PROTECTED] writes: http://linuxtoday.com/news_story.php3?ltsn=2001-06-20-018-20-NW-MS-SW Doesn't this mean software developed with Microsoft's SDK is viral? And doesn't *that* mean you're not allowed to develop it with Microsoft's SDK? And doesn't this sound a bit circular? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Your new web site
David Preece [EMAIL PROTECTED] writes: Is anyone close enough to drive round and have a quiet word? Netiquette for instance. Or asking for trouble. Or lookity shiny new baseball bat? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: real time
Joel Sherrill [EMAIL PROTECTED] writes:
RTEMS is not pure-GPL -- it does allow binary redistribution.
So does pure GPL, as long as you make the sources available. If you
mean that you can redistribute (potentially modified) RTEMS binaries
without providing the source code, then you've effectively got a
{BSD,MIT,Apache} license (except for a few details about attributions
and the naming of derivative software), and you might as well make the
change in name as well as in function.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: whois(1) patch for review
Mike Barcroft [EMAIL PROTECTED] writes: Arg.. I wish you had contacted me before doing this work. From looking at your patch, your using an old copy of my work. The newest one is available at: http://testbed.q9media.net/freebsd/whois.patch and will be committed very-shortly-now(tm). Since Mike's patch is a style cleanup with no functional impact except plugging a memory leak, I feel it's better to commit it first, and merge in Alexey's patch later, after it's been reviewed by this forum. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
Peter [EMAIL PROTECTED] writes: GPL is great for simple things, that don't create any standard, but work upon one. But as even RMS [I think it was RMS] agreed, BSD license is much better for 'standards'. -- ie the oog format was BSD licensed and the GPL people endorsed it because this would allow oog to grow, as now corps can [try to] make money off a format in their proprietary devices, unlike if oog was GPLed, it would die as no one would support it except for the linux folks. Beware. Richard Stallman also advocates changing to more restrictive licenses once the software (in general, not ogg in particular) has gather sufficient momentum. He wrote a diatribe a year or two back where he argued that the time had come to switch glibc (IIRC) from LPGL to GPL so that all the commercial software vendors who had become dependent on Linux would be forced to GPL their software or fold. Talk about bait-and-switch! It's for this reason, by the way, that the LGPL has been renamed from Library GPL to Lesser GPL. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Article Network performance by OS
Rik van Riel [EMAIL PROTECTED] writes: Not quite. Linux distributions tend to be extremely conservative in the IDE options (DMA, interrupt unmasking, write caching, etc. all disabled) while FreeBSD seems to have write caching and DMA on by default... Ahem. First of all, Linux' file system (ext2fs) is more or less equivalent, in terms of performance and integrity, to async ffs. This gives Linux a big performance edge out of the box, and FreeBSD a big reliability edge - but benchmark authors rarely care about fs integrity, as shutting off the power during heavy disk I/O isn't generally part of their benchmark. Second, we tried turning write caching on ATA drives off by default, and boy were you (the user community) pissed. Yes, turning wc off shows you just how crappy those non-tagged-queueing 4000 RPM ATA drives you picked up at Fry's for some pocket change are. So we turned it back on. If you're not happy with that, put 'hw.ata.wc=0' in your /boot/loader.conf and they'll be off after the next reboot. Or get real disks. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: modified natd again
Urban Olsson [EMAIL PROTECTED] writes: Another strange thing is that when I try to use tcpdump it doesn´t show all packets. No packets are dropped by kernel but tcpdump have received packets but don´t show them. Could this in some way be related. Use the -n option. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: strangeness in web interface of send-pr
Giorgos Keramidas [EMAIL PROTECTED] writes: You can clearly see that (in line 3), I have chosen to view only PRs whose state is `open' AND (line 2) severity is `critical', in an effort to help closing first those PRs that are more important. Just ignore the severity and priority. They are set by the submitter and rarely if ever changed by committers, and are usually far more indicative of the submitter's state of mind than of the PR's importance. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: import NetBSD rc system
Kevin Way [EMAIL PROTECTED] writes: I just ordered a spare machine a few days ago. I'll install -CURRENT on it, and start the integration. I've been needing something to keep myself out of trouble. That's our new slogan: FreeBSD - keeping kids off the street DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Patented algorithm in FreeBSD
Mike Smith [EMAIL PROTECTED] writes: Every time I tease my housemate's cat with a laser pointer, I am violating a US patent. (No, really.) I need to get a laser pointer... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Tuning, security, firewall man pages up for review
Matt Dillon [EMAIL PROTECTED] writes: http://apollo.backplane.com/FreeBSD/tuning.html In the kernel config tuning section, you've misspelt NSFBUFS as NFSBUFS, which doesn't exist. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sysctl(8) and opaque MIB entries
Sheldon Hearn [EMAIL PROTECTED] writes: That would meet my needs. Are you sure this is a better route than allowing a limiting parent node to be specified along with -A and -a? Seems to me that the latter would avoid introducing yet more options and the functionality I'm proposing seems intuitive to me and Peter at least. :-) Maybe so, but I've always thought -A and -X were *counter*intuitive, and the current behaviour of 'sysctl foo' where foo is the name of an opaque variable is, to say the least, surprising. Adding the -x option makes it slightly less so. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sysctl(8) and opaque MIB entries
Sheldon Hearn [EMAIL PROTECTED] writes: Is there a good reason why sysctl(8) won't display _any_ output for opaque MIB entries named as arguments? Yes it will, with -X. The interesting question is why there isn't an option to make it display just one variable in hex, and why it doesn't print a message when it omits printing an opaque variable. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sysctl(8) and opaque MIB entries
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
Sheldon Hearn [EMAIL PROTECTED] writes:
Is there a good reason why sysctl(8) won't display _any_ output for
opaque MIB entries named as arguments?
Yes it will, with -X. The interesting question is why there isn't an
option to make it display just one variable in hex, and why it doesn't
print a message when it omits printing an opaque variable.
Here's a patch that:
1) introduces the -x option, which makes opaque variables visible.
2) allows variables to be set without the -w option.
3) undocuments the now-superfluous -w option.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
Index: sysctl.8
===
RCS file: /home/ncvs/src/sbin/sysctl/sysctl.8,v
retrieving revision 1.31
diff -u -r1.31 sysctl.8
--- sysctl.8 2001/02/01 16:32:12 1.31
+++ sysctl.8 2001/05/07 17:21:58
@@ -40,14 +40,11 @@
.Nd get or set kernel state
.Sh SYNOPSIS
.Nm
-.Op Fl bNn
-.Ar name ...
+.Op Fl bNnx
+.Ar name Ns Op = Ns Ar value
+.Ar ...
.Nm
-.Op Fl bNn
-.Fl w
-.Ar name Ns = Ns Ar value ...
-.Nm
-.Op Fl bNn
+.Op Fl bNnx
.Fl aAX
.Sh DESCRIPTION
The
@@ -69,10 +66,10 @@
flag; for the opaque values,
information about the format and the length is printed in addition the first
few bytes is dumped in hex.
-.It Fl X
+.It Fl X
Same as
.Fl A
-except the entire value of opaque variables is hexdumped.
+.Fl x .
.It Fl N
Show only variable names, not their values.
.It Fl n
@@ -87,17 +84,8 @@
Force the value of the variable(s) to be output in raw, binary
format. No names are printed and no terminating newlines are output.
This is mostly useful with a single variable.
-.It Fl w Xo
-.Ar name Ns = Ns Ar value ...
-.Xc
-Set the MIB
-.Ar name
-to the new
-.Ar value .
-If just a MIB style
-.Ar name
-is given,
-the corresponding value is retrieved.
+.It Fl x
+Display opaque variables (in hex).
.El
.Pp
The information available from
Index: sysctl.c
===
RCS file: /home/ncvs/src/sbin/sysctl/sysctl.c,v
retrieving revision 1.31
diff -u -r1.31 sysctl.c
--- sysctl.c 2001/01/14 19:08:58 1.31
+++ sysctl.c 2001/05/07 17:10:44
@@ -58,7 +58,7 @@
#include string.h
#include unistd.h
-static int Aflag, aflag, bflag, Nflag, nflag, wflag, Xflag;
+static int Aflag, aflag, bflag, Nflag, nflag, xflag;
static int oidfmt(int *, int, char *, u_int *);
static void parse(char *);
@@ -70,12 +70,10 @@
usage(void)
{
- (void)fprintf(stderr, %s\n%s\n%s\n%s\n%s\n,
- usage: sysctl [-bNn] variable ...,
- sysctl [-bNn] -w variable=value ...,
- sysctl [-bNn] -a,
- sysctl [-bNn] -A,
- sysctl [-bNn] -X);
+ (void)fprintf(stderr, %s\n%s\n%s\n,
+ usage: sysctl [-bxNn] variable[=value] ...,
+ sysctl [-bxNn] -a,
+ sysctl [-bxNn] -A);
exit(1);
}
@@ -86,7 +84,7 @@
setbuf(stdout,0);
setbuf(stderr,0);
- while ((ch = getopt(argc, argv, AabNnwX)) != -1) {
+ while ((ch = getopt(argc, argv, AabNnwxX)) != -1) {
switch (ch) {
case 'A':
Aflag = 1;
@@ -104,10 +102,14 @@
nflag = 1;
break;
case 'w':
- wflag = 1;
+ /* compatibility */
break;
+ case 'x':
+ xflag = 1;
+ break;
case 'X':
- Xflag = Aflag = 1;
+ /* backwards compatibility */
+ xflag = Aflag = 1;
break;
default:
usage();
@@ -116,7 +118,7 @@
argc -= optind;
argv += optind;
- if ((wflag (Aflag || aflag)) || (Nflag nflag))
+ if (Nflag nflag)
usage();
if (Aflag || aflag)
exit (sysctl_all(0, 0));
@@ -146,17 +148,12 @@
bufp = buf;
snprintf(buf, BUFSIZ, %s, string);
if ((cp = strchr(string, '=')) != NULL) {
- if (!wflag)
- errx(2, must specify -w to set variables);
*strchr(buf, '=') = '\0';
*cp++ = '\0';
while (isspace(*cp))
cp++;
newval = cp;
newsize = strlen(cp);
- } else {
- if (wflag)
- usage();
}
len = name2oid(bufp, mib);
@@ -166,7 +163,7 @@
if (oidfmt(mib, len, 0, kind))
err(1, couldn't find format of oid '%s', bufp);
- if (!wflag) {
+ if (newval == NULL) {
if ((kind CTLTYPE) == CTLTYPE_NODE) {
sysctl_all(mib, len);
} else {
@@ -468,14 +465,14 @@
}
/* FALL THROUGH */
default:
- if (!Aflag)
+ if (!Aflag !xflag)
return (1);
if (!nflag)
printf(%s: , name);
printf(Format:%s Length:%d Dump:0x, fmt, len);
while (len--) {
printf(%02x, *p++);
- if (Xflag || p val+16)
+ if (xflag || p val+16)
continue;
printf(...);
break;
Re: sysctl(8) and opaque MIB entries
Sheldon Hearn [EMAIL PROTECTED] writes: On 07 May 2001 18:51:22 +0200, Dag-Erling Smorgrav wrote: Yes it will, with -X. The interesting question is why there isn't an option to make it display just one variable in hex, and why it doesn't print a message when it omits printing an opaque variable. Do you think it'd be okay to allow an argument to -a and -A that specifies the sysctl node from which to descend? Have you tried e.g. 'sysctl hw' lately? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sysctl(8) and opaque MIB entries
Peter Pentchev [EMAIL PROTECTED] writes: How about e.g. 'sysctl -a hw', which still shows *all* MIB's? At least on ref5 as of this very moment.. Yes, because '-a' means 'show all non-opaque' and 'hw' is ignored. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sysctl(8) and opaque MIB entries
Peter Pentchev [EMAIL PROTECTED] writes: On Mon, May 07, 2001 at 07:52:15PM +0200, Dag-Erling Smorgrav wrote: Peter Pentchev [EMAIL PROTECTED] writes: How about e.g. 'sysctl -a hw', which still shows *all* MIB's? Yes, because '-a' means 'show all non-opaque' and 'hw' is ignored. OK, so I slipped up; so how about this: Yes, what about this? It's still the exact same thing, the -A and -X options are variants of the -a option. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FPU exception, kernel panic
Valentin Nechayev [EMAIL PROTECTED] writes: (I cannot even guarantree 50% this is the same problem, but...) There were some reports in current@ about incorrect usage of i586_bzero() which uses FPU for zero-filling. It generated random kernel panics mainly on K6-2, also on P5-MMX and similars. You can try to disable such bzero, but IMHO it is reasonable to upgrade to 4.3-RELEASE (RELENG_4_3) first. 1) this bug only occurs on -CURRENT systems that have interrupt preemption enabled (i.e. anything newer than february) 2) the symptoms are nowhere near what's described here anyway - you'd see the kernel stack getting smashed, not an FPU exception. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FPU exception, kernel panic
Rohit Rakshe [EMAIL PROTECTED] writes: 1. The code which I added in kernel does not use any floats. So I am wondering why this problem should happen at all. The kernel uses the FPU to optimize certain bcopy- or bzero-like operations. 2. pc register in FPU should give address of the instruction which caused this exception, right ? Possibly. I'm not very familiar with the FPU. 3. If yes, how do I translate this 48 bit address in a linear address which gdb can understand ? You don't. FreeBSD uses a flat address space, you can disregard the segment descriptor. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: squeeze freeBSDs' kernel size
Aman [EMAIL PROTECTED] writes: kldstat shows the kernel as a loaded module. does it mean the kernel after getting in the core is resident to it's complete physical size. Kldstat will tell you exactly how much space the kernel text (i.e. actual code) is taking up. As to memory used for kernel data, try 'vmstat -m'. my question is, does the pagedaemon carry out any sort of paging or segmentation on the kernel and it's loadable modules though the latter seems necessary. No. how much size can be really squeezed out of the kernel Ask the freebsd-small mailing list. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Getting peer credentials on a unix domain socket
Alfred Perlstein [EMAIL PROTECTED] writes: The silly part of it is that the socket's initial credentials might be different than the holder's credentials. That's a feature, just like you can open /dev/io as root, then drop root privs and do direct I/O to your heart's content even if you're no longer root. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Fetching an index of an FTP site using fetch...
Sean Chittenden [EMAIL PROTECTED] writes: Does anyone have any ideas as far as a way in which it'd be possible to fetch a directory index using fetch? No. It's not intended for that purpose, though it would be a nice addition. PS I've looked through the source of fetch and libfetch, and it seems like there's some stub code that hasn't been flushed out completely. Anyone know of any plans to finish this up? Feel free to send patches :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
