Re: New SCSI: can't 'make depend'
I think this is in -STABLE not -CURRENT, I'm having this problem there. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Recommended MP development machines...
Hi, I know everyone says they all work but i'd like some recommendations on MP machines for -CURRENT work. I'll be ordering one this week. Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd redux
Is there any particular reason for using -current for that? The problem is that -current is in horrible state now (gcc 3.1, KSE-III and so on), so that I'd suggest to use -stable branch or -current sources just before gcc 3.1 import. Well there are two things going on. My employer wants to use -CURRENT and is willing to let me hack on it, and the other is that I volunteered to do some of the multi-threading/locking work in the network stack. If I can kill these two birds with one stone I can do work for the project while also getting paid. Alas the paid part gets a higher priority :-) When, exactly, was the 3.1 import? Later, George -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
picobsd redux
Hey Folks, So now I'm working somewhere that we're trying to use Picobsd on the Soekris boards (www.soekris.com). Right now there is a build problem I'm trying to solve. When picobsd goes to build the libraries etc. it chokes on the csu stuff: CC=cc MKDEP_CPP_OPTS=-M -DCRT_BEGIN mkdep -f .depend -a -nostdinc -I/sandb oxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/sandboxes /gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/config -I/sandboxes/gnn/FreeBS D/src/gnu/lib/csu/../../../contrib/gcc -I. -I/sandboxes/gnn/FreeBSD/src/gnu/lib / csu/../../usr.bin/cc/cc_tools /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../ c ontrib/gcc/crtstuff.c cc -nostdinc -I/sandboxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_ FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-o mit-frame-pointer -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc / config -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc -I. -I/san dboxes/gnn/FreeBSD/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -g0 -DCRT_BEGIN - c -o crtbegin.o /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crt s tuff.c In file included from /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/g c c/crtstuff.c:63: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:37 : field `array' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:13 5 : field `augmentation' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:14 3 : field `pc_begin' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:254: warn ing: `used' attribute directive ignored /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: In funct ion `__do_global_dtors_aux': /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:256: synt ax error before `completed' /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: `com pleted' undeclared (first use in this function) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: (Eac h undeclared identifier is reported only once /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: for each function it appears in.) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: At top l evel: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:298: warn ing: `used' attribute directive ignored *** Error code 1 Any pointers would be great, I need to get this stuff back up to snuff fast. Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
Does this include getting someone to fix picobsd for -CURRENT? Is this important for the snapshots? Later, George *** Making static libraries cd /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf; make depend; make all; make install rm -f .depend mkdep -f .depend -a -nostdinc -DSTANDARD_INCLUDE_DIR=/home/gnn/FreeBSD/src.la t est../usr/include -I/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common / home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crti.S /home/gnn/FreeBSD/src.latest /lib/csu/i386-elf/crtn.S mkdep -f .depend -a -nostdinc -DSTANDARD_INCLUDE_DIR=/home/gnn/FreeBSD/src.la t est../usr/include -I/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common /ho me/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:30: stddef.h: No such file or directory /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:31: stdlib.h: No such file or directory In file included from /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:32: /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common/crtbrand.c:28: sys/param .h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf. *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest. *** Error code 1 -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
gtags? htags?
Are these supposed to be part of the base install of FreeBSD? I can't find them anywhere and they're not in ports. They're needed for the tags: target in the kernel makefiles and since I'd like to be able to browse code... Thanks for any pointers, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Discussion of guidelines for additional version control mechanisms (fwd)
What I mean by imposing structure is: - Identify patterns of development and structure that seem to have evolved naturally as part of the maturing of the FreeBSD Project - Determine which patterns tend to result in the most productive and parallel development efforts, not to mention which are the most popular - Selectively reinforce those patterns to improve the ability of developers to rely on the patterns This sounds fine to me but we're going to have to write it down somewhere and then discuss it. This tossing ideas in the ether is not going to work because to refer back to earlier points we have to either have huge emails with everyone's comments in them, or constantly be reading the archives. So, please, if you think this is important write down your findings/current beliefs somewhere (I think TWiki or something like it is perfect for this) and let everyone comment and modify them until we have an understanding. Then lets figure out what structure we need and write that down as well. Think of it as a FreeBSD constitution if you must, only much more lightweight. You're obviously taking the lead here and that's fine, every project (and this discussion is really a project) needs a leader. I think we're in the same boat here. You believe that process can help streamline the development process, and be used to help avoid the disagreements we've run into recently (assuming I read you correctly :-). I think so too. I agree we can't bring too much process--that won't work for a large number of reasons. But a little bit of process can go a long way. In particular, I'm looking for a little bit of process that will help address the perceived problems of the current situation. Yes, you read me correctly. My mantra is, Write it down. :-) Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Discussion of guidelines for additional version control mechanisms (fwd)
Certainly -- the intent that I expressed in my original e-mail was to fish for people's thoughts on the issue, which would then be codified in some form. I'm interested in hearing a little more back on how people feel about the notion of how larger projects should coordinate work given the assumption that locks are advisory, but plan to write up a strawman sometime in the next week or so. Probably the process forward there will be to run the first pass by the core team for some immediate feedback regarding the strength of the recommendations, and whether it meets our goals concerning addressing the problems that have been discussed. Then I'll spit a copy out for more general comments. Sounds like a great plan to me. Alas I think you'll get more feedback once you have the strawman proposal, people just seem to work that way. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Discussion of guidelines for additional version control mechanisms (fwd)
In addition to process it might be attitude. It might be a stretch but they are kind of the same. Good processes come from good attitude. It is extraordinarily hard for most people (especially smart people) to be introspective on such questions when they think they already have the answer. Sometimes people think that because something works for them it will work in a group. But we know that's not always the case. So, how do we get our attitudes adjusted before hitting a wall, as many companies I've worked for did? It comes back to agreeing on a process by which we work. We have one now, it may not all be written down, but we do have it. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
You'll have to pay some money if you need a 24-hour responsiveness. :-) The check is in the mail ;-) What src/release PicoBSD script should I try to run to reproduce this? -CURRENT as of Monday. Things work fine in a checkout from 20 Feb 2002 and that's what I'm working with. If you can give me a bit of info (or a place to look) I can help address this problem. I'm going to try to work with Luigi on maintaining picobsd as this will be my main development system. It's a very good way for embedded systems hacks (like myself) to work. Very natural. And it's nice that I don't have to worry about having -CURRENT on my development machine. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Discussion of guidelines for additional version control mechanisms (fwd)
One of the disagreements that seems to be evolving is whether or not the project formally supports a task-oriented structure. A couple of people have asserted that people might claim tasks (such as myself) and by virtue of claiming the task, be provided with some notion of ownership that is supported in a more formal sense. Others have pointed out that in a volunteer environment, people simply do what they want to regardless of any task ownership, and would prefer a first-past-the-post model to a task ownership model. My assumption had been that disagreement existed to some extent based on the nature and strength of ownership, but it seems that I've made a fundamental assumption there that not everyone agrees with. My feeling has always been that imposing some modicrum of structure is important: to avoid people stepping on toes, people can announce what they're working on, and expect that others might avoid replicating the work, or at least be communicated with before it happens. The rationale for this lies both in efficiency (non-replication of work), and to avoid toe-stepping, since there's a natural notion of ownership over work done, and a desire to not see it discarded. Perhaps this can't be supported in our environment. I think we need to avoid the concept of imposing some modicum of structure. If we create structure it is because we need it. Just like software. There was a good comment recently about software gets created to scratch an itch. I'd say that structure gets created because you're tired of losing fingers and toes to the person next to you wielding the axe. It's great that your friends are helping you clear the forest but you'd all like to be able to walk and pick up your cup of coffee at the end of the day as well. We are always going to have first past the post problems. If someone comes along and has rewritten a whole subsystem, and testing and performance measurement show that it's an order of magnitude better (faster, smaller, etc.) than what we have we'd be idiots not to take it, right? The question is What processes do we need to put in place to make a project of this size and dynamisticity work? I put forward a few of them. I suggest we start somewhere (including airing gripes people have with the current system) and write down (i.e. build a web page, use TWiki) what we're going to do about it. I hate to make this analogy but we need a constitution or something like it. Not so grandiose of course, but a written set of rules and are easy to interpret that can take care of the 80% case. The 20% we'll always get to argue over but I'd rather not argue over the 100%. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Discussion of guidelines for additional version controlmechanisms (fwd)
Hi Folks, I've put up the following TWiki page: http://www.neville-neil.com/twiki/bin/view/Freebsd/DevelopmentProcess as a scribbling area for a possible set of rules/practices that we can use to address the issues raised in this discussion. For those not familiar with TWiki who want to know what this is before scribbling please start here: www.twiki.org Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
This still doesn't answer my question -- how can I reproduce the problem? cd /foo/bar make grrr Something like that... Whoops, sorry. To reproduce this do: cd /usr/src ./release/picobsd/build/picobsd --src /usr/src --init yes, I know that --src is unnecessary but I always use it since I'm often using a tree that's NOT at /usr/src so I include it here. The --init will break with: mkdep -f .depend -a -nostdinc -DSTANDARD_INCLUDE_DIR=/home/gnn/FreeBSD/src.latest../usr/include -I/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:32: stddef.h: No such file or directory /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:33: stdlib.h: No such file or directory In file included from /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:34: /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common/crtbrand.c:28: sys/param.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf. *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest. *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest. --- fail: Error 1 error code libraries in Error: failed while making libraries --- Aborting ./release/picobsd/build/picobsd Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Are there periodic GOOD tags in CVS for -CURRENT?
Hi Folks, I'm wondering if anyone has been laying down periodic good tags in -CURRENT so that people who are just starting with it have a place to start that is reasonably stable. Yes, I know about -STABLE but that's not what I mean. Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Latest versions of bsd.lib.mk break picobsd...
Hi Folks,
I've tried contacting [EMAIL PROTECTED] directly but haven't seen anything so I
figure I'll throw this out to the list. On 21 Feb 2002 a change was made to
the
bsd.lib.mk and bsd.prog.mk which is commented, in part, as:
Get rid of the (now unneeded) -I${DESTDIR}/usr/include magic in bsd.prog.mk
and bsd.lib.mk. Finish the removal of LDDESTDIR in bsd.lib.mk,v 1.55 -- we
no longer have users of it.
This change was made by ru. Alas this breaks the picobsd build since the
statically built libraries need some way to know to get their includes from the
directory you're building in. This does not affect a general 5.0 build (I checked
that this morning) but is still very problematic. I'm only just starting with the
picobsd stuff and I would love to fix this bug in the right place if only someone
could tell me what this change meant and how pervasive it was.
Putting in an extra CFLAG for -I${SRC}usr/include works for some libraries but
breaks libbind as alluded to by this comment in the same checkin:
(Attempt to move the -nostdinc -I... part of CFLAGS into the new CINCLUDES
(modeled after a similar CXXINCLUDES) eventually failed because hard-coding
${WORLDTMP}/usr/include to be the first in the include list does not always
work, e.g. lib/libbind.)
So, can someone help me out here?
Thanks,
George
--
George V. Neville-Neil [EMAIL PROTECTED]
NIC:GN82
Those who would trade liberty for temporary security deserve neither
- Benjamin Franklin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Problems with picobsd...
Hi Folks, I'm now mirroring the CVS repository locally (with cvsup) and then checking out the head of the tree with cvs co src to get at -CURRENT. I'm trying to work with picobsd but I get the following on the latest (24 Feb 2002, 22:25 Pacific Time) stuff when I just try to --init the system: cd /home/gnn/FreeBSD/src/lib/csu/i386-elf; make depend; make all; make install cc -nostdinc -elf -Wall -fkeep-inline-functions -I/home/gnn/FreeBSD/src/lib/c su/i386-elf/../common -c /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c -o crt1.o /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c:32: stddef.h: No such file or directory /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c:33: stdlib.h: No such file or directory In file included from /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c:34: /home/gnn/FreeBSD/src/lib/csu/i386-elf/../common/crtbrand.c:28: sys/param.h: No such file or directory *** Error code 1 Stop in /home/gnn/FreeBSD/src/lib/csu/i386-elf. *** Error code 1 Stop in /home/gnn/FreeBSD/src. *** Error code 1 Stop in /home/gnn/FreeBSD/src. --- fail: Error 1 error code libraries in Error: failed while making libraries --- Aborting ./release/picobsd/build/picobsd This comes from the command: ./release/picobsd/build/picobsd --src /home/gnn/FreeBSD/src --init Clues? Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: TWiki as promised...
So how do I add NewCard project to this TWiki? Go into the CurrentProjects area and edit the page. Add a WikiWord that's something like NewCard. You'll see that when you're done editing the new word shows up as an incomplete link (It has a ? at the end). Click on the ? and then you get a fresh page. Add whatever you like to it. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: TWiki as promised...
Would you mind changing the description of the twiki to something else than where all FreeBSD collaboration happens? It might give people the wrong impression. Sure. Suggestions? I don't mind what people put into this, that's much of the point. It's just a place holder. Remember, anyone can edit, it's social pressure that keeps things from a state of chaos. Anyways, what would people like? Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: TWiki as promised...
Information and discussions about various FreeBSD subprojects? Sounds good. Check that in there. BTW, why don't you want a FreeBSD WikiTerm? Well it's a bit odd. Anywhere you put the word FreeBSD lights up as a link. I guess we could put a generic page under it or something but it's annoying (to me at least) to see FreeBSD as a link everywhere when it's mostly just a name. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
TWiki as promised...
Hi Folks, In an attempt to help out with coordination on projects I've put up a TWiki (see www.twiki.org for info on TWiki) site on my web server. As a guest you can read but not update, you have to register to update content. There is a Freebsd web and it has 1 topic which is the SMP project. I have put the entire page from http://www.freebsd.org/smp/ into TWiki. The local references on that page (i.e. the href:./foo.txt stuff) are now external references but we could fix that. A few notes might be helpful. 1) Why did you do this? TWiki (and Wiki's in general) allow people to easily update centralized web content without haveing to have real logins on the web serving computer. This makes keeping things like worklists trivial. The language used by TWiki is NOT HTML but a clever subset that requires a lot less work. For instance a table looks like this: | Task | Responsible | Date| | Task 1| GeorgeNevilleNeil| 2 March 2002 | This will get translated into a nice, simple HTML table by the TWiki stuff. 2) What do I have to do to use this? To read the stuff just go to: http://www.neville-neil.com/twiki/bin/view/Main/WebHome and click on the Freebsd label. To update you must register. Go to the main page and register yourself. The passwords are encrypted but I WOULD NOT use my system password here. Actually, I'd like it if you didn't use any important password there, I don't want to be responsible for y'all in that way. 3) How do I learn more about TWiki? Go to www.twiki.org In particular check out: http://TWiki.org/cgi-bin/view/Main/TWikiPresentation s to see why and how we should be using TWiki. ONE FINAL NOTE. TWiki uses WordsLikeThis to denote automatic links. This means that FreeBSD is an automatic link. If you MUST type FreeBSD then put a nop before it on the page. I'm working with the author to come up with a way to make it so that FreeBSD never gets converted within our TWiki Web. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: TWiki as promised...
Hmm cute I added a comment as an experiment.. really quite easy to use after the first 5 minute learning curve. Well, you're the only one to use it thus far so let's see what others think as well. Thanks for checking it out though. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.)
I'm not in the core of the SMP stuff (the closest I'll get is the networking stuff) but I wonder if there is: 1) A work list of things that need to be done. 2) If that list is easy to read/update. Has anyone considered a Wiki to do this kind of coordination? We used TWiki at my last employer to decent effect. Check out www.twiki.org. Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD Project management (was: Patch sets to date and timi
There is http://www.freebsd.org/smp/ If someone wanted to convert this over to Twiki, go for it. New ideas to add to the list are welcome as well. I'll install TWiki on my home server tomorrow and publish when I'm ready, probably a day or so if all goes well. Then people can try it out and if people like it that will be fine. I'll write up a short email with pointers etc. so people will have an idea what to expect. If people hate it, well there is always rm :-) Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more -current testers
As someone who's just starting down this path as well, I'd say the sooner the better. Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
A quick, dumb, question...
Is there a single document, or small set of documents, that describes getting started kernel hacking on FreeBSD? How about a set of URLs? I would like something that tells me about (in no particular order) 1) debugging over the serial line, and remote debugging in general 2) Building for 5.0 on 4.x (if possible though I suspect I should not do this) 3) Best practices for dealing with my own versions of files while also working with cvsup. Those are a good start for now. BTW If none exists I will try to write this up in the form of a tutorial and post it at some point. Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: re-entrancy and the IP stack.
Are y'all going to discuss this at BSDCon? I'm probably going there and would like to contribute if I could. Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: re-entrancy and the IP stack.
I recommend you all look at The Click Modular router http://www.pdos.lcs.mit.edu/click/ which is a step in the right direction. Of course given the current architecture it may be very hard to adapt it to this kind of model. I led/worked on a project at Wind River Systems to do a multi-instance stack based off of the 4.4 BSD lite code. I can tell you that without quite a bit of rearchitecting what you get is always a hack. There are (were?) over 100 global variables in the 4.4BSD lite code. I've not counted on 4.4 or -CURRENT so I can't say. There are also the issues of the locks though I suspect in -CURRENT (since the kernel is MP) you have handled these in some way. An extensible, multi-threaded TCP/IP would NOT look like the 4.4BSD-Lite code. Is this a goal of FreeBSD now? I am working on some things to make this possible but it is independent of FreeBSD and very very early days as yet. Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Getting a first build up and running?
Hi, I have a machine I want to use as a FreeBSD-Current machine since I want to work with some of the new features in 5.x that I require for a port (I'm trying to port The Click Modular Router from Linux and it would be good to have kernel threads). The problem is that the machine is right now at 4.0-RELEASE. I've done a cvsup for current and am trying to build. I get the following error during make buildworld. The error output is at the end of the email. So, do I need to do something special? Is there a CURRENT-STABLE label of some sort as the last time that -CURRENT was known to build/install? I can't find anything in the handbook on this kind of thing. Is there a "guide to -CURRENT" somewhere? Thanks, George stage 3: cross tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=i386 TOOLS_PREFIX=/usr/obj/usr/src/i386 PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/ src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin TARGET_ARCH=i386 make -f Makefile.inc1 -DNO_FORTRAN -DNO_GDB -DNOHTML -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cross-tools cd /usr/src/gnu/usr.bin/perl/libperl; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl created for /usr/src/gnu/usr.bin/perl/libperl Extracting config.h (with variable substitutions) rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include /usr/src/gnu/usr.bin/perl/libperl/../../.. /../contrib/perl5/perl.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/ perl5/gv.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/toke.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perly.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/op.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/regcomp.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/dump.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/mg.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/hv.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/av.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/run.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp_hot.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/sv.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/scope.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp_ctl.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp_sys.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/doop.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/doio.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/regexec.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/utf8.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/taint.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/deb.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/universal.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/xsutils.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/globals.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perlio.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perlapi.c cd /usr/src/gnu/usr.bin/perl/libperl; make _EXTRADEPEND cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/perl.c -o perl.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/gv.c -o gv.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/toke.c -o toke.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/op.c -o op.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE
Re: Getting a first build up and running?
The click router was designed around he same time as netgraph with many of the same design goals, except they wanted to make it slightly less lego than I did. It is interesting how many common ideas came up but also how many differences As one of the designers of netgraph I'd be interested to hear your thoughts on the comparison. I've looked at both but only played with netgraph a little. Having read the major papers on Click I think it's an excellent way to build highly extensible, field upgradable, fast routers. I guess we'll see of course :-) Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
