Re: Fundraising for FreeBSD development.
Simon L. Nielsen wrote: I cannot promise exposure on the main FreeBSD Project pages, that would be up to the webmasters (and to some extent the core team) to arrange and allow for such precense. We currently have list of donors both on http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/index.html#DONORS and on http://www.freebsd.org/donations/donors.html so I don't see a reason why donations to phk's project could not be somewhere on the main FreeBSD website. Surely PHK's appeal could be linked to in the news section reguardless of whether the final contributors are listed on FreeBSD.org or not? That's sure to increase the awareness of what PHK's trying to do. Andrew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SPAM/virii apparently from freeBSD addresses.
Dag-Erling Smørgrav wrote: Somewhere out there there is a ?Virus?/?Hacker?/?Spammer? getting really annoying.. Yeah, but what do you expect anyone to do about it? Swen and MyDoom are easy to detect and reject at the SMTP stage. The fact that our mail servers don't do this is a PITA, as it forces list subscribers to accept them as well (if you reject list mail because it contains a virus, Mailman disables your subscription). You shoudn't reject email because it contains Swen or MyDoom anyway, all you'll do is generate a bounce message to someone who never sent you the infected mail in the first place - becuase the SMTP envelope addresses are forged. I believe the correct thing to do is to accept in and silently drop it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCM options (was Re: Where is FreeBSD going?)
Peter Jeremy wrote: Most of the noteworthy features of subversion are listed on the project front page: http://subversion.tigris.org/ A significant one of which is the fact that it's available under a BSD-style license. Meaning that the project wouldn't have to rely on more GPLed code. I wonder if our SCM would be brought into the base system or whether it would just be left in ports? We haven't even started to *test* subversion yet, so I think it's a bit early to worry about this question! > I disagree. Andrew raised two issues (type of license and port vs base location). The type of license is an input to the decision as to which SCM to choose - BSD would be preferable but GPL is probably acceptable (given two potential SCMs with similar features, the BSD licensed one would be selected in preference to the GPL one). Indeed - I was just adding to the comments about subversion by pointing out that its BSDness is a point in its favour. The decision on how to manage the SCM is totally independent of the choice of SCM - it relates to the ease of maintenance of the SCM. There's no reason why an "in principle" decision couldn't be made now. Except that the decision of whether our SCM was imported into src/contrib or not might be effected by its license. I mean I know there's plenty of GPLed code in there already, but adding to it might not be such a popular move. Anywho - the topic of SCM is something that rears it's head once in a while (I've really enjoyed how one post from our troll has led to conversations about just about everything :D ). I think we need to wait for subversion to hit 1.0 and then evaluate it carefully. I can't really think of a change to FreeBSD more wide-ranging than changing our SCM, and it would need buy-in from your common-or-garden CVSup user, through commiters and the core team. That's not to say that we can't change. The benefits of doing so are obvious. But we certainly don't want any nasty surprises on the way. Andrew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCM options (was Re: Where is FreeBSD going?)
Peter Schuller wrote: Most of the noteworthy features of subversion are listed on the project front page: http://subversion.tigris.org/ A significant one of which is the fact that it's available under a BSD-style license. Meaning that the project wouldn't have to rely on more GPLed code. I wonder if our SCM would be brought into the base system or whether it would just be left in ports? Andrew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BSDWorld (Was: Hi!Dear FreeBSD!)
Julian Elischer wrote: maybe we should make some sort of geographical registration web page so that people can find each other? A bunch of people from FreeBSD's UKUG started working on this. It was to be hosted on www.bsdworld.net (not generally viewable yet), although it was started it seemed to run out of steam pretty quickly. I've cc'ed the UKUG list in case someone else on there knows what the current situation is. Cheers. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: in-kernel HTTP Server for FreeBSD?
Terry Lambert wrote: >>What about HyperTransport? >>(Not that I know anything about it, but those nice AMD guys keep >>mentioning it in sales garbage :) >> > >They keep mentioning "SledgeHammer", too... > >Have you seen silicon for either one of them yet? > I don't pretend to know much about any of this, but nVidia's new nForce chipset claims to support AMD's HyperTransport. It's mentioned on the bottom of http://www.nvidia.com/view.asp?IO=nppa and possibly in one of the tech brief PDF's in more detail. And nForce motherboards are certainly available to buy right now. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: OS Textbook FreeBSD Appendix
Ronald G Minnich wrote: > >where'd they get this? that's an odd statement. Shared memory was used all >the time on Unix on -11s, that's the whole point of the shared text a.out >format. Of course shared read-only text is not exactly the standard shared >memory, but at the same time it shows feasibility. The address space was >so small though that other mechanisms were used. > Thanks to everyone for their comments! Despite the slight disagreement on this issue of shared memory, I think a link to this PDF is still worth including on the web site and it the programmer's manual. I'll see about getting this added sometime soon. Thanks again! Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
OS Textbook FreeBSD Appendix
Hi all! Apologies if this is common knowledge, but I recently bought Operating System Concepts by Silberschatz, Galvin and Gagne (published by Wiley) for my Computer Science course and the book has several appendices which are available for download from Wiley's web site. One of these appendices is all about FreeBSD and its internals. It's 48 pages long and is available from http://www.wiley.com/college/silberschatz6e/0471417432/pdf/bsd.pdf with the other appendices available on http://www.wiley.com/college/silberschatz6e/0471417432/student.html I don't really know enough detail about FreeBSD to know if what they've written is accurate or worthwhile but I thought if you guys could give it the quick once over, then it could be linked to from somewhere on the web site and perhaps in the Developer's Guide as well. Thanks. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: -Stable installation...
On Tuesday 07 August 2001 4:05 am, Geoff Mohler wrote: > Whats a good reference guide on how to install a -STABLE release? The handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html and the freebsd-stable mailing list, which you should subscribe to and read in order to keep up with the latest comings and goings. An archive of recent messages is available from http://docs.freebsd.org/mail/current/freebsd-stable.html -- Andrew Boothman <[EMAIL PROTECTED]> http://sour.cream.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Automatic Documentation Index
[This was posted to -ports, to no response] Happy New Year, everyone! With the world apparently still in one piece after the celebrations and the few Y2K incidents, I guess we're back to our regular transmissions. Since this message is going outside of -doc where it has been discussed before, I'll offer up a full explanation of what's going on. What is proposed is a system where all the documentation installed through the ports system, or locally by a sysadmin, is collected together and indexed on one HTML page; say /usr/local/share/doc/instdocs.html This page is created by a perl script, docindex, which I envisage being run either from a /etc/periodic/* or /etc/rc or both. The script gets its information from +DOCS files contained within the /var/db/pkg directory for each installed port. These files consist of three fields, colon seperated. The first field being the name of the item of documentation, the second being a filetype, and the third a full path to the file. For example, for Sharity Light : FAQ:txt:/usr/local/share/doc/Sharity-Light/FAQ README:txt:/usr/local/share/doc/Sharity-Light/README In addition the local sysadmin can add similarly formatted files into, say, /etc/docs.local/ that will also be read in and included in the index. In order to help the ports maintainers, and others, create these DOCS files that will be needed, there is a script called docsmaker. This script has a _very_ rough guess from the CONTENTS file of a port what might be documentation. But I stress that the file which it creates will still need to be checked for files that shouldn't be there, files that have been missed, and any other stupid mistakes. :-) Right, I think I'm just about finished. Apart from to say that current versions of the scripts I've been talking about and example outputs from all this are available from http://ukug.uk.freebsd.org/~andrew/docindex/ Does anyone have any thoughts or comments on how to proceed? Many thanks! --- Andrew Boothman <[EMAIL PROTECTED]> FreeBSD UK User Group http://ukug.uk.FreeBSD.org/~andrew/ http://ukug.uk.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
DMI Support
Hi! What's the current situation with DMI support on FreeBSD? A search of the mail archives reveal that we have support for finding the code in the BIOS but not a lot else. Is that still accurate? Do we have any plans to add more support? This is the kind of thing that I would LOVE to help out on myself, but my knowledge of FreeBSD isn't detailed enough, and my knowledge of OS programming is even worse! :) So while I'm still learning, is anyone else working on this? Many thanks! --- Andrew Boothman <[EMAIL PROTECTED]> FreeBSD UK User Group http://ukug.uk.FreeBSD.org/~andrew/ http://ukug.uk.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
compat22 / ld.so - FAQ Addition
Greetings! I've noticed that questions- frequently gets many people asking about "ld.so" problems that they've had since upgrading to 3.x from 2.2.x and the answer to their problem is almost always the same. Therefore I'd like to make sure that the following information is accurate before I submit it to the docproj. Thanks! 500a501,511 > > > I've upgraded from 2.2.x to 3.x and now I get ld.so errors > 3.x FreeBSD systems by default use a different binary format from the > 2.2.x systems. For this reason, when upgrading, the libraries that were > used to execute the old 2.2.x binaries are upgraded so that you can > execute the new 3.x binaries. > > If you need to execute 2.2.x binaries on a 3.x system you should > install the 'compat22' port in /usr/ports/compat22/ which > will install the old 2.2.x libraries. --- Andrew Boothman http://sour.cream.org Unmetered Telecoms. Join the Fight! http://www.unmetered.org.uk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
