BSD voice synthesis
Just fetched and compiled the "festival" package. http://www.cstr.ed.ac.uk/projects/festival it has support for FreeBSD already (seems to work fine) Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word "FreeBSD" when I asked it to say (from the manual) [you need..] A Unix machine, Festival has compiled and run on Suns (SunOS and Solaris), FreeBSD, Linux, SGIs, HPs and DEC Alphas but should be portable to any standard Unix machine. julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Support for ez USB chips, anchorchips
A down-/uploader for the EZ USB chip is available from http://www.etla.net/~ezload.tar.gz See also the AnchorChips home page http://www.anchorchips.com/ The utility is courtesy of Dirk van Gulik, WebWeaving Consultancy and ActiveWire, Inc. (prototype board, http://www.activewireinc.com/) Cheers, Nick Hibma FreeBSD USB Project mailing list: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
IDE quirk in 3.2-STABLE kernel ?
Hi, On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk When I boot up under a 3.2-STABLE kernel (recently updated), wdc1 is "not found" However when I boot up under a 3.1-RELEASE "generic" kernel it sees the drive (wd2) and controller (wdc1) ok. (And yes I do have an entry for wdc1,wd2,wd3 in the config file for the 3.2-STABLE kernel) However, when I plugged in a CDROM drive in place of wd2, both kernels saw it ok. Maybe the wd2 disk has a quirk in it, but how come it works in one version and not in the next ? Any ideas ? - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Multiple versions of FreeBSD on one HDD
Hi all I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but am not having much luck. I have tried several approaches, in particular creating four partitions, the first two for the respective root slices, the third for swap, and the fourth for the remaining slices. If I create the first two partitions as small as 50Mb, sysinstall still complains that it can't make a root slice in the second partition as the boot loader can't deal with that location. If I create the /usr and /var slices for the second OS and then say `Use defaults for all' it creates a 32MB root slice in the second partition, so that seems to get around the problem, but I can't boot this after the install is done. If I install DOS in the first 50Mb partition, then there is no problem. So it seems the presence of a FreeBSD partition preceding the one in which I want to make the root slice prevents things from working. Is there a way around this (other than using a second drive?) TIA gram -- Dr Graham WheelerE-mail: [EMAIL PROTECTED] Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 3:39 PM To: [EMAIL PROTECTED] Subject: IDE quirk in 3.2-STABLE kernel ? Hi, On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk When I boot up under a 3.2-STABLE kernel (recently updated), wdc1 is "not found" However when I boot up under a 3.1-RELEASE "generic" kernel it sees the drive (wd2) and controller (wdc1) ok. (And yes I do have an entry for wdc1,wd2,wd3 in the config file for the 3.2-STABLE kernel) However, when I plugged in a CDROM drive in place of wd2, both kernels saw it ok. Maybe the wd2 disk has a quirk in it, but how come it works in one version and not in the next ? Any ideas ? - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IDE quirk in 3.2-STABLE kernel ?
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju Normally for my own kernel, I set the IDE delay very low (IDEDELAY=1000 in conf file) to speed up booting..I'll try increasing this for my 3.2-STABLE kernel, reboot and see if it detects wdc1 + wd2...Otherwise there must be something changed between 3.1-RELEASE generic and 3.2-STABLE ?? Cheers, - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 4:28 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: IDE quirk in 3.2-STABLE kernel ? Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju Normally for my own kernel, I set the IDE delay very low (IDEDELAY=1000 in conf file) to speed up booting..I'll try increasing this for my 3.2-STABLE kernel, reboot and see if it detects wdc1 + wd2...Otherwise there must be something changed between 3.1-RELEASE generic and 3.2-STABLE ?? Cheers, - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multiple versions of FreeBSD on one HDD
I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but am not having much luck. I have tried several approaches, in particular creating four partitions, the first two for the respective root slices, the third for swap, and the fourth for the remaining slices. If I create the first two partitions as small as 50Mb, sysinstall still complains that it can't make a root slice in the second partition as the boot loader can't deal with that location. If I create the /usr and /var slices for the second OS and then say `Use defaults for all' it creates a 32MB root slice in the second partition, so that seems to get around the problem, but I can't boot this after the install is done. Not too sure what exactly you're trying to do here -but how about creating a separate *slice* for the two versions, then go install one version into one slice, carve that slice up into partitions (one for root /usr swap etc.) reboot, then go install the other version into the other slice, carve it up into partitions etc. This way you should have something similar to: da0s1 = FreeBSD 2.2.8, da0s2 = FreeBSD 3.2 AFAIK, wd0a will refer to wd0s1a etc. Hope this helps, but why do you want 2.2.8 ? 3.2 is much better :) - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju I just set IDE_DELAY=4000 in my 3.2-STABLE kernel, and now it sees all disks on both controllers. I think the problem was that one of my IDE disks is a "Joe IDE device" (TM). Depending on which controller it was put would cause that controller to be "not found". Ok, my problem is solved - don't know about that ATAPI drive of yours though...Is it only detected at boot time when there's a CD in it ? is it detected ok in other OS's without the need for putting the CD in ? - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: more NFS questions, why is the VFS_FHTOVP weird?
Alfred Perlstein [EMAIL PROTECTED] writes:
the problem with nfsrv_fhtovp is that it is overkill for my application
(it checks perms where i don't need it to, so i would have to fake
a lot of stuff to look like i was authorized)
What's your application?
so instead I gutted nfsrv_fhtovp a bit and came up with this sequence:
fhp = nfh.fh_generic;
error = copyin(u_fhp, fhp, fhlen);
if (error)
return(error);
/* find the mount point */
mp = vfs_getvfs(fhp-fh_fsid);
if (!mp)
return (ESTALE);
/* now give me my vnode, it gets returned to me locked */
error = VFS_FHTOVP(mp, fhp-fh_fid, nam, vp, exflags, credanon);
if (error)
return (error);
the copying is from userspace, it's a NFS handle...
now here's where I get very confused...
in src/nfs/nfs_vfsops.c around line 1100:
/*
* At this point, this should never happen
*/
/* ARGSUSED */
static int
nfs_fhtovp(mp, fhp, nam, vpp, exflagsp, credanonp)
register struct mount *mp;
struct fid *fhp;
struct sockaddr *nam;
struct vnode **vpp;
int *exflagsp;
struct ucred **credanonp;
{
return (EINVAL);
}
ok, now if you look at the first piece of code it obviously
fails if nfsrv_fhtovp fails, and nfsrv_fhtovp fails if VFS_FHTOVP
fails...
so how does NFS work? where is this magic function?
The NFS server is calling the FHTOVP function of the exported file
system. You're looking at the FHTOVP function for the NFS file system
itself. Look for example at ffs_fhtovp and ufs_check_export.
the macro VFS_FHTOVP is defined in mount.h:
#define VFS_FHTOVP(MP, FIDP, NAM, VPP, EXFLG, CRED) \
(*(MP)-mnt_op-vfs_fhtovp)(MP, FIDP, NAM, VPP, EXFLG, CRED)
I do think that checking for what file systems are exported has no
place in FHTOVP and this should probably be rewritten similar to the
way it has recently been done in NetBSD, namely with a new vfs
operation:
int (*vfs_checkexp) __P((struct mount *mp, struct mbuf *nam,
int *extflagsp, struct ucred **credanonp));
And they have also added fhopen and other syscalls that take file
handles instead of file names.
btw, since this seems to work... is it ok to pass in a NULL
sockaddr *? (nam)
I think that nam == NULL means the default export list which doesn't
sound as what you want do do?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD voice synthesis
On Tue, 3 Aug 1999, Julian Elischer wrote: Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word "FreeBSD" when I asked it to say (from the manual) I'm using a pIII-450 and it pronounces it "freebs". However if you spell it "Free B S D" it does just fine. Seems to do well with most words I've thrown at it - including some last names (it does mine almost perfect, but blows some real easy ones). [you need..] A Unix machine, Festival has compiled and run on Suns (SunOS and Solaris), FreeBSD, Linux, SGIs, HPs and DEC Alphas but should be portable to any standard Unix machine. Did gmake test work for you in festival? It did for me in speech-tools but not festival even tho it seems to work well. Sure is gonna make some of these boring README files easier! ...wonder how hard it'd be to tie it into the select buffer in X... Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
Peter Wemm wrote: Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, one device (codadev) and one vfs (coda). It seems to me that the one who gets the arguments is the one who searches for it. :-) Either that, or the first file in the module. I don't recall right now the precise structure of this in memory. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] - Jordan, God, what's the difference? - God doesn't belong to the -core. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Interesting Kernel Config
Greets ... I just noticed that on my 2.2.6 System, I had to enable the options ATAPI options ATAPI_STATIC device wcd0 before the following had any effect: controller wdc1 at disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 in my kernel config file. So, the second controller was only seen after I enabled ATAPI? eT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
"Daniel C. Sobral" wrote: assuming we are making it at all, the less pain. It provides a way of getting parameters that is compatible with what is already possible with loader (ie, the module need not differentiate between it's method of loading). The code is working and ready. Actually... Loader passes a string. It seems the kldcode is passing argv[]. Juha, you sure you have they both working the same way (from a module's perspective)? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] - Jordan, God, what's the difference? - God doesn't belong to the -core. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multiple versions of FreeBSD on one HDD
This works, but has the restriction that I have to enter a command line at the boot prompt to boot one of the two. I would much prefer partitions, as I can use a boot selector instead, and also change the default as appropriate. If you do have the installations in two seperate slices on the one disk, you should be able to use a boot selector to boot which ever slice you want. I don't know if this will work with booteasy the boot manager that comes with FreeBSD by default, but there is a nice boot manager called OS Select (tools/os-bs.exe in the FreeBSD distribution I think).. (the setup program is an MSDOS exe) It allows you to create a menu of OS's to boot from by selecting the relevant slices from the list it shows. It also allows you to set a default slice to boot aswell as a timeout counter. Whether it will work or not in your situation remains to be seen.. :) Regards, - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multiple versions of FreeBSD on one HDD
Cillian Sharkey wrote: I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but am not having much luck. I have tried several approaches, in particular creating four partitions, the first two for the respective root slices, the third for swap, and the fourth for the remaining slices. If I create the first two partitions as small as 50Mb, sysinstall still complains that it can't make a root slice in the second partition as the boot loader can't deal with that location. If I create the /usr and /var slices for the second OS and then say `Use defaults for all' it creates a 32MB root slice in the second partition, so that seems to get around the problem, but I can't boot this after the install is done. Not too sure what exactly you're trying to do here -but how about creating a separate *slice* for the two versions, then go install one version into one slice, carve that slice up into partitions (one for root /usr swap etc.) reboot, then go install the other version into the other slice, carve it up into partitions etc. This works, but has the restriction that I have to enter a command line at the boot prompt to boot one of the two. I would much prefer partitions, as I can use a boot selector instead, and also change the default as appropriate. Hope this helps, but why do you want 2.2.8 ? 3.2 is much better :) I have system software (including kernel hacks) written on 2.2.7 that needs to be ported to 2.2.8 and 3.2, for different reasons. -- Dr Graham WheelerE-mail: [EMAIL PROTECTED] Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Overloading my machine?
From brodnik Tue Aug 3 15:27:35 1999 Subject: Overloading my machine? To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Tue, 3 Aug 1999 15:27:35 +0200 (CEST) Organization: IBC, Iskra Systems Reply-To: [EMAIL PROTECTED] (Andrej Brodnik (Andy)) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2692 Status: RO Hi there, I want to put on my machine the following HW (I'll be running FBSD-3.2) beside the usual HW (serial and parallel ports etc.): - three IDE disks - floppy - IDE CD-ROM - three ep NIC - Adaptec PCI bus SCSI adapter Now, this is not a lot of burden (I think) for the processor, but I'm a bit afraid about the architecture. Will this work? In particular, I'm worried about the interrupts. Any suggestions how to configure them? Thanx in advance for your assistance! LPA PS: Here is dmesg for the current FBSD which doesn't have SCSI adapter installed. -- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.8-STABLE #0: Wed Jan 20 13:08:03 MET 1999 [EMAIL PROTECTED]:/usr/ports/FreeBSD-src/sys/compile/IRENA CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 134217728 (131072K bytes) avail memory = 129335296 (126304K bytes) Probing for devices on PCI bus 0: chip0 Intel 82439 rev 3 on pci0:0:0 chip1 Intel 82371SB PCI-ISA bridge rev 1 on pci0:7:0 chip2 Intel 82371SB IDE interface rev 0 on pci0:7:1 pci0:7:2: Intel Corporation, device=0x7020, class=serial, subclass=0x03 int d irq 11 [no driver assigned] vga0 VGA-compatible display device rev 64 on pci0:19:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color 4 virtual consoles, flags=0x0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): WDC AC22100H wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): WDC AC22100H wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): FUJITSU MPA3026ATU wd3: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S 3 3C5x9 board(s) on ISA found at 0x300 0x260 0x280 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*BNC*] address 00:60:97:3a:73:bf ep1 at 0x280-0x28f irq 5 on isa ep1: aui/utp/bnc[*BNC*] address 00:a0:24:dd:96:fe ep2 at 0x260-0x26f irq 11 on isa ep2: utp[*UTP*] address 00:60:97:4e:e5:93 npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: RE: DOC volunteer WAS:RE: userfs help needed.
Ach. As I read my original mail here I realize that I didn't make clear that the chief aim of developing this FS is to glean information for the FS doc. My idea is to learn by writing a toy FS and to elaborate upon the experience in the form of a FS-doc. I'll hold off until the new FS code is here. What are the perceived shortcomings of the current VFS? What suggestions are being considered for the new design? What are the principal design objectives? -Original Message- From: Matthew Dillon [SMTP:[EMAIL PROTECTED]] Sent: Friday, July 30, 1999 9:20 PM To: Alton, Matthew Cc: 'Nik Clayton'; David E. Cross; [EMAIL PROTECTED] Subject: Re: RE: DOC volunteer WAS:RE: userfs help needed. :Anyway, Mr. Dillon, once I have a development box to smack around, I :intend to start with your suggestion of implementing a filesystem :of my own concoction by returning an error for all VOP calls and :issuing a kernel printf. How visible will the new VOP code be to :me at this level? The Penguins are rewriting the bejesus out of their :VFS system to the point where all the existing FS code must be redone :to conform. Please debifurcate: :1) Any attempt from-scratch FS development should definitely wait for :the new VFS code. Start now and you'll only end up rewiting in the :Fall. :2) Hack away. All changes will be completely transparent to the FS :coder. Your code, as well as everything in 2.x and 3.x will drag :and drop right into the new model and build like the very wind. :Thanks I would go with option #2. The VFS/BIO changes are several months away at the very least. The framework hasn't even been worked out yet. The new model will not be compatible with the old, but if your stuff is in the source tree whoever winds up doing the major porting work will port it along with everything else. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
On Tue, 3 Aug 1999, Peter Wemm wrote: Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, one device (codadev) and one vfs (coda). Yes, the naming 'module_get_file_argstr()' had the _file_ for just this reason, filewide argument string. I didn't know any plans were already made on these circles, had only buggered Mr. Rabson once about arguments. Well, no harm done, I hope. Juha To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
NSS Project
Following on the NSS (Name Service Switch):
*Step One: I ported the NetBSD implementation of nsdispatch(3) as implemented
by Luke Mewburn. See attached patch to libc and new header file. I'm also
attaching the man page for /etc/nsswitch.conf. Right now it compiles,
installs, and works for some simple tests I've run.
*Step Two: make getpwent, getgrent, and friends actually use the nsdispatch
function. I've already started looking at the source, but am having trouble
with the NIS part. Maybe someone more knowledgeable could write the NIS
function.
Basically we have to reduce each of the functions to a simple nsdispatch
call and then implement the real functions... Here's an example from
getpwent.c
/* Basically we reduce getpwent to a simple nsdispatch call */
struct passwd *
getpwent()
{
int r;
static const ns_dtab dtab[] = {
NS_FILES_CB(_local_getpw, NULL)
NS_DNS_CB(_dns_getpw, NULL)
NS_NIS_CB(_nis_getpw, NULL)
NS_COMPAT_CB(_compat_getpwent, NULL)
{ 0 }
};
r = nsdispatch(NULL, dtab, NSDB_PASSWD, "getpwent", compatsrc,
_PW_KEYBYNUM);
if (r != NS_SUCCESS)
return (struct passwd *)NULL;
return _pw_passwd;
}
The we have to implement _local_getpw, _dns_getpw, _nis_getpw,
and _compat_getpwent and make them behave as expected.
NetBSD seems to support having the passwd database on DNS using something
called HESIOD (I hadn't heard about it before). I don't think FreeBSD has
any sort of support for this.
*Step Three: Implement _ldap_getpw :)
If anyone has any comments, suggestions, etc. I would appreciate it.
Regards,
-Oscar
--
For PGP Public Key: finger [EMAIL PROTECTED]
.\" $NetBSD: nsswitch.conf.5,v 1.14 1999/03/17 20:19:47 garbled Exp $
.\"
.\" Copyright (c) 1997, 1998, 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" This code is derived from software contributed to The NetBSD Foundation
.\" by Luke Mewburn.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by Luke Mewburn.
.\" 4. The name of the author may not be used to endorse or promote products
.\" derived from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
.\" OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
.\" TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
.\" USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd January 22, 1998
.Dt NSSWITCH.CONF 5
.Os
.Sh NAME
.Nm nsswitch.conf
.Nd name-service switch configuration file
.Sh DESCRIPTION
The
.Nm
file specifies how the
.Xr nsdispatch 3
(name-service switch dispatcher) routines in the C library should operate.
.Pp
The configuration file controls how a process looks up various databases
containing information regarding hosts, users (passwords), groups,
netgroups, etc.
Each database comes from a source (such as local files, DNS, and
.Tn NIS ) ,
and the order to look up the sources is specified in
.Nm nsswitch.conf .
.Pp
Each entry in
.Nm
consists of a database name, and a space separated list of sources.
Each source can have an optional trailing criterion that determines
whether the next listed source is used, or the search terminates at
the current source.
Each criterion consists of one or more status codes, and actions to
take if that status code occurs.
.Ss Sources
The following sources are implemented:
.Bl -column "compat" -offset indent -compact
.Sy Source Description
.It files Local files, such as
.Pa /etc/hosts ,
and
.Pa /etc/passwd .
.It dns Internet Domain Name System.
.Dq hosts
and
.Sq networks
use
.Sy IN
class entries, all other databases use
.Sy HS
class (Hesiod) entries.
.It nis NIS (formerly YP)
.It compat support
.Sq
Re: Multiple versions of FreeBSD on one HDD
If you do have the installations in two seperate slices on the one disk, you should be able to use a boot selector to boot which ever slice you want. Boot selector programs like os-bs work with partitions, not disk slices. That's why I wanted separate partitions. At the moment I have os-bs installed but it will only get me as far as a BSD boot. I then have to quickly hit a key and enter: 0:wd(0,c)/kernel to boot 2.2.8 (3.2 will boot by default). Ah yes, I see the problem now. Even if you have two seperate slices say wd0s1 and wd0s2 and boot into your selected one via os-bs, the boot prompt on either will always be 0:wd(0,a)/kernel ..and wd0a always points to the first BSD slice found on the disk. (in this case wd0s1 which is either 2.2.8 or 3.2 depending on where you installed them). I think the FreeBSD boot loader might need the option of specifying which *slice* to boot from rather than just which disk (0,1,2 etc.) and partition (a,b,c,d etc.) for the moment I think you'll just have to type in the line above every time you need to boot into 2.2.8 (or get another HD but that was the problem we've been trying to solve :) Anybody else out there have suggestions ? - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multiple versions of FreeBSD on one HDD
This works, but has the restriction that I have to enter a command line at the boot prompt to boot one of the two. I would much prefer partitions, as I can use a boot selector instead, and also change the default as appropriate. If you do have the installations in two seperate slices on the one disk, you should be able to use a boot selector to boot which ever slice you want. Just to elaborate on this: The new boot code is specifically designed to handle the separate slices case. Where multiple FreeBSD slices are found, it will prefer the one marked active; the old boot code always chose the first slice. For this to work optimally, it's best to replace your 2.2 boot blocks with ones from 3.2 (or otherwise ensure the 2.2 system occupies the first FreeBSD slice). You also need to use a boot manager which sets the "active" flag of the selected slice. I don't know if this will work with booteasy the boot manager that comes with FreeBSD by default, but there is a nice boot manager called OS Select (tools/os-bs.exe in the FreeBSD distribution I think). Both booteasy and boot0 (distributed in place of booteasy from 3.1R) work as well. -- Robert Nordier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD voice synthesis
Julian Elischer wrote: Just fetched and compiled the "festival" package. http://www.cstr.ed.ac.uk/projects/festival it has support for FreeBSD already (seems to work fine) Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word "FreeBSD" when I asked it to say (from the manual) Try Free B S D. Tricks like that used to work well with the simple ones available for "home" computers decades ago. (Anyone else here ever use SAM "the Software Automated Mouth" for the Atari 800 or Commodore 64?) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NSS Project
On Tue, 3 Aug 1999, Oscar Bonilla wrote:
Following on the NSS (Name Service Switch):
*Step One: I ported the NetBSD implementation of nsdispatch(3) as implemented
by Luke Mewburn. See attached patch to libc and new header file. I'm also
attaching the man page for /etc/nsswitch.conf. Right now it compiles,
installs, and works for some simple tests I've run.
Great. I haven't alnalyse all of the code but this thing looks
a little bit limited:
/* Basically we reduce getpwent to a simple nsdispatch call */
struct passwd *
getpwent()
{
int r;
static const ns_dtab dtab[] = {
NS_FILES_CB(_local_getpw, NULL)
NS_DNS_CB(_dns_getpw, NULL)
NS_NIS_CB(_nis_getpw, NULL)
NS_COMPAT_CB(_compat_getpwent, NULL)
{ 0 }
};
May be I'm totally wrong, but dtab[] array can be constructed (or
extended) dynamically, based on configuration file and _*_getpw()
functions can be placed in shared libraries (just like PAM modules). In
this case it is possible to extend NSS space without disturbing libc code.
--
Boris Popov
http://www.butya.kz/~bp/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Overloading my machine?
:Hi there, : :I want to put on my machine the following HW (I'll be running :FBSD-3.2) beside the usual HW (serial and parallel ports etc.): : : - three IDE disks : - floppy : - IDE CD-ROM : - three ep NIC : - Adaptec PCI bus SCSI adapter : :Now, this is not a lot of burden (I think) for the processor, but I'm :a bit afraid about the architecture. Will this work? In particular, :I'm worried about the interrupts. Any suggestions how to configure :them? : :Thanx in advance for your assistance! : :LPA : :PS: Here is dmesg for the current FBSD which doesn't have SCSI adapter :installed. : :FreeBSD 2.2.8-STABLE #0: Wed Jan 20 13:08:03 MET 1999 :[EMAIL PROTECTED]:/usr/ports/FreeBSD-src/sys/compile/IRENA :CPU: Pentium/P54C (166.19-MHz 586-class CPU) :... Well, the burden will not come from the devices but instead will come from the load you place on them. So, the real question should be: how do you intend to use the machine? The only hardware recommendation I can make would be to watch out re: the IDE disks. You may not be able to use DMA on all of them and that will really take the cpu out for lunch. SCSI is the better choice there if you intend to load the disks down. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposing argv for klds and preloaded modules
Juha Nurmela wrote: On Tue, 3 Aug 1999, Daniel C. Sobral wrote: Actually... Loader passes a string. It seems the kldcode is passing argv[]. Juha, you sure you have they both working the same way (from a module's perspective)? It's splatted together, by just putting ' ' between words, somewhere in there. Search for strbuf Juha Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, one device (codadev) and one vfs (coda). This is why Warner's X-resource-like proposal is the only method for passing parameters to modules that I am likely to accept. argv/argc and getopt() are just not good enough. If someone want to implement a simple resource matcher, you could start by coming up with a tiny, tidy glob() for the kernel. We can use it elsewhere as well... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Berkeley IRS and NSS
Anyone knows about the BSD Information Retrieval Service (IRS) mentioned in http://www.padl.com/nss_ldap.html ? It seems to accomplish the same thing as the NSS stuff we've been talking about. Regards, -Oscar -- For PGP Public Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no elf(5) man page (docs/7914)
* Wes Peters ([EMAIL PROTECTED]) [990803 10:13]: Jeroen Ruigrok/Asmodai wrote: * Andy Doran ([EMAIL PROTECTED]) [990802 00:53]: Wes Peters writes: NetBSD doesn't have one as of 1.4, so they may be interested in yours. ;^) It'd be cool if Asmodai could bounce this around one of the NetBSD lists once it's near completion. tech-toolchain@ or tech-userlevel@ would be the right place I guess. I already saw some differences in the stucture member names though, so ye will need to adjust those. Ain't cooperation great? ;^) Now if our OpenBSD friend will provide us with a mailing list or doc reviewer there, we can kill THREE birds with one stone. I know a committer there =) I have cc:'d him and hope he likes the idea as well. [hey Art ;)] OpenBSD, and pardon if saying it wrongly here, took the definitions from elf_common.h, so that's at least consistent. NetBSD defines some macros with other values =\ There goes some compatibility. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Overloading my machine?
"Andrej Brodnik (Andy)" schrieb: Hi there, I want to put on my machine the following HW (I'll be running FBSD-3.2) beside the usual HW (serial and parallel ports etc.): - three IDE disks - floppy - IDE CD-ROM - three ep NIC - Adaptec PCI bus SCSI adapter Now, this is not a lot of burden (I think) for the processor, but I'm a bit afraid about the architecture. Will this work? In particular, I'm worried about the interrupts. Any suggestions how to configure them? The ISA NIC's would made me worry. An ISA Ethernet NIC with a rate of ~ 1 MB/s utilizes the CPU up to 50-70% (regardless of the CPU speed). On practictal tests the ISA bus maxes out at around 3MB/s at 100 % CPU load (unless the ISA device does DMA) For more than average network traffic, I'd put some cheap PCI NICs in. You should have at least 2 PCI slots free. Unless you are using this machine also as a workstation, you could throw out the PCI VGA adapter and just use a plain old ISA one, so you will gain another PCI slot. Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multiple versions of FreeBSD on one HDD
By now the floppies for PowerBoot had come, so I tried installing that. I could now boot the HD, and PowerBoot can see the two partitions with freebsd installed (it even recognizes them as freebsd). Right now, my situation is that: - If I select WinNT at the PowerBoot menu, it comes up fine. Everything looks about as I'd expect. - If I select 2.2.8 at the PowerBoot menu, it comes up with one error message about "no /boot/loader", but then it comes right up in the 2.2.8 system. So this works fine, although it looks odd. You're using the new boot blocks for 2.2.8, and these always try to pass control to loader(8). To get rid of the message, create a /boot.config file with the line /kernel in it. - If I select 3.2 at the PowerBoot menu, it comes up with two messages about "invalid partition", one about "no boot loader", and then it can't automatically boot up anything. The interesting thing is that I'm in the 2.2.8 bootloader at this point, not the 3.2 one. It seems to want to boot 'da(0,a)/kernel', but if I type in 'da(0,e)/kernel', then it boots up fine. The problem here is a missing `a' partition. Seems like your first partition on that slice is `e'. There's a one-line patch to boot2 to get this working, but the standard version only autoboots from the `a' partition. My last partition is meant for installing OpenBSD, but I wasn't ready to do that yet. Later I was talking with one of the other guys here, and I went to show him what I did by trying to do another freebsd install into that 4th partition. Much to my surprise, it won't *let* me install into that partition. It's usually best to temporarily change fdisk partition types, so that sysinstall sees no existing FreeBSD slice on the drive. However, there may be other problems involved here as well. (note that I wanted to try PowerBoot because I also have a second hard disk, and I want to install Win98 on that one, along with BeOS and maybe some other OS's. It seemed to me that multi-disk situations could use something more than booteasy). Actually booteasy can handle two drives, and boot0 (which replaced booteasy in 3.1R) can handle more than that. However, the OSes on the higher drives must be capable of booting from the non-default drive. Most can do that -- even UnixWare -- though not Windows, which ignores the drive number passed in to it. So, for Windows, something that swaps drive letters is more suitable. So, my guess is that my primary problem is that I have only a vague idea of what I'm doing... Where is a good point to start looking for a better idea? I tried searching the web site for "multi-boot", but that didn't turn up much. I have a number of questions from doing this: 1. why does the install turn my HD unbootable? (invalid partition table). I didn't ask it to re-fdisk anything, and I didn't ask for it to change my boot loader. There are a number of possibilities, but one would have to look at a copy of the broken MBR to be sure. (The most usual reason for an "invalid partition table" message is multiple partitions flagged as active, or partitions that use the new-style active flag that is supported from Win95. This can be sorted out by booting from floppy or CD-ROM and using fdisk.) 2. I have the BIOS option on so I can boot off larger hard disks, and indeed it seems I can boot to the first three partitions. Why can't I get to that final one? You need to enable something more than the BIOS option. For instance, for FreeBSD, you need to enable LBA support in the boot blocks by means of a build option, and use boot0cfg(8) to turn on "packet" support in boot0. 3. Can I get it so that booting off the third partition will smoothly boot into 3.2-stable? Either patch boot2 or change to using an `a' partition. 4. given the rapidly-expanding size of HD's, would it be useful to support installs into DOS-style extended partitions? Or are they a problem which we're better off to avoid? I think support for extended partitions is inevitable (it's now the RedHat default), whether it really is a good idea or not. Technically, it violates the IBM specification that deals with fdisk partitions, though I'm not sure that matters very much. It will break some older OS/2 device drivers, for instance, though. -- Robert Nordier 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 [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 Tue, 3 Aug 1999, Nik Clayton wrote: 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. LyX can generate good LaTeX code, actually... But in all seriousness, I'd really LOVE to use LaTeX instead of .roff and and all the mdoc macros. I like LaTeX as a format much better than any of the alternatives. That and SGML... 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 Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Multiple versions of FreeBSD on one HDD
I should mention that what I have on the disk right now (with
the three systems) isn't too critical, so it is alright if I
have to start over and reinstall everything. On the other
hand, reinstalling does get a little tiring after awhile, so
I want to have a better idea of what I'm doing before I take
another stab at this, to minimize the number of reinstalls
that I wind up doing.
I should also mention that while I do have a second 4-gig scsi
disk to use, it isn't actually installed yet.
Also, I did intend to have a freebsd 4-current system as part
of this multi-boot mix. I don't think I mentioned that last
time. Perhaps I should create one fdisk-style partition per
hard disk, and put all freebsd-related slices (for all the
different freebsd installs) into that one partition? Would
that make things go smoother? (particularly if I put all the
boot-related slices at the start of that fdisk-style partition)
Using BSD terminology, "slice" == fdisk partition, and partitions
('a', 'e', etc.) are just "partitions". Though, IIRC, SVR5 uses
the terms the other way round.
I'd suggest you install one system per fdisk partition. I had a
system set up with 2.0R, 2.1R, 2.2R and 3-current (as was) in
separate slices, when testing the new boot code.
Some people do prefer the multiple systems per slice approach,
though, which is all that used to be supported. So either can
be made to work.
--
Robert Nordier
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Berkeley IRS and NSS
On Tue, 3 Aug 1999 11:28:29 -0600 Oscar Bonilla [EMAIL PROTECTED] wrote: Anyone knows about the BSD Information Retrieval Service (IRS) mentioned in http://www.padl.com/nss_ldap.html ? It seems to accomplish the same thing as the NSS stuff we've been talking about. In NetBSD, we specifically didn't go with IRS because we felt it was not flexible enough. -- Jason R. Thorpe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Results of investigating optimizing calloc()...
Sorry for posting this out-of-the-blue, I meant to post it last week
while the thread was still fresh, but I got distracted by work and other
projects, so here it is a tad late.
For those of you who hadn't been following the previous calloc() thread:
I had theorized that we could see an improvement in the performance of
calloc() by optimizing the case where there were no free memory was on the
heap and sbrk() was called to extend the process's address space. Since
sbrk() ensures that the newly available virtual address space is zeroed, it
seemed logical that calloc() could just return memory from that space.
Currently calloc() just calls malloc() which either returns free memory
already on the heap or extends the heap (using sbrk() ). Calloc() then calls
bzero() to clear the memory before returning it. The idea was to make
calloc() as smart as malloc() so it didn't waste its time bzero()ing memory
that was already cleared (courtesy of the kernel and sbrk() ).
However, after spending several hours wrapping my head around the malloc()
implementation (btw, thanks need to go to Poul-Henning Kamp for the great
malloc we have...someone should by him a beer ;) ), I realized as
Mattew Dillon and Dag-Erling Smorgrav predicted that this was fruitless
effort. The reason: the best case I could hope for calloc() would be the
worst case for malloc(). This is to say, that with all the work to make
calloc() smarter, the best it could hope for would be to need to sbrk()
more memory (relatively rare I discovered through some diagnostic
printf()s);
by comparison that is the worst thing malloc() ever has to do (often just
pulling memory out of a free list on the heap to serve the request).
But what about paging, that was the other concern. calloc() currently
touches all of the pages of memory in order to zero them. Well, this is the
only place where making calloc() smarter would help. The results below
illustrate the point:
All tests were performed on a 486/66 with 16M of RAM running FreeBSD-3.2:
malloc calloc malloc+wrt calloc+wrt
real time0.31 77.3375.76 100.67
user time0.11 15.9916.45 32.00
sys time0.18 37.4737.37 37.91
maximum resident set size 3081324 1252 1284
average shared memory size 4 44 4
average unshared data size 477 744 744744
average unshared stack size 37 129 128128
page reclaims 0 124799 124788 124780
page faults 0 410 0
swaps 0 00 0
voluntary context switches 0 00 0
involuntary context switches 3 604 593761
As you can see, calloc() takes drastically longer to allocate the same
amount of memory as malloc() does. The difference being that calloc()
touches every page (look at the huge number of page reclaims). But as the
latter 2 columns show, if you actually ever use the memory, then you are
pretty much even. We expect that writing to all the malloc()'ed memory
should be the same as calloc() since that is how calloc() is implemented...
and sure enough it is. And we see that writing to calloc()'ed memory is
only as expensive as the write itself (no change in sys time nor page
reclaims). If you consider the vast amount of memory that was written
(1000! * 1024 bytes = 4.12e+2570 bytes) in the tests, then you can see
how little overhead the write itself actually is for real-world programs.
So what does it all mean: it means I was wrong. We really don't stand
to gain anything from making calloc() smarter. At best I could have hoped
to optimize the rare case of needing to sbrk() more memory to fulfill a
calloc() request, and even then we see that the optimization isn't that
great. If anyone is interested, following are the actually test programs.
Kelly
~[EMAIL PROTECTED]~
FreeBSD - The Power To Serve - http://www.freebsd.org/
Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD/
/* malloctest.c */
#include stdlib.h
void main() {
int i;
void *loc;
for(i=0; i1000; i++) {
loc=malloc(i * 1024);
free(loc);
}
}
/* calloctest.c */
#include stdlib.h
void main() {
int i;
void *loc;
for(i=0; i1000; i++) {
loc=calloc(i, 1024);
free(loc);
}
}
/* malloctest2.c */
#include stdlib.h
#include string.h
void main() {
int i;
void *loc;
for(i=0; i1000; i++) {
loc=malloc(i * 1024);
memset(loc, 'A', i * 1024);
free(loc);
}
}
/* calloctest2.c */
#include stdlib.h
#include string.h
void main() {
int i;
void *loc;
for(i=0; i1000; i++) {
loc=calloc(i, 1024);
memset(loc, 'A', i * 1024);
free(loc);
}
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Tuning web benchmarks
On Tue, Aug 03, 1999, David Miller wrote: After the "Broken pipe" message it dies with a returncode of 141. You might want to try the Apache lists for this. -- |Chris Costello [EMAIL PROTECTED] |When all else fails, let a = 7. |If that doesn't help, then read the manual. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: more NFS questions, why is the VFS_FHTOVP weird?
On 3 Aug 1999, Assar Westerlund wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
* At this point, this should never happen
*/
/* ARGSUSED */
static int
nfs_fhtovp(mp, fhp, nam, vpp, exflagsp, credanonp)
register struct mount *mp;
struct fid *fhp;
struct sockaddr *nam;
struct vnode **vpp;
int *exflagsp;
struct ucred **credanonp;
{
return (EINVAL);
}
ok, now if you look at the first piece of code it obviously
fails if nfsrv_fhtovp fails, and nfsrv_fhtovp fails if VFS_FHTOVP
fails...
so how does NFS work? where is this magic function?
The NFS server is calling the FHTOVP function of the exported file
system. You're looking at the FHTOVP function for the NFS file system
itself. Look for example at ffs_fhtovp and ufs_check_export.
ah thank you it makes more sense now, i'm working on patches
to make this more like netbsd's way.
the macro VFS_FHTOVP is defined in mount.h:
#define VFS_FHTOVP(MP, FIDP, NAM, VPP, EXFLG, CRED) \
(*(MP)-mnt_op-vfs_fhtovp)(MP, FIDP, NAM, VPP, EXFLG, CRED)
I do think that checking for what file systems are exported has no
place in FHTOVP and this should probably be rewritten similar to the
way it has recently been done in NetBSD, namely with a new vfs
operation:
int (*vfs_checkexp) __P((struct mount *mp, struct mbuf *nam,
int *extflagsp, struct ucred **credanonp));
And they have also added fhopen and other syscalls that take file
handles instead of file names.
I just booted my NetBSD box and saw the implemented functions.
:)
btw, since this seems to work... is it ok to pass in a NULL
sockaddr *? (nam)
I think that nam == NULL means the default export list which doesn't
sound as what you want do do?
no it's not what I want to do, thank you for the help.
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
systems administrator and programmer
Wintelcom - http://www.wintelcom.net/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding disks -the pain. Also vinum
On Tue, Aug 03, 1999 at 03:59:46PM +0930, Greg Lehey wrote: On Tuesday, 3 August 1999 at 8:12:17 +0200, Bernd Walter wrote: For UFS/FFS there is nothing worth seting the stripesize to low. It is generally slower to acces 32k on different HDDs than to acces 64k on one HDD. It is always slower where the positioning time is greater than the transfer time for 32 kB. On modern disks, 32 kB transfer in about 300 µs. The average rotational latency of a disk running at 10,800 rpm is 2.8 ms, and even with spindle synchronization there's no way to avoid rotational latency under these circumstances. It shouldn't be the latency, because with spindlesync they are the same on both disks if the transfer is requested exactly the same time what is of course idealized.. The point is that you have more then a single transfer. With small transfers spindle sync is able to winback some of the performance you have lost with a to small stripe size. Spindle Sycronisation won't bring you that much on modern HDDs - I tried it using 5 Seagate Elite 2.9G (5,25" Full-Height). It should be useful for RAID-3 and streaming video. I case of large transfers it will make sense - but FFS is unable to set up big enough requests. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
What's new in Linux 2.4
Jordan recently mentioned "Wonderful World of Linux 2.4 (Second Edition)" http://features.linuxtoday.com/stories/8191.html. This article makes the statement "Linux is still the only operating system completely compatible with the IPv4 specification", which is further expanded in a followup article by [EMAIL PROTECTED]: http://features.linuxtoday.com/talkback/29410.html. Does anyone know what Joe and Soren are talking about here? I was under the impression that BSD (probably 4.3BSD) was the Reference Implementation for IPv4. Where does FreeBSD differ from the relevant RFCs? Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Mentioning RFC numbers in /etc/services
Assar Westerlund [EMAIL PROTECTED] wrote:
As an enhancement, the strtol() check should verify that the passed
service number is completely numeric:
--- inetd.c.orig Mon Aug 2 22:35:28 1999
+++ inetd.c Mon Aug 2 22:41:52 1999
@@ -830,34 +830,50 @@
continue;
}
if (!sep-se_rpc) {
+ int port;
+char *ep;
+
sp = getservbyname(sep-se_service, sep-se_proto);
if (sp == 0) {
- syslog(LOG_ERR, "%s/%s: unknown service",
+ port = htons(strtol (sep-se_service,
+ ep, 0));
+if (port = 0 || *ep) {
...
and similarly for the RPC service number.
Brian Somers [EMAIL PROTECTED] wrote:
I know I'd be pretty annoyed if I tried to do something like ``ssh -p
1234 somewhere'' after configuring my interface in single-user modem
with nis in /etc/host.conf and found that ssh was looking up 1234 in
/etc/services. Even if this is right, it's not intuitive.
Adding definitions like ': 1 2 ;' to forth is always good for confusing
people. Similarly, adding lines like '1234 4321/tcp' to /etc/services
will lead to counter-intuitive behaviour.
That said, I think that the get...byname() should preceed the strtol()
for general consistency.
Brian Somers [EMAIL PROTECTED] wrote:
I've been stung with things like pipe() for exactly the same reasons.
IMHO, pipe() should *not* behave like socketpair() as it encourages
FreeBSD developers to write bad code :-(
SVR4 provides bi-directional pipe(2) FD's. Digital UNIX (aka OSF/1
aka Tru64) seems to support both behaviours. I suspect the trend will
be for pipe()'s to be bi-directional. Feel free to add a sysctl to
make pipe's unidirectional.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Solution for mail pseudo-users?
:On Tue, 3 Aug 1999, Markus Stumpf wrote: : : I just don't see any justification in hacking away at all of your software : to bypass the passwd database. What is gained? : : If you have 10+ users you'll run out of UIDs (see recent thread). : :I find it hard to believe that handling 100,000 users on one box is a good :idea in the first place. : : Also you'll have to run the script to allow users to change passwords as : "root", which you probably will NOT want to do (same for adding/ : deleting/changing users) : :So with your setup, any user can add/delete/modify existing users? Yeah, :that's secure. : : Also with 3+ (maybe even with 1+) users each rebuild of the : passwd database will become SLOW and you have to take care about locking : and such ... been there, tried it, didn't like it. : :Yes, but with 100k+ users, a database (that requires slow rebuilding) is :faster to find random records in than a flat text file. In fact, perhaps :you should have instituted some sort of cron'd rebuild (once every 30 :minutes for instance), and then queued the changes, so as to prevent users :from frobbing in an incorrect manner. : :- alex : :You better believe that marijuana can cause castration. Just suppose your :girlfriend gets the munchies! I'm going to try again. The last response I posted to the wrong thread. This is what I do. I create a pseudo domain and a separate kmap in sendmail and route the mail to a separate backend. There are no user id's to have to worry about. The password file is not involved at all. Here's an example. S98 # ... whatever else was in ruleset 98 before ... R$+ + $* @ pplus . $=w $* $#popplus $: $1 @ pplus . $3 $4 R$+ + $* @ pplus . $=w . $* $#popplus $: $1 @ pplus . $3 $4 R$* @ pplus . $=w $*$#popplus $: $1 @ pplus . $2 $3 R$* @ pplus . $=w . $* $#popplus $: $1 @ pplus . $2 $3 Add to the SBasic_check_rcpt rule: R$+ @ pplus . $=w$@ OK Add to the mailers ( this is just an example, you would need to construct your own backend though, I suppose, I could make my dpopper backend available. It is not 100% finished though ). Mpopplus, P=/usr/local/bin/dpopmail, F=SDEFhlMsu, S=10/30, R=20/40, U=dpop, A=dpopmail $u Then all I do is create entries in my forwarding Kmaps or aliases file to direct somecomplexusername to [EMAIL PROTECTED] Ok, that seems a bit more complex that it really is, but if you are handling hundreds or thousands of users it is worth the trouble to setup something like this. Sendmail operates off of KMap's ... basically dbmed map files. At BEST, before I left, some of our sendmail KMaps had over a fifty-thousand entries in them. It's worth doing. Linear files are death. You can easily support several hundred thousand users with a setup like this. Even more. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
TCP stack hackers take a bow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Unmodified FreeBSD TCP at 1Gb/s. http://www.sciencedaily.com/releases/1999/08/990802072727.htm -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBN6dyYmlM93/mX/l7EQKDKgCfR7pUXdp6yU4+gmVf8SgyUaCRZlwAoKKc OZ/kSNLtUVb0lWIISZM5c0wW =gwyI -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Jail syscalls
Speaking of the jail() syscall -- it really needs to be revamped a little before people really start using it wholeheartedly. The size of the jail structure needs to be passed in the syscall to allow backwards compatibility when things change such as, for example, the size of the IP address. -Matt Matthew Dillon [EMAIL PROTECTED] : Jail is in RELENG_3 : :Not according to the CVS logs which lists kern_jail.c only for CURRENT. : :=== :File: kern_jail.c Status: Up-to-date : : Working revision:1.3 Fri Apr 30 06:51:51 1999 : Repository revision: 1.3 /spare/FreeBSD-current/src/sys/kern/kern_jail.c,v : Sticky Tag: (none) : Sticky Date: (none) : Sticky Options: (none) : : Existing Tags: :POST_VFS_BIO_NFS_PATCH (revision: 1.3) :PRE_VFS_BIO_NFS_PATCH (revision: 1.3) : :-- :Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] :FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999 : : : :To Unsubscribe: send mail to [EMAIL PROTECTED] :with "unsubscribe freebsd-hackers" in the body of the message : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Jail syscalls
Speaking of the jail() syscall -- it really needs to be revamped a little before people really start using it wholeheartedly. The size of the jail structure needs to be passed in the syscall to allow backwards compatibility when things change such as, for example, the size of the IP address. Actually, with interfaces like this you should generally pass a pointer to the structure in userspace, and stick a version number constant in the beginning of the structure. The size is often not enough of a determining factor... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
hi, I tried yesterday to make the kernel understand my CD ROM drive.. but it refused. Here is the dmesg (of boot -v)... is my config wrong or i missed something? The drive is Acer 32X and connected as secondary slave. It is seen by Win98 and BIOS. Can someone help? And what does "ide_pci: generic_dmainit 01f0:0: warning, IDE controller timing not set" mean? -biju Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #0: Tue Aug 3 22:06:49 IST 1999 root@bash:/usr/src/sys/compile/bash Calibrating clock(s) ... TSC clock: 233886023 Hz, i8254 clock: 1193298 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium/P55C (233.87-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 16777216 (16384K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00285000 - 0x00ffdfff, 14127104 bytes (3449 pages) avail memory = 14139392 (13808K bytes) Found BIOS32 Service Directory header at 0xc00fae60 Entry = 0xfb2e0 (0xc00fb2e0) Rev = 0 Len = 1 PCI BIOS entry at 0xb310 DMI header at 0xc00f5cc0 Version 2.0 Table at 0xf1000, 25 entries, 557 bytes Other BIOS signatures found: ACPI: $PnP: 000fbf30 Preloaded elf kernel "kernel" at 0xc0274000. VESA: information block 56 45 53 41 02 01 6d 27 00 c0 00 00 00 00 14 00 00 01 10 00 03 01 04 01 00 01 01 01 05 01 11 01 14 01 10 01 13 01 02 01 06 01 12 01 7c 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 13 mode(s) found pci_open(1):mode 1 addr port (0x0cf8) is 0x8074 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55971039) Probing for devices on PCI bus 0: found- vendor=0x1039, dev=0x5597, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Host to PCI bridge (vendor=1039 device=5597) rev 0x02 on pci0.0.0 found- vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 found- vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 01f0, size 3 map[1]: type 4, range 32, base 03f4, size 2 map[2]: type 4, range 32, base 0170, size 3 map[3]: type 4, range 32, base 0374, size 2 map[4]: type 4, range 32, base 4000, size 4 ide_pci0: PCI IDE controller (busmaster capable) rev 0xd0 int a irq 14 on pci0.1.1 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 0 status: 04 from port: 4002 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 1 status: 04 from port: 400a found- vendor=0x1039, dev=0x7001, revid=0x10 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e200, size 12 found- vendor=0x1013, dev=0x00b8, revid=0x45 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 3, range 32, base e000, size 25 map[1]: type 1, range 32, base e2001000, size 12 map[2]: type 1, range 32, base e2002000, size 12 vga0: Cirrus Logic GD5446 SVGA controller rev 0x45 on pci0.9.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0x Comp ID: @@@ [0x] Called nullpnp_probe with tag 0x0001, type 0x3642630e port 0x0534 0x0388 0x0220 0x irq 5:0 drq 1:3 en 1 port 0x0534 0x0388 0x0220 0x irq 5:0 drq 1:3 en 1 mss_attach CS42361 at 0x530 irq 5 dma 1:3 flags 0x13 pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 flags 0x13 on isa Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 flags 0x2 on isa sc0: fb0 kbd0 sc0: VGA color 16 virtual consoles, flags=0x2 ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d psm0: current command byte:0047 kbdc: TEST_AUX_PORT status: kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID: psm: status 00 02 64 psm: status 90 02 3c psm: status 90 02 3c psm: status 90 02 3c psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on
Re: NSS Project
hi, there!
On Tue, 3 Aug 1999, Oscar Bonilla wrote:
*Step One: I ported the NetBSD implementation of nsdispatch(3) as implemented
by Luke Mewburn. See attached patch to libc and new header file. I'm also
attaching the man page for /etc/nsswitch.conf. Right now it compiles,
installs, and works for some simple tests I've run.
*Step Two: make getpwent, getgrent, and friends actually use the nsdispatch
function. I've already started looking at the source, but am having trouble
with the NIS part. Maybe someone more knowledgeable could write the NIS
function.
Basically we have to reduce each of the functions to a simple nsdispatch
call and then implement the real functions... Here's an example from
getpwent.c
/* Basically we reduce getpwent to a simple nsdispatch call */
struct passwd *
getpwent()
{
int r;
static const ns_dtab dtab[] = {
NS_FILES_CB(_local_getpw, NULL)
NS_DNS_CB(_dns_getpw, NULL)
NS_NIS_CB(_nis_getpw, NULL)
NS_COMPAT_CB(_compat_getpwent, NULL)
{ 0 }
};
r = nsdispatch(NULL, dtab, NSDB_PASSWD, "getpwent", compatsrc,
_PW_KEYBYNUM);
if (r != NS_SUCCESS)
return (struct passwd *)NULL;
return _pw_passwd;
}
The we have to implement _local_getpw, _dns_getpw, _nis_getpw,
and _compat_getpwent and make them behave as expected.
NetBSD seems to support having the passwd database on DNS using something
called HESIOD (I hadn't heard about it before). I don't think FreeBSD
*Step Three: Implement _ldap_getpw :)
pam/nss ldap modules are already available (http://www.padl.com)
i think we should implement NSS in that way so we need not recompile if we
want to add third-party nss module. Also compatibility with Solaris is
desirable.
/fjoe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: What's new in Linux 2.4
* Peter Jeremy ([EMAIL PROTECTED]) [990804 01:13]: Jordan recently mentioned "Wonderful World of Linux 2.4 (Second Edition)" http://features.linuxtoday.com/stories/8191.html. This article makes the statement "Linux is still the only operating system completely compatible with the IPv4 specification", which is further expanded in a followup article by [EMAIL PROTECTED]: http://features.linuxtoday.com/talkback/29410.html. Does anyone know what Joe and Soren are talking about here? I was under the impression that BSD (probably 4.3BSD) was the Reference Implementation for IPv4. Where does FreeBSD differ from the relevant RFCs? I think that Linux is not fully compliant. Mayhaps it is nowadays, but the last time I delved around there were some problems regarding ARP, some ICMP [which was recently fixed IIRC] and a few others which I cannot remember from the top of my head though... I think some other people in here might elaborate some more. The point with the RFC's are the MAY, SHOULD and MUST keywords. One can be fully compatible and yet miss a lot of features. Oh wait, we're talking Linux here. Hmm, then the features will be present. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding disks -the pain. Also vinum
On Tue, Aug 03, 1999 at 01:35:54PM +0930, Greg Lehey wrote: On Tuesday, 3 August 1999 at 11:11:39 +0800, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: No, it would cause a higher I/O load. Vinum doesn't transfer entire stripes, it transfers what you ask for. With a large stripe size, the chances are higher that you can perform the transfer with only a single I/O. If you use n*64K stripes a UFS/FFS should never access 2 disks at once. Looking at the systat display, the 8k fs blocks do seem to be clustered into larger requests, so I'm not too worried about the FS block size. What have people observed with trying larger FS block sizes? I don't know if anybody has tried larger FS blocks than 8 kB. I once created a file system with 256 kB blocks (just to see if it could be done). I also tried 512 kB blocks, but newfs died of an overflow. I'd expect that you would see a marked drop in performance, assuming that it would work at all. AFAIK the limit is 64k because clustering is limitited to 64k and the fs don't seem to handle it well. I'm using 64k very often, because my growfs tool is already able with this blocksize to grow a ffs over 1Tb. -- B.Walter COSMO-Project http://www.cosmo-project.de ti...@cicely.de Usergroupi...@cosmo-project.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Documenting writev(2) ENOBUFS error
Nik Clayton wrote: 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 Mmmm. Yummy. Do we want to mention that one or more of the vectors may have been written before the failure occurred, or is that OTTMCO? ;^) -- Where am I, and what am I doing in this handbasket? Wes Peters Softweyr LLC http://softweyr.com/ w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Adding disks -the pain. Also vinum
On Tue, Aug 03, 1999 at 12:16:06PM +0800, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: No, it would cause a higher I/O load. Vinum doesn't transfer entire stripes, it transfers what you ask for. With a large stripe size, the chances are higher that you can perform the transfer with only a single I/O. Even if I'm using really large reads? Several month ago I beleaved the same but there are severall points here: - UFS/FFS don't handle clustering over 64k - modern harddisks do preread simply by having a reversed sector layout. - without spindle syncronisation you will have additional latency - vinum don't aggregate access to subdisks, so the transfer to the subdisks is limited by the stripe size. For UFS/FFS there is nothing worth seting the stripesize to low. It is generally slower to acces 32k on different HDDs than to acces 64k on one HDD. Spindle Sycronisation won't bring you that much on modern HDDs - I tried it using 5 Seagate Elite 2.9G (5,25 Full-Height). There was no win using FFS. If you need performance try softupdates. At least for writing it should benefit much from striped partitions. I never realy measured but I was astounished that you can have over 800 transactions/sec on a ccd with 6 striped disks. -- B.Walter COSMO-Project http://www.cosmo-project.de ti...@cicely.de Usergroupi...@cosmo-project.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Jail syscalls
According to Brian F. Feldman: Jail is in RELENG_3 Not according to the CVS logs which lists kern_jail.c only for CURRENT. === File: kern_jail.c Status: Up-to-date Working revision:1.3 Fri Apr 30 06:51:51 1999 Repository revision: 1.3 /spare/FreeBSD-current/src/sys/kern/kern_jail.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) Existing Tags: POST_VFS_BIO_NFS_PATCH (revision: 1.3) PRE_VFS_BIO_NFS_PATCH (revision: 1.3) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: no elf(5) man page (docs/7914)
Jeroen Ruigrok/Asmodai wrote: * Andy Doran (a...@netbsd.org) [990802 00:53]: Wes Peters writes: NetBSD doesn't have one as of 1.4, so they may be interested in yours. ;^) It'd be cool if Asmodai could bounce this around one of the NetBSD lists once it's near completion. tech-toolchain@ or tech-userlevel@ would be the right place I guess. Will do. I already saw some differences in the stucture member names though, so ye will need to adjust those. Ain't cooperation great? ;^) Now if our OpenBSD friend will provide us with a mailing list or doc reviewer there, we can kill THREE birds with one stone. -- Where am I, and what am I doing in this handbasket? Wes Peters Softweyr LLC http://softweyr.com/ w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Mentioning RFC numbers in /etc/services
In message 199908022217.xaa02...@keep.lan.awfulhak.org Brian Somers writes: : Yes, but do it the other way 'round - strtol first, if it's not all : numeric, getservbyname(). I did it getservbyname first in case there were any legacy services that were all numbers. Traditionally, this is hwo things were done with IP addresses, although a quickie survey shows it to be a mixed bag. The biggest reason for not doing getservbyname first is that it will hang (long timeout) if the databsae behind it goes away. Exactly - ditto for gethostbyname(). In the case of gethostbyname(), I believe that domain names can't have a number as the first character - I would have thought this idea should follow through with services. I know I'd be pretty annoyed if I tried to do something like ``ssh -p 1234 somewhere'' after configuring my interface in single-user modem with nis in /etc/host.conf and found that ssh was looking up 1234 in /etc/services. Even if this is right, it's not intuitive. Warner -- Brian br...@awfulhak.orgbr...@freebsd.org http://www.Awfulhak.org br...@openbsd.org Don't _EVER_ lose your sense of humour ! br...@freebsd.org.uk To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Mentioning RFC numbers in /etc/services
In some email I received from Brian Somers, sie wrote: [.] Yes, but do it the other way 'round - strtol first, if it's not all numeric, getservbyname(). No, the patch was correct. Not in my book - see my other posting :] -- Brian br...@awfulhak.orgbr...@freebsd.org http://www.Awfulhak.org br...@openbsd.org Don't _EVER_ lose your sense of humour ! br...@freebsd.org.uk To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Adding disks -the pain. Also vinum
On Tuesday, 3 August 1999 at 8:12:17 +0200, Bernd Walter wrote: On Tue, Aug 03, 1999 at 12:16:06PM +0800, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: No, it would cause a higher I/O load. Vinum doesn't transfer entire stripes, it transfers what you ask for. With a large stripe size, the chances are higher that you can perform the transfer with only a single I/O. Even if I'm using really large reads? Several month ago I beleaved the same but there are severall points here: - UFS/FFS don't handle clustering over 64k - modern harddisks do preread simply by having a reversed sector layout. - without spindle syncronisation you will have additional latency - vinum don't aggregate access to subdisks, so the transfer to the subdisks is limited by the stripe size. Note, BTW, that this wouldn't make much sense. To aggregate access to consecutive stripes, your transfer would have to involve *all* the disks in the stripe set, which would be a ridiculous performance hit. Read http://www.lemis.com/vinum/Performance-issues.html for more details. For UFS/FFS there is nothing worth seting the stripesize to low. It is generally slower to acces 32k on different HDDs than to acces 64k on one HDD. It is always slower where the positioning time is greater than the transfer time for 32 kB. On modern disks, 32 kB transfer in about 300 µs. The average rotational latency of a disk running at 10,800 rpm is 2.8 ms, and even with spindle synchronization there's no way to avoid rotational latency under these circumstances. Spindle Sycronisation won't bring you that much on modern HDDs - I tried it using 5 Seagate Elite 2.9G (5,25 Full-Height). It should be useful for RAID-3 and streaming video. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Mentioning RFC numbers in /etc/services
In message 199908030624.haa00...@keep.lan.awfulhak.org Brian Somers writes: : Exactly - ditto for gethostbyname(). In the case of gethostbyname(), : I believe that domain names can't have a number as the first : character - I would have thought this idea should follow through with : services. No. That is in error. 3com.com or 2112.com. See RFC 1123 for the loosening of the restriction. You have to parse the whole string to know if it is a valid IP address or not anyway. : I know I'd be pretty annoyed if I tried to do something like ``ssh -p : 1234 somewhere'' after configuring my interface in single-user modem : with nis in /etc/host.conf and found that ssh was looking up 1234 in : /etc/services. Even if this is right, it's not intuitive. But inetd isn't involved here at all. You do bring up a good point here in argument by analogy. However your rule for isdigit(arg[0]) breaks the following services: 3com-tsmux 106/tcp 3com-tsmux 106/udp 914c/g 211/tcp#Texas Instruments 914C/G Terminal 914c/g 211/udp#Texas Instruments 914C/G Terminal 9pfs564/tcp#plan 9 file service 9pfs564/udp#plan 9 file service 3l-l1 1511/tcp 3l-l1 1511/udp 3ds-lm 1538/tcp 3ds-lm 1538/udp 3m-image-lm 1550/tcp#Image Storage license manager 3M Company 3m-image-lm 1550/udp#Image Storage license manager 3M Company at least we know there are no all numeric service names in the standard /etc/services file. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
BSD voice synthesis
Just fetched and compiled the festival package. http://www.cstr.ed.ac.uk/projects/festival it has support for FreeBSD already (seems to work fine) Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word FreeBSD when I asked it to say (from the manual) [you need..] A Unix machine, Festival has compiled and run on Suns (SunOS and Solaris), FreeBSD, Linux, SGIs, HPs and DEC Alphas but should be portable to any standard Unix machine. julian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Support for ez USB chips, anchorchips
A down-/uploader for the EZ USB chip is available from http://www.etla.net/~ezload.tar.gz See also the AnchorChips home page http://www.anchorchips.com/ The utility is courtesy of Dirk van Gulik, WebWeaving Consultancy and ActiveWire, Inc. (prototype board, http://www.activewireinc.com/) Cheers, Nick Hibma FreeBSD USB Project mailing list: usb-...@egroups.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
more NFS questions, why is the VFS_FHTOVP weird?
If you look in src/nfs/nfs_serv.c in almost every call you'll see
this:
nfsm_srvmtofh(fhp);
nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED);
error = nfsrv_fhtovp(fhp, 1, vp, cred, slp, nam, rdonly,
(nfsd-nd_flag ND_KERBAUTH), TRUE);
if (error) {
nfsm_reply(NFSX_UNSIGNED);
nfsm_srvpostop_attr(1, (struct vattr *)0);
error = 0;
goto nfsmout;
}
my interest is the third function called (nfsrv_fhtovp)
it is in nfs_subs.c around line 1953
the problem with nfsrv_fhtovp is that it is overkill for my application
(it checks perms where i don't need it to, so i would have to fake
a lot of stuff to look like i was authorized)
so instead I gutted nfsrv_fhtovp a bit and came up with this sequence:
fhp = nfh.fh_generic;
error = copyin(u_fhp, fhp, fhlen);
if (error)
return(error);
/* find the mount point */
mp = vfs_getvfs(fhp-fh_fsid);
if (!mp)
return (ESTALE);
/* now give me my vnode, it gets returned to me locked */
error = VFS_FHTOVP(mp, fhp-fh_fid, nam, vp, exflags, credanon);
if (error)
return (error);
the copying is from userspace, it's a NFS handle...
now here's where I get very confused...
in src/nfs/nfs_vfsops.c around line 1100:
/*
* At this point, this should never happen
*/
/* ARGSUSED */
static int
nfs_fhtovp(mp, fhp, nam, vpp, exflagsp, credanonp)
register struct mount *mp;
struct fid *fhp;
struct sockaddr *nam;
struct vnode **vpp;
int *exflagsp;
struct ucred **credanonp;
{
return (EINVAL);
}
ok, now if you look at the first piece of code it obviously
fails if nfsrv_fhtovp fails, and nfsrv_fhtovp fails if VFS_FHTOVP
fails...
so how does NFS work? where is this magic function?
the macro VFS_FHTOVP is defined in mount.h:
#define VFS_FHTOVP(MP, FIDP, NAM, VPP, EXFLG, CRED) \
(*(MP)-mnt_op-vfs_fhtovp)(MP, FIDP, NAM, VPP, EXFLG, CRED)
btw, since this seems to work... is it ok to pass in a NULL
sockaddr *? (nam)
thanks for all the help,
-Alfred Perlstein - [bri...@rush.net|bri...@wintelcom.net]
systems administrator and programmer
Wintelcom - http://www.wintelcom.net/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
IDE quirk in 3.2-STABLE kernel ?
Hi, On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk When I boot up under a 3.2-STABLE kernel (recently updated), wdc1 is not found However when I boot up under a 3.1-RELEASE generic kernel it sees the drive (wd2) and controller (wdc1) ok. (And yes I do have an entry for wdc1,wd2,wd3 in the config file for the 3.2-STABLE kernel) However, when I plugged in a CDROM drive in place of wd2, both kernels saw it ok. Maybe the wd2 disk has a quirk in it, but how come it works in one version and not in the next ? Any ideas ? - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Multiple versions of FreeBSD on one HDD
Hi all I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but am not having much luck. I have tried several approaches, in particular creating four partitions, the first two for the respective root slices, the third for swap, and the fourth for the remaining slices. If I create the first two partitions as small as 50Mb, sysinstall still complains that it can't make a root slice in the second partition as the boot loader can't deal with that location. If I create the /usr and /var slices for the second OS and then say `Use defaults for all' it creates a 32MB root slice in the second partition, so that seems to get around the problem, but I can't boot this after the install is done. If I install DOS in the first 50Mb partition, then there is no problem. So it seems the presence of a FreeBSD partition preceding the one in which I want to make the root slice prevents things from working. Is there a way around this (other than using a second drive?) TIA gram -- Dr Graham WheelerE-mail: g...@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju -Original Message- From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-hack...@freebsd.org]on Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 3:39 PM To: hack...@freebsd.org Subject: IDE quirk in 3.2-STABLE kernel ? Hi, On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk When I boot up under a 3.2-STABLE kernel (recently updated), wdc1 is not found However when I boot up under a 3.1-RELEASE generic kernel it sees the drive (wd2) and controller (wdc1) ok. (And yes I do have an entry for wdc1,wd2,wd3 in the config file for the 3.2-STABLE kernel) However, when I plugged in a CDROM drive in place of wd2, both kernels saw it ok. Maybe the wd2 disk has a quirk in it, but how come it works in one version and not in the next ? Any ideas ? - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: IDE quirk in 3.2-STABLE kernel ?
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju Normally for my own kernel, I set the IDE delay very low (IDEDELAY=1000 in conf file) to speed up booting..I'll try increasing this for my 3.2-STABLE kernel, reboot and see if it detects wdc1 + wd2...Otherwise there must be something changed between 3.1-RELEASE generic and 3.2-STABLE ?? Cheers, - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju -Original Message- From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-hack...@freebsd.org]on Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 4:28 PM To: b...@wipinfo.soft.net Cc: hack...@freebsd.org Subject: Re: IDE quirk in 3.2-STABLE kernel ? Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju Normally for my own kernel, I set the IDE delay very low (IDEDELAY=1000 in conf file) to speed up booting..I'll try increasing this for my 3.2-STABLE kernel, reboot and see if it detects wdc1 + wd2...Otherwise there must be something changed between 3.1-RELEASE generic and 3.2-STABLE ?? Cheers, - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but am not having much luck. I have tried several approaches, in particular creating four partitions, the first two for the respective root slices, the third for swap, and the fourth for the remaining slices. If I create the first two partitions as small as 50Mb, sysinstall still complains that it can't make a root slice in the second partition as the boot loader can't deal with that location. If I create the /usr and /var slices for the second OS and then say `Use defaults for all' it creates a 32MB root slice in the second partition, so that seems to get around the problem, but I can't boot this after the install is done. Not too sure what exactly you're trying to do here -but how about creating a separate *slice* for the two versions, then go install one version into one slice, carve that slice up into partitions (one for root /usr swap etc.) reboot, then go install the other version into the other slice, carve it up into partitions etc. This way you should have something similar to: da0s1 = FreeBSD 2.2.8, da0s2 = FreeBSD 3.2 AFAIK, wd0a will refer to wd0s1a etc. Hope this helps, but why do you want 2.2.8 ? 3.2 is much better :) - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju I just set IDE_DELAY=4000 in my 3.2-STABLE kernel, and now it sees all disks on both controllers. I think the problem was that one of my IDE disks is a Joe IDE device (TM). Depending on which controller it was put would cause that controller to be not found. Ok, my problem is solved - don't know about that ATAPI drive of yours though...Is it only detected at boot time when there's a CD in it ? is it detected ok in other OS's without the need for putting the CD in ? - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: more NFS questions, why is the VFS_FHTOVP weird?
Alfred Perlstein bri...@rush.net writes:
the problem with nfsrv_fhtovp is that it is overkill for my application
(it checks perms where i don't need it to, so i would have to fake
a lot of stuff to look like i was authorized)
What's your application?
so instead I gutted nfsrv_fhtovp a bit and came up with this sequence:
fhp = nfh.fh_generic;
error = copyin(u_fhp, fhp, fhlen);
if (error)
return(error);
/* find the mount point */
mp = vfs_getvfs(fhp-fh_fsid);
if (!mp)
return (ESTALE);
/* now give me my vnode, it gets returned to me locked */
error = VFS_FHTOVP(mp, fhp-fh_fid, nam, vp, exflags, credanon);
if (error)
return (error);
the copying is from userspace, it's a NFS handle...
now here's where I get very confused...
in src/nfs/nfs_vfsops.c around line 1100:
/*
* At this point, this should never happen
*/
/* ARGSUSED */
static int
nfs_fhtovp(mp, fhp, nam, vpp, exflagsp, credanonp)
register struct mount *mp;
struct fid *fhp;
struct sockaddr *nam;
struct vnode **vpp;
int *exflagsp;
struct ucred **credanonp;
{
return (EINVAL);
}
ok, now if you look at the first piece of code it obviously
fails if nfsrv_fhtovp fails, and nfsrv_fhtovp fails if VFS_FHTOVP
fails...
so how does NFS work? where is this magic function?
The NFS server is calling the FHTOVP function of the exported file
system. You're looking at the FHTOVP function for the NFS file system
itself. Look for example at ffs_fhtovp and ufs_check_export.
the macro VFS_FHTOVP is defined in mount.h:
#define VFS_FHTOVP(MP, FIDP, NAM, VPP, EXFLG, CRED) \
(*(MP)-mnt_op-vfs_fhtovp)(MP, FIDP, NAM, VPP, EXFLG, CRED)
I do think that checking for what file systems are exported has no
place in FHTOVP and this should probably be rewritten similar to the
way it has recently been done in NetBSD, namely with a new vfs
operation:
int (*vfs_checkexp) __P((struct mount *mp, struct mbuf *nam,
int *extflagsp, struct ucred **credanonp));
And they have also added fhopen and other syscalls that take file
handles instead of file names.
btw, since this seems to work... is it ok to pass in a NULL
sockaddr *? (nam)
I think that nam == NULL means the default export list which doesn't
sound as what you want do do?
/assar
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju I just set IDE_DELAY=4000 in my 3.2-STABLE kernel, and now it sees all disks on both controllers. I think the problem was that one of my IDE disks is a Joe IDE device (TM). Depending on which controller it was put would cause that controller to be not found. Great! Ok, my problem is solved - don't know about that ATAPI drive of yours though...Is it only detected at boot time when there's a CD in it ? is it detected ok in other OS's without the need for putting the CD in ? True. The second wd controller is not recognized. Probably i will try with different delay. Even bios detects it as a ATAPI cdrom drive 32X! And yes!! i get a strange message while booting.. Since my box is at home, i cant give the error message.. probably tomorrow i'll be back with more findings cheers, -biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
subscribe
subscribe ? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD voice synthesis
On Tue, 3 Aug 1999, Julian Elischer wrote: Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word FreeBSD when I asked it to say (from the manual) I'm using a pIII-450 and it pronounces it freebs. However if you spell it Free B S D it does just fine. Seems to do well with most words I've thrown at it - including some last names (it does mine almost perfect, but blows some real easy ones). [you need..] A Unix machine, Festival has compiled and run on Suns (SunOS and Solaris), FreeBSD, Linux, SGIs, HPs and DEC Alphas but should be portable to any standard Unix machine. Did gmake test work for you in festival? It did for me in speech-tools but not festival even tho it seems to work well. Sure is gonna make some of these boring README files easier! ...wonder how hard it'd be to tie it into the select buffer in X... Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Interesting Kernel Config
Greets ... I just noticed that on my 2.2.6 System, I had to enable the options ATAPI options ATAPI_STATIC device wcd0 before the following had any effect: controller wdc1 at disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 in my kernel config file. So, the second controller was only seen after I enabled ATAPI? eT To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Proposing argv for klds and preloaded modules
Daniel C. Sobral wrote: assuming we are making it at all, the less pain. It provides a way of getting parameters that is compatible with what is already possible with loader (ie, the module need not differentiate between it's method of loading). The code is working and ready. Actually... Loader passes a string. It seems the kldcode is passing argv[]. Juha, you sure you have they both working the same way (from a module's perspective)? -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org - Jordan, God, what's the difference? - God doesn't belong to the -core. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Overloading my machine?
Overloading my machine?
Hi there, I want to put on my machine the following HW (I'll be running FBSD-3.2) beside the usual HW (serial and parallel ports etc.): - three IDE disks - floppy - IDE CD-ROM - three ep NIC - Adaptec PCI bus SCSI adapter Now, this is not a lot of burden (I think) for the processor, but I'm a bit afraid about the architecture. Will this work? In particular, I'm worried about the interrupts. Any suggestions how to configure them? Thanx in advance for your assistance! LPA PS: Here is dmesg for the current FBSD which doesn't have SCSI adapter installed. -- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.8-STABLE #0: Wed Jan 20 13:08:03 MET 1999 r...@irena.iskrasistemi.si:/usr/ports/FreeBSD-src/sys/compile/IRENA CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping=12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 134217728 (131072K bytes) avail memory = 129335296 (126304K bytes) Probing for devices on PCI bus 0: chip0 Intel 82439 rev 3 on pci0:0:0 chip1 Intel 82371SB PCI-ISA bridge rev 1 on pci0:7:0 chip2 Intel 82371SB IDE interface rev 0 on pci0:7:1 pci0:7:2: Intel Corporation, device=0x7020, class=serial, subclass=0x03 int d irq 11 [no driver assigned] vga0 VGA-compatible display device rev 64 on pci0:19:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color 4 virtual consoles, flags=0x0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): WDC AC22100H wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): WDC AC22100H wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): FUJITSU MPA3026ATU wd3: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S 3 3C5x9 board(s) on ISA found at 0x300 0x260 0x280 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*BNC*] address 00:60:97:3a:73:bf ep1 at 0x280-0x28f irq 5 on isa ep1: aui/utp/bnc[*BNC*] address 00:a0:24:dd:96:fe ep2 at 0x260-0x26f irq 11 on isa ep2: utp[*UTP*] address 00:60:97:4e:e5:93 npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
Cillian Sharkey wrote: I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but am not having much luck. I have tried several approaches, in particular creating four partitions, the first two for the respective root slices, the third for swap, and the fourth for the remaining slices. If I create the first two partitions as small as 50Mb, sysinstall still complains that it can't make a root slice in the second partition as the boot loader can't deal with that location. If I create the /usr and /var slices for the second OS and then say `Use defaults for all' it creates a 32MB root slice in the second partition, so that seems to get around the problem, but I can't boot this after the install is done. Not too sure what exactly you're trying to do here -but how about creating a separate *slice* for the two versions, then go install one version into one slice, carve that slice up into partitions (one for root /usr swap etc.) reboot, then go install the other version into the other slice, carve it up into partitions etc. This works, but has the restriction that I have to enter a command line at the boot prompt to boot one of the two. I would much prefer partitions, as I can use a boot selector instead, and also change the default as appropriate. Hope this helps, but why do you want 2.2.8 ? 3.2 is much better :) I have system software (including kernel hacks) written on 2.2.7 that needs to be ported to 2.2.8 and 3.2, for different reasons. -- Dr Graham WheelerE-mail: g...@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Proposing argv for klds and preloaded modules
On Tue, 3 Aug 1999, Daniel C. Sobral wrote: Actually... Loader passes a string. It seems the kldcode is passing argv[]. Juha, you sure you have they both working the same way (from a module's perspective)? It's splatted together, by just putting ' ' between words, somewhere in there. Search for strbuf Juha To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
This works, but has the restriction that I have to enter a command line at the boot prompt to boot one of the two. I would much prefer partitions, as I can use a boot selector instead, and also change the default as appropriate. If you do have the installations in two seperate slices on the one disk, you should be able to use a boot selector to boot which ever slice you want. I don't know if this will work with booteasy the boot manager that comes with FreeBSD by default, but there is a nice boot manager called OS Select (tools/os-bs.exe in the FreeBSD distribution I think).. (the setup program is an MSDOS exe) It allows you to create a menu of OS's to boot from by selecting the relevant slices from the list it shows. It also allows you to set a default slice to boot aswell as a timeout counter. Whether it will work or not in your situation remains to be seen.. :) Regards, - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Proposing argv for klds and preloaded modules
Juha Nurmela wrote: On Tue, 3 Aug 1999, Daniel C. Sobral wrote: Actually... Loader passes a string. It seems the kldcode is passing argv[]. Juha, you sure you have they both working the same way (from a module's perspective)? It's splatted together, by just putting ' ' between words, somewhere in there. Search for strbuf Juha Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, one device (codadev) and one vfs (coda). Cheers, -Peter -- Peter Wemm - pe...@freebsd.org; pe...@yahoo-inc.com; pe...@netplex.com.au 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.
I'll follow these guidelines. Thank you. -Original Message- From: Nik Clayton [SMTP:n...@nothing-going-on.demon.co.uk] Sent: Friday, July 30, 1999 6:47 PM To: Alton, Matthew Cc: 'Nik Clayton'; 'Matthew Dillon'; David E. Cross; freebsd-hackers@FreeBSD.ORG; d...@freebsd.org Subject: 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 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Proposing argv for klds and preloaded modules
Peter Wemm wrote: Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, one device (codadev) and one vfs (coda). It seems to me that the one who gets the arguments is the one who searches for it. :-) Either that, or the first file in the module. I don't recall right now the precise structure of this in memory. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org - Jordan, God, what's the difference? - God doesn't belong to the -core. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Proposing argv for klds and preloaded modules
Daniel C. Sobral wrote: Peter Wemm wrote: Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, on e device (codadev) and one vfs (coda). It seems to me that the one who gets the arguments is the one who searches for it. :-) Either that, or the first file in the module. I don't recall right now the precise structure of this in memory. The Plan(TM) was that things will be able to query the resource database. What I've had in mind for a while is to take the argument strings etc and merge them into the tables, but that's a rather device centric view. They would be installable either via preload args, kldload args and/or settable via some userland tool (sysctl would be ideal, but it's too limited in it's design - it can't have arbitary strings, everything has to translate to an OID first). Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: RE: DOC volunteer WAS:RE: userfs help needed.
Ach. As I read my original mail here I realize that I didn't make clear that the chief aim of developing this FS is to glean information for the FS doc. My idea is to learn by writing a toy FS and to elaborate upon the experience in the form of a FS-doc. I'll hold off until the new FS code is here. What are the perceived shortcomings of the current VFS? What suggestions are being considered for the new design? What are the principal design objectives? -Original Message- From: Matthew Dillon [SMTP:dil...@apollo.backplane.com] Sent: Friday, July 30, 1999 9:20 PM To: Alton, Matthew Cc: 'Nik Clayton'; David E. Cross; freebsd-hackers@FreeBSD.ORG Subject: Re: RE: DOC volunteer WAS:RE: userfs help needed. :Anyway, Mr. Dillon, once I have a development box to smack around, I :intend to start with your suggestion of implementing a filesystem :of my own concoction by returning an error for all VOP calls and :issuing a kernel printf. How visible will the new VOP code be to :me at this level? The Penguins are rewriting the bejesus out of their :VFS system to the point where all the existing FS code must be redone :to conform. Please debifurcate: :1) Any attempt from-scratch FS development should definitely wait for :the new VFS code. Start now and you'll only end up rewiting in the :Fall. :2) Hack away. All changes will be completely transparent to the FS :coder. Your code, as well as everything in 2.x and 3.x will drag :and drop right into the new model and build like the very wind. :Thanks I would go with option #2. The VFS/BIO changes are several months away at the very least. The framework hasn't even been worked out yet. The new model will not be compatible with the old, but if your stuff is in the source tree whoever winds up doing the major porting work will port it along with everything else. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Proposing argv for klds and preloaded modules
On Tue, 3 Aug 1999, Peter Wemm wrote: Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, one device (codadev) and one vfs (coda). Yes, the naming 'module_get_file_argstr()' had the _file_ for just this reason, filewide argument string. I didn't know any plans were already made on these circles, had only buggered Mr. Rabson once about arguments. Well, no harm done, I hope. Juha To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
NSS Project
Following on the NSS (Name Service Switch):
*Step One: I ported the NetBSD implementation of nsdispatch(3) as implemented
by Luke Mewburn. See attached patch to libc and new header file. I'm also
attaching the man page for /etc/nsswitch.conf. Right now it compiles,
installs, and works for some simple tests I've run.
*Step Two: make getpwent, getgrent, and friends actually use the nsdispatch
function. I've already started looking at the source, but am having trouble
with the NIS part. Maybe someone more knowledgeable could write the NIS
function.
Basically we have to reduce each of the functions to a simple nsdispatch
call and then implement the real functions... Here's an example from
getpwent.c
/* Basically we reduce getpwent to a simple nsdispatch call */
struct passwd *
getpwent()
{
int r;
static const ns_dtab dtab[] = {
NS_FILES_CB(_local_getpw, NULL)
NS_DNS_CB(_dns_getpw, NULL)
NS_NIS_CB(_nis_getpw, NULL)
NS_COMPAT_CB(_compat_getpwent, NULL)
{ 0 }
};
r = nsdispatch(NULL, dtab, NSDB_PASSWD, getpwent, compatsrc,
_PW_KEYBYNUM);
if (r != NS_SUCCESS)
return (struct passwd *)NULL;
return _pw_passwd;
}
The we have to implement _local_getpw, _dns_getpw, _nis_getpw,
and _compat_getpwent and make them behave as expected.
NetBSD seems to support having the passwd database on DNS using something
called HESIOD (I hadn't heard about it before). I don't think FreeBSD has
any sort of support for this.
*Step Three: Implement _ldap_getpw :)
If anyone has any comments, suggestions, etc. I would appreciate it.
Regards,
-Oscar
--
For PGP Public Key: finger oboni...@fisicc-ufm.edu
.\ $NetBSD: nsswitch.conf.5,v 1.14 1999/03/17 20:19:47 garbled Exp $
.\
.\ Copyright (c) 1997, 1998, 1999 The NetBSD Foundation, Inc.
.\ All rights reserved.
.\
.\ This code is derived from software contributed to The NetBSD Foundation
.\ by Luke Mewburn.
.\
.\ Redistribution and use in source and binary forms, with or without
.\ modification, are permitted provided that the following conditions
.\ are met:
.\ 1. Redistributions of source code must retain the above copyright
.\ notice, this list of conditions and the following disclaimer.
.\ 2. Redistributions in binary form must reproduce the above copyright
.\ notice, this list of conditions and the following disclaimer in the
.\ documentation and/or other materials provided with the distribution.
.\ 3. All advertising materials mentioning features or use of this software
.\ must display the following acknowledgement:
.\ This product includes software developed by Luke Mewburn.
.\ 4. The name of the author may not be used to endorse or promote products
.\ derived from this software without specific prior written permission.
.\
.\ THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
.\ IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
.\ OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
.\ IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
.\ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
.\ BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
.\ OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
.\ ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
.\ TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
.\ USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\
.Dd January 22, 1998
.Dt NSSWITCH.CONF 5
.Os
.Sh NAME
.Nm nsswitch.conf
.Nd name-service switch configuration file
.Sh DESCRIPTION
The
.Nm
file specifies how the
.Xr nsdispatch 3
(name-service switch dispatcher) routines in the C library should operate.
.Pp
The configuration file controls how a process looks up various databases
containing information regarding hosts, users (passwords), groups,
netgroups, etc.
Each database comes from a source (such as local files, DNS, and
.Tn NIS ) ,
and the order to look up the sources is specified in
.Nm nsswitch.conf .
.Pp
Each entry in
.Nm
consists of a database name, and a space separated list of sources.
Each source can have an optional trailing criterion that determines
whether the next listed source is used, or the search terminates at
the current source.
Each criterion consists of one or more status codes, and actions to
take if that status code occurs.
.Ss Sources
The following sources are implemented:
.Bl -column compat -offset indent -compact
.Sy Source Description
.It files Local files, such as
.Pa /etc/hosts ,
and
.Pa /etc/passwd .
.It dns Internet Domain Name System.
.Dq hosts
and
.Sq networks
use
.Sy IN
class entries, all other databases use
.Sy HS
class (Hesiod) entries.
.It nis NIS (formerly YP)
.It compat support
.Sq +/-
in the
.Dq passwd
and
.Dq group
Re: Multiple versions of FreeBSD on one HDD
Cillian Sharkey wrote: This works, but has the restriction that I have to enter a command line at the boot prompt to boot one of the two. I would much prefer partitions, as I can use a boot selector instead, and also change the default as appropriate. If you do have the installations in two seperate slices on the one disk, you should be able to use a boot selector to boot which ever slice you want. Boot selector programs like os-bs work with partitions, not disk slices. That's why I wanted separate partitions. At the moment I have os-bs installed but it will only get me as far as a BSD boot. I then have to quickly hit a key and enter: 0:wd(0,c)/kernel to boot 2.2.8 (3.2 will boot by default). I have only a couple of seconds to hit a key to get this right, and no way (that I know of) to change the default. So it works, but not like I'd like it to. -- Dr Graham WheelerE-mail: g...@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
If you do have the installations in two seperate slices on the one disk, you should be able to use a boot selector to boot which ever slice you want. Boot selector programs like os-bs work with partitions, not disk slices. That's why I wanted separate partitions. At the moment I have os-bs installed but it will only get me as far as a BSD boot. I then have to quickly hit a key and enter: 0:wd(0,c)/kernel to boot 2.2.8 (3.2 will boot by default). Ah yes, I see the problem now. Even if you have two seperate slices say wd0s1 and wd0s2 and boot into your selected one via os-bs, the boot prompt on either will always be 0:wd(0,a)/kernel ..and wd0a always points to the first BSD slice found on the disk. (in this case wd0s1 which is either 2.2.8 or 3.2 depending on where you installed them). I think the FreeBSD boot loader might need the option of specifying which *slice* to boot from rather than just which disk (0,1,2 etc.) and partition (a,b,c,d etc.) for the moment I think you'll just have to type in the line above every time you need to boot into 2.2.8 (or get another HD but that was the problem we've been trying to solve :) Anybody else out there have suggestions ? - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
This works, but has the restriction that I have to enter a command line at the boot prompt to boot one of the two. I would much prefer partitions, as I can use a boot selector instead, and also change the default as appropriate. If you do have the installations in two seperate slices on the one disk, you should be able to use a boot selector to boot which ever slice you want. Just to elaborate on this: The new boot code is specifically designed to handle the separate slices case. Where multiple FreeBSD slices are found, it will prefer the one marked active; the old boot code always chose the first slice. For this to work optimally, it's best to replace your 2.2 boot blocks with ones from 3.2 (or otherwise ensure the 2.2 system occupies the first FreeBSD slice). You also need to use a boot manager which sets the active flag of the selected slice. I don't know if this will work with booteasy the boot manager that comes with FreeBSD by default, but there is a nice boot manager called OS Select (tools/os-bs.exe in the FreeBSD distribution I think). Both booteasy and boot0 (distributed in place of booteasy from 3.1R) work as well. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD voice synthesis
Julian Elischer wrote: Just fetched and compiled the festival package. http://www.cstr.ed.ac.uk/projects/festival it has support for FreeBSD already (seems to work fine) Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word FreeBSD when I asked it to say (from the manual) Try Free B S D. Tricks like that used to work well with the simple ones available for home computers decades ago. (Anyone else here ever use SAM the Software Automated Mouth for the Atari 800 or Commodore 64?) -- Where am I, and what am I doing in this handbasket? Wes Peters Softweyr LLC http://softweyr.com/ w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: NSS Project
On Tue, 3 Aug 1999, Oscar Bonilla wrote:
Following on the NSS (Name Service Switch):
*Step One: I ported the NetBSD implementation of nsdispatch(3) as
implemented
by Luke Mewburn. See attached patch to libc and new header file. I'm also
attaching the man page for /etc/nsswitch.conf. Right now it compiles,
installs, and works for some simple tests I've run.
Great. I haven't alnalyse all of the code but this thing looks
a little bit limited:
/* Basically we reduce getpwent to a simple nsdispatch call */
struct passwd *
getpwent()
{
int r;
static const ns_dtab dtab[] = {
NS_FILES_CB(_local_getpw, NULL)
NS_DNS_CB(_dns_getpw, NULL)
NS_NIS_CB(_nis_getpw, NULL)
NS_COMPAT_CB(_compat_getpwent, NULL)
{ 0 }
};
May be I'm totally wrong, but dtab[] array can be constructed (or
extended) dynamically, based on configuration file and _*_getpw()
functions can be placed in shared libraries (just like PAM modules). In
this case it is possible to extend NSS space without disturbing libc code.
--
Boris Popov
http://www.butya.kz/~bp/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Overloading my machine?
:Hi there, : :I want to put on my machine the following HW (I'll be running :FBSD-3.2) beside the usual HW (serial and parallel ports etc.): : : - three IDE disks : - floppy : - IDE CD-ROM : - three ep NIC : - Adaptec PCI bus SCSI adapter : :Now, this is not a lot of burden (I think) for the processor, but I'm :a bit afraid about the architecture. Will this work? In particular, :I'm worried about the interrupts. Any suggestions how to configure :them? : :Thanx in advance for your assistance! : :LPA : :PS: Here is dmesg for the current FBSD which doesn't have SCSI adapter :installed. : :FreeBSD 2.2.8-STABLE #0: Wed Jan 20 13:08:03 MET 1999 :r...@irena.iskrasistemi.si:/usr/ports/FreeBSD-src/sys/compile/IRENA :CPU: Pentium/P54C (166.19-MHz 586-class CPU) :... Well, the burden will not come from the devices but instead will come from the load you place on them. So, the real question should be: how do you intend to use the machine? The only hardware recommendation I can make would be to watch out re: the IDE disks. You may not be able to use DMA on all of them and that will really take the cpu out for lunch. SCSI is the better choice there if you intend to load the disks down. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Proposing argv for klds and preloaded modules
Juha Nurmela wrote: On Tue, 3 Aug 1999, Daniel C. Sobral wrote: Actually... Loader passes a string. It seems the kldcode is passing argv[]. Juha, you sure you have they both working the same way (from a module's perspective)? It's splatted together, by just putting ' ' between words, somewhere in there. Search for strbuf Juha Don't forget, there are zero or more modules per file. Which one gets the arguments? Coda (for example) is structured so that it has two modules, one device (codadev) and one vfs (coda). This is why Warner's X-resource-like proposal is the only method for passing parameters to modules that I am likely to accept. argv/argc and getopt() are just not good enough. If someone want to implement a simple resource matcher, you could start by coming up with a tiny, tidy glob() for the kernel. We can use it elsewhere as well... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msm...@freebsd.org \\-- Joseph Merrick \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
At 12:55 PM +0200 8/3/99, Graham Wheeler wrote: Hi all I am trying to install both 2.2.8 and 3.2 on a single 17Gb HDD, but am not having much luck. I am also interested in doing things like this, and my initial attempts didn't work quite the way I had hoped. Earlier I had a dual-boot setup with WinNT and FreeBSD 2.2.5, using the booteasy loader. I managed to get that going easily enough, even though I didn't have any clue about what I was doing, so after I replaced the HD (for unrelated reasons) I thought I'd get more ambitious. So, armed with a brand new hard 4-gig SCSI disk, I installed WinNT, and had it create several partitions which I expected to use for other OS's. This install went fine. I then went to install FreeBSD 2.2.8, only to realize that all the partitions WinNT created were extended partitions in one real partition. So, I used the fdisk-part of the install to blow away those partitions and create three new partitions. I installed 2.2.8 in one of those, but told it that I wanted nothing done for a boot loader (because I planned to install PowerBoot, but I didn't have those disks yet). If I booted off the CD-ROM, I could then switch to this 2.2.8 install and it worked fine. The thing is, I couldn't boot up off the hard disk anymore. Apparently something in the freebsd install resulted in an invalid partition table. I assumed this was because I had fdisk-ed the second partition that winNT had created into three partitions, so I went and reinstalled WinNT in the first partition. At that point I could boot either system (using the CD when I wanted to boot off the freebsd system). I then installed Freebsd 3.2-stable in the third partition. Since I didn't need to fdisk anything, and I said I didn't want to install any boot-loader, I figured this would be safe. Again, I ended up with an unbootable HD. I could boot either freebsd system by first booting off a CD. By now the floppies for PowerBoot had come, so I tried installing that. I could now boot the HD, and PowerBoot can see the two partitions with freebsd installed (it even recognizes them as freebsd). Right now, my situation is that: - If I select WinNT at the PowerBoot menu, it comes up fine. Everything looks about as I'd expect. - If I select 2.2.8 at the PowerBoot menu, it comes up with one error message about no /boot/loader, but then it comes right up in the 2.2.8 system. So this works fine, although it looks odd. - If I select 3.2 at the PowerBoot menu, it comes up with two messages about invalid partition, one about no boot loader, and then it can't automatically boot up anything. The interesting thing is that I'm in the 2.2.8 bootloader at this point, not the 3.2 one. It seems to want to boot 'da(0,a)/kernel', but if I type in 'da(0,e)/kernel', then it boots up fine. My last partition is meant for installing OpenBSD, but I wasn't ready to do that yet. Later I was talking with one of the other guys here, and I went to show him what I did by trying to do another freebsd install into that 4th partition. Much to my surprise, it won't *let* me install into that partition. (note that I wanted to try PowerBoot because I also have a second hard disk, and I want to install Win98 on that one, along with BeOS and maybe some other OS's. It seemed to me that multi-disk situations could use something more than booteasy). So, my guess is that my primary problem is that I have only a vague idea of what I'm doing... Where is a good point to start looking for a better idea? I tried searching the web site for multi-boot, but that didn't turn up much. I have a number of questions from doing this: 1. why does the install turn my HD unbootable? (invalid partition table). I didn't ask it to re-fdisk anything, and I didn't ask for it to change my boot loader. 2. I have the BIOS option on so I can boot off larger hard disks, and indeed it seems I can boot to the first three partitions. Why can't I get to that final one? 3. Can I get it so that booting off the third partition will smoothly boot into 3.2-stable? 4. given the rapidly-expanding size of HD's, would it be useful to support installs into DOS-style extended partitions? Or are they a problem which we're better off to avoid? --- Garance Alistair Drosehn = g...@eclipse.acs.rpi.edu Senior Systems Programmer or dro...@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Berkeley IRS and NSS
Anyone knows about the BSD Information Retrieval Service (IRS) mentioned in http://www.padl.com/nss_ldap.html ? It seems to accomplish the same thing as the NSS stuff we've been talking about. Regards, -Oscar -- For PGP Public Key: finger oboni...@fisicc-ufm.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: no elf(5) man page (docs/7914)
* Wes Peters (w...@softweyr.com) [990803 10:13]: Jeroen Ruigrok/Asmodai wrote: * Andy Doran (a...@netbsd.org) [990802 00:53]: Wes Peters writes: NetBSD doesn't have one as of 1.4, so they may be interested in yours. ;^) It'd be cool if Asmodai could bounce this around one of the NetBSD lists once it's near completion. tech-toolchain@ or tech-userlevel@ would be the right place I guess. I already saw some differences in the stucture member names though, so ye will need to adjust those. Ain't cooperation great? ;^) Now if our OpenBSD friend will provide us with a mailing list or doc reviewer there, we can kill THREE birds with one stone. I know a committer there =) I have cc:'d him and hope he likes the idea as well. [hey Art ;)] OpenBSD, and pardon if saying it wrongly here, took the definitions from elf_common.h, so that's at least consistent. NetBSD defines some macros with other values =\ There goes some compatibility. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
At 1:24 PM -0400 8/3/99, i (Garance A Drosihn) wrote: So, my guess is that my primary problem is that I have only a vague idea of what I'm doing... Where is a good point to start looking for a better idea? I tried searching the web site for multi-boot, but that didn't turn up much. I have a number of questions from doing this: 1. why does the install turn my HD unbootable? (invalid partition table). I didn't ask it to re-fdisk anything, and I didn't ask for it to change my boot loader. 2. I have the BIOS option on so I can boot off larger hard disks, and indeed it seems I can boot to the first three partitions. Why can't I get to that final partition? 3. Can I get it so that booting off the third partition will smoothly boot into 3.2-stable? I should mention that what I have on the disk right now (with the three systems) isn't too critical, so it is alright if I have to start over and reinstall everything. On the other hand, reinstalling does get a little tiring after awhile, so I want to have a better idea of what I'm doing before I take another stab at this, to minimize the number of reinstalls that I wind up doing. I should also mention that while I do have a second 4-gig scsi disk to use, it isn't actually installed yet. Also, I did intend to have a freebsd 4-current system as part of this multi-boot mix. I don't think I mentioned that last time. Perhaps I should create one fdisk-style partition per hard disk, and put all freebsd-related slices (for all the different freebsd installs) into that one partition? Would that make things go smoother? (particularly if I put all the boot-related slices at the start of that fdisk-style partition) --- Garance Alistair Drosehn = g...@eclipse.acs.rpi.edu Senior Systems Programmer or dro...@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Overloading my machine?
Andrej Brodnik (Andy) schrieb: Hi there, I want to put on my machine the following HW (I'll be running FBSD-3.2) beside the usual HW (serial and parallel ports etc.): - three IDE disks - floppy - IDE CD-ROM - three ep NIC - Adaptec PCI bus SCSI adapter Now, this is not a lot of burden (I think) for the processor, but I'm a bit afraid about the architecture. Will this work? In particular, I'm worried about the interrupts. Any suggestions how to configure them? The ISA NIC's would made me worry. An ISA Ethernet NIC with a rate of ~ 1 MB/s utilizes the CPU up to 50-70% (regardless of the CPU speed). On practictal tests the ISA bus maxes out at around 3MB/s at 100 % CPU load (unless the ISA device does DMA) For more than average network traffic, I'd put some cheap PCI NICs in. You should have at least 2 PCI slots free. Unless you are using this machine also as a workstation, you could throw out the PCI VGA adapter and just use a plain old ISA one, so you will gain another PCI slot. Daniel To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
By now the floppies for PowerBoot had come, so I tried installing that. I could now boot the HD, and PowerBoot can see the two partitions with freebsd installed (it even recognizes them as freebsd). Right now, my situation is that: - If I select WinNT at the PowerBoot menu, it comes up fine. Everything looks about as I'd expect. - If I select 2.2.8 at the PowerBoot menu, it comes up with one error message about no /boot/loader, but then it comes right up in the 2.2.8 system. So this works fine, although it looks odd. You're using the new boot blocks for 2.2.8, and these always try to pass control to loader(8). To get rid of the message, create a /boot.config file with the line /kernel in it. - If I select 3.2 at the PowerBoot menu, it comes up with two messages about invalid partition, one about no boot loader, and then it can't automatically boot up anything. The interesting thing is that I'm in the 2.2.8 bootloader at this point, not the 3.2 one. It seems to want to boot 'da(0,a)/kernel', but if I type in 'da(0,e)/kernel', then it boots up fine. The problem here is a missing `a' partition. Seems like your first partition on that slice is `e'. There's a one-line patch to boot2 to get this working, but the standard version only autoboots from the `a' partition. My last partition is meant for installing OpenBSD, but I wasn't ready to do that yet. Later I was talking with one of the other guys here, and I went to show him what I did by trying to do another freebsd install into that 4th partition. Much to my surprise, it won't *let* me install into that partition. It's usually best to temporarily change fdisk partition types, so that sysinstall sees no existing FreeBSD slice on the drive. However, there may be other problems involved here as well. (note that I wanted to try PowerBoot because I also have a second hard disk, and I want to install Win98 on that one, along with BeOS and maybe some other OS's. It seemed to me that multi-disk situations could use something more than booteasy). Actually booteasy can handle two drives, and boot0 (which replaced booteasy in 3.1R) can handle more than that. However, the OSes on the higher drives must be capable of booting from the non-default drive. Most can do that -- even UnixWare -- though not Windows, which ignores the drive number passed in to it. So, for Windows, something that swaps drive letters is more suitable. So, my guess is that my primary problem is that I have only a vague idea of what I'm doing... Where is a good point to start looking for a better idea? I tried searching the web site for multi-boot, but that didn't turn up much. I have a number of questions from doing this: 1. why does the install turn my HD unbootable? (invalid partition table). I didn't ask it to re-fdisk anything, and I didn't ask for it to change my boot loader. There are a number of possibilities, but one would have to look at a copy of the broken MBR to be sure. (The most usual reason for an invalid partition table message is multiple partitions flagged as active, or partitions that use the new-style active flag that is supported from Win95. This can be sorted out by booting from floppy or CD-ROM and using fdisk.) 2. I have the BIOS option on so I can boot off larger hard disks, and indeed it seems I can boot to the first three partitions. Why can't I get to that final one? You need to enable something more than the BIOS option. For instance, for FreeBSD, you need to enable LBA support in the boot blocks by means of a build option, and use boot0cfg(8) to turn on packet support in boot0. 3. Can I get it so that booting off the third partition will smoothly boot into 3.2-stable? Either patch boot2 or change to using an `a' partition. 4. given the rapidly-expanding size of HD's, would it be useful to support installs into DOS-style extended partitions? Or are they a problem which we're better off to avoid? I think support for extended partitions is inevitable (it's now the RedHat default), whether it really is a good idea or not. Technically, it violates the IBM specification that deals with fdisk partitions, though I'm not sure that matters very much. It will break some older OS/2 device drivers, for instance, though. -- Robert Nordier 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 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 Tue, 3 Aug 1999, Nik Clayton wrote: 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. LyX can generate good LaTeX code, actually... But in all seriousness, I'd really LOVE to use LaTeX instead of .roff and and all the mdoc macros. I like LaTeX as a format much better than any of the alternatives. That and SGML... 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 Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Multiple versions of FreeBSD on one HDD
I should mention that what I have on the disk right now (with
the three systems) isn't too critical, so it is alright if I
have to start over and reinstall everything. On the other
hand, reinstalling does get a little tiring after awhile, so
I want to have a better idea of what I'm doing before I take
another stab at this, to minimize the number of reinstalls
that I wind up doing.
I should also mention that while I do have a second 4-gig scsi
disk to use, it isn't actually installed yet.
Also, I did intend to have a freebsd 4-current system as part
of this multi-boot mix. I don't think I mentioned that last
time. Perhaps I should create one fdisk-style partition per
hard disk, and put all freebsd-related slices (for all the
different freebsd installs) into that one partition? Would
that make things go smoother? (particularly if I put all the
boot-related slices at the start of that fdisk-style partition)
Using BSD terminology, slice == fdisk partition, and partitions
('a', 'e', etc.) are just partitions. Though, IIRC, SVR5 uses
the terms the other way round.
I'd suggest you install one system per fdisk partition. I had a
system set up with 2.0R, 2.1R, 2.2R and 3-current (as was) in
separate slices, when testing the new boot code.
Some people do prefer the multiple systems per slice approach,
though, which is all that used to be supported. So either can
be made to work.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
