Re: fsck: % done possible?
On Sun, May 16, 2004 at 04:44:08PM -0300, Marc G. Fournier wrote: Cause I never knew about that? :) I take it that that is the SIGINFO refer'd in: If fsck receives a SIGINFO (see the ``status'' argument for stty(1)) sig- nal, a line will be written to the standard output indicating the name of the device currently being checked, the current phase number and phase- specific progress information. Quite a few commands support SIGINFO now. cp(1) for example. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) pgps9m6fHVIr8.pgp Description: PGP signature
Re: handbook submissions
On Wed, Mar 24, 2004 at 06:44:36PM +0100, Harti Brandt wrote: what is the correct address to send handbook submissions (in text form, I'm not an SGML guru) to, so that they get picked up? I've send a submission several months ago to one of our committers, but he seems to be more involved with DF-BSD nowadays. send-pr. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) pgp0.pgp Description: PGP signature
Re: Discussion on the future of floppies in 5.x and 6.x
On 8 Jan 2004, at 14:39, Leo Bicknell wrote: Then, to replace the current floppy process, a new floppy installer is created. It may or may not be based on FreeBSD, but what it needs to be able to do is boot, load a network driver, configure the network, and ftp the above mentioned iso into ram, and then jump into the kernel from the iso as if it had been loaded from a CD. Or mount the ISO image from a FAT, NTFS, UFS, or EXT2FS filesystem on a disk that's already in the machine... N PGP.sig Description: This is a digitally signed message part
Re: Making a FreeBSD DVD
On Sun, Nov 23, 2003 at 09:28:37PM -0500, Leo Bicknell wrote: I'd like to make my own distribution DVD's. I know how to make CD's, but looking at release(7) I see lots of documentation for CD's, and none for DVD's. Googling turns up nothing of interest in the first three pages. Can anyone point me to the documentation on how to build DVD's, a-la what they sell on FreeBSD mall? Do you mean one offs, using a DVD burner, or do you mean in bulk, using a DVD replication house? If it's the former, ports/sysutils/dvd+rw-tools. If it's the latter, ports/sysutils/dvdtape. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) pgp0.pgp Description: PGP signature
Re: Hi!Dear FreeBSD!
On Sun, Feb 02, 2003 at 10:37:21AM -0600, Stephen Hilton wrote: I really like this idea :-), and think that a database of all types of FreeBSD people from end-users to commiters who want to opt-in to this listing could spawn a lot of educational and fun opportunities for individuals who could drag themselves away from their screens on occasion ;-) Why not base it on latitude and longitude, along with an email address and text fields to allow for some self expression of areas of interest etc...? A clickable map would be a nice interface for the database lookups with a max radius factor, but really is just icing on the cake. Please, no wheel reinvention. http://www.pm.org/groups/index.html N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg40002/pgp0.pgp Description: PGP signature
Re: Mac iBook OS10 + BSD
On Wed, Jan 15, 2003 at 12:37:25AM -0500, void wrote: On Thursday, December 26, 2002, at 09:59 AM, Andrew Gallatin wrote: I think he means text-only syscons like vtys. MacOSX does not have them. I don't know about *multiple* text-only vtys, but it's easy enough to get the system into a no-graphics mode. In case anyone's wondering how you do this on OS X, just log in at the GUI with the username 'console' (no quotes). N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg39317/pgp0.pgp Description: PGP signature
Re: troff vs. DocBook (was: Request for submissions: FreeBSD Bi-Monthly Development Status Report (fwd))
On Mon, Jul 22, 2002 at 09:58:23AM +0930, Greg 'groggy' Lehey wrote: IMO the tags aren't the problem with DocBook. It's just *really* difficult to get good-looking results with. What did you think of the 2nd edition of the Handbook? That was Docbook toolchain all the way (with the possible exception of some small hand-tweaks to the finished postscript by Murray). N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg35943/pgp0.pgp Description: PGP signature
Re: Limiting clients per source IP address (ftpd, inetd, etc.)
On Fri, Jun 21, 2002 at 03:09:25AM +0300, Giorgos Keramidas wrote: I've been thinking for quite some time to add per-client-IP limiting to ftpd, I needed to do this. Then I discovered that ipfw's limit directive lets you limit the number of incoming connections, which proved much more powerful. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg35241/pgp0.pgp Description: PGP signature
Re: USB: Anyone working on it?
On Thu, Jun 06, 2002 at 02:09:08PM -0500, Larry Rosenman wrote: Is there anyone out there working on USB stuff? Joe Karthauser -- [EMAIL PROTECTED] I reported kern/37624 a while back, and have heard nothing on it. He's on holiday at the moment. Back in a few weeks, IIRC. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg34890/pgp0.pgp Description: PGP signature
Re: allocating memory
On Thu, Jun 06, 2002 at 12:47:54PM -0500, Mike Silbersack wrote: See the paper on porting NetBSD to hammer that was presented at some recent usenix convention for more info. (I think it was usenix, but I'm not sure.) BSDCon US 2002. It was presented by Frank van der Linden. From my notes of the conference, Frank said the porting effort took about six weeks of effort. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg34891/pgp0.pgp Description: PGP signature
Re: using vnconfig devices instead of partitions for jails ?
On Thu, Feb 28, 2002 at 02:32:03PM -0800, Patrick Thomas wrote: thank you - I am glad to see that this is a good way of doing things Two quick items: 1 How do I give each jail a 'proc' filesystem in its /proc using this configuration ? mount -t procfs proc /usr/local/jails/foocom/proc Do this *after* you've mounted the vn device on /usr/local/jails/foocom 2 Is there any downside to this whatsoever ? This seems infinitely better than a new partition for each jail, so was I just silly for doing it that way ? The only real problems I've run into relate to the fact that the FreeBSD startup scripts know nothing about jails So there's some script writing required to get things to start up appropriately at boot time N -- FreeBSD: The Power to Serve http://wwwfreebsdorg/ (__) FreeBSD Documentation Projecthttp://wwwfreebsdorg/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- \_/_) msg32274/pgp0.pgp Description: PGP signature
Re: using vnconfig devices instead of partitions for jails ?
On Wed, Feb 27, 2002 at 03:03:11PM -0600, Kirk Strauser wrote: At 2002-02-27T20:49:18Z, Patrick Thomas [EMAIL PROTECTED] writes: I would like to put a large number of jails (16 or 20) on a server for testing purposes. I have two options so far: create 16 or 20 partitions OR just put them all in one partition, but the downside of that is that then I cannot enforce disk usage between jails. So at this point, 16-20 partitions seems the safest route. Good question. Is there any ability at all within the system to set a quota on a jail? Each vn* device has to be baced by a physical file on the system. Simply make sure that this physical device is the maximum size you want to allow in the jail. For example, on a server with 160GB of (RAID) disk, and 12 jails, each 10GB in size, I just have 12 jails; On the 'master' host for the jails. # cd /usr/local/jails/disk-images # ls -l totall 1758115 drwxr-xr-x 2 root wheel 512 Jan 23 00:40 . drwxr-xr-x 4 root wheel 512 Jan 23 00:39 .. -rw-r--r-- 1 root wheel 136 Jan 22 18:45 README -rw-r--r-- 1 root wheel 10737418240 Feb 27 23:35 foo.com.vn -rw-r--r-- 1 root wheel 10737418240 Feb 27 23:35 bar.com.vn -rw-r--r-- 1 root wheel 10737418240 Feb 27 23:35 baz.com.vn ... These were created with truncate 10G file, and are then mounted configued on different vn* devices, which are then mounted as normal. # mount ... /dev/vn0a on /usr/local/jails/foo.com /dev/vn1a on /usr/local/jails/bar.com /dev/vn2a on /usr/local/jails/baz.com ... N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg32219/pgp0.pgp Description: PGP signature
Re: stack alignment issues
Bruce, On Tue, Feb 05, 2002 at 05:01:29PM +1100, Bruce Evans wrote: My patch is not suitable for committing verbatim. It has 2 or 3 XXX's. Do you make these patches available anywhere, so that other people can look over them and maybe help you on the XXX'd sections? N -- FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Projecthttp://www.freebsd.org/docproj/\\\'',) \/ \ ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/_) msg31430/pgp0.pgp Description: PGP signature
Re: how to mirror gnats db?
On Fri, Dec 21, 2001 at 04:54:43AM -0800, Hiten Pandya wrote: I wanted to ask, how I could mirror the gnats database to my own system. I have cvsup. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/gnats.html N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- msg30394/pgp0.pgp Description: PGP signature
Re: making /usr/share/mk apps PREFIX-independant???
On Fri, Dec 21, 2001 at 10:49:13AM +0200, Sheldon Hearn wrote:
On Fri, 21 Dec 2001 09:30:30 +0200, Ruslan Ermilov wrote:
I'm against PREFIX in share/mk files. Instead, just setting
DESTDIR=${PREFIX} should (almost) be enough.
I agree. See ports/mail/popd/Makefile for an example of a port that
uses a pure bsd.prog.mk-driven Makefile for ${PREFIX}-sensitive
installation.
Doesn't it strike anyone as being a bit, well, icky, that we have to do
this for software developed on this platform, using this platform's
standard infrastructure for defining Makefiles?
Perhaps just a USES_BSD_MK=yes flag to wrap this for other ports as
well (I'm thinking specifically of the scr* stuff I wrote, but there may
be others).
N
--
FreeBSD: The Power to Serve http://www.freebsd.org/
FreeBSD Documentation Project http://www.freebsd.org/docproj/
--- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 ---
msg30350/pgp0.pgp
Description: PGP signature
Re: making /usr/share/mk apps PREFIX-independant???
On Fri, Dec 21, 2001 at 01:16:41PM +0200, Ruslan Ermilov wrote: You don't listen. :-) snip I don't pretend that this solution is ideal, as a port may need different BINDIR settings for its different parts. I have given a little thinking to this, just to demonstrate that the fixes should go into ports/Mk, not into the base .mk files. That's what I meant. We're in violent agreement :-) N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- msg30355/pgp0.pgp Description: PGP signature
Re: Tangent for discussion: FreeBSD performs worse that Linux
On Mon, Dec 10, 2001 at 03:24:14PM -0600, D J Hawkey Jr wrote: Doesn't mean that you need 100% coverage though. If you produce something that only gets in 80% of the patches that could be applied back that's still better than what we have now. And it makes it easier for someone else to help out with the missing 20%. Huh? You completely list me with this. Are you trying to say that some feature of a patch that applies to just the last three of four prior releases is OK, 'cuz right now none are (except for security fixes to RELENG_(current - 1))? I meant that any effort you put in is better than none. For example, if you decide to start producing patches for 4.4 that bring in some features from -stable (e.g., delayed acks) that's far better than you not doing it at all. Don't feel that because you can't do everything you want to do that you shouldn't do any of it. If you get the ball rolling, and become known as *the* place to go for extra patches, you'll find that other people start sending you additional patches to include. Pretty soon we'll get bored of having people ask Hey, why aren't these patches in RELENG_4_4 (or whatever) and we'll corral you in to becoming a committer so that you can make this an 'official' part of FreeBSD. So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. Not exactly the repertoire one would need to garner interest and momentum. It's a start. What's the URL? You're kidding, right? I only started thinking about doing this yesterday! The patches are sitting right here, in $(HOME)/projects. OK. Well, if you put them up on a web site, we can link to them. If you can think of appropriate other places on the FreeBSD web site to mention them then we can do that too. Don't be put off because you want to start small. . . N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- msg29969/pgp0.pgp Description: PGP signature
Re: Tangent for discussion: FreeBSD performs worse that Linux
On Sun, Dec 09, 2001 at 12:17:03PM -0600, D J Hawkey Jr wrote: Seems to me that were I to do this, and I would, it would only be as viable as the patches themselves. That is, I (and any contributors) would have to be able to stay abreast of those things going on in -STABLE that could get backported to previous releases (could being a significant word here). Well, yeah. That's pretty much a pre-requisite. Doesn't mean that you need 100% coverage though. If you produce something that only gets in 80% of the patches that could be applied back that's still better than what we have now. And it makes it easier for someone else to help out with the missing 20%. So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. Not exactly the repertoire one would need to garner interest and momentum. It's a start. What's the URL? N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- msg29898/pgp0.pgp Description: PGP signature
Re: Tangent for discussion: FreeBSD performs worse that Linux
On Sun, Dec 09, 2001 at 11:15:23AM -0600, D J Hawkey Jr wrote: I could maintain a not-FreeBSD-sanctioned site for patches of -CURRENT and -STABLE code applyable to previous releases, but that would only muddy the FreeBSD maintenance and distribution waters that I think work well for what they're intended to address, as well as open myself up to all sorts of support and maintenance headaches. Actually, that's probably the best thing you could do. Because then it shows that you've got the commitment to do this sort of thing and maintain it. The project isn't short of people having good ideas, it's short of people willing to do the actual work. If you do this, and show that the idea is viable, it will be much easier to come back in a few months time to get these patches integrated in to the various RELENG_* branches, and to bring you in as a committer. I'm sure we can make sure that any site you set up to do this is linked to from the FreeBSD web site. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- msg29838/pgp0.pgp Description: PGP signature
Re: Mea Culpa on C++ and ISO Sockets
[ Note reply-to ] On Tue, Nov 13, 2001 at 12:45:20PM -0800, Mike Smith wrote: All I want to know is if anyone else has had problems using C++ (in general) crashing the kernel during subsequent initialization of the same program or specifically with AF_ISO family (-liso) sockets. Nothing more than that. I suspect that the ISO socket code is woefully under-tested, and may in fact demonstrate never-really-worked-the-first-time syndrome. Mike Smith (again, not THE Mike Smith) You're no more or less Mike Smith than I am, dude. 8) In some sense I suspect that we all, in fact, may be Mike Smith. Nik Mike Smith Clayton -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- msg28537/pgp0.pgp Description: PGP signature
Re: FINAL REMINDER: FreeBSD Monthly Development Status Report -- Request For Submissions
On Fri, Sep 07, 2001 at 10:34:29AM -0400, Robert Watson wrote: Project: (name here -- required field) URL: (URL, if any, here -- omit field if none) Contact: (name and e-mail address of one or more contact points -- required field) Project: Documentation Project URL: http://www.FreeBSD.org/docs.html URL: http://www.FreeBSD.org/docproj/index.html Contact: Documentation Project [EMAIL PROTECTED] The Handbook has been the main focus of activity this month. Due to go to the printers on the 15th a vast amount of new content has been submitted and committed. This includes a complete rewrite of the Installing FreeBSD, which massively expands the amount of information available to people new to FreeBSD. It even includes screenshots. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html Comments, and contributions are, of course, welcome. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: Page Coloring
On Sun, Aug 05, 2001 at 12:20:36PM -0700, Matt Dillon wrote: It's a good description but it might be better to simplify it a bit. You don't need to go into that level of detail. There is a short page coloring explanation at the end of my VM article which might be more suitable to a man page: http://www.daemonnews.org/21/freebsd_vm.html That got pulled in to the documentation project a while ago, and can be found at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vm-design/index.html This makes it pretty easy for us (you) to keep it up to date as you change FreeBSD's VM system. . . :-) N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Diagram / description of a packets path
How do, Something I've wanted for a while, and not found (and don't know enough to write myself) is a description of the path an IP packet takes through the kernel, and where things like ipfw, ipfilter, natd, ipdivert, and so on, take effect. Something like (and keep in mind I've got no idea how accurate this is): [in] -- Interface the packet arrives on (e.g., fxp0) | | V [ipfw] --. -- Processing by IPFW || | |`[divert]--' -- Processing by IPFW divert rules V [...] and so on. Anyone up for this? N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: getting rid of sysinstall
Actually, this is what I did for Google, we were able to have 40 machines installed in about an hour: http://people.freebsd.org/~alfred/pxe/ Or http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/index.html N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: FreeBSD Mall now BSDCentral
On Tue, Jul 10, 2001 at 03:51:15AM +, Terry Lambert wrote: ] I never said a CDROM must boot to sysinstall and I challenge you to ] find a quote to that effect. What both Nik and I said was that it ] must be an OPTION to do so, somehow, or you haven't provided a stock ] FreeBSD experience and people are potentially going to be confused as ] to what FreeBSD means. This holds especially true if you haven't ] provided source code to your wizzy installer and they have no way of ] figuring out how or why it's even misbehaving, which you can bet it ] will since nobody ever writes perfect software. You know that the CDROM boot process is based on a 2.88M floppy image. If it must be an OPTION to do so, then you are saying the same thing: that it must boot to sysinstall. Not at all. If you're thinking of shipping a CD, make sure that somewhere on that CD is a copy of the existing two floppy images, a copy of fdimage (or similar), and a paragraph of documentation that says: If you would prefer to use the standard FreeBSD installer (sysinstall) then take two blank floppies. Insert the first floppy, and run fdimage mfsroot.flp a:, then insert the second floppy and run fdimage boot.flp a:. Leave that floppy in the drive, and reboot (making sure to set your BIOS to boot from floppy). The FreeBSD Project installer will then start. Using this installer is not documented here (we strongly urge you to use the installer we provide and document) but it is covered in chapter 2 of the FreeBSD Handbook, at http://www.FreeBSD.org/. That would completely satisfy the requirements I've outlined. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: FreeBSD Mall now BSDCentral
On Tue, Jul 10, 2001 at 02:26:43PM +0200, Olaf Hoyer wrote: We agreed to do something in Europe: - providing informational structure for BSD - providing a channel where people that want to do booths at exhibitions etc may contact and get some help, pre-financing (perhaps) and merchandise articles to help financing the whole thing. Can I point you at the BSD EU Group mailing list, [EMAIL PROTECTED], where much the same discussions are happening at the moment. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: FreeBSD Mall now BSDCentral
On Mon, Jul 09, 2001 at 10:10:37AM -0700, Terry Lambert wrote: Nik Clayton wrote: The thorny question of What do they have to include and still call it FreeBSD? is resolved by saying that any FreeBSD distribution must include, as a minimum, the contents of the mini ISO (including sysinstall). Anyone that wants to include an alternative installation routine (open or closed source) can do, as long as sysinstall is still there. Then the FreeBSD docs can continue to refer to sysinstall, and the project doesn't get flack if someone puts together a distribution with a crap installer, because sysinstall will always be there as a fallback. First: sysinstall must die: this is non-negotiable. Second: it is an albatross, and forcing people to include it is obnoxious, and definitely not in the long term best interests of the project. Third: tying the hands of distributors with regard to what they must distribute is stupid: you might as well GPL the damn thing, and call it a day, if you want that level of editorial control over third party distributors content. It's reasonable to want to control what get's called FreeBSD. The intent here is not to prevent third party installers -- they can be open source, closed source, or whatever mix you want. If you want to produce a commercial distribution of FreeBSD that does not use sysinstall as the default installation mechanism then go right ahead, make it the default, have it come up automatically when your customers boot from CD, and so on. However, if you want to call it FreeBSD, then, somewhere, sysinstall (and whatever replaces it) must be available. Put it on boot-legacy.flp if you want, and strongly urge your customers not to use it. But make it available to those that want it. Then I can make sure that the Handbook chapter on installation says, right at the beginning: This chapter describes how to install FreeBSD using the installation software provided by the project. Third party vendors are completely free to provide their own installation routine, document it, and support it. However, they must also provide and document a mechanism for you to use sysinstall. This is the only installer we document here, and it's very likely that the members of -questions mailing list will only be able to answer installation related questions if you're using sysinstall. If, at some point, you (or whatever third party develops a better installation system) donates it back to the project then it becomes the sysinstall replacement we've all yearned for, and the documentation can be updated accordingly. Personally, I'd be perfectly happy to trust people to do right by the project; I'd be happy with an X server that configured itself in software, and with a default boot-to-X and that Java version of the InstallShield product. I'd also like to see someone produce a handicap accessible version of FreeBSD: e.g. there would be no sysinstall. I'd like to see a distribution that Installed multiple roots, and supported fail-over booting like nextboot used to. And I want to see a distribution where / is mounted read-only, with only the necessary parts being mounted writeable at all. All of that is fine. Indeed, I'd like to see them happen as well. Making people keep sysinstall precludes innovations which make FreeBSD more accessible to more people, and broaden the user base. Just to make sure we're not talking at cross purposes -- all I'm saying is that sysinstall must be available somewhere on the installation media that you provide, and that instructions on how to boot from it as an alternative to whatever installation mechanism you provide must also be available. I am *not* saying that sysinstall *must* be used, just that it *must* be available for use. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: FreeBSD Mall now BSDCentral
On Mon, Jul 09, 2001 at 11:32:53AM -0700, Terry Lambert wrote: Historically, you've always held that the CDROM must boot to sysinstall. As the software's daddy, I can see why you'd want that; but your baby is ugly. That's changed -- it's certainly what I was discussing with Jordan. You just have to make a bootable image with sysinstall available on the media; it does not need to be the default installer. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: FreeBSD Mall now BSDCentral
On Sun, Jul 08, 2001 at 10:04:31PM +0100, Brian Somers wrote: Poul-Henning Kamp wrote: Perhaps this labelling can be in the form of information on the FreeBSD.ORG web site that lists distributions that merit the official label. That seems to make a lot of sense. In this context, ``official'' really means ``sanctioned by the FreeBSD project''. Sounds like prime fodder for the Obtaining FreeBSD section of the Handbook (which should be linked to by everywhere on the website that talks about getting FreeBSD -- if it doesn't, it's a bug which should be PR'd). N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: FreeBSD Mall now BSDCentral
On Fri, Jul 06, 2001 at 12:55:25AM -0600, Wes Peters wrote: Ted Mittelstaedt wrote: If WindRiver gets on the ball and keeps fulfilling CD orders, why then this name might continue to be worth something. Otherwise, it will go away and the FreeBSD CD distributions will simply take place through other distributors. Or not, if every other distributor that actually cares to distribute FreeBSD has dried up and blown away because WRS has been handing out exclusive access to the official FreeBSD ISO images. This came up in discussions at Usenix between myself and several members of -core. I agree that the project needs a clearer distinction between releases made by the project, and releases made by commercial third parties, such as Wind River, or the DVDs put out by FreeBSD Services Ltd (or the various distributions put together by other European and Japanese companies). I think that the conclusion is that the project should be putting out five ISOs and making them freely available. Four of them would correspond with the four discs that have traditionally made up the commercial CD sets. The fifth one would be a mini-ISO that contains everything needed to do a complete install, but now ports or packages (basically, the existing disc 1 with no third party apps, except, possibly, XFree86). This ISO would only be about 200-250MB in size, and is more useful to the people who only download the ISO to do an install, and use the net for packages/ports. Third parties can then base their commercial distributions around these ISOs. They might simply repackage them (on CD, or DVD). Or they might provide value-add services, such as additional documentation, more packages and so on. The thorny question of What do they have to include and still call it FreeBSD? is resolved by saying that any FreeBSD distribution must include, as a minimum, the contents of the mini ISO (including sysinstall). Anyone that wants to include an alternative installation routine (open or closed source) can do, as long as sysinstall is still there. Then the FreeBSD docs can continue to refer to sysinstall, and the project doesn't get flack if someone puts together a distribution with a crap installer, because sysinstall will always be there as a fallback. N -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- PGP signature
Re: strangeness in web interface of send-pr
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 13 June 2001 8:57 pm, Giorgos Keramidas wrote: I have a few hours to spare tonight, and I was using the query-pr-summary.cgi script to view the open PRs. [snip] Looks like this has been resolved. However, if this is something you want to do on a regular basis, you might want to take a look at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/gnats.html which explains how to keep a local copy of the GNATS repo up to date using CVSup -- then you can use local tools to query it. N - -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjsp6jQACgkQk6gHZCw343VcbwCfcHsJKGqhiFehoE9udjmwQ3+a YssAn2jTa6fEBL4xsCDuwR+ZgeK5q/Uj =iqb1 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Updating mmap(2) [nik@freebsd.org: Re: pipe]
There was no comment to these. Any objections if I commit my proposed changes? N - Forwarded message from Nik Clayton [EMAIL PROTECTED] - Date: Thu, 7 Dec 2000 16:33:32 + From: Nik Clayton [EMAIL PROTECTED] To: Dag-Erling Smorgrav [EMAIL PROTECTED] Cc: "G. Adam Stanislav" [EMAIL PROTECTED], Stephen McKay [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: pipe On Wed, Dec 06, 2000 at 09:50:55AM +0100, Dag-Erling Smorgrav wrote: "G. Adam Stanislav" [EMAIL PROTECTED] writes: On Tue, Dec 05, 2000 at 06:11:06PM +0100, Dag-Erling Smorgrav wrote: The second and third sentences of the second paragraph (the one that starts on line 23), as well as the entire eighth paragraph (that starts on line 45), address the questions you asked in your previous mail. I know it addresses it. Unfortunately, I didn't understand a word of it. I don't see how it could get any clearer. [...] If addr is zero, an address will be selected by the system. The actual starting address of the region is returned. NAME mmap - map files or devices into memory [...] doesn't immediately shout "You can use this function to allocate memory as well". Perhaps mmap - allocate memory, or map files or devices into memory would be better? In addition, mmap isn't listed in the SEE ALSO for malloc(3), nor is it listed in memory(3). mmap() is listed in malloc(3), but only in an error message. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message - End forwarded message - -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: documenting an ioctl interface
On Mon, Feb 05, 2001 at 05:18:22PM -0800, Brooks Davis wrote: I'm working one some code which among other things introduces a new ioctl interface for IEEE802.11 devices. Since there are a number of useful apps which might want to use this iterface and a number of drivers which will need to implement it that I can't test it seems like I should write a manpage for this. Can anyone point me to a sample of such documentation to give me an idea of how to structure it? Nothing immediately leaps to mind. I've cc'd this to the freebsd-hackers mailing list for suggestions. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: docs/24035: ptrace(2) PT_STEP incorrect documentation
Folks, On Tue, Jan 02, 2001 at 09:05:29PM -0800, [EMAIL PROTECTED] wrote: Number: 24035 Category: docs Synopsis: ptrace(2) PT_STEP incorrect documentation snip Description: in the man pge PT_STEP The traced process is single stepped one instruction. The addr and data fields are not used. this is a lie. you must feed ptrace() a valid value for addr, just like PT_CONTINUE ? I've poked through ptrace.S, but it's been a long time since I did any assembler, and when I did, it was 6502. . . N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: anyone want to learn XML / work on FreshPorts2?
On Sat, Dec 23, 2000 at 01:36:16AM +1300, Dan Langille wrote: I plan to parse the cvs-all messages into an XML log. The first stage is to create an XML template. This template will be used by any source tree which wishes to input data into FreshPorts2. But for now, we'll concentrate on cvs-all from FreeBSD. Look at ports/devel/cvs2cl, which converts CVS logs in to GNU style changelogs. One of the output options is the CVS logs in XML form. That's probably a good starting point. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Thinkpad Partition Problem Solved?
x-posting to -hackers On Fri, Dec 22, 2000 at 12:18:05PM -0800, Bruce A. Mah wrote: qandaentry + question id="boot-on-thinkpad" + paraI have an IBM Thinkpad A20p that FreeBSD installs on, but then + the machine locks up on next boot. How can I solve this?/para + /question I'd start with "I have an IBM ThinkPad in the A, T, or X series...". My wonderful (actually it *is*, now that this problem's solved) T20 crapped out to start this off. Is there any way we can detect this at boot time, or sysinstall time? It would be nice to throw up a WARNING You are attempting to install on an IBM ThinkPad A, T, or X series machine. A BIOS bug makes it likely that FreeBSD's default install will leave your computer in an unbootable state. Unless you have read and are planning to follow the instructions at http://www.FreeBSD.org/faq/... you should exit this install immediately. message? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: keeping lots of systems all the same...
On Wed, Dec 20, 2000 at 03:15:40AM -0500, Mike Nowlin wrote: I'm planning on building a fairly big machine to do world builds on to keep these machines (30-ish) all synced to the same OS version, probably with weekly installworlds on them. Have you had a look at PXE? Basically, each time the machine reboots you can have it reimage itself from a master server. See http://people.freebsd.org/~alfred/pxe/ for details. Your NIC has to support it, and I don't know how long the reimaging process takes over 100Mbit, but it's probably less maintenance effort for you in the long run. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need to edit VM tuning section in handbook, any special requirements?
On Mon, Dec 18, 2000 at 09:31:37PM -0800, Matt Dillon wrote: Is there anything special I need to do to edit a section in the handbook, or can I just commit it? A pass through -doc for review wouldn't be amiss. In general, this means that we make sure that none of the rules at http://www.freebsd.org/tutorials/docproj-primer/writing-style.html are broken. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: pipe
On Wed, Dec 06, 2000 at 09:50:55AM +0100, Dag-Erling Smorgrav wrote: "G. Adam Stanislav" [EMAIL PROTECTED] writes: On Tue, Dec 05, 2000 at 06:11:06PM +0100, Dag-Erling Smorgrav wrote: The second and third sentences of the second paragraph (the one that starts on line 23), as well as the entire eighth paragraph (that starts on line 45), address the questions you asked in your previous mail. I know it addresses it. Unfortunately, I didn't understand a word of it. I don't see how it could get any clearer. [...] If addr is zero, an address will be selected by the system. The actual starting address of the region is returned. NAME mmap - map files or devices into memory [...] doesn't immediately shout "You can use this function to allocate memory as well". Perhaps mmap - allocate memory, or map files or devices into memory would be better? In addition, mmap isn't listed in the SEE ALSO for malloc(3), nor is it listed in memory(3). mmap() is listed in malloc(3), but only in an error message. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: int80h.org
On Sun, Nov 26, 2000 at 11:16:49PM -0600, G. Adam Stanislav wrote: Anyway, I decided to really write something serious about assembly language programming under FreeBSD. So much so that I secured a domain just for that purpose: int80h.org (mostly because I got the impression from www.linuxassembly.org that int 80h belongs to Linux!). I have just placed the first page on it. I hope I have configured my .htaccess properly so, as soon as the DNS system realizes there is a http://www.int80h.org/ it will send you the right page (I am sharing it with my main web site whizkidtech.net, and simply ask .htaccess to give you a different start page if you come to int80h.org - that is why I said I hope it is going to work). If curious, you can read it even now. If your browser cannot locate int80h.org yet (it should tomorrow), you can find the same page as http://www.whizkidtech.net/int80h.hed for now. It certainly looks interesting. One thing though -- have you considered DocBook as the documentation format? That would make it much easier to integrate this with the existing FreeBSD documentation (either as part of the Handbook, or as a separate book). This would bring a number of benefits: * Immediate access to your text via CVS for the rest of the world. * Your text would be mirrored automatically by all the FreeBSD mirrors. * It becomes much easier for the various FreeBSD translation teams to translate your document. More information can be found at http://www.freebsd.org/tutorials/docproj-primer/ N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need dotfiles for various L10N groups
On Sat, Oct 28, 2000 at 04:04:38PM -0500, Michael C . Wu wrote:
I am trying to collect various dotfiles (.cshrc, .profile, .Xresources,
.Xdefaults, ~/.*) for various language localization groups.
As I discussed with Nik Clayton, I hope to create
/usr/share/skel/{chinese, japanese, french, russian, korean, vietnamese *}
Shouldn't these be /usr/share/skel/{ja_JP.eucJP, zh_TW.Big5, ...} to cater
for the same language/multiple encodings problem?
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: sysctl interface for apm?
On Mon, Jul 17, 2000 at 01:12:23PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Nick Sayer writes: : The "why bother" is easy -- one should not have to belong to group : operator to determine the current battery state. Too many things : already have to be sgid (at least) without making this another reason. You should already be a member of group operator so that you can suspend your machine :-). Not necessarily. Fn+Esc (or Fn+F12) works quite nicely on this VAIO. However, wouldn't it be much simpler and easier to make apm world readable instead? Hmmm, and hack apm.c to open readonly. Hmmm, there are other problems with that since you can do the nasty things... But those should be fixed. I'd prefer getting the permissions right as well. Querying the current battery state shouldn't require special privs. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Can anyone recommend a good clustering software?
On Tue, Jul 11, 2000 at 04:17:53PM +0200, Frederik Meerwaldt wrote: Can anyone tell me a clustering software for FreeBSD? PolyServe? No URL, as I'm in the air at the moment, but try a general web search, or look at past announcements on DaemonNews, where it was mentioned a few weeks back. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Documentation selection in sysinstall
On Mon, Jun 26, 2000 at 09:37:40AM -0700, Jordan K. Hubbard wrote: In theory, this is a doddle. sysinstall already lets the user choose from packages to install. In practice, I think it's a little more difficult, because: I'm still wondering why the docs bits can't be, at a minimum, "front-ended" by the ports collection in a new doc category? We could do this -- I'd probably use the ports collection to front-end the binary packages. Otherwise, the user might as well just go and CVSup the doc/ collection themselves, and build it that way. I'm thinking of initially presenting a dialog box that looks like this: I'm certain that once you start writing code for libdialog, my suggestions above will start sounding a lot less icky than they probably do to you right now. :-) I have no intention of going anywhere near libdialog -- like I say, I can either put forward proposals and ideas, and assist with them, or I can try and do one thing at a time. At the moment, keeping up with the -doc mail is almost a full time job in itself. What happened to the plans to move to the TurboVision library? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Documentation selection in sysinstall
[ Going to -doc where it's pertinent, -hackers where it might find someone who's prepared to do the work, and jkh for any expert commentary he feels like tossing in. And while I've got Jordan's attention -- did the last attempt at re-writing sysinstall generate any specification documents? If nothing else, they'd be useful content for the doc project. ] [ I didn't go through this at Usenix -- not enough time ] The documentation is now being built and made available as FreeBSD packages (one package per combination of document, language, and output format). This means we could do away with the "doc" distribution when installing FreeBSD, and instead allow the user to choose which documentation packages they want to install. In theory, this is a doddle. sysinstall already lets the user choose from packages to install. In practice, I think it's a little more difficult, because: 1. [ I haven't run the code to confirm this, not having a network connection at the moment. ] When you do the "post-install" configure via sysinstall, it wants to grab the INDEX file from somewhere (CDROM, the 'net, or whatever) in order to present you with an up-to-date list of packages to install. The doc package building doesn't work like that. There is no INDEX file for sysinstall to grok. We need to find some other way for sysinstall to get the list of docs, languages, and formats that are supported it. This shouldn't be too hard -- looking in /pub/FreeBSD/doc/packages on the FTP site gives a complete list of what's currently built in terms of languages and output formats, and the filenames are easily parseable. 2. We need to find a UI model that allows the user to efficiently select the language and formats they want to install. I'm thinking of initially presenting a dialog box that looks like this: Documentation is available in the following languages: English Spanish French Japanese Chinese with the list extending as necessary, based on what sysinstall found on the FTP site. After the user has chosen a language, then present them with a list like this: Now choose the documentation you would like to install, and the formats you would like to use. HTML HTMLText PS PDF PDB RTF Split Books Handbook[ ][X] [ ][ ] [ ] [ ] [ ] FAQ [X][X] [ ][ ] [ ] [ ] [ ] Porter's Handbook [ ][ ] [ ][X] [ ] [ ] [ ] [... and so on ...] From my reading of dialog(3) I believe this to be, uh, optimistic at best. I've also glossed over the issue of how sysinstall turns "porters-handbook" in a filename to "Porter's Handbook" on screen. Thinking about it, we will probably need an INDEX.lang file that maps filenames to titles -- we should be able to generate this when we build the packages by grabbing the first title element from a document. The alternative to a display like this would seem to be a fairly horrendous nest of menus and sub-menus that the user would have to navigate through. That's about where I am in my thinking about this so far. Alternative viewpoints, suggestions, offers to do the work, and prototypes are gratefully received. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multilingual Installer for 3.2-RELEASE (Re: pccard boot.flp...)
On Thu, Jun 01, 2000 at 07:00:08PM -0700, Jordan K. Hubbard wrote: Just following up on this - are there any plans to merge this work back into the mainstream so that we can generate "localized" installation floppies for the Japanese community in future releases? Thanks! (Yes, I'm really catching up on email over a year old today). Likewise, the French translation team have expressed a strong interest in working on a localised sysinstall. If someone's already done most of the work then I'd like to know more too. Cheers, N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Teaching sysinstall about the documentation packages
[ -doc, -hackers, and jkh.pl on the To: line. Watch those replies :-) ] For those that haven't been keeping up at the back, Doc. Project package generation is now pretty stable. What this means is that if you take yourself off to ftp.FreeBSD.org:/pub/FreeBSD/doc/packages/ and take a look in there, you'll see one package for each document, format, and language combination we currently support, all ripe for putting through pkg_add(1). Modulo some final testing, automatic generation of these is pretty much sorted. So, the time has come to think about ripping out the doc distro from "make release", and to teach sysinstall about these packages instead. Much as I relish the chance to do this, I'm already up to here with other doc. proj. pointy-hair work and all the fun things that entails, so I'm not going to get the chance to do this any time soon. Any volunteers? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
/usr/share/examples/cvsup - /usr/local/share/examples/cvsup
Folks, Would anyone object to pulling /usr/share/examples/cvsup out of the base system, and into /usr/local/share/examples/cvsup, to be installed by the CVSup port? There's no technical reason for the change, but it would be more consistent with our other ports. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Asus K7V boot failure
On Fri, Apr 28, 2000 at 04:13:32PM -0400, Chris Shenton wrote: On Fri, 28 Apr 2000 23:15:55 +0200, Jeroen Hogeveen [EMAIL PROTECTED] said: Jeroen Hey Chris and Jordan, I've got one too, you should however Jeroen disable your boot virus protection in the bios setup! Jeroen This will fix the problem you described. Jeroen Maybe something to mention in the FAQ, if it is not yet there. Yup, fixed here, and something definetely for an FAQ. Many thanks! I'll be committing this information shortly. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Maybe need to be corrected?
Stanislav, I'm replying to this and including the -hackers list, in the hope that someone can confirm this. Thanks for getting in touch. N On Thu, Apr 27, 2000 at 04:40:19PM +0200, Koschinsky Stanislav wrote: I've read the part of FreeBSD book 21.3 "DMA: What it is and how it works". I like it very much. But I suppose that there is a mistakes (or misprints maybe) in descriptions of "DMA Address and Count Registers" and "DMA command registers". The numbers of registers does not correspond ones that are in the description of IBM compaitible XT computer. (DMA Registers: 0x2, 0x4, 0x6 etc.) I think there should be something like this: 0x0 write/read Channel 0 starting/current address 0x2 write/read Channel 1 starting/current address 0x4 write/read Channel 2 starting/current address 0x6 write/read Channel 3 starting/current address 0x1 write/read Channel 0 starting/remaining byte count 0x3 write/read Channel 1 starting/remaining byte count 0x5 write/read Channel 2 starting/remaining byte count 0x7 write/read Channel 3 starting/remaining byte count 0x8 write/read command register 0x9 write request register ... Please, verify the numbers. -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: No route for 127/8 to lo0 (?)
On Mon, Apr 24, 2000 at 07:28:32PM -0400, Joseph Jacobson wrote:
See RFC1122, section 3.2.1.3, available at
http://www.cis.ohio-state.edu/htbin/rfc/rfc1122.html
http://www.faqs.org/rfcs/rfc1122.html
Right. Assuming we're looking at the same section, it says:
[...]
(g) { 127, any }
Internal host loopback address. Addresses of this form
MUST NOT appear outside a host.
[...]
which is the only discussion of 127/8 I see in that document.
The behaviour I'm seeing is that packets to 127.255.255.255 (i.e.,
broadcasts on the 127/8 net) are being sent out the default route,
because on FreeBSD (at least, FreeBSD 3-stable), there's only a host
route for 127.0.0.1, not a network route. Per the RFC, that's
incorrect behaviour, right?
The RFC also says:
For most purposes, a datagram addressed to a broadcast or
multicast destination is processed as if it had been
addressed to one of the host's IP addresses;
Is there some special-case for 127/8 that's covered by the "For most
purposes" line?
Cheers,
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: No route for 127/8 to lo0 (?)
On Fri, Mar 31, 2000 at 12:57:40PM +0100, Nik Clayton wrote:
In the course of debugging why Samba was bringing my modem link up
periodically, I discovered it was sending netbios packets to
127.255.255.255. Because the relevent entries from the routing table
looked like
DestinationGatewayFlags Refs Use Netif Expire
default158.152.1.222 UGSc 220 tun0
127.0.0.1 127.0.0.1 UH 0 201 lo0
[...]
127.255.255.255 was going out of the default route, tun0, and bringing
the line up.
[...]
I thought that 127/8 was the "local net", and that packets sent to any of
those addresses would go via the loopback interface. That seems to be
how Linux and Windows 98 do things (the only systems I can check this on
at the moment). Assuming that's the case, why does FreeBSD only add a
a host route to 127.0.0.1, and not a network route for 127/8? Various
other people have confirmed that they only have a 127.0.0.1 host route
as well, so I don't believe this is a misconfiguration of my system.
No one's actually been able to answer this, save a few comments that the
loopback interface is special-cased to do this in the code, and that the
code in question is quite old.
In light of that, I'd like to commit:
Index: rc.network
===
RCS file: /home/ncvs/src/etc/rc.network,v
retrieving revision 1.74
diff -u -r1.74 rc.network
--- rc.network 2000/02/29 12:53:28 1.74
+++ rc.network 2000/04/21 18:48:15
@@ -254,6 +254,9 @@
done
fi
+ # 127/8 goes through lo0.
+ route add -net 127 -interface lo0
+
echo -n 'Additional routing options:'
case ${tcp_extensions} in
[Yy][Ee][Ss] | '')
as a stop gap.
FWIW, the code in question is sys/netinet/in.c:in_ifinit(), around line
701. Comments?
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Hardware crypto support
[ slashdot.org hat firmly on head, FU set to me ] Does FreeBSD support hardware crypto? There'll shortly be a story on /. about OpenBSD's hardware crypto support, in the form of the HiFn 7751 chip. OpenBSD recommend buying them from www.powercrypt.com. If you go there you'll see that FreeBSD support is listed, but there are no details. If FreeBSD's got support for this card (even if it's through third party drivers) I'll recast the story so it's more of a "BSD supports hardware crypto", rather than being solely OpenBSD. But if OpenBSD have it first they get the honours :-) If you're using this (or any other) card for hardware crypto, can you drop me a line? If you can include real-world performance details as well that'd be great. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: somewhat random mostly-lockups in 5.0
On Mon, Apr 10, 2000 at 07:48:45AM -0400, Brian Fundakowski Feldman wrote: On Sun, 9 Apr 2000, Alfred Perlstein wrote: In otherwords, unplug your palm pilot and attach a console. I'm going to get my friend to get a traceback and whatever else is possible. He has a laptop and "null" serial cable to use, and he experiences these problems as much as I do; I'll just convince him to keep running the latest -CURRENT and get the serial console working. "ptelnet" for the Palm will do a serial connection over the Hotsync cradle. I have it on reasonable authority from a friend that they've booted FreeBSD this way, interacting with the boot loader via the Palm as they go. Not that I'm recommending this for day to day use, or anything, but if all you have is a Palm. . . N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Structuring the Developer Handbook
[ -doc, -hackers, FU set to -doc ] Recent discussion on -doc has bought forth the suggestion that the Handbook could usefully be split in to a number of smaller books. Rough consensus is that chunks of the existing Handbook should form parts of a new "FreeBSD Developer Handbook", to cover information useful to FreeBSD developers (and developers using FreeBSD). Specifically, the sort of people who inhabit -hackers. http://people.freebsd.org/~nik/developer-handbook/index.html (or /book.html if you want one big file) shows a very early cut at how the Developer Handbook might be structured. It includes some content culled from the current Handbook. What I'd like is feedback on this structure (which is flexible and open to change) from the developers, along with suggestions for extra material that should be included. I'm sufficiently removed from the development code face to be totally unsure about the best way to organise topics from a developer's point of view. Any and all suggestions welcome. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Task for -doc newbie / XML'ing LINT. . .
Hi,
[ sent to -doc, where it's on topic.
Sent to -stable, where there's been much discussion of the docs
recently. If anyone's got any energy left from that they could usefully
expend it on this.
Sent to -hackers, where the last chunk about XML is on topic, and will
probably get me lynched. . .
Follow-ups *not* set, as depending on which bits you reply to might
make it more appropriate for one list or another. ]
If anyone's looking for a relatively simple, but quite involving task. . .
Update section 2.3 of the Handbook, "Supported Hardware". In particular,
for each piece of hardware I'd like to know
* The name of the hardware (which we already have, pretty much)
* The category ("Disk Controller", "NIC", "USB", "ISDN", "Serial",
"Mice", "Scanners", Other. . .)
* The name of the driver/kernel config entry it's associated with
* A URL for a page on the manufacturer's website that describes the
product (if it exists).
* Other URLs of interest (for example, if someone else has a page up
that explains how to use this device with FreeBSD).
* Assorted notes about the product
What would be particularly useful is if we can get this information in
a queryable form (XML, rah rah rah). We could then
* Convert it to DocBook for inclusion in the Handbook
* Build something much like the BSDI's website "Supported Hardware"
section, where you can search for your hardware, and it gives you
back lots of info about the device.
[ OK, I'm pushing the boat out big time on this one, and it'll probably
get shot down, but what the hell ]
* Use this as *documentation in the source tree* to build chunks of
the LINT config file.
Imagine, for example, src/sys/pci/DRIVERS.xml, which looked something
like (and I'm doodling on the back of an envelope at the moment)
controller
typepci/type
device
typeNIC/type
namefxp/name
descrEtherExpress Pro/10, Pro/100B, Pro/100+ Fast Ethernet
adapters, based on the Intel i82557 or i82559
chipsets./descr
/device
device
[ ... ]
/device
option
namePCI_QUIET/name
descrquiets PCI code on chipset settings/descr
/option
/controller
LINT would then become some boiler plate text for things we don't
want to describe this way, plus the output of a process which takes
the above and turns it into a config(8) style file.
When you add a new driver, update the .xml file(s) as necessary. Next
time LINT is built it contains the appropriate text, next time the
Handbook is built it lists the device as supported. . .
Thoughts?
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Unicode on FreeBSD
On Mon, Apr 03, 2000 at 11:37:22AM -0700, Eugene M. Kim wrote: On 2 Apr 2000, Christian Weisgerber wrote: | I also think the creating of a freebsd-i18n list is long overdue. | I18N issues are largely lost among the traffic on -hackers and | -questions, and it has become something of a specialty area since | most people appear to be served well by the existing non-solutions. I second this idea. I do, sort of. I think (BICBW) there's a big overlap between carrying out i18n work on the code and message catalogs, and carrying out i18n work on the documentation. There is already a freebsd-translators (@ngo.org.uk) mailing list with very little traffic that could be migrated to freebsd.org and used for both. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Mirror requirements
Lloyd, On Fri, Mar 31, 2000 at 10:06:02AM +0100, Lloyd Rennie wrote: I was about to say. On ftp3.FreeBSD.org we use 3 9 Gb SCSI disks in a vinum stripe to hold just XFree86 and a partial mirror of FreeBSD and it runs at about 86% capacity. Right. Thanks to all who replied - will budget lots and lots of gigs ;-) When you get this done, could you drop the -doc list a note saying what resources you used, and how much space it takes up. I think this sort of information should be in the FAQ or Handbook. Thanks, N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
No route for 127/8 to lo0 (?)
[ Sigh. I had hoped to keep this to the uk mailing list, limiting the
exposure of my ignorance. Sadly I now have to expose it to the whole
world. This is on a 3.x-stable system. ]
In the course of debugging why Samba was bringing my modem link up
periodically, I discovered it was sending netbios packets to
127.255.255.255. Because the relevent entries from the routing table
looked like
DestinationGatewayFlags Refs Use Netif Expire
default158.152.1.222 UGSc 220 tun0
127.0.0.1 127.0.0.1 UH 0 201 lo0
[...]
127.255.255.255 was going out of the default route, tun0, and bringing
the line up.
Obviously, there are several ways to fix this. You could add a network
route ("route add -net 127 -interface lo0"), you could configure PPP's
dial filter to ignore them, or you could filter them with a firewall.
I thought that 127/8 was the "local net", and that packets sent to any of
those addresses would go via the loopback interface. That seems to be
how Linux and Windows 98 do things (the only systems I can check this on
at the moment). Assuming that's the case, why does FreeBSD only add a
a host route to 127.0.0.1, and not a network route for 127/8? Various
other people have confirmed that they only have a 127.0.0.1 host route
as well, so I don't believe this is a misconfiguration of my system.
Or am I misguided, and need to go buy a copy of Stevens?
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Sysinstall 'A'uto partitioning
On Fri, Mar 10, 2000 at 03:25:33AM +0300, Aleksandr A.Babaylov wrote: Yes, it's good. But it's better just mount partition on it's own place, no symlinks, I disagree. such as: /dev/sd1s1f 3942238 2151773 147508659%/usr /dev/sd0s1g98553538016 868677 4%/usr/ports /dev/wd2g 2030095 1437551 43013777%/usr/ports/distfiles /dev/sd0s1h985535 155771 75092217%/usr/src In this example, you've hardcoded the size of /usr/ports, /usr/ports/distfiles, and /usr/src. What happens when the contents of these filesystems outgrow these limits? You can't grow (or shrink) a ufs filesystem. So you need to add another disk, and/or create symlinks in to another filesystem. and /local is not the best plase for out of the hier(7) things. use special partition for mount points: /dev/ad4s2h 455 39 380 9%/mnt glip:/mnt/d 4053998 3356969 37271090%/mnt/d /dev/ad0 1056751 10212653548697%/mnt/w /dev/ad4s2e 16183272 1135371 13753240 8%/mnt/e You can do that. The precise name of /local is immaterial. For example, you might want /mnt/local/ /mnt/nfs /mnt/smb /mnt/ext2fs and so on, depending on your precise requirements. The documentation I posted is primarily internal notes for myself (and my hopefully soon to be employees) rather than hard and fast rules that everyone has to follow. Hopefully, though, in those notes, people will get ideas as to how best to partition for their needs. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Sysinstall 'A'uto partitioning
This looks like as good a place as any to hang this;
On Tue, Mar 07, 2000 at 09:14:34PM -0800, Matthew Dillon wrote:
I'll tell ya, I *never* use the auto-defaults. They are way too
tiny. A 50MB root barely fits the kernel and you can run it out of
space doing an installworld. I almost always do this:
/ 128M
swap(double system memory at a minimum)
/var128M
/var/tmp128M
/usr(at least 1G)
/u1 (remainder, if it's a big disk)
/tmp softlink to /var/tmp(because having two tmp's is stupid)
/home softlink to /u1/home
Here's a documentation of my current recommended practice which'll
probably turn in to an article somewhere in the doc/ tree some time.
Comments welcome.
N
Recommended disk and partition layout
In order to reduce space wastage, and provide a flexible partition layout
for future work, the following disk partition layout is recommended.
First, you need three 'standard' filesystems, of roughly this size:
/50m
/var 50m
/usr 250m
A 50m / should be sufficient for static /bin and /sbin, as well as /etc,
other configuration files, and a local /tmp.
Similarly, a 50m /var covers most log files, assuming the machine isn't
doing anything too log intensive. Don't worry about the size of incoming
and outgoing mail spools, or the print spooler at the moment.
Finally, a 250m /usr covers all the standard stuff, and leaves room for
expansion in the future.
Now, create one more filesystem,
/local/0 rest of the disk
If you have any more disks, create 1 filesystem per disk, and arrange to
mount them as /local/1, /local/2, and so on.
The known space fillers can then be moved on to /local/{0,1,2,...} as
necessary, and then symlinked back in to place. For example;
mkdir -p /local/0/usr
mkdir -p /local/0/var
mkdir -p /local/0/home
cd /usr
mv src /local/0/usr
mv obj /local/0/usr
mv ports /local/0/usr
mv X11R6 /local/0/usr
ln -s /local/0/usr/* .
cd /var
mv mail /local/0/var
mv spool /local/0/var
ln -s /local/0/var/* .
and so on. Adjust the disks you move stuff to, depending on how many disks
you have, and expected usage.
For example, if you only have one disk, then /local/0/usr/{src,ports,obj}
and /local/0/home/ncvs[1] will all have to be on one disk.
When you add a second disk, you will definitely want to move
/local/0/usr/obj to /local/1/usr/obj, and /local/0/home/ncvs to
/local/1/home/ncvs (and update their symlinks). This is because:
1. If you do a CVS checkout from /home/ncvs to /usr/src, two different
disks will be used, speeding things up considerably.
2. If you do a "make world", the source will be read from /usr/src,
on the first disk, and the compiled programs (and object files)
will be written to /usr/obj, on the second disk, and again, this
will speed things up.
Problems with this approach
By placing everything on one (or a few) large filesystems, you lose
finegrained control.
For example, if /var/mail and /var/spool are symlinks to /local/0/var/mail
and /local/0/var/spool respectively, then there is the possibility that
large incoming e-mails can use up all the disk space, preventing anything
that requires /var/spool (such as lpd(8)) from working properly -- and vice
versa, as large print jobs may halt reception of incoming e-mail.
To an extent, you can work around this problem with quotas. For example,
the mail system runs as group 'mail', so you can set a group quota for mail
to prevent it filling up the disk. Some daemons also have configuration
options to prevent them filling up the disk, such as the lpd(8) minfree
file.
--
[1] Assuming you've got a local copy of the CVS tree you checkout /usr/src
from
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Threads and my new job.
Jason, On Mon, Nov 22, 1999 at 06:52:20PM -0800, Jason Evans wrote: Walnut Creek has hired me as a full time employee to work primarily on improving and expanding FreeBSD's threads support. This is very exciting to me, and I hope my work will be of benefit the FreeBSD community. That's great. Is it part of your remit to maintain http://www.FreeBSD.org/threads/? That URL doesn't exist at the moment, but if we're going to have an active threads project, it probably should. Are you (or anyone else reading this, you don't have to be a committer at the moment) interested in keeping this section up to date? N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: netgraph into -stable.
On Thu, Nov 18, 1999 at 01:58:59PM -0800, Julian Elischer wrote: for info on what it is, see: ftp://ftp.whistle.com/pub/archie/netgraph/index.html or in an http form: http://www.elischer.org/netgraph/index.html Thanks a lot. Very interesting reading. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
docs/14112: replacement for diediedie() in docs
-hackers, Could someone take a look at docs/14112 please. The online kernel debugging section in the Handbook mentions calling diediedie() or boot() to reboot the system. According to the PR, these don't exist in 3.3-R, and I don't know what calls / actions should replace the existing text. Any help appreciated. Thanks, N -- A different "distribution" of Linux is really a different operating system. They just refuse to call it that because it's bad press. But that's what the shoe fits. -- Tom Christiansen, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSDCon pictures
On Sun, Oct 24, 1999 at 03:59:00PM -0700, John Polstra wrote: I put a few pictures from FreeBSDCon here for your enjoyment: http://www.freebsd.org/~jdp/freebsdcon1999/ Ugh! That's a horrible picture of me on there. Similarly, http://www.freebsd.org/~nik/freebsdcon-1999/pictures/ No captions yet though. Of those, http://www.freebsd.org/~nik/freebsdcon-1999/pictures/Tuesday/P118.JPG is really quite amusing. . . More pics to follow. N 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 Mon, Sep 27, 1999 at 10:22:34AM +1000, Andrew Reilly wrote: What I'd like is a little weekly crontab script that runs after my weekly ports cvsup, and tells me which of the ports that I "subscribe to" has changed, so that I can think about rebuilding it. ports/sysutils/pkg_version. Then apply the patches at http://www.freebsd.org/~nik/pkg_version.diff pkg_version.1.diff and use the -c flag. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] 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 at 01:11:32AM +0200, Christian Carstensen wrote: On Sat, 25 Sep 1999, Chris Costello wrote: 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! that's right. i thought about having some kind of exclude list for ports that shall never be upgraded automatically. anyway, the script will just generate a shell script output. it should not replace packages without manual intervention. If you're interested, I've got patches for sysutils/pkg_version that support a '-c' flag (for 'commands') that show you the commands you should run to update any out of date ports. I cron this and mail the output out once a week. You could have it automatically create and execute a shell script if you wanted. Sample output from one of my boxes is: # # ORBit # needs updating (index has 0.4.93) # cd /usr/ports/devel/ORBit make clean all pkg_delete -f ORBit-0.4.3 make install # # docbook-xml # needs updating (index has 3.1.5) # cd /usr/ports/textproc/docbook-xml make clean all pkg_delete -f docbook-xml-3.1.4 make install # # fetchmail # needs updating (index has 5.0.8) # cd /usr/ports/mail/fetchmail make clean all pkg_delete -f fetchmail-5.0.3 make install # # less # needs updating (index has 340) # cd /usr/ports/misc/less make clean all pkg_delete -f less-337 make install [...] I sent these to the maintainer/author a while back, but they were never integrated. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] 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 at 08:53:32PM +0200, Christian Carstensen wrote: On Sun, 26 Sep 1999, Nik Clayton wrote: If you're interested, I've got patches for sysutils/pkg_version that support a '-c' flag (for 'commands') that show you the commands you should run to update any out of date ports. I cron this and mail the output out once a week. in deed, i am very interested in it. having your patches, do you think, there's any need for a tool in perl? i'm recently testing my version and it seems to work as expected. could you possibly send me your patches? Various people have asked for these. http://www.freebsd.org/~nik/pkg_version.diff pkg_version.1.diff N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] 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 at 06:08:15PM -0400, Rajappa Iyer wrote:
4. The number of times that I've had a random bug in the
{pre|post}{install|remove} scripts essentially render the system
unupgradeable is not funny. I have had to go and physically remove
some files and edit the package database by hand to get the system
back to some sane state.
You have sent in PRs for the ports/packages where you've had this problem,
right?
N
--
[intentional self-reference] can be easily accommodated using a blessed,
non-self-referential dummy head-node whose own object destructor severs
the links.
-- Tom Christiansen in [EMAIL PROTECTED]
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 at 12:32:16PM -0400, John Baldwin wrote: Re-read the first para of his message: - I completely agree!! Debian's package manager is one of the most - infuriatingly buggy piece of software that I've ever used. He's complaining about Debian's stuff, not the Ports Collection. :) Ah, oops. My humble apologies to Rajappa. As penance, I'm about to work my way through the 76 messages in -doc that need my attention, roughly half of which probably have PRs attached. . . N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio_*
On Mon, Sep 13, 1999 at 10:02:40PM -0700, Jayson Nordwick wrote: While reading through (at least trying to... I wish there was some sort of kernel documentation available, the entry fee is very high) What we need is people like yourself, who are having to go through the learning curve, to document stuff as you're finding it out. It doesn't matter if your notes are a bit rough and ready, because the next person to use them can improve on them, and the next person, and the next person, and so on, until we have great kernel documentation. Any takers? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [Fwd: Re: cvs commit: doc/en/handbook/ports chapter.sgml]
On Sat, Aug 28, 1999 at 11:45:42PM +0900, Daniel C. Sobral wrote: You know how people can get sidetracked easily. :-) For that matter, if chapter.sgml still has a log of why the version changed, then I think it would be a good thing to insert the above comment in param.h. I don't recall seeing any objections, though I can imagine some people might think it's not appropriate for the source to refer to an outside documentation such as the handbook. Given that: 1. The 'committer rules' document will apply to doc/ just as much as it applies to src/. 2. The FDP mailing list is @FreeBSD.org 3. After a big discussion recently, the FDP documentation will continue to be installed under /usr/share/doc/ (rather than /usr/local/share/doc, which is where third-party documentation is installed) I think it's safe to say that the source code should be able to refer to any documentation in the doc/ tree. If you don't beat me to it, I'll commit that comment. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: Re: cvs commit: doc/en/handbook/ports chapter.sgml]
On Sat, Aug 28, 1999 at 11:45:42PM +0900, Daniel C. Sobral wrote: You know how people can get sidetracked easily. :-) For that matter, if chapter.sgml still has a log of why the version changed, then I think it would be a good thing to insert the above comment in param.h. I don't recall seeing any objections, though I can imagine some people might think it's not appropriate for the source to refer to an outside documentation such as the handbook. Given that: 1. The 'committer rules' document will apply to doc/ just as much as it applies to src/. 2. The FDP mailing list is @FreeBSD.org 3. After a big discussion recently, the FDP documentation will continue to be installed under /usr/share/doc/ (rather than /usr/local/share/doc, which is where third-party documentation is installed) I think it's safe to say that the source code should be able to refer to any documentation in the doc/ tree. If you don't beat me to it, I'll commit that comment. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Please review: rc file changes
On Fri, Aug 27, 1999 at 11:23:06AM -0700, Doug wrote: On Fri, 27 Aug 1999, Nate Williams wrote: Sentences are supposed to have two spaces before you start the next sentence. Well, that was definitely the old typographical convention, but in the digital age it's fallen into disfavor. It was easier to delete the second space to make them all consistent, but I can go with double spaces if that's the consensus. I did this change over on the FDP in the Handbook, thinking it didn't make any difference either. Then I got deluged with e-mail from people telling me that lots of editors use the double space as part of their heuristic to determine where sentences start and end. And I turned it back :-) N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Please review: rc file changes
On Fri, Aug 27, 1999 at 11:23:06AM -0700, Doug wrote: On Fri, 27 Aug 1999, Nate Williams wrote: Sentences are supposed to have two spaces before you start the next sentence. Well, that was definitely the old typographical convention, but in the digital age it's fallen into disfavor. It was easier to delete the second space to make them all consistent, but I can go with double spaces if that's the consensus. I did this change over on the FDP in the Handbook, thinking it didn't make any difference either. Then I got deluged with e-mail from people telling me that lots of editors use the double space as part of their heuristic to determine where sentences start and end. And I turned it back :-) N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [Fwd: Re: cvs commit: doc/en/handbook/ports chapter.sgml]
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote: While going through old cvs commit log, I spotted this: snip + +/* Please update doc/en/handbook/ports/chapter.sgml when changing */ #undef __FreeBSD_version #define __FreeBSD_version 48 /* Master, propagated to newvers */ snip Well spotted. I'll fix this shortly. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: Re: cvs commit: doc/en/handbook/ports chapter.sgml]
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote: While going through old cvs commit log, I spotted this: snip +/* Please update doc/en/handbook/ports/chapter.sgml when changing */ #undef __FreeBSD_version #define __FreeBSD_version 48 /* Master, propagated to newvers */ With the recent changes to the doc tree, should this file be updated too? (Or maybe it was and I haven't seen that log yet :) Hang on a second, I spoke too soon. I've just had a look at that file, and I can see no trace of that comment in there. I can't see "handbook" in /home/ncvs/src/sys/sys/param.h,v either. Or was the point that this coment *should* be added to that file, but hasn't been yet? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: Re: cvs commit: doc/en/handbook/ports chapter.sgml]
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote: While going through old cvs commit log, I spotted this: snip + +/* Please update doc/en/handbook/ports/chapter.sgml when changing */ #undef __FreeBSD_version #define __FreeBSD_version 48 /* Master, propagated to newvers */ snip Well spotted. I'll fix this shortly. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [Fwd: Re: cvs commit: doc/en/handbook/ports chapter.sgml]
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote: While going through old cvs commit log, I spotted this: snip +/* Please update doc/en/handbook/ports/chapter.sgml when changing */ #undef __FreeBSD_version #define __FreeBSD_version 48 /* Master, propagated to newvers */ With the recent changes to the doc tree, should this file be updated too? (Or maybe it was and I haven't seen that log yet :) Hang on a second, I spoke too soon. I've just had a look at that file, and I can see no trace of that comment in there. I can't see handbook in /home/ncvs/src/sys/sys/param.h,v either. Or was the point that this coment *should* be added to that file, but hasn't been yet? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Package creation without installation
-hackers, I'm playing around with the pkg_create(1) command at the moment, trying to get the creation of pre-built versions (HTML, PS, etc) of the FDP documentation working. One of the things I'm trying to do is *not* require that the doc that's being packaged up be installed first. For example, if I'm building the PS version of the FAQ then I can # pwd /tmp/niks-package-build-area # cd doc/en_US.ISO_8859-1/books/faq # make FORMATS=ps What I'd like to do is then create a package from this file, such that when it is installed it does not default to installing in to /tmp/niks-package-build-area/docs/en_US.ISO_8859-1/books/faq but instead defaults to installing somewhere under /usr/doc/.
Re: BSD voice synthesis
On Tue, Aug 03, 1999 at 12:37:39AM -0700, Julian Elischer wrote: Just fetched and compiled the festival package. http://www.cstr.ed.ac.uk/projects/festival Likewise, based on your comments. Has anyone had any problems with the volume being far too low? The sound card on this box is a pcm2 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 fl ags 0x13 on isa and I run mixer pcm 80 in /etc/rc.local, to set the volume to a comfortable level for playing .mp3 files and the like. If I turn the speakers right up then I can hear the output, but then everything else is distorted. Any thoughts? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: no getkerninfo() man page (docs/12220)
On Wed, Aug 04, 1999 at 03:59:00PM -0500, Jonathan Lemon wrote: getkerninfo() is depreciated, we use sysctl() instead. In fact, most of the information provided by getkerninfo() is implemented in terms of sysctl(). snip The route(4) manpage says: User processes can obtain information about the routing entry to a spe- cific destination by using a RTM_GET message, or by reading the /dev/kmem device, or by issuing a getkerninfo(2) system call. IMHO, the above sentence should probably be altered by replacing the first comma with a period, and throwing away the rest of it. Sounds fair enough. I'll allow 24 hours for objections, and then commit based on that, OK? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: TCP stack hackers take a bow
On Tue, Aug 03, 1999 at 07:52:26PM -0400, Bill Fumerola wrote: On Tue, 3 Aug 1999, Ted Faber wrote: http://www.sciencedaily.com/releases/1999/08/990802072727.htm The Duke release credits one Andrew Gallatin for a couple quotes. Not only FreeBSD in the news, but one of our own committers. Cool. I've submitted this to /., we'll see what happens. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no getkerninfo() man page (docs/12220)
On Wed, Aug 04, 1999 at 03:59:00PM -0500, Jonathan Lemon wrote: getkerninfo() is depreciated, we use sysctl() instead. In fact, most of the information provided by getkerninfo() is implemented in terms of sysctl(). snip The route(4) manpage says: User processes can obtain information about the routing entry to a spe- cific destination by using a RTM_GET message, or by reading the /dev/kmem device, or by issuing a getkerninfo(2) system call. IMHO, the above sentence should probably be altered by replacing the first comma with a period, and throwing away the rest of it. Sounds fair enough. I'll allow 24 hours for objections, and then commit based on that, OK? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
no getkerninfo() man page (docs/12220)
-hackers, As docs/12220 points out; We want to extract routing information by specifying a particular destination IP address. The man page on Route and Rtentry mention that this information can be acquired using getkerninfo command. But there is no such man page. Is it possible to get the information as how to use this command. Or if there is any other method of acquiring this information. Can anyone oblige with a getkerninfo() man page? Cheers, N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: TCP stack hackers take a bow
On Tue, Aug 03, 1999 at 07:52:26PM -0400, Bill Fumerola wrote: On Tue, 3 Aug 1999, Ted Faber wrote: http://www.sciencedaily.com/releases/1999/08/990802072727.htm The Duke release credits one Andrew Gallatin for a couple quotes. Not only FreeBSD in the news, but one of our own committers. Cool. I've submitted this to /., we'll see what happens. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: DOC volunteer WAS:RE: userfs help needed.
On Sun, Aug 01, 1999 at 03:00:49PM -0400, Brian F. Feldman wrote: Judging by your description, why don't we use LyX? :) LaTeX sounds about right. Argh -- contextual sense of humour failure. Smiley not withstanding, I can't decide if the above question was asked in all seriousness or not. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: DOC volunteer WAS:RE: userfs help needed.
On Sun, Aug 01, 1999 at 03:00:49PM -0400, Brian F. Feldman wrote: Judging by your description, why don't we use LyX? :) LaTeX sounds about right. Argh -- contextual sense of humour failure. Smiley not withstanding, I can't decide if the above question was asked in all seriousness or not. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Documenting writev(2) ENOBUFS error
On Sat, Jul 31, 1999 at 06:50:09PM -0600, Wes Peters wrote: So, do you want to enumerate the cases in which this error can occur in the man page? This is not generally done, now that we have verified it is possible for the system to generate ENOBUFS on a writev. I think the text stands as it is. FWIW, I committed: [ENOBUFS]The mbuf pool has been completely exhausted when writing to a socket ... N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Documenting writev(2) ENOBUFS error
On Sat, Jul 31, 1999 at 06:50:09PM -0600, Wes Peters wrote: So, do you want to enumerate the cases in which this error can occur in the man page? This is not generally done, now that we have verified it is possible for the system to generate ENOBUFS on a writev. I think the text stands as it is. FWIW, I committed: [ENOBUFS]The mbuf pool has been completely exhausted when writing to a socket ... N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: DOC volunteer WAS:RE: userfs help needed.
[ cc'd to -doc, reply-to points there ] On Fri, Jul 30, 1999 at 04:09:20PM -0500, Alton, Matthew wrote: I prefer to work in flat ASCII. Perhaps the doc project can HTMLize the final product. We can, it just takes longer, that's all. It would make life simpler if you can follow the general structure, which basically consists of an overall document, containing zero or more parts, each part containing one or more chapters, each chapter containing zero or more sections, each section divided in to zero or more subsections (and so on, down to sub-sub-sub-sub-sub-sections). Each part, chapter, and section has a mandatory title. The Handbook is a good example of a document that uses parts, further divided in to chapters, and the Doc. Proj. primer is a good example of a document that dispenses with parts, and just uses chapters and sections. Generally, something like Title Abstract . . . Chapter 1: Overview . . . and then further chapters as necessary. Within the text, set off things that are 'out of band' information, like notes, tips, and important information. If you include instructions for the user to follow, please use "#" for the root prompt, and "%" for the regular user prompt. Refer to commands as 'command(n)', and assume that in the web (and PDF) version that will be generated that this will automatically turn in to a link to the manual page. The Doc. Proj. primer has a (sparse) writing style chapter that covers things like contractions, serial commas, and so on. Of course, you don't have to do any of this, it just makes it harder for whoever turns it in to DocBook (which will probably be me) to do the conversion. Once again, thanks for volunteering to do this. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: DOC volunteer WAS:RE: userfs help needed.
[ cc'd to -doc, reply-to points there ] On Fri, Jul 30, 1999 at 04:09:20PM -0500, Alton, Matthew wrote: I prefer to work in flat ASCII. Perhaps the doc project can HTMLize the final product. We can, it just takes longer, that's all. It would make life simpler if you can follow the general structure, which basically consists of an overall document, containing zero or more parts, each part containing one or more chapters, each chapter containing zero or more sections, each section divided in to zero or more subsections (and so on, down to sub-sub-sub-sub-sub-sections). Each part, chapter, and section has a mandatory title. The Handbook is a good example of a document that uses parts, further divided in to chapters, and the Doc. Proj. primer is a good example of a document that dispenses with parts, and just uses chapters and sections. Generally, something like Title Abstract . . . Chapter 1: Overview . . . and then further chapters as necessary. Within the text, set off things that are 'out of band' information, like notes, tips, and important information. If you include instructions for the user to follow, please use # for the root prompt, and % for the regular user prompt. Refer to commands as 'command(n)', and assume that in the web (and PDF) version that will be generated that this will automatically turn in to a link to the manual page. The Doc. Proj. primer has a (sparse) writing style chapter that covers things like contractions, serial commas, and so on. Of course, you don't have to do any of this, it just makes it harder for whoever turns it in to DocBook (which will probably be me) to do the conversion. Once again, thanks for volunteering to do this. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Is the _Device Driver Writers Guide_ still apropos?
On Fri, Jul 30, 1999 at 11:48:47PM +0200, Jeroen Ruigrok/Asmodai wrote: * Nik Clayton (n...@nothing-going-on.demon.co.uk) [990730 23:37]: Is the FreeBSD Device Driver Writers Guide at http://www.freebsd.org/tutorials/ddwg/ddwg.html still correct? I know there have been changes to this area of the tree over the past 6 months or so, but I don't know how much of that document is still appropriate for what we have now. As far as I have been able to learn and glance from Bill Paul and some other device driver guru's too much has changed in order for it to be correct under CURRENT. A rewrite is on my to-do list for the PDP, however, should people feel like they want to rewrite it, be my guest and cc: me on any submissions so I can include it in the PDP. Else I will start this ASAHP. How does the attached patch grab you? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu Index: ddwg.sgml === RCS file: /home/ncvs/doc/en/tutorials/ddwg/ddwg.sgml,v retrieving revision 1.6 diff -u -r1.6 ddwg.sgml --- ddwg.sgml 1998/06/18 13:20:41 1.6 +++ ddwg.sgml 1999/07/31 18:25:12 @@ -28,6 +28,13 @@ toc +sect2.x specific + +pDue to changes in FreeBSD over time, this guide is only accurate as +regards FreeBSD 2.x. A replacement guide for FreeBSD 3.x and beyond +is being written. Please contact Jeroen Ruigrok tt/lt;asmo...@wxs.nlgt;/ +if you would like to help with this. + sect Overview p it
No elf(5) man page (docs/7914)
Hi folks, We have an a.out(5), but no elf(5) (as pointed out in docs/7914). Does anyone feel up to writing one? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Is the _Device Driver Writers Guide_ still apropos?
-hackers, Is the FreeBSD Device Driver Writers Guide at http://www.freebsd.org/tutorials/ddwg/ddwg.html still correct? I know there have been changes to this area of the tree over the past 6 months or so, but I don't know how much of that document is still appropriate for what we have now. Thanks, N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: DOC volunteer WAS:RE: userfs help needed.
On Thu, Jul 29, 1999 at 10:45:51AM -0500, Alton, Matthew wrote: I ran screaming into the woods last year from trying to grok VOP_foo. The prospect of a rewrite fills me with warmth and fuzziness. I hereby volunteer to maintain the VOP(9) man pages and to flesh out my notes into a big, beefy FS-implementer's Guide to the new VOP_foo. All the coders have to do is answer my (at least marginally clueful) questions along the way and keep posted as to what's going on in new VM-land. I won't even pester anyone with design suggestions... very much. Solid offer, kids. Everybody wins. Give it some thought. Sounds good. Yell for any assistance you need from the Doc. Proj. In particular, the FS Implementer's Guide sounds good. What (markup) language were you planning on using? N PS: Reply-to: should probably be set to doc, but I've left that at your discretion. -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
No elf(5) man page (docs/7914)
Hi folks, We have an a.out(5), but no elf(5) (as pointed out in docs/7914). Does anyone feel up to writing one? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Is the _Device Driver Writers Guide_ still apropos?
-hackers, Is the FreeBSD Device Driver Writers Guide at http://www.freebsd.org/tutorials/ddwg/ddwg.html still correct? I know there have been changes to this area of the tree over the past 6 months or so, but I don't know how much of that document is still appropriate for what we have now. Thanks, N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: DOC volunteer WAS:RE: userfs help needed.
On Thu, Jul 29, 1999 at 10:45:51AM -0500, Alton, Matthew wrote: I ran screaming into the woods last year from trying to grok VOP_foo. The prospect of a rewrite fills me with warmth and fuzziness. I hereby volunteer to maintain the VOP(9) man pages and to flesh out my notes into a big, beefy FS-implementer's Guide to the new VOP_foo. All the coders have to do is answer my (at least marginally clueful) questions along the way and keep posted as to what's going on in new VM-land. I won't even pester anyone with design suggestions... very much. Solid offer, kids. Everybody wins. Give it some thought. Sounds good. Yell for any assistance you need from the Doc. Proj. In particular, the FS Implementer's Guide sounds good. What (markup) language were you planning on using? N PS: Reply-to: should probably be set to doc, but I've left that at your discretion. -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in 37514...@cs.colorado.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Documenting writev(2) ENOBUFS error
-hackers, Could someone who knows write/writev(2) take a quick look at docs/10512. In essence, writev(2) can fail with ENOBUFS if (and I quote from the PR) if you "exhaust writev'able buffer space". This doesn't mean a great deal to me, and I'm hoping one of you can take a look at come up with a phrasing suitable for a man page. Cheers, N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
