Re: Replacing GNU grep revisited
On Sunday, June 22, 2003, Sean Farley wrote: Reasons to consider for switching: 1. GNU's grep -r option is broken according to the following post. The only thing I have noticed is that FreeGrep has more options for controlling how symbolic links are traversed. http://groups.google.com/groups?hl=enlr=lang_enie=UTF-8selm=xzp7kchblor.fsf_flood.ping.uio.no%40ns.sol.net A workaround for this problem in the meantime would be to use find directory -type f | xargs grep EXPR Just FYI. -- Chris Costello[EMAIL PROTECTED] FreeBSD Project http://www.FreeBSD.org/ TrustedBSD Project http://www.TrustedBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Request for info from SiS chipset owners
$ pciconf -l chip0@pci0:0:0: class=0x06 card=0x chip=0x07351039 rev=0x01 hdr=0x00 pcib2@pci0:1:0: class=0x060400 card=0x chip=0x00011039 rev=0x00 hdr=0x01 isab0@pci0:2:0: class=0x060100 card=0x chip=0x00081039 rev=0x00 hdr=0x00 ohci0@pci0:2:2: class=0x0c0310 card=0x0a141019 chip=0x70011039 rev=0x07 hdr=0x00 ohci1@pci0:2:3: class=0x0c0310 card=0x0a141019 chip=0x70011039 rev=0x07 hdr=0x00 atapci0@pci0:2:5: class=0x010180 card=0x55131039 chip=0x55131039 rev=0xd0 hdr=0x00 pcm0@pci0:2:7: class=0x040100 card=0x030013f6 chip=0x70121039 rev=0xa0 hdr=0x00 sis0@pci0:3:0: class=0x02 card=0x0a141019 chip=0x09001039 rev=0x90 hdr=0x00 ed0@pci0:13:0: class=0x02 card=0x802910ec chip=0x802910ec rev=0x00 hdr=0x00 none0@pci1:0:0: class=0x03 card=0x03001039 chip=0x03001039 rev=0x90 hdr=0x00 -- Chris Costello[EMAIL PROTECTED] FreeBSD Project http://www.FreeBSD.org/ TrustedBSD Project http://www.TrustedBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Anyone like obscure stdio problems?
On Sunday, December 29, 2002, Jordan Hubbard wrote: I have no problem admitting that I've traced through the innards of _fseeko a few times now and am no closer to finding out exactly where the problem is, though I have a suspicion it has to do with when the file pointer's buffer is allocated and initially populated. In any case, here's a particularly weird one from the Apple Files that also occurs on FreeBSD The following program, also available from http://narcissus.queasyweasel.com/fump.c, demonstrates the problem. If you change the top #define of FIRST_SEEK to 0 instead of 1, the program will work. If you leave it at 1, the initial (and theoretically redundant and no-op) fseek on readMidFP will bugger up stdio's internal state somehow. If anyone with more stdio-fu than me would like to poke at it, I'd be interested in hearing what you find out. If this is breaking some undocumented rule of stdio I'd like to know that too so that I can document it both in FreeBSD and Mac OS X. Thanks. As we discussed on IRC, the problem lies in line 254 of libc/stdio/fseek.c. Since in your case the buffer is not modified (no __SMOD flag, see a few lines back in fseek.c), it assumes that the buffer that it filled after the first fseek but before the write is still OK, and simply copies out from it when you read it looking for your B's. Placing a pointless fgetln() after the first fseek() will make this obvious: if (fseek(rp, (long)(i / 2), SEEK_SET) != 0) err(1, fseek on rp); (void)fgetln(rp, throwaway); fgetln() will set __SMOD for rp's buffer and so stdio is forced to discard it and refill it from the file (which contains the B's). -- Chris Costello[EMAIL PROTECTED] FreeBSD Project http://www.FreeBSD.org/ TrustedBSD Project http://www.TrustedBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: troff vs. DocBook (was: Request for submissions: FreeBSD Bi-Monthly Development Status Report (fwd))
[Cc: list massively trimmed.] On Monday, July 22, 2002, Greg 'groggy' Lehey wrote: IMO the tags aren't the problem with DocBook. It's just *really* difficult to get good-looking results with. I've actually converted the FreeBSD book into DocBook (anybody want a perl script?), but jade can't format it, and gmat is a real kludge. Theoretically, DocBook is better, but I want something that works. Well, getting something that looks good out of DocBook is a trivial exercise for somebody who knows how to handle the formatting-related bits (i.e. the *.dsl stylesheets). Comparing ms(7) and DocBook is sort of like comparing apples and oranges. Basically when you're writing a DocBook document, you're simply marking up the information--telling DocBook what's what in terms of paragraphs, lists, host names, the like. ms(7) macros allow you to do a lot of the formatting on your own. I imagine that ORA is moving/has moved away from it for that reason: they want their books to look exactly alike, which is easily accomplished by having authors submit works in DocBook and applying their own `custom' stylesheet. -- +---+---+ | Chris Costello| Diagnostics are the programs that | | [EMAIL PROTECTED] | run when nothing else will. | +---+---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: chowning problem or somthing...
On Tuesday, March 12, 2002, Bri wrote: %pwd /usr/home %chown testuser4:staff testuser4/ %ls -l | grep testuser4 drwxr-xr-x 2 testuser3 staff 512 Feb 21 15:06 testuser4 %whoami root %uname -r 4.5-RELEASE Do testuser3 and testuser4 have the same UID? -- +---+-+ | Chris Costello| The computer is mightier than the pen, | | [EMAIL PROTECTED] | the sword, and usually, the programmer. | +---+-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Assembler programmer needed
[Thread moved to -jobs] On Monday, January 28, 2002, Lorene Ledingham wrote: Hi, My name is Lorene Ledingham and I am a professional recruiter. A client of mine is looking for a programmer with background in Assembly Language, C++, Unix, etc. and if anyone on this list can help me with names of people I can network with I would greatly appreciate it. Please respond by email or call. If this is not a good source for networking, please accept my apologies. This is not the correct mailing list to solicit/recruit employees. There is a mailing list for those posting resumes/job offers: [EMAIL PROTECTED] Followups to this thread should be sent to that list. -- +---+---+ | Chris Costello| You depend too much on computers for information. | | [EMAIL PROTECTED] | | +---+---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD.org SIte
[Thread moved to freebsd-doc] On Sunday, January 20, 2002, MSC Sharp wrote: I was just wondering if the FreeBSD team would accept a new web site from an emerging web design company. All work would be done for free of course and would consist of remodeling the whole or any part of the web site that your organization requested. If you are interested please contact me with some specifications of work you would like done or just a yes or no reply. If you accept we will contact you again in a few weeks to show you some samles of our work. You may want to consult with Nik Clayton and the FreeBSD Documentation ([EMAIL PROTECTED] and [EMAIL PROTECTED] respectively) on this. We are currently in the process of updating the Web site's layout anyway, making a more extensive use of XML and XSLT than before (or at least, a more _proper_ use). That is, if you're serious about helping. :) -- +---+--+ | Chris Costello| Computer and car salesmen differ in that | | [EMAIL PROTECTED] | the latter know when they are lying. | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: jail.c.patch (allowing to use hostnames when invoking jail(8))
On Saturday, November 24, 2001, Igor M Podlesny wrote:
i = inet_aton(argv[3], in);
- if (!i)
- errx(1, Couldn't make sense of ip-number\n);
+ if (!i) {
+ /* check if it is resolveable */
+ struct hostent *hp;
+ hp = gethostbyname(argv[3]);
+ if (hp == NULL) {
+ errx(1, Couldn't make sense of the jail address\n);
+ }
+ else {
+ char **p = hp-h_addr_list;
+ if (p[1] != NULL) {
+ errx(1, Jail should have only one ip-address
associated with!\n);
+ }
+ else {
+ memcpy(in.s_addr, p[0], sizeof(in.s_addr));
+ }
+ }
+ }
I'd rewrite the above (`i = inet_aton' all the way down) as
hp = gethostbyname(argv[3]);
if (hp == NULL) {
errx(1, %s: %s, argv[3], hstrerror(h_errno));
}
in = *(struct in_addr *)hp-h_addr_list[0];
This makes the call to inet_aton() unnecessary (and really
shortens the code!).
--
+---+--+
| Chris Costello| It is easier to change the specification |
| [EMAIL PROTECTED] | to fit the program than vice versa. |
+---+--+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: head(1) speedup
On Friday, November 02, 2001, Alfred Perlstein wrote: I'm curious--does using fgetln here always result in a win, or just with short lines? I'm thinking of the impact of realloc and memcpy on speed. Ugh, I should have checked that, my guess is that performance isn't going ot be much worse, if there is a real problem I'll rework it some more, possibly using fread instead of fgetln. Well, fgetln should probably be quicker than fread, due to the fact that fgetln will buffer the next incoming line and return a pointer into the stdio internal buffer, while fread has to copy out N times into a separate buffer (also from the read buffer). -- +---+--+ | Chris Costello| ...now touch these wires to your tongue! | | [EMAIL PROTECTED] | | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Request for submissions: FreeBSD Monthly Development Status Report
On Sunday, October 14, 2001, Robert Watson wrote: For future reports, we will also support SGML submissions using a style sheet developed by Nik Clayton. Those who wish to submit reports in the aforementioned XML format, see http://www.FreeBSD.org/news/status/report-sample.xml -- and remember, the deadline's coming up in just two days! -- +---++ | Chris Costello| That does not compute. | | [EMAIL PROTECTED] || +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: My contributions to the close a PR campaign
On Thursday, October 11, 2001, Mike Meyer wrote: kern/25266 chrisfdesc file system in -STABLE locks up during nightly builds Fixed in -current, awaiting decision as to whether or not it should be MFC'ed. If it's not going to be MFC'ed, it should be closed. Hopefully, fdesc will be taken out of stable at about that time as well. Thank you for raising this report; I've just sent an email to -arch on this subject and plan on merging the code more or less as it is in -CURRENT, lest the issue of people being astonished by the somewhat different layout be too great (which I doubt, as it seems very few people actually use it.) -- +---+-+ | Chris Costello| Aibohphobia:| | [EMAIL PROTECTED] | The fear of palindromes | +---+-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Question about pthread
On Thursday, October 04, 2001, Oleg Golovanov wrote:
static void *coms(void *arg)
{
pthread_detach(pthread_self());
write((int)arg, Test, sizeof(test));
close((int)arg);
return(NULL);
}
For starters, this function should be rewritten as
static void *coms(void *arg)
{
int fd;
fd = *(int *)arg;
pthread_detach(pthread_self());
write(fd, Test, 4);
close(fd);
return (NULL);
}
Because you're passing the _address_ of `confd', not the
value. You must first cast arg to an int pointer, and then
dereference it (and assign its value to `fd').
--
+---+---+
| Chris Costello| CCITT - Can't Conceive Intelligent Thoughts Today |
| [EMAIL PROTECTED] | |
+---+---+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: Question about pthread
On Wednesday, October 03, 2001, Chris Costello wrote: Because you're passing the _address_ of `confd', not the Er, sorry, `connfd' _is_ the address to a value (it's a pointer). But you're still passing an address, and I believe what I posted will solve the problem. -- +---+---+ | Chris Costello| Implementation is the sincerest form of flattery. | | [EMAIL PROTECTED] | | +---+---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel Hacker task: improve vnode-v_tag
On Tuesday, September 18, 2001, Maxim Sobolev wrote: Oh, yes, you are correct obviously (don't know what I was thinking about). In this case, it looks like v_tag is redundant, because f_fstypename could be used instead in a few places where v_tag is abused (the same applies to the statfs.f_type because essentually it is the same thing as v_tag). Poul, what do you think about it? In the meantime, I found another place in the kernel where VT_* macros are [ab]used - it is Linuxlator, attached please find patches to fix it - please review. Actually, I've got work that's a lot like the patch you attached to this message; when I can merge some of the latest changes, I'll have a diff at least to KSE_PRE_MILESTONE_2. Give me more time and I'll have a diff to HEAD. -- +---++ | Chris Costello| Performance is easier to add than clarity. | | [EMAIL PROTECTED] || +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel Hacker task: improve vnode-v_tag
On Saturday, September 08, 2001, Maxim Sobolev wrote:
I don't like idea to hardcode the same string (procfs), with the
same meaning in several places across kernel. As for your proposition
to use f_fstypename to set v_tag, it is even more bogus because
value of the f_fstypename is supplied from the user level, so
potentially it could be anything and we can't make any reasonable
assumptions about mapping between its value and type of the filesystem
in question.
How do you figure? The contents if `f_fstypename' must match
a configured file system exactly, so it could _not_ be anything.
To quote sys/kern/vfs_syscalls.c:mount():
if ((error = copyinstr(SCARG(uap, type), fstypename, MFSNAMELEN, NULL))
vput(vp);
return (error);
}
for (vfsp = vfsconf; vfsp; vfsp = vfsp-vfc_next)
if (!strcmp(vfsp-vfc_name, fstypename))
break;
if (vfsp == NULL) {
/* ... try and load a module ... */
/* ... fail if no module can be found, or no
* matching VFS is loaded */
}
--
+---+---+
| Chris Costello| You depend too much on computers for information. |
| [EMAIL PROTECTED] | |
+---+---+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel Hacker task: improve vnode-v_tag
On Saturday, September 08, 2001, Maxim Sobolev wrote:
No, it should be pre-defined, because otherwise we will be
unable to use strcmp() in a few places when v_tag is abused.
So in these cases (which ideally would be eliminated rather
than considered for support), why can't you do:
if (strcmp(vp-v_tag, procfs) == 0) {
rather than
if (strcmp(vp-v_tag, VT_PROCFS) == 0) {
in the case of procfs? As for a solution to the problem, I'm
not entirely sure, but maybe this is a case for either a new
vnode flag, `VUNSAFE', for files which should be closed across
exec() calls (this is all setugidsafety() and its hackish
is_unsafe() companion are used for as far as I can tell).
--
+---++
| Chris Costello| Let the machine do the dirty work. |
| [EMAIL PROTECTED] |- Elements of Programming Style |
+---++
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: tiny patch to pkg_add
On Friday, September 07, 2001, Leo Bicknell wrote: I think Chris's version is right, although if you're writing a security app, or just want to be overly paranoid in general you could use: bzero((void *)packagesite, sizeof(packagesite)); That's unnecessary unless you know you're going to be reading data from that string starting somewhere other than packagesite[0];. And the `void *' cast is unnecessary, as an array is converted to a pointer when passed to a function, and any data pointer is also implicitly converted to a `void *' pointer where necessary. -- +---++ | Chris Costello| Save energy: | | [EMAIL PROTECTED] | Drive a smaller shell. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel Hacker task: improve vnode-v_tag
On Saturday, September 08, 2001, Poul-Henning Kamp wrote: No actually not, I want something short and predictable like VT_CODA. How about my second suggestion: making v_tag point to mp-mnt_stat.f_fstypename, or a copy thereof? -- +---+--+ | Chris Costello| Why do we want intelligent terminals | | [EMAIL PROTECTED] | when there are so many stupid users? | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel Hacker task: improve vnode-v_tag
On Tuesday, September 04, 2001, Maxim Sobolev wrote: Content-Description: ASCII C program text Index: coda/coda.h === RCS file: /home/ncvs/src/sys/coda/coda.h,v retrieving revision 1.9 diff -d -u -r1.9 coda.h --- coda/coda.h 1999/12/29 04:54:30 1.9 +++ coda/coda.h 2001/09/04 18:46:42 @@ -41,7 +41,7 @@ #ifndef _CODA_HEADER_ #define _CODA_HEADER_ - +#define VT_CODA VT_CODA ... I don't think that the point of this is to use a string like that, but rather a descriptive string, i.e. #define VT_FDESCFS file-descriptor file system #define VT_NFS network file system But is it necessary that you really use those defines? The idea is not to use them globally. Perhaps getnewvnode() should get the string from `mp-mnt_stat.f_mntfromname', instead... -- +---+---+ | Chris Costello| As far as we know, our computer has never | | [EMAIL PROTECTED] | had an undetected error.- Weisert | +---+---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel Hacker task: improve vnode-v_tag
On Friday, September 07, 2001, Chris Costello wrote: But is it necessary that you really use those defines? The idea is not to use them globally. Perhaps getnewvnode() should get the string from `mp-mnt_stat.f_mntfromname', instead... ^ Er, fstypename... -- +---++ | Chris Costello| Unprecedented performance: | | [EMAIL PROTECTED] | Nothing ever ran this slow before. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Should URL's be pervasive.
On Friday, August 31, 2001, Michael Sinz wrote: I too have been hoping for (and building internal tools) that work this way. I really wish you could just do: open(nfs://server.name.dom/directory/file.txt) and have it work. That would be nice. (Replace the above with ftp: or http: or whatever other protocol would provide read and/or write access.) Anyway, I don't see it happening quickly but I don't see it as a bad thing and I would guess that it will eventually get to that point. (The network includes your local machine so why not) Whatever happened to not distinguishing different types of file systems from one another in pathnames? And are you suggesting that we add network overhead (I'd still imagine lo0 can't help speeding things up...) to file system accesses? -- +---+-+ | Chris Costello| It's not hard to meet expenses, they're everywhere. | | [EMAIL PROTECTED] | | +---+-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Should URL's be pervasive.
On Friday, August 31, 2001, Joseph Mallett wrote: Check out ftpfs in the HURD. That might be a better way to do it. No, I think that we're better off with NFS... -- +---+--+ | Chris Costello| Help support helpless victims of computer error. | | [EMAIL PROTECTED] | | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Should URL's be pervasive.
On Friday, August 31, 2001, Leo Bicknell wrote: Presumably 'file:/etc/passwd' would not go through lo0. I understood his statement (`the network includes the local machine') to imply that he wants to do nfs://localhost/etc/passwd rather than file:/etc/passwd. -- +---++ | Chris Costello| All the simple programs have been | | [EMAIL PROTECTED] | written, and all the good names taken. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Proposed Utility - detach(1)
On Friday, August 24, 2001, Mike Barcroft wrote: I would appreciate comments on the usefulness of a utility which would allow one to detach a process from a TTY. I imagine the utility would be very small and just call daemon(3) and execlp(3). Would a utility like this be useful? Is this functionality already available in a system utility? All shells implement this: sh: $ sleep 5 $ [1] 61049 Exit 0 sleep 5 ksh: $ sleep 5 [1] 61052 $ [1] + Donesleep 5 csh: % sleep 5 [1] 61058 % [1]Done sleep 5 etc. Why does this need to be implemented in a separate executable? -- +---++ | Chris Costello| God didn't create the world in 7 days. | | [EMAIL PROTECTED] | He pulled an all-nighter on the 6th. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Silly crackers... NT is for kids...
On Friday, August 17, 2001, Jonathan M. Slivko wrote: I'm saying without any intervention of any kind. -- Jonathan Hence the part about By default. If the person installing FreeBSD does nothing when asked about inetd.conf, no inetd services are enabled. This means telnetd, too. -- +---++ | Chris Costello| Wasting time is an important part of life. | | [EMAIL PROTECTED] || +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
For review: Patch to ps(1) old-style option parsing.
This is pretty low-priority and I don't think it needs to be
MFC'd for the 4.4 release, but there is a small error in ps's
old-style option handling. An outstanding example of this is
when one runs `ps Uroot':
$ ps Uroot
ps: rooT: no such user
ps: No users specified
The problem is that the function ps.c:kludge_oldps_options()
capitalizes any 't' at the end of the option string, regardless
of whether it's a flag or an option argument. The patch attached
to this message should fix the problem.
--
+---++
| Chris Costello| The cost of living hasn't affected its popularity. |
| [EMAIL PROTECTED] ||
+---++
Index: ps.c
===
RCS file: /home/ncvs/src/bin/ps/ps.c,v
retrieving revision 1.40
diff -u -r1.40 ps.c
--- ps.c2001/05/30 03:27:07 1.40
+++ ps.c2001/08/15 20:55:04
@@ -599,8 +599,12 @@
* if last letter is a 't' flag with no argument (in the context
* of the oldps options -- option string NOT starting with a '-' --
* then convert to 'T' (meaning *this* terminal, i.e. ttyname(0)).
+*
+* However, if a flag accepting a string argument is found in the
+* option string, the remainder of the string is the argument to
+* that flag; do not modify that argument.
*/
- if (*cp == 't' *s != '-')
+ if (strcspn(s, MNOoUW) == len *cp == 't' *s != '-')
*cp = 'T';
else {
/*
Re: FreeBSD Monthly Development Status Report, June 2001
On Thursday, June 14, 2001, Alexey Zelkin wrote: ps: But I think it can be good idea to put sgml'ified copy of this report (and others) to web site, like we had Really Quick Newsletter for some time. Any takers ? Hmmm. I just noticed this email. It sounds like a nice idea to keep it in www, actually. Do you mean formatted using DocBook, or just HTML? -- +---++ | Chris Costello| All new: | | [EMAIL PROTECTED] | The software is not compatible with previous versions. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: libc_r locking... why?
On Friday, June 29, 2001, E.B. Dreger wrote: Please pardon the cross-posting; I'd rather keep responses on whichever list is more appropriate. Why are bind(2), accept(2), kevent(2), etc. wrapped in libc_r? Currently, the pthreads implementation is done entirely in userland. This means that a syscall which would normally block needs to have code in it to check if it would block (write(2) is a really simple example of this), and if it would, schedule another thread (cancelling, or blocking, the calling thread) to run, and eventually get back to the thread which is blocking on write, check for/read more data, cancel again, etc., until the requested amount of data has been read or an error occurs. This example, of course, applies to instances where write() is called on a file descriptor which does _NOT_ have O_NONBLOCK set. kevent(2), bind(2), accept(2) etc. all do the same thing for the same reasons. -- +---+-+ | Chris Costello| Advanced design:| | [EMAIL PROTECTED] | Upper management doesn't understand it. | +---+-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: libc_r locking... why?
On Friday, June 29, 2001, E.B. Dreger wrote: Am I correct that libc_r does _not_ use multiple processes to create threads? Grepping for fork in *.c files under /usr/src/lib/libc_r leads me to believe that this is so... That's correct. It's implemented using setjmp/longjmp, and storing stack pointers and the like in thread-specific data structures. -- +---++ | Chris Costello| A bug in the code is worth two | | [EMAIL PROTECTED] | in the documentation. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Monthly Development Status Report, June 2001
[Adding -doc because this applies to the doc project now] On Wednesday, June 13, 2001, Dima Dorfman wrote: If this ends up being the case (i.e., there's an issue approx. once a month), how about archiving them on the web site? We used to have a newsletter, but it quickly grew stale. This sounds like something developers actually might be interested in (there's no glory in writing something if nobody knows about it ;-) ), so it has a much better chance of succeeding. I don't know if it's worth putting the first issue up not knowing if there will be more; anybody else have an opinion on this? I'm thinking perhaps it should be made into part of the doc project. I'm in the middle of converting it into a DocBook article and will post a URL to it soon. -- +---++ | Chris Costello| Where the system is concerned, | | [EMAIL PROTECTED] | you are not allowed to ask Why?. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD
On Thursday, June 07, 2001, tywain.griffen wrote: To whom this concern, Please send me a FreeBSD. My address is: 110 Juniper Dr. Ozark, Al 36360 If anything, this should've gone to [EMAIL PROTECTED], but it really doesn't belong there, either. To get FreeBSD sent to you, please order it from http://www.FreeBSDMall.com/. Thanks. -- +---++ | Chris Costello| Anybody can win, | | [EMAIL PROTECTED] | unless there happens to be a second entry. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: easy way to crash freebsd
On Friday, March 02, 2001, Dan Phoenix wrote: People asking me how this could be used as a local user. Well i guess if you wanted to you could find something root runs that writes to /tmp then umask resolv.conf and echo "" resolv.conf Could you expand on this, please? What does finding a root utility that writes to /tmp have to do with umasking a file? (I've found it rather difficult to umask files in the past.) -- +---+----+ | Chris Costello| I just found the last bug. | | [EMAIL PROTECTED] || +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fdescfs oddities
On Saturday, February 03, 2001, Christian Weisgerber wrote: While we are talking about fdesc(fs), how does it relate to devfs? I.e. will devfs make fdesc useless, or require it, or...? I don't really know yet. The reason I did it was to make it the code used by devfs, but I haven't heard anything about it in a good while. -- +---+--+ | Chris Costello| I do not fear computers. | | [EMAIL PROTECTED] | I fear the lack of them. - Isaac Asimov | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fdescfs oddities
On Thursday, February 01, 2001, Maxime Henrion wrote: I run a 4.2-STABLE machine, world done this morning. I had some troubles with fdescfs. Reading the fdesc(5) manual page, I have to mount the fdescfs like I would mount procfs. But if I compile my kernel with options FDESC or if I load the fdesc.ko kernel module, I have access to /dev/fd/* and /dev/std* without mounting anything. Outdated documentation ? The real problem comes when I actually try to mount fdescfs. I was able to mount it several times on the same place (/dev) and 'mount' reported fdescfs as mounted several times. Just after this, my box locked up. I was able to switch to another virtual tty with alt+Fx but wasn't able to type anything nor to reboot with ctrl+alt+suppr. I've done some work on fdescfs in -CURRENT a while back that gutted a lot of the old code, including what may have been making your shell have difficulties with /dev/tty. The proper way to do it is to union mount it on /dev. I have no idea as to what extent of testing my code has received, so I'm rather reluctant to commit it to -STABLE. There's nothing really wrong with the /dev/fd and /dev/tty you have without fdesc as far as you or your programs are concerned, but the implementation (as opposed to interface) is a bit of a hack. -- +---+---+ | Chris Costello| CCITT - Can't Conceive Intelligent Thoughts Today | | [EMAIL PROTECTED] | | +---+---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Running FreeBSD off of CDROM
On Wednesday, January 24, 2001, Dave Hayes wrote: I was asked recently if it was possible to run a FreeBSD server entirely off of CDROM. Now I know that things like /var need to be writable, and that the initial question as worded was rather naive. However, modulo writable filesystems which can be mounted separately, has anyone ever done something like this? I've never done it personally, but it is extremely possible. What you'd need is a writable medium, preferable a hard disk, with whatever file system you want to use on it, and a CD with a stripped-down FreeBSD installation, complete with a kernel that matches your hardware. When you boot into your CD, and after the CD is mounted as /, mount the disk as a union with the CD /. The result is that you'll have the executables on the CD, but any data being written will go to the disk. It's the same basic model the FreeBSD 'emergency CD' uses--however, the FreeBSD emergency CD mounts an MFS partition for you, instead. I wouldn't be surprised at all if this works out perfectly for you, for whatever reason you need such a setup. -- +---++ | Chris Costello| If at first you don't succeed, | | [EMAIL PROTECTED] | you must be a programmer. | +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Running FreeBSD off of CDROM
On Wednesday, January 24, 2001, Warner Losh wrote: You don't need a writable medium to run FreeBSD. Well, I take that back, you do need a writable partition, but that can be mfs. We run off CF which is mounted read only with the usual rc.diskless tricks for creating /var and /dev. Similar techniques could be used for booting off of cdrom. I'm assuming that there's some data he wants to permenantly store on a disk. But yes, just like the live FS CDROM, MFS can easily be used. -- +---+--+ | Chris Costello| If the code and the comments disagree, | | [EMAIL PROTECTED] | then both are probably wrong. - Schryer | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IP Address Overtaking
On Tuesday, January 23, 2001, Dejvid Zaninovic wrote: I could not find any non-commercial IP Address overtaking solution for FreeBSD so I wrote this simple shell script. If you find it useful you can use it. Just a note: This script doesn't look like it implements anything that our own /bin/sh needs. Should somebody make this into a port, that's one less dependancy. -- +---+--+ | Chris Costello| Herblock's Law: | | [EMAIL PROTECTED] | If it is good, they will stop making it. | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ssh - are you nuts?!?
On Friday, December 22, 2000, [EMAIL PROTECTED] wrote: Thank you for your attention. Next month I'm giving a talk about the evils of SSH. If you don't know anything about it, why do you claim it's evil? -- +---+--+ | Chris Costello| I modem, but they grew back. | | [EMAIL PROTECTED] | | +---+--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why not another style thread? (was Re: cvs commit:src/lib/libc/gen getgrent.c)
On Sunday, December 17, 2000, Jacques A. Vidrine wrote: What do folks think about 1)if (data) free(data); versus 2)free(data); versus 3)#define xfree(x) if ((x) != NULL) free(x); xfree(data); 2. The C standard dictates that free() does nothing when it gets a NULL argument. The other two are just extra clutter. -- +---+-+ | Chris Costello| This system will self-destruct in five minutes. | | [EMAIL PROTECTED] | | +---+-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why not another style thread? (was Re: cvs commit:src/lib/libc/gen getgrent.c)
On Sunday, December 17, 2000, Bosko Milekic wrote: Agreed. However, in the kernel, all free()s should be made as in (1), in my opinion. (2) is dangerous, and (3) would just obfuscate the code. (I know this does not apply to the commit, but should be noted) Yes, I agree; however free() in the kernel is an entirely different case and is not governed by the C standard. If you ask anyone in comp.lang.c, they'll tell you that our kernel is only written in a language _similar_ to C, and I can understand that, because many standard C functions behave differently in the kernel. (malloc and free come to mind, obviously.) -- +---++ | Chris Costello| Don't stop at one bug. | | [EMAIL PROTECTED] || +---++ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why not another style thread? (was Re: cvs commit:src/lib/libc/gen getgrent.c)
On Sunday, December 17, 2000, Jacques A. Vidrine wrote:
I don't blame authors of storage allocation code if they do not write
free like this:
void
free(void *p)
{
if (p == NULL)
return;
.
.
.
It would be silly to optimize for freeing NULL pointers.
You mean as seen in:
static void
ifree(void *ptr)
{
struct pginfo *info;
int index;
/* This is legal */
if (!ptr)
return;
.
.
.
called by free():
void
free(void *ptr)
{
THREAD_LOCK();
malloc_func = " in free():";
if (malloc_active++) {
wrtwarning("recursive call.\n");
malloc_active--;
return;
} else {
ifree(ptr);
.
.
.
That's how it's worked since before FreeBSD came into being.
It wasn't implemented the same, but it behaved the same.
--
+---+----+
| Chris Costello| All the simple programs have been |
| [EMAIL PROTECTED] | written, and all the good names taken. |
+---++
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Why not another style thread? (was Re: cvs commit:src/lib/libc/gen getgrent.c)
On Sunday, December 17, 2000, Jacques A. Vidrine wrote: I may have missed your point ... or maybe you are just agreeing with what I wrote. For this particular implementation of free, you get the following for `free(foo)' when foo == NULL: function call and stack overhead for free() lock something if we are threaded pointer assignment increment compare and branch function call and stack overhead for ifree() compare and branch unwind ifree() More stuff if HAVE_UTRACE decrement unlock something unwind free() FreeBSD's free() is not optimized for freeing NULL pointers. Not that I think it should be -- as I said, that would be silly. The code I pasted _was_ FreeBSD's code, and it does optimize for freeing NULL pointers. You can still check for the pointer if you wish, before you call free(). -- +---+-+ | Chris Costello| Backups? We doan *NEED* no | | [EMAIL PROTECTED] | steenking baX%^~,VbKxNO CARRIER | +---+-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: thr_sleep() and thr_wakeup()
On Friday, December 01, 2000, John Baldwin wrote: Can we kill these syscalls? They are not used anywhere in the kernel and although they have wrapper functions in libc, no header contains prototypes for these wrappers. According to the CVS log they were originally brought in for POSIX threads and AIO, neither of which use this facility. Comments? Agreed. Also, this is UNIX International thread namespace (thr_*). -- |Chris Costello [EMAIL PROTECTED] |Your e-mail has been returned due to insufficient voltage. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Problems with pthread
On Thursday, October 19, 2000, Steve Dobson wrote: I have written a little simple program (attached with its Makefile) that also exhibits the same problem. When I run the program I see the following error reported from gdb: (gdb) run Starting program: nod Program received signal SIGSEGV, Segmentation fault. 0x280747b8 in pth_cancel_point () from /usr/local/lib/libpthread.so.13 (gdb) This is GNU Pth, not FreeBSD pthreads. Use the ``-pthread'' cc(1) switch to link to the FreeBSD threads library. -- |Chris Costello [EMAIL PROTECTED] |Design simplicity: It was developed on a shoe-string budget. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: We need your old laptop for a committer...
On Monday, October 09, 2000, Dan Evensen wrote: I stand by my opinion. I live in Free Country with a free voice. I stand by what I said. There are millions of deserving people in this world. If this person is so good WHY cant they afford a Laptop Successful people could. The difference, however, is that Poul-Henning Kamp has made a structured, formal, properly punctuated request, for somebody who has already _given_ time and effort to the FreeBSD Project. You're just making randomly capitalize complaints because you want a free laptop. -- |Chris Costello [EMAIL PROTECTED] |Those who can't write, write help files. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: find /proc
On Thursday, October 05, 2000, void wrote: Why does find(1) operate non-recursively in /proc? Because the procfs_readdir() code does not report directories as the correct type (DT_REG as opposed to the proper DT_DIR). -- |Chris Costello [EMAIL PROTECTED] |TRAPEZOID - A device for catching zoids. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Fdescfs updates--coming to a devfs near you!
Over the past few months, I've been working on the /dev/fd file system
("fdescfs"). After weeks of occasionally-hacking and putting it off, I've
finalized a patch for fdescfs.
What this patch changes:
+ fdesc_allocvp() becomes curproc-free as a `struct proc' pointer is passed
as the new fourth parameter.
+ All usage of the `DTYPE' open file type macros are removed. Anything
whose fo_stat() operation does not return proper fdesc information is
broken. The checks for DTYPE_VNODE (for determining whether setattr()
will do anything) are replaced by getvnode() so that if the method for
determining a vnode from a file entry changes, (hopefully) that's the
only place it will happen.
There is one loose end I'm not sure I know just how to tie up yet. I'm
having trouble modifying src/sys/kern/sys_pipe.c:pipe_stat() to return the
right st_mode flags based on various conditions. I'd appreciate it if
someone else who knows about the pipe code could point me in the right
direction as to what conditions permit reading and what conditions permit
writing (and what makes them fail).
The patch is available at
http://people.FreeBSD.org/~chris/fdesc-dtype.patch,
Documentation for it is available at
http://people.FreeBSD.org/~chris/fdesc/
all in one page:
http://people.FreeBSD.org/~chris/fdesc/article.html
|Chris Costello [EMAIL PROTECTED]
|Press [ESC] to detonate or any other key to explode.
`
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: UNSUBSCRIBE REMOVE
On Saturday, August 26, 2000, [EMAIL PROTECTED] wrote: [2,640 lines removed] ... and this was at the bottom of the message you quoted: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message At the very least, don't just mail a whole day's worth of data back to the list with "UNSUBSCRIBE REMOVE" affixed to the subject line. Don't you know how much bandwidth and money you're wasting for people who have to pay for the amount of data they download? I'm sending this to the list because hopefully someone else reading it and wanting to unsubscribe won't make the same mistake. -- |Chris Costello [EMAIL PROTECTED] |Justify my text? I'm sorry but it has no excuse. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach)
On Saturday, August 26, 2000, Farid Hajji wrote: are there plans to replace FreeBSD's libc with GNU glibc in the near or medium future? Linux moved also from it's own libc5 to glibc (=libc6) some time ago and it may be useful to do the same in FreeBSD too. There are no such plans for that type of downgrade. If the software you need to use externally calls nonstandard C library functions consider porting the library and linking it manually, or fixing the software: cc -o my-hurd-program -nostdlib -lglibc ... or something along those lines. -- |Chris Costello [EMAIL PROTECTED] |You can't make a program without broken egos. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 2 inetd's with 2 nics
On Sunday, August 13, 2000, Leif Neland wrote: Is it possible and a good idea to have one inetd for the inside nic and another with fewer services for the outside on a gateway machine, or should I just use ipfw/ipchain for this? From the inetd man page: -a Specify a specific IP address to bind to. Alternatively, a host- name can be specified, in which case the IPv4 or IPv6 address which corresponds to that hostname is used. Usually a hostname is specified when inetd is run inside a jail(8), in which case the hostname corresponds to the jail(8) environment. -- |Chris Costello [EMAIL PROTECTED] |If a group of N persons implements a COBOL compiler, there will be N-1 |passes. Someone in the group has to be the manager.-- T. Cheatham `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: limit processes that a user can 'see'
On Sunday, August 13, 2000, Maxime Henrion wrote: By using the 'ps' command, any user logged in the system can view all the running processes, including root's one and processes of other users. My idea is to limit a bit this behaviour. If you want to keep your users completely out of the main system, including root's processes, just use jail. This sets up more or less a 'virtual machine' you can use to effectively act as another running FreeBSD system. ``man 8 jail''. -- |Chris Costello [EMAIL PROTECTED] |How do I set my Laser printer to "Stun"? `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: God I feel stupid (gcc issue)
On Tuesday, August 08, 2000, Laurence Berland wrote: So I thought, "we don't define __GNUC__?" I figured I'd check. After much mind wracking, I can't for the life of me figure out how to get gcc to output a list of what is and isnt defined by default... help! gcc -E -dM - /dev/null -- |Chris Costello [EMAIL PROTECTED] |Use free-form input where possible. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: malloc to arrays?
On Wednesday, August 02, 2000, Mike Smith wrote: tcpcash_addr = (typeof(tcpcash_addr)) malloc(sizeof(*tcpcash_addr) * TCPCASH_ROWSIZE * TCPCASH_COOLSIZE); Just as a note on coding style, this will only hide warnings caused by not including stdlib.h. malloc(3) returns void * and does not need to be cast. -- |Chris Costello [EMAIL PROTECTED] |Last one out, turn off the computer! ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: malloc to arrays?
On Wednesday, August 02, 2000, [EMAIL PROTECTED] wrote: Sorry I have no other direction to ask this: I have declaration: u_int32_t *(tcpcash_addr[256]); and want malloc some memory for tcpcash_addr: tcpcash_addr = (typeof(tcpcash_addr))malloc(u_int32_t * 256 * n); and have an error: ra-sum.c:386: cast specifies array type *** Error code 1 Try this: u_int32_t *tcphash_haddr; tcphash_addr = malloc(sizeof(*tcphash_addr) * 256); You shouldn't be casting malloc and I don't see any reason to use *(foo[nmemb]) syntax. -- |Chris Costello [EMAIL PROTECTED] |Performance proven: It works through beta test. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Howto profile my code?
On Monday, July 31, 2000, Bjorn Tornqvist wrote: Howdy! Anyone know a working method to get profiling to work? (i.e. seeing something like "method a::getValue() spent 12s Usertime, 3s Kerneltime" etc). I've tried with gcc -mprofiler-epilogue but got the following linker error: MessageCenter.o: In function `MessageCenter::OpenNewInput(basic_stringchar, string_char_traitschar, __default_alloc_templatetrue, 0 )': MessageCenter.o(.text+0x954): undefined reference to `mexitcount' So, searching the headers (in machine/asmacros.h) I found some reference to GPROF so I tried to define it, but it still doesn't work. Actually: the complete argumentlist to gcc is this: In the cc(1) man page, you can use -pg to create GNU gprof profiling output for your binary: -pgGenerate extra code to write profile information suitable for the analysis program gprof. -- |Chris Costello [EMAIL PROTECTED] |There are always at least two ways to program the same thing. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD,Posix,Linux Threading - Are they really useable?
On Monday, July 31, 2000, Bjorn Tornqvist wrote: But how do I know if my pthreads aren't secretely blocking for a very short time in read() and write()? Documentation anywere? They 'block' for the duration of time it takes to make a non-blocking call to read() or write(), which is, as far as your program cares, practically zero. I thought he had seen the term 'kernel threads' in the context of FreeBSD before, likely in the context of kthread_create() in the kernel. Actually I have, but I haven't tried them since I found no documentation on them (I even emailed [EMAIL PROTECTED] (he's listed as maintainer in sys/kthread.h) but got no reply). Just aswell, seeing how wrong I was. I think I'll stick to pthreads for now; which will make it easier to modify the code later on when we have ''real'' threads. (Sorry, I come from a BeOS background). Pthreads is only a specification of an interface, not a form of user threads. We just implement them in the form of user threads. Another question for you all: Does FreeBSD have any notion of kernel mutexes and/or semaphores (that can be used to control concurrent processes), and that can be shared between processes using pthreads? pthread_mutex_init is local to a process and thus of little use. (FYI: The application my company is developing consists of several processes, all of which must have a couple of worker threads). Yes. We do have SysV shared memory support. Try ``man -k ^shm'' and ``man -k ^sem''. -- |Chris Costello [EMAIL PROTECTED] |Printed on 100% recyclable phosphor. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD,Posix,Linux Threading - Are they really useable?
On Friday, July 28, 2000, Nate Williams wrote: That is incorrect. FreeBSD's userland pthread implementation does not block the whole process on I/O. POSIX does not specify this behavior either. Actually, sometimes it does (for example when reading from an I/O device where select can't be used succesfully). Hmm. That's true. And that's where uthreads has its main problems as I understand it. FreeBSD Kernel-threads (dunno what they are called actually) can't be used natively!? (Searched the archives and found an explanation that the only way to access normal kernel SMP-thread functionality is to use LinuxThreads) FreeBSD's kernel threads are for separate threads of execution in the kernel and aren't the same thing as threads for a user process. You're missing the point. He's asking for 'kernel threads' so that multiple independant thread of execution for a given 'userland process' can be running simulataneously (virtually on a UP, and realistically on a MP). I thought he had seen the term 'kernel threads' in the context of FreeBSD before, likely in the context of kthread_create() in the kernel. -- |Chris Costello [EMAIL PROTECTED] |May the force be... your umbrella! - Plucky Duck `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD,Posix,Linux Threading - Are they really useable?
On Friday, July 28, 2000, Bjorn Tornqvist wrote: PosixThreads are userland threads - if one thread blocks on i/o the whole process is blocked. Which makes PosixThreads rather useless. That is incorrect. FreeBSD's userland pthread implementation does not block the whole process on I/O. POSIX does not specify this behavior either. FreeBSD Kernel-threads (dunno what they are called actually) can't be used natively!? (Searched the archives and found an explanation that the only way to access normal kernel SMP-thread functionality is to use LinuxThreads) FreeBSD's kernel threads are for separate threads of execution in the kernel and aren't the same thing as threads for a user process. LinuxThreads: While they are kernel-threads, if one thread receives an uncought signal, all threads are killed (as they should be), but the resulting coredump is useless since it only captures the state of the last-killed-thread (or process or whatever you want to call it. LinuxThreads seems like just a big hack...). LinuxThreads on FreeBSD cannot be kernel threads because that would require modifications to our scheduler which simply have not been made. -- |Chris Costello [EMAIL PROTECTED] |Save energy: Drive a smaller shell. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: problem on 4.1-RC (4.0-stable)
On Thursday, July 20, 2000, Ulf Zimmermann wrote: Yep, you were right. /dev/null was a plain file. Strange Just guessing here--ps probably uses /dev/null for all the files passed to kvm_open(3). I imagine it uses kvm_getprocs for its process listing, which is implemented using sysctl. -- |Chris Costello [EMAIL PROTECTED] |Programmer: One who is too lacking in people skills |to be a software engineer. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: DEVFS
On Sunday, July 16, 2000, Coleman Kane wrote:
This is a great idea. We need a good, well drawn out description of
what DEVFS is supposed to accomplish and how we'd like it to work. I
will be glad to help out, and perhaps we can get some movement on this.
Personally, I'd like to see DEVFS completely replace the current system
of nodes in /dev.
That's the point of it, or so I've heard.
One nice feature would also be to be able to define aliases of certain
devices, such as cdrom, modem, etc... I suppose these could get handled
in rc/rc.conf.
Probably using symlinks:
if [ "X$default_modem_device" != "X" ]
then
ln -sf /dev/defaultmodem ${default_modem_device}
fi
if [ "X$default_cdrom_device" != "X" ]
then
ln -sf /dev/cdrom ${default_cdrom_device}
fi
...
I would like to point out that if anyone does this, my advance
suggestion is that you differentiate between data and audio
CDROM.
--
|Chris Costello [EMAIL PROTECTED]
|Swap read error. You lose your mind.
`-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: DEVFS
On Saturday, July 15, 2000, Adrian Chadd wrote: Ok, how about you, phk and julian throw up a list of what devfs should do? I am forming some ideas on how to solve the namespace and device cloning issues, we might make some forward work on this finally? :-) I'm not Boris, phk or Julian, but I'd like to add that it should probably integrate the fdesc code. Especially since I'm working on (and am soon going to hopefully commit) code to do more relatively major repairs to fdesc[1]. -- |Chris Costello [EMAIL PROTECTED] |[1] Removing all references to DTYPE_* macros. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dev to name
On Sunday, July 02, 2000, Fox Anderson wrote: Hi. How can i find out the name of device file by device major/minor? The devtoname() function. ``man devtoname'' -- |Chris Costello [EMAIL PROTECTED] |To define recursion, we must first define recursion. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: style(9)
On Friday, June 30, 2000, Neil Blakey-Milner wrote: No. Anyway, you can set your tab size to whatever you want. So long as it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the margin constantly, you should simplify your code, or break it up into (preferably reusable) functions that perform one task. Setting a tab width to something other than 8 would tend to break formatting for people with normal editors. Just try viewing bsd.port.mk in vi with default settings and not seeing clutter. -- |Chris Costello [EMAIL PROTECTED] |Random access is the optimum of the mass storages. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: struct proc
On Monday, June 26, 2000, Fox Anderson wrote:
Hi all!
What is the difference between p and curproc in my syscall?
static int
my_syscall(struct proc *p, my_syscallargs *uap) {
curproc-..
}
p is the process that made the syscall, curproc is the current
running process. You should be using p for the process that
called my_syscall.
--
|Chris Costello [EMAIL PROTECTED]
|It wasn't as easy to get programs right as we had thought. - Wilkes, 1949
`--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Korn shell STDOUT
On Tuesday, June 20, 2000, gerald stoller wrote: Anybody know how I can easily change the STDOUT to be unbuffered? Using setbuf(3). (``man setbuf'') -- |Chris Costello [EMAIL PROTECTED] |You had mail, but the super-user read it, and deleted it! `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kerneld for FreeBSD
On Sunday, June 04, 2000, Alfred Perlstein wrote: I thought Linux did away with thier kerneld concept. Afaik we can currently load a kld from within kernel context, can you please explain further what you want to do? We can, and we also dynamically load modules when needed (ifconfig, mount). The kernel can also load modules from KLD files "on its own" via kern_linker.c:linker_load_file(). An example of usage is in vfs_syscalls.c:mount(), where if a specified file system configuration structure (vfsconf) is not found in the list of 'configured' file systems, mount(2) attempts to load a module for the file system, if one exists. -- |Chris Costello [EMAIL PROTECTED] |Debugger: A tool that substitutes afterthought for forethought. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: utmpx, this is gonna hurt...
On Monday, May 15, 2000, James Howard wrote: How about adding the utmpx as required by SUSV2? It would make writing programs that need to talk to utmp/utmpx a lot simpler. Yes? No? I agree that this would be a good idea. -- |Chris Costello [EMAIL PROTECTED] |Performance proven: It works through beta test. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multithreaded server performance
On Monday, April 24, 2000, Brian O'Shea wrote: On Mon, Apr 24, 2000 at 06:13:53AM -0400, Daniel Eischen wrote: On Mon, 24 Apr 2000, Brian O'Shea wrote: I was under the impression that, because user thread scheduling is done in user mode, a thread that goes to sleep calling a blocking read() system call will put the entire process to sleep until that read() returns (and so all user threads in the process will also be blocked). Is this correct? 1. You are mistaken. Could you elaborate? The text that I am using [1] warns about blocking system calls putting the process (and thus all user threads) to sleep. This book has no FreeBSD specific information, so anything specific to FreeBSD would be really interesting to hear. FreeBSD's threads implement has its own read() function which will make a non-blocking read() call (using the _real_ syscall) for the specified amount of bytes. Now a non-blocking read() call fails unless all the data in nbytes can be read into buf. So our implementation will continue to do a non-blocking read until all the data can be copied and then allows the thread continue, thus blocking only the calling thread. At least that's what the source code tells me. -- |Chris Costello [EMAIL PROTECTED] |I smell a wumpus. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multithreaded server performance
On Monday, April 24, 2000, Brian O'Shea wrote: Yea, I took a look at lib/libc_r/uthread/uthread_read.c too, but it didn't paint the whole picture for me. Specifically, I couldn't find the definition for the _thread_sys_read() function. It looks like the polling magic to which Jason Evans referred occurs in some interesting code in uthread_kern.c, though. _thread_sys_read() is the real read(2) syscall. They're renamed to ``_thread_sys_SYSCALL()'' for the purpose of reimplementing them in a thread-friendly manner, as you see with read() there. -- |Chris Costello [EMAIL PROTECTED] |Do something unusual today. Accomplish work on the computer. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RFC: Patches for mounting fdesc on /dev/fd and general cleanup
(Trying -hackers since -current wasn't very interested. Maybe someone might actually see it this time.) I've modified the fdesc file system so that it will be mounted on /dev/fd directly (rather than as a union mount on /dev) and have fixed a lot of items relating to missing data and incorrect cloning. I'm looking for some review and feedback on this. Thanks. Documentation: http://www.FreeBSD.org/~chris/fdesc/ The patch: http://www.FreeBSD.org/~chris/fdesc.patch -- |Chris Costello [EMAIL PROTECTED] |Make input easy to proofread. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposed new Bourne shell init files
On Friday, March 31, 2000, Doug Barton wrote: I guess that's not the best term to use, so let me try and rephrase my argument. All Bourne shells and derivatives have an export command. On all Bourne shells and derivatives, you _can_ do: var=foo export var It is not true however, that on all Bourne shells and derivatives that you can do: export var=foo However, on all _POSIX_ shells, ``export var=foo'' is valid, if I remember correctly. -- |Chris Costello [EMAIL PROTECTED] |A closed mouth gathers no feet. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Dreamweaver 2
On Saturday, March 25, 2000, VR Dredge wrote: Hi, my name is Robert. I came across your address while trying to find a crack for Dreamweaver 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm asking if you have or know where I can it. Also are there any programs for generating cracks, passwords and so on Where did you get this address as a place to get cracks for Windows software? This mailing list is for general FreeBSD technical discussion. -- |Chris Costello [EMAIL PROTECTED] |All the simple programs have been written, and all the good names taken. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Where is pci_intr_establish() _thread_sys_read()?
On Monday, March 06, 2000, Zhihui Zhang wrote: Can anyone tell me where is the code for pci_intr_establish() and _thread_sys_read()? I could not find them under /usr/src. I can tell you offhand that _thread_sys_anything is the _real_ syscall for `anything'. This is because a lot of syscalls are reimplemented within libc_r for reasons that are kind of obvious (directly calling the read syscall from one thread would block all the other threads in a process). So _thread_sys_open() == open(2), _thread_sys_read() == read(2), etc. I don't know about pci_intr_establish. -- |Chris Costello [EMAIL PROTECTED] |Today's assembler command : EXOP Execute Operator ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: empty lists in for
On Monday, March 06, 2000, Max Khon wrote:
However, under Solaris 2.6:
clone$uname -a
SunOS clone 5.6 Generic_105181-13 sun4u sparc SUNW,Ultra-1-Engine
clone$/bin/ksh
clone$for i in ; do echo $i; done
/bin/ksh: syntax error: `;' unexpected
clone$
It is likely you are running the ksh88 version, which has
quite a few ``pre-POSIX'' features. Try this command to see
whether you have ksh88 or ksh93:
echo ${.sh.version}
If you have ksh93, you'll see something like
Version M 1993-12-28 i
Perhaps with a different letter at the end (`i' is the source
release). I believe you'll get an error or nothing if it's
ksh88.
--
|Chris Costello [EMAIL PROTECTED]
|Know Thy User.
`--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: DeCSS
On Monday, February 21, 2000, Bill Fumerola wrote: You're one of those people who follows instructions, are you? You're one of those people who out words, aren't you? :) -- |Chris Costello [EMAIL PROTECTED] |Design simplicity: It was developed on a shoe-string budget. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ls: alpha - numeric sorting
On Friday, February 11, 2000, W.H.Scholten wrote: I've also attached a complete little test program with debug output etc. The code could be improved by renaming some variables to longer names (couldn't think of any good ones ;) and probably the implementation too (haven't tried to optimize). FreeBSD already supports an `-n' option, so you probably don't want to go with that. Probably if it does go in, both systems should use -N or something else unused, if only for consistancy amongst the two. -- |Chris Costello [EMAIL PROTECTED] |Host System Not Responding, Probably Down. Do you want to wait? (Y/N) `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: DreamWeaver Crack 3.0
On Sunday, January 30, 2000, [EMAIL PROTECTED] wrote: Hey I know its not a cracking mailing list but does anybody have the Crack for Dreamweaver 3.0 I don't think freebsd-hackers or linux-admin are the right places to ask for this sort of thing. FreeBSD-hackers is for discussing programming on FreeBSD and for FreeBSD, and I'd imagine linux-admin is for discussing administration on Linux systems. -- |Chris Costello [EMAIL PROTECTED] |A list is only as strong as its weakest link. - Don Knuth `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libelf and Elf Interface Routines
On Fri, Jan 14, 2000, Ronald F. Guilmette wrote: (I never asked what the letters B-F-D stood for. I always figured that they had the obvious meaning. :-) BFD stands for Binary File Descriptor. -- |Chris Costello [EMAIL PROTECTED] |I'm sorry my Karma ran over your Dogma. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: your mail
On Thu, Jan 13, 2000, Ramiro Amaya wrote: I am new in this mail list, so I do not have so much experience about the questions I should ask, If I am in the worng place let me know, please. Well my question is related with Solaris 2.6, the story is like this: What does this have to do with the FreeBSD operating system? -- |Chris Costello [EMAIL PROTECTED] |Software is mind work. Having the right frame of mind is essential. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody know if there is any way to make ports use different workdir?
On Sat, Dec 18, 1999, Matthew Dillon wrote: It would be nice if there were a way to tell the ports system to put the work directory somewhere other then where it is currently placed. For example, to put it in /usr/obj or something like that. Has anyone done this? The authors of bsd.port.mk have. Try this: $ cd /usr/ports/misc/rtfm $ WRKDIRPREFIX=/tmp DISTDIR=/tmp make rtfm-0.2.tar.gz doesn't seem to exist on this system. Attempting to fetch from http://www.freebsd.org/~chris/distfiles/. Receiving rtfm-0.2.tar.gz (4881 bytes): 100% 4881 bytes transferred in 0.1 seconds (48.25 Kbytes/s) === Extracting for rtfm-0.2 Checksum OK for rtfm-0.2.tar.gz. === Patching for rtfm-0.2 === Applying FreeBSD patches for rtfm-0.2 === Configuring for rtfm-0.2 === Building for rtfm-0.2 cc -o rtfm rtfm.c -O -pipe -Wall Simply set WRKDIRPREFIX and DISTDIR and nothing gets written to the ports directory. Obviously you could put this in /etc/make.conf and make it much easier on yourself. Note that you end up in this case with /tmp/usr/ports/misc/rtfm/work/rtfm-0.2/ that you get to rip out later. Additionally, a /tmp/rtfm-0.2.tar.gz is left behind. -- |Chris Costello [EMAIL PROTECTED] |State-of-the-practice: What we can do with the money you have. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Upper -Lower in shell script
On Fri, Dec 17, 1999, Alex wrote: I need in my shell script change upper case to lower case for characters. Cureently , I call c programm from script which do it. Is anybody did this inside script? Shells such as ksh (both PDKSH and ATT KSH, available in ports, support this) and bash have a typeset command. To convert something to all upper-case is surprisingly easy: typeset -u variable Example: $ typeset -u f $ f=abc $ echo $f ABC -- |Chris Costello [EMAIL PROTECTED] |Beware of programmers who carry screwdrivers. - Leonard Brandwein `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Upper -Lower in shell script
On Fri, Dec 17, 1999, Alex wrote: I need in my shell script change upper case to lower case for characters. Cureently , I call c programm from script which do it. Is anybody did this inside script? Oops. That should be typeset -l. $ typeset -l var $ var=ABC $ echo $var abc -- |Chris Costello [EMAIL PROTECTED] |Random access is the optimum of the mass storages. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: technical info needed
On Mon, Dec 13, 1999, Ilia Chipitsine wrote:
Is it called once an year or 50 times a second ?
Is there a way how can I determine it by myself ?
Add a statement like
printf("somefunc() being called!\n");
to the top of the function you want to 'measure'.
--
|Chris Costello [EMAIL PROTECTED]
|Nobody has ever, ever, EVER learned all of WordPerfect.
`---
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: incoming directory on freebsd.org
On Sat, Dec 11, 1999, Josef Grosch wrote: I have a patch to FreeBSD but I am not sure where to upload this file. Can someone point me to the directory? Use send-pr and include it there. -- |Chris Costello [EMAIL PROTECTED] |If it was easy, the hardware people would take care of it. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux ioctl not implemented error
On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: Wait... vmware for linux works under FreeBSD now??? or it just runs freebsd??? It runs on FreeBSD. -- |Chris Costello [EMAIL PROTECTED] |What do computer engineers use for birth control? Their personalities. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: A file with holes - a bug?
On Mon, Nov 22, 1999, Zhihui Zhang wrote: lseek(fileno(fp), 3 * 8192, SEEK_CUR); If I remove the fflush(fp), then the characters 0x30-0x39 will be all written at the end of the file (use hexdump to find out), not as expected (one at the beginning and the other at the end). It seems to me that the first for loop happens AFTER the lseek() statement without fflush(). Can anyone explain this to me? I am using FreeBSD 3.3-Release. That line (as quoted) where you use lseek is broken. Use fseek instead. Use only one method to access files. Either stdio or the open/read/write syscalls. -- |Chris Costello [EMAIL PROTECTED] |If a group of N persons implements a COBOL compiler, there will be N-1 |passes. Someone in the group has to be the manager.-- T. Cheatham `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Implementing ioctl to set MAC address -- question.
I'm trying to implement Bill Paul's "setmac" code in the actual source code as a project (and will have it reviewed before it's committed -- if I ever get that far!). However, I'm getting stuck in that ether_ioctl is never getting the ioctl request. I've added the case statement for "SIOCSIFMAC" (probably to be renamed) to net/if.c and dev/ed/if_ed.c (which is the card I'm using) as well as net/if_ethersubr.c. Are there any other files that need to know about the ioctl or am I going about this the wrong way entirely? -- |Chris Costello [EMAIL PROTECTED] |This BBS is ancient. Some say from the echocene. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: X11/C++ question
On Tue, Oct 26, 1999, Thomas David Rivers wrote:
extern "C" {
void
callback_function(arg1)
void *arg1;
{
/* Call the method */
myclass::mymethod(arg1);
As far as I've seen, you can't directly call a class method
without an object.
--
|Chris Costello [EMAIL PROTECTED]
|A closed mouth gathers no feet.
`--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: module names
On Tue, Oct 26, 1999, Pascal Hofstee wrote: Hi, With the recent addition of more and more KLDs to the /modules directory i was wondering if perhaps it would be a good idea to name these modules more consistantly: if_*: For all network modules (done already) ng_*: For all netgraph related modules (done already) fs_*: For all filesystem modules saver_* : For all screensavers (probably would prefer a shorter prefix) emu_* : For binary compatibilty modules like linux/ibcs2/svr4 I agree with the idea but some of the name ideas are a little off. What would Vinum go under? I also disagree with your usage of ``emu_''. I would prefer ``compat_''. -- |Chris Costello [EMAIL PROTECTED] |If at first you don't succeed, you must be a programmer. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio_read kills machine
On Mon, Oct 11, 1999, Chad David wrote: Some replys indicated that I should use -current for aio_*. Would this be true also for any serious threading? Is -current ready for a semi-production environment? Not really. The fact is that a user program can crash 3.3-STABLE and that is unacceptable. No user program should be able to bring down a system, _especially_ in -STABLE. The source for this code is available from http://www.guild.ab.ca/killer.tar.gz if anyone would like to take a look. The crash has been truncating main.c, so you may want to copy it before running the program. Thanks. Chad -- |Chris Costello [EMAIL PROTECTED] |TRAPEZOID - A device for catching zoids. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unquoted mail (was: aio_read kills machine)
On Tue, Oct 12, 1999, Greg Lehey wrote: It doesn't have anything to do with the MUA. The message arrived here without a in front of the 'From ' at the beginning of the line, which is an indication that it's a new message. But it's interesting that it didn't happen to everybody. Some MTA between him and me (his mail server, calldei.com's mail server, or my fetchmail) has quoted it on my message. Greg -- |Chris Costello [EMAIL PROTECTED] |State-of-the-art: What we could do with enough money. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: bogomips CPU performance metric
On Sun, Oct 10, 1999, Laurence Berland wrote: I like the idea as an optional LINT parameter that is NOT in the generic kernel. Might make some linux people feel comfortable with the switch, or might prove useful under some odd circumstances, but I agree it'd be silly to include it by default (kindof on the level of a splash screen) I disagree. BogoMIPS is a completely meaningless measurement and does not belong in our source tree as it will only produce repository bloat. -- |Chris Costello [EMAIL PROTECTED] |A bug in the code is worth two in the documentation. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio_read kills machine
On Wed, Jan 01, 1997, Chad David wrote: I am certain that my program is not correct (besides the obvious consiquence of running it :) ), but I would also like to determine why it kills the machine. I was not root either time I ran the code. Then FreeBSD does have a problem. Please file a PR using the ``send-pr'' command or http://www.freebsd.org/send-pr.html and supply the source to your program and whatever other information you think will help us in figuring out the problem. -- |Chris Costello [EMAIL PROTECTED] |Field tested: Manufacturing doesn't have a test system. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file system system calls
On Sun, Oct 10, 1999, Alfred Perlstein wrote:
grep ^somefuncname */*
this is because the concention is to write functions like so:
int
somefunctioname(foo) {
You mean
int
somefuncname(char *foo)
{
--
|Chris Costello [EMAIL PROTECTED]
|Death is a nonmaskable interrupt.
`--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: file system full
On Fri, Oct 08, 1999, James Howard wrote: When running "strobe" (from the ports collection, it is a port scanner), I often or always get the message "file: table is full" many, many times. I have seen this under 2.2.6 through 4.0. What exactly is going wrong here and what should I do to fix it? Too many open file descriptors. This has nothing to do with the file system. -- |Chris Costello [EMAIL PROTECTED] |Never lick a gift horse in the mouth. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Stupid Newbie questions (was re: developer assessment)
On Tue, Oct 05, 1999, [EMAIL PROTECTED] wrote: Might the following be helpful? Or, does it exist somewhere on the net now? http://www.blackhelicopters.org/~dispatch/stupid-bsd-questions.txt If it is of any use, I'll clean it up for general consumption. This is a very interesting article! Perhaps it could go into the handbook, or perhaps be an article of its own. -- |Chris Costello [EMAIL PROTECTED] |As of next week, passwords will be entered in Morse code. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: updating packages automatically...
On Sun, Sep 26, 1999, Christian Carstensen wrote: hi *, i'm thinking about writing a perl script that updates installed packages automatically, if there's a newer version in the ports directory. unfortunately, the package name, as in /var/db/pkg, in some cases does not correspond to the ports directory name at all. for example, the port in 'archivers/gshar+gunshar' contains the package 'sharutils-4.2'. would it be a good idea to store the port's path information somewhere, e.g. in a file 'pkg/+PORTPATH'? Aah! No! I tried that with GNOME once and it drove me insane for about two weeks. Auto-upgrades on ports would be _very_ _very_ bad, especially for those using apache from ports! -- |Chris Costello [EMAIL PROTECTED] |State-of-the-practice: What we can do with the money you have. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: A new package fetching utility, pkg_get
On Sat, Sep 25, 1999, Bill Fumerola wrote: Patches to do this would be trivial. It would have to be a flag you'd use with '-r' otherwise we'd have to call the program 'fetch'. What about the graphical interface and Java versions? Any plans for that in pkg_install? -- |Chris Costello [EMAIL PROTECTED] |It's 10 o'clock. Do you know where your child processes are? `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: A new package fetching utility, pkg_get
On Fri, Sep 24, 1999, Nate Williams wrote: Unfortunately, as with all 'slick' products we've talked about, it still requires a working X setup in order to run. You could do one as a CUI, but doing it in Java would be just as hard as anything else at this point. :( There's nothing keeping it from being a port or being an optional part of a distribution that can be installed if X is installed (emphasis on ``optional''). We've got what we need behind-the-scenes, now we need to put a good show on stage. Let's show Linux what package management is all about. :) [If these words aren't motivational, I give up.] -- |Chris Costello [EMAIL PROTECTED] |Eunuchs, the non-gender-specific OS ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GNU GLOBAL
On Mon, Sep 20, 1999, Shigio Yamaguchi wrote: But GPLed command brings no problem, because the rest of the system just "utilize" it, not "use it. GPL is not applied to "utilize". So the rest of the system is safe from GPL. You cannot modify and incorporate a GPL command into a product which is sold in binary form only. You also cannot do such things with an embedded Unix system using said command. -- |Chris Costello [EMAIL PROTECTED] |My mail reader can beat up your mail reader. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
