Re: So, back on the topic of enabling bpf in GENERIC...

[Mark Murray]

> This is a clear security vs functionality issue and I need to get a
> good feel for which "cause" is ascendent here in knowing which way to
> jump on the matter.  Can we now hear the closing arguments from the
> pro and con folks?

I am pro.

It takes a root compromise to use it anyway, and its usefulness
for DHCP and rarpd is too compelling.

Perhaps the comments in the GENERIC file could be updated.

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: So, back on the topic of enabling bpf in GENERIC...

[Jordan K. Hubbard]

> I am pro.
> 
> It takes a root compromise to use it anyway, and its usefulness
> for DHCP and rarpd is too compelling.
> 
> Perhaps the comments in the GENERIC file could be updated.

Well, given that I've gotten primarily positive support for this I
guess it's time to do it.  Warner, do you want to commit a securelevel
hack before I throw the switch in GENERIC?

- Jordan


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Brian F. Feldman]

On Tue, 3 Aug 1999, Mike Smith wrote:

> > 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...

Actually, the structure shouldn't change size because it should be
using a sockaddr.

> 
> -- 
> \\  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
> 

 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: Jail syscalls

[Doug Rabson]

On Wed, 4 Aug 1999, Brian F. Feldman wrote:

> On Tue, 3 Aug 1999, Mike Smith wrote:
> 
> > > 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...
> 
> Actually, the structure shouldn't change size because it should be
> using a sockaddr.

The argument for versioning is not simply because the size of ip_number
might change (it should be a sockaddr) but because other fields might be
added or removed. To avoid allocating a new syscall whenever this happens,
the structure should be versioned.

Putting sizeof(whatever) at the beginning of the structure works
surprisingly well as a versioning system.

--
Doug Rabson Mail:  d...@nlsystems.com
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

[Fwd: Please support FreeBSD 3.x as host OS]

[Niall Smart]

Olivia Cheriton wrote:
> 
> Niall,
> 
> VMware will support FreeBSD as a guest operating system, but unfortunately
> we currently do not have plans to support FreeBSD as a host operating
> system.  I have noted your request of FreeBSD host support in case we review
> this in the future.
> 
> Best regards,
> 
> Olivia Cheriton
> VMware, Inc.
> 
> - Original Message -
> From: Niall Smart 
> To: 
> Cc: 
> Sent: Saturday, July 24, 1999 11:09 AM
> Subject: Please support FreeBSD 3.x as host OS
> 
> > Hi.
> >
> > I'd like to see FreeBSD 3.x supported as a host OS, I'll
> > certainly be buying a copy of VMware if this happens.
> >
> > Regards,
> >
> > Niall Smart
> > Senior Software Developer
> > Trinity Commerce


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 ?

[Vince Vielhaber]

On Wed, 4 Aug 1999, Biju Susmer wrote:

> 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?

You have the CD connected as the secondary slave and no secondary master.
That's the problem.  It's an illegal configuration as the IDE controller
is actually on the drive itself.  Move the jumper on the CD to master and
it'll be recognized.

Vince.
-- 
==
Vince Vielhaber -- KA8CSH   email: v...@michvhf.com   flame-mail: /dev/null
   # includeTEAM-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

Re: BSD voice synthesis

[Ville-Pertti Keinonen]

w...@softweyr.com (Wes Peters) writes:

> available for "home" computers decades ago.  (Anyone else here ever use
> SAM "the Software Automated Mouth" for the Atari 800 or Commodore 64?)

Yes.

It's almost surprising how little speech synthesis has improved, at
least judging from the festival demos (it is, of course, better than
SAM, but apparently the data and processing requirements are several
orders of magnitude greater).  I haven't downloaded all of the
required stuff, yet, so I don't know how good or bad it actually might
be.

I certainly don't expect any of the available voices to be able to
pronounce Finnish names correctly, even with phonetic specifications.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Solution for mail pseudo-users?

[Markus Stumpf]

On Tue, Aug 03, 1999 at 02:22:17PM -0700, Alex Zepeda wrote:
> > 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. 

With your setup that would hold, too.
But with my setup the effective user doesn't have to be root, so if there
is an exploit the intruder doesn't gain root privileges the first place
and it reduces the possibilities that e.g. the whole subnet is compromised
by sniffing or the like.

> > 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. 

A e.g. database isn't a flat text file. Nobody said that one should use a
linear search on a flat text file. You're free to plug in whatever
backend you want (Berkley DB, SQL database, cdb, ...), but you don't
have to rebuild the whole database, but just the record modified.

Queuing changes is IMHO not an option.
When a user changes his password, he want it to be effective
immediately, not after 5, 10, 15 oder 30 minutes.

\Maex

-- 
SpaceNet GmbH |   http://www.Space.Net/   | Yeah, yo mama dresses
Research & Development| mailto:maex-...@space.net | you funny and you need
Joseph-Dollinger-Bogen 14 |  Tel: +49 (89) 32356-0| a mouse to delete files
D-80807 Muenchen  |  Fax: +49 (89) 32356-299  |


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Onstream?

[Vince Vielhaber]

Out of curiousity, have there been any successes in the drivers for
the OnStream tape drives (SCSI or IDE)?

Vince.
-- 
==
Vince Vielhaber -- KA8CSH   email: v...@michvhf.com   flame-mail: /dev/null
   # includeTEAM-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

Re: Onstream?

[Soren Schmidt]

It seems Vince Vielhaber wrote:
> 
> Out of curiousity, have there been any successes in the drivers for
> the OnStream tape drives (SCSI or IDE)?

Working on it (for IDE that is), support is planned for, but I have
no release date yet... I know that there is work done on the SCSI
end too...


-Søren


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

[Mike Pritchard]

> At 8:01 PM +0200 8/3/99, Robert Nordier wrote:
> 
> > > - If I select 3.2 at the PowerBoot menu, it comes up
> > >   with two messages about "invalid partition", [...]
> > >   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.

I have my main machine setup to boot 3 different operating systems all
on one harddisk.  My disk is paritioned into 4 fdisk partitions, as follows:

1:  Win98 (ugh, but I need to have it to play games :-) (bootable)
2:  extended dos partition (non-bootable)
3:  FreeBSD 3.2-stable (bootable)
4:  FreeBSD 4.0 -current (bootable)

Here is my file system layout when running 4.0:

/dev/wd0s4a on / (local, soft-updates, writes: sync 16 async 14249)
/dev/wd0s3a on /root32 (local, writes: sync 2 async 44)
/dev/wd0s3e on /root32/usr (local, writes: sync 2 async 7099)
/dev/wd0s4f on /usr (local, soft-updates, writes: sync 2 async 8148)
/dev/wd0s4h on /shared (local, soft-updates, writes: sync 1963 async 263656)
/dev/wd0s3f on /root32/var (local, writes: sync 2 async 40)
/dev/wd0s4g on /var (local, soft-updates, writes: sync 4604 async 69441)
(along with a wd0s4b swap partition, which is shared between both
FreeBSD versions)

When I first tried this, I couldn't boot the 4.0 version because 
the 4.0 root device was named wd0s4e by my initial 3.2 sysinstall.  I had 
to run disklabel and change the partition name to wd0s4a.  After doing 
that, both versions would boot no problem.  I just hit F3 for 3.2-stable, 
or F4 for 4.0-current.

All of my boot blocks were orignally written out with 3.2-stable,
but I've since re-written them with 4.0-current boot blocks.

-Mike
-- 
Mike Pritchard
m...@freebsd.org or m...@mpp.pro-ns.net


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSD voice synthesis

[Dag-Erling Smorgrav]

Ville-Pertti Keinonen  writes:
> I certainly don't expect any of the available voices to be able to
> pronounce Finnish names correctly, even with phonetic specifications.

If the software were *designed* to speak Finnish, I'd expect it to
cope with Finnish much better than it currently does with English,
seeing as you guys have nearly phonetic spelling.

DES
-- 
Dag-Erling Smorgrav - d...@flood.ping.uio.no


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Assar Westerlund]

"Brian F. Feldman"  writes:
> On Tue, 3 Aug 1999, Mike Smith wrote:
> > 
> > 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...
> 
> Actually, the structure shouldn't change size because it should be
> using a sockaddr.

No, because sizeof(struct sockaddr) < sizeof(struct sockaddr_in6).
This is kind of bad but that's the way it is.  It would make sense to
use a `struct sockaddr_storage' but I still think it's worthwhile and
better to have a version number.

/assar


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Results of investigating optimizing calloc()...

[Dag-Erling Smorgrav]

"Kelly Yancey"  writes:
> [...]

Which reminds me - has anyone thought of using DMA for zeroing pages,
to avoid cache invalidation? The idea is to keep a chunk of zeroes on
disk and DMA it into memory instead of clearing pages "manually". This
assumes your disk supports DMA, of course.

DES
-- 
Dag-Erling Smorgrav - d...@flood.ping.uio.no


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Tekram DC-390U2W support (80Mb/sec operation)

[Kevin]

Hey all, I purchased a Tekram DC-390U2W scsi controller to use with a
FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) chipset(s). I
see that ncr.c supports the NCR 53c8xx family of chipsets..
which the controller is seen as having a 53c895, which only supports
40Mb/sec operation(?)


 {NCR_895_ID, 0x00, "ncr 53c895 fast40 wide scsi",  7, 31, 7,
 FE_WIDE|FE_ULTRA2|FE_QUAD|FE_CACHE_SET|FE_DFS|FE_LDSTR|FE_PFEN|FE_RAM}


I am assuming that it only supports 40Mb/sec operation.. could someone
prove me wrong? I just want to get 80Mb/sec operation (would I need to have
support for the 53c141 driver? are there any out there, is it in the
works?). Tekram has FreeBSD drivers on their site but they say it is
supported in 3.0, I can't find anything newer. They are working on a new
one.. They already have support for the DC-390U2W on various Linux's of
course :(

Could anyone *please* enlighten me? I would be grateful.

Please reply to my email address, as I am not subsribed to these lists.

Thanks a lot,

Kevin



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: NSS Project

[Alfred Perlstein]

On Wed, 4 Aug 1999, Peter Jeremy wrote:

> Oscar Bonilla  wrote:
> >If anyone has any comments, suggestions, etc. I would appreciate it.
> 
> Overall, I like the idea of NSS.  But, having worked on Solaris 2.x
> for some time, we need to avoid some of the blunders Sun made: The
> biggest problem with Sun's NSS implementation is that it's no longer
> possible to statically link an application that uses any of the
> get...byname() functions that have NSS backends.
> 
> We need to be able to build an application that has no dynamically
> loaded code for recovery purposes (/stand and /sbin) as well as for
> security.

well you could just link in the shared nss object statically into
it...?

-Alfred



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSD voice synthesis

[Ville-Pertti Keinonen]

d...@flood.ping.uio.no (Dag-Erling Smorgrav) writes:

> Ville-Pertti Keinonen  writes:
> > I certainly don't expect any of the available voices to be able to
> > pronounce Finnish names correctly, even with phonetic specifications.

> If the software were *designed* to speak Finnish, I'd expect it to
> cope with Finnish much better than it currently does with English,
> seeing as you guys have nearly phonetic spelling.

Festival is basically language-independent, each voice is associated
with a specific language, so with a Finnish voice it should be able to
pronounce Finnish reasonably.

Since the English voices have dictionaries for pronunciation, anyhow,
a Finnish voice wouldn't necessarily do a better job in terms of
pronunciation, although a Finnish voice should require fewer distinct
phonemes.

Creating voices does seem to involve quite a bit of work, though.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Alfred Perlstein]

On Wed, 4 Aug 1999, Niall Smart wrote:

> Olivia Cheriton wrote:
> > 
> > Niall,
> > 
> > VMware will support FreeBSD as a guest operating system, but unfortunately
> > we currently do not have plans to support FreeBSD as a host operating
> > system.  I have noted your request of FreeBSD host support in case we review
> > this in the future.
> > 
> > Best regards,
> > 
> > Olivia Cheriton
> > VMware, Inc.
> > 
> > - Original Message -
> > From: Niall Smart 
> > To: 
> > Cc: 
> > Sent: Saturday, July 24, 1999 11:09 AM
> > Subject: Please support FreeBSD 3.x as host OS
> > 
> > > Hi.
> > >
> > > I'd like to see FreeBSD 3.x supported as a host OS, I'll
> > > certainly be buying a copy of VMware if this happens.
> > >

I heard they have released the source to the kernel modules needed
to run it.

why not port them over? :)

-Alfred




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Tekram DC-390U2W support (80Mb/sec operation)

[Stuart Henderson]

> Hey all, I purchased a Tekram DC-390U2W scsi controller to use with 
> a FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) 
> chipset(s). I see that ncr.c supports the NCR 53c8xx family of 
> chipsets.. which the controller is seen as having a 53c895, which 
> only supports 40Mb/sec operation(?)

http://www.freebsd.org/cgi/search.cgi?words=53c895+80mbps&max=25&sort=score&source=freebsd-scsi


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

RE: Tekram DC-390U2W support (80Mb/sec operation)

[Nigel Roles]

The 53c141 is an auto-sensing single-ended/LVDS terminator, permitting
you to connect single-ended and LVDS drives to the same cable. It is
transparent.

If you want 80mbps you need

1. a wide LVDS (aka Ultra2 or fast40) drive
2. a wide LVDS terminator

The 40 in the portion of ncr.c you quote is MHz not megabytes. By having a
wide
(16 bit) drive (and bus) you get 16bits * 40MHz or 80mbps. 

What makes you think you haven't got 80mbps? How would you tell?

-Original Message-
From: Kevin [mailto:kb...@primenet.com]
Sent: Wednesday, August 04, 1999 12:42 PM
To: freebsd-hackers@FreeBSD.ORG; freebsd-s...@freebsd.org
Subject: Tekram DC-390U2W support (80Mb/sec operation)


Hey all, I purchased a Tekram DC-390U2W scsi controller to use with a
FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) chipset(s). I
see that ncr.c supports the NCR 53c8xx family of chipsets..
which the controller is seen as having a 53c895, which only supports
40Mb/sec operation(?)


 {NCR_895_ID, 0x00, "ncr 53c895 fast40 wide scsi",  7, 31, 7,
 FE_WIDE|FE_ULTRA2|FE_QUAD|FE_CACHE_SET|FE_DFS|FE_LDSTR|FE_PFEN|FE_RAM}


I am assuming that it only supports 40Mb/sec operation.. could someone
prove me wrong? I just want to get 80Mb/sec operation (would I need to have
support for the 53c141 driver? are there any out there, is it in the
works?). Tekram has FreeBSD drivers on their site but they say it is
supported in 3.0, I can't find anything newer. They are working on a new
one.. They already have support for the DC-390U2W on various Linux's of
course :(

Could anyone *please* enlighten me? I would be grateful.

Please reply to my email address, as I am not subsribed to these lists.

Thanks a lot,

Kevin



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-scsi" 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

[Graham Wheeler]

Robert Nordier wrote:
> 
> 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.

Hmmm. This sounds a good plan. Would the following then work
(I'm using `partition' to refer to a fdisk partition, and `file
system' to refer to a BSD partition):

* I partition my drive into 4 equal partitions (rather than 2;
this gives me more future flexibility)

* I install 2.2.8 in the first partition.

* I change the type to something other than FreeBSD

* I install 3.2 into the second partition

* I change the type of the first partition back to FreeBSD

* I install os-bs or some other boot selector

* And now, hopefully, I can simply boot either from the boot
selector menu?


-- 
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

double vfs_object_create in open syscall?

[Alfred Perlstein]

Why does open() at "sys/kern/vfs_syscalls.c" line 1023 call
vfs_object_create() when vnopen() ("sys/kern/vfs_vnops.c" line 174)
already does so?

vfs_object_create checks for this and doesn't leak, but it looks
funny to me.

-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

Re: Tekram DC-390U2W support (80Mb/sec operation)

[Stuart Henderson]

> What makes you think you haven't got 80mbps? How would you tell?

Something like this in your dmesg/boot output.
da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing
Enabled


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Assar Westerlund]

Alfred Perlstein  writes:
> I heard they have released the source to the kernel modules needed
> to run it.
> 
> why not port them over? :)

I started looking at the kernel modules and porting them, however, I
must confess that I don't fully understand exactly what the linux
kernel module does, which makes it somewhat harder to implement the
same functionality on FreeBSD :-)

/assar


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

[Graham Wheeler]

Graham Wheeler wrote:
> 
> Robert Nordier wrote:
> >
> > 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.
> 
> Hmmm. This sounds a good plan. Would the following then work
> (I'm using `partition' to refer to a fdisk partition, and `file
> system' to refer to a BSD partition):
> 
> * I partition my drive into 4 equal partitions (rather than 2;
> this gives me more future flexibility)
> 
> * I install 2.2.8 in the first partition.
> 
> * I change the type to something other than FreeBSD
> 
> * I install 3.2 into the second partition
> 
> * I change the type of the first partition back to FreeBSD
> 
> * I install os-bs or some other boot selector
> 
> * And now, hopefully, I can simply boot either from the boot
> selector menu?

I tried this, and the installation went through fine. But after 
installing 3.2, I get a `Missing operating system' when I try to
boot the second partition (the first still has its type set to 
something other than FreeBSD, so it won't boot either).

Robert, you seem quite knowledgeable about all this, and seem to have
had considerable success. How do I get this right? I want to install
2.2.8 in one partition and 3.2 in another. If I don't change the 
fdisk partition type after installing 2.2.8, then sysinstall won't
allow me to install the second OS (it complains when I try to make the 
root BSD partition that the boot loader can't handle it). If I do
change the fdisk partition type first, the install is fine, but I can't
boot afterwards, as described above.

-- 
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: [Fwd: Please support FreeBSD 3.x as host OS]

[Soren Schmidt]

It seems Assar Westerlund wrote:
> Alfred Perlstein  writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> > 
> > why not port them over? :)
> 
> I started looking at the kernel modules and porting them, however, I
> must confess that I don't fully understand exactly what the linux
> kernel module does, which makes it somewhat harder to implement the
> same functionality on FreeBSD :-)

If you provide an URL to those files, I'd give them a look...

-Søren


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Alfred Perlstein]

On 4 Aug 1999, Assar Westerlund wrote:

> Alfred Perlstein  writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> > 
> > why not port them over? :)
> 
> I started looking at the kernel modules and porting them, however, I
> must confess that I don't fully understand exactly what the linux
> kernel module does, which makes it somewhat harder to implement the
> same functionality on FreeBSD :-)

a quick scan of the vmware site didn't reveal where the kernel
mods are.  are they available freely? can i have a url please?

-Alfred



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

[Robert Nordier]

> > > 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.
> > 
> > Hmmm. This sounds a good plan. Would the following then work
> > (I'm using `partition' to refer to a fdisk partition, and `file
> > system' to refer to a BSD partition):
> > 
> > * I partition my drive into 4 equal partitions (rather than 2;
> > this gives me more future flexibility)
> > 
> > * I install 2.2.8 in the first partition.
> > 
> > * I change the type to something other than FreeBSD
> > 
> > * I install 3.2 into the second partition
> > 
> > * I change the type of the first partition back to FreeBSD
> > 
> > * I install os-bs or some other boot selector
> > 
> > * And now, hopefully, I can simply boot either from the boot
> > selector menu?
> 
> I tried this, and the installation went through fine. But after 
> installing 3.2, I get a `Missing operating system' when I try to
> boot the second partition (the first still has its type set to 
> something other than FreeBSD, so it won't boot either).
> 
> Robert, you seem quite knowledgeable about all this, and seem to have
> had considerable success. How do I get this right? I want to install
> 2.2.8 in one partition and 3.2 in another. If I don't change the 
> fdisk partition type after installing 2.2.8, then sysinstall won't
> allow me to install the second OS (it complains when I try to make the 
> root BSD partition that the boot loader can't handle it). If I do
> change the fdisk partition type first, the install is fine, but I can't
> boot afterwards, as described above.

"Missing operating system" indicates that the first sector of the
OS bootstrap (boot1 in the FreeBSD case) isn't flagged bootable:
that is, it doesn't have the bytes 0x55 and 0xaa right at the end.

Almost invariably, the cause of this is a mismatch between the disk
geometry the BIOS is using, and what FreeBSD thought the geometry
was during the install.  (So the wrong sector is read by the MBR
code.)

The first partition is less sensitive to geometry mismatches than
the others, since it has a starting CHS value of 0,1,1.  That relies
only on "sectors per track" and not "number of heads".

Because most modern BIOSes do CHS translation, the BIOS geometry is
not always evident from the geometry reported by the drive, and
FreeBSD may get this wrong, particularly if no existing partitions
are defined.

Since you are installing to a drive with no pre-existing non-FreeBSD
partitions, I suspect sysinstall got the geometry wrong.  Probably
you should re-install and use the 'G' command in sysinstall's fdisk,
after determining what geometry the BIOS is actually using.

The best way to determine BIOS geometry in FreeBSD is to boot -v
(but it should be from the old "boot:" prompt, not from loader(8)
in 3.2R) and then check using dmesg(8) for "BIOS Geometries"
information.

-- 
Robert Nordier


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

fetch: default to passive mode?

[Chuck Youse]

I have a really strong urge to submit a PR to make fetch default to passive
mode, instead of requiring a command-line switch ...

In this day and age, with firewalls and NAT abound, it's a bit odd that such
a change has not already been made.  Am I missing something?  Is there a
reason we haven't done this yet?

Chuck Youse
Director of Engineering
CyberSites, Inc.





To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Milan Kopacka]

On Wed, 4 Aug 1999, Alfred Perlstein wrote:

> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
> 
> a quick scan of the vmware site didn't reveal where the kernel
> mods are.  are they available freely? can i have a url please?

Source code is included in the distribution. They have modules precompiled
only for certain versions of Linux kernel. You may have to compile them
yourself when you are running some other version. 

  Milan Kopacka

--
... a koho system nachyta na procesoru, tomu snizi prioritu.




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Alfred Perlstein]

On Wed, 4 Aug 1999, Milan Kopacka wrote:

> On Wed, 4 Aug 1999, Alfred Perlstein wrote:
> 
> > > I started looking at the kernel modules and porting them, however, I
> > > must confess that I don't fully understand exactly what the linux
> > > kernel module does, which makes it somewhat harder to implement the
> > > same functionality on FreeBSD :-)
> > 
> > a quick scan of the vmware site didn't reveal where the kernel
> > mods are.  are they available freely? can i have a url please?
> 
> Source code is included in the distribution. They have modules precompiled
> only for certain versions of Linux kernel. You may have to compile them
> yourself when you are running some other version. 

so one must purchase the program to get the kernel mods, is there
an evaluation that can be downloaded?

-Alfred



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Milan Kopacka]

On Wed, 4 Aug 1999, Alfred Perlstein wrote:

> so one must purchase the program to get the kernel mods, is there
> an evaluation that can be downloaded?

They have all described on website. The program is key-protected, you can
buy a key, or ask for evaluation key, which will work one month.

You need the key to run the virtual machine, archive unpacking and
installation can be done without the key.

  Milan Kopacka

--
... a koho system nachyta na procesoru, tomu snizi prioritu.



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

[Graham Wheeler]

Robert Nordier wrote:
> 
> Because most modern BIOSes do CHS translation, the BIOS geometry is
> not always evident from the geometry reported by the drive, and
> FreeBSD may get this wrong, particularly if no existing partitions
> are defined.
> 
> Since you are installing to a drive with no pre-existing non-FreeBSD
> partitions, I suspect sysinstall got the geometry wrong.  Probably
> you should re-install and use the 'G' command in sysinstall's fdisk,
> after determining what geometry the BIOS is actually using.
> 
> The best way to determine BIOS geometry in FreeBSD is to boot -v
> (but it should be from the old "boot:" prompt, not from loader(8)
> in 3.2R) and then check using dmesg(8) for "BIOS Geometries"
> information.

Hmmm - perhaps it isn't possible then to do what I want (without 
losing most of the drive). The drive is 17Gb, consisting of 
33416 cyls, 16 heads and 63 sectors. The BIOS reports 1023 cyls, 255
heads and 63 sectors - which is approximately 8Gb. This doesn't change
if I change the BIOS mode between normal, large or LBA, nor if I make
the disk type in the BIOS user defined and enter the real parameters
(the BIOS is an Award BIOS v4.51PG, probably from about 1996).

I assume that if I set the gemoetry in fdisk to be the BIOS figures,
that I will lose the other half of the disk?

-- 
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: Jail syscalls

[Brian F. Feldman]

On 4 Aug 1999, Assar Westerlund wrote:

> "Brian F. Feldman"  writes:
> > On Tue, 3 Aug 1999, Mike Smith wrote:
> > > 
> > > 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...
> > 
> > Actually, the structure shouldn't change size because it should be
> > using a sockaddr.
> 
> No, because sizeof(struct sockaddr) < sizeof(struct sockaddr_in6).
> This is kind of bad but that's the way it is.  It would make sense to
> use a `struct sockaddr_storage' but I still think it's worthwhile and
> better to have a version number.

As I read it, sockaddr is a transparent type (overloaded, as it were).
So we would use something like:
struct jail {
...
struct sockaddr;
char [SOCK_MAXADDRLEN - sizeof(struct sockaddr)];
char [sizeof(int) - SOCK_MAXADDRLEN % sizeof(int)];/* padding */
...
}

> 
> /assar
> 
> 
> 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: Jail syscalls

[Brian F. Feldman]

On Wed, 4 Aug 1999, Doug Rabson wrote:

> The argument for versioning is not simply because the size of ip_number
> might change (it should be a sockaddr) but because other fields might be
> added or removed. To avoid allocating a new syscall whenever this happens,
> the structure should be versioned.

Ahh, okay. If we plan on changing it, I agree.

> 
> Putting sizeof(whatever) at the beginning of the structure works
> surprisingly well as a versioning system.

Or a version field at a set offset, like in struct ip :)

> 
> --
> Doug Rabson   Mail:  d...@nlsystems.com
> Nonlinear Systems Ltd.Phone: +44 181 442 9037
> 
> 
> 

 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: [Fwd: Please support FreeBSD 3.x as host OS]

[Assar Westerlund]

Soren Schmidt  writes:
> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
> 
> If you provide an URL to those files, I'd give them a look...

Try .  To run it you
need to get an `evaluation key' but the tarboll itself is just
downloadable.  Then you want to look at driver-only.tar and
vmnet-only.tar that are included in the outer tarboll.

/assar


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Assar Westerlund]

"Brian F. Feldman"  writes:
> As I read it, sockaddr is a transparent type (overloaded, as it were).
> So we would use something like:
>   struct jail {
>   ...
>   struct sockaddr;
>   char [SOCK_MAXADDRLEN - sizeof(struct sockaddr)];
>   char [sizeof(int) - SOCK_MAXADDRLEN % sizeof(int)];/* padding */
>   ...
>   }

Yes, that would work, as would:

union {
struct sockaddr sa;
struct sockaddr_storage ss;
} u;

I was just trying to say that not all socket addresses fit into a
`struct sockaddr' but they should fit into a `struct
sockaddr_storage'.

/assar


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: NSS Project

[Assar Westerlund]

Peter Jeremy  writes:
> We need to be able to build an application that has no dynamically
> loaded code for recovery purposes (/stand and /sbin) as well as for
> security.

Isn't that the same problem as with PAM?

/assar


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

[Robert Nordier]

> > Because most modern BIOSes do CHS translation, the BIOS geometry is
> > not always evident from the geometry reported by the drive, and
> > FreeBSD may get this wrong, particularly if no existing partitions
> > are defined.
> > 
> > Since you are installing to a drive with no pre-existing non-FreeBSD
> > partitions, I suspect sysinstall got the geometry wrong.  Probably
> > you should re-install and use the 'G' command in sysinstall's fdisk,
> > after determining what geometry the BIOS is actually using.
> > 
> > The best way to determine BIOS geometry in FreeBSD is to boot -v
> > (but it should be from the old "boot:" prompt, not from loader(8)
> > in 3.2R) and then check using dmesg(8) for "BIOS Geometries"
> > information.
> 
> Hmmm - perhaps it isn't possible then to do what I want (without 
> losing most of the drive). The drive is 17Gb, consisting of 
> 33416 cyls, 16 heads and 63 sectors. The BIOS reports 1023 cyls, 255
> heads and 63 sectors - which is approximately 8Gb. This doesn't change
> if I change the BIOS mode between normal, large or LBA, nor if I make
> the disk type in the BIOS user defined and enter the real parameters
> (the BIOS is an Award BIOS v4.51PG, probably from about 1996).

1023/255/63 as the BIOS geometry is OK.  It means that only about
half the drive will be accessible through the BIOS CHS interface,
but there is an "8.4GB" CHS limit anyway.

The BIOS CHS interface is mainly needed only for booting.  Some OSes
support booting using a more recent BIOS LBA interface, which doesn't
(effectively) have a size limit.  Windows 9x and FreeBSD can do that,
provided your BIOS LBA support isn't broken.

Because not many OSes (or boot managers) support BIOS LBA, how you
set up your partitions, and what OSes you choose to install in which
partitions, needs some thought.

Personally, for maximum flexibility, I'd use FreeBSD's boot0 (or some
commercial boot manager that also supports LBA).  And I'd install 2.2.8
in partition 4, but using the boot blocks from -current.  I'd also
suggest ending partition 2 about 32-64M below cylinder 1024.

So it isn't completely straightforward, but you can make use of the
whole disk.

> I assume that if I set the gemoetry in fdisk to be the BIOS figures,
> that I will lose the other half of the disk?

Use 2096/255/63 in sysinstall.

-- 
Robert Nordier


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Matthew Dillon]

:The argument for versioning is not simply because the size of ip_number
:might change (it should be a sockaddr) but because other fields might be
:added or removed. To avoid allocating a new syscall whenever this happens,
:the structure should be versioned.
:
:Putting sizeof(whatever) at the beginning of the structure works
:surprisingly well as a versioning system.
:
:--
:Doug RabsonMail:  d...@nlsystems.com
:Nonlinear Systems Ltd. Phone: +44 181 442 9037

I think we basically have two choices:

* Pass the sizeof(struct) as part of the system call.  Please, not as 
  part of the structure!  That would make this syscall the odd-man-out
  compared to all the other syscalls that take size arguments.

* Make the first field of the structure a real version id, one that is
  taken from the same include file that the structure was defined in,
  and require that the field be filled in.

  e.g.

  #include 

  struct jail fubar = { JAIL_VERSION };

I kinda like the second choice the best but the first choice is what most
other system calls use.

-Matt
Matthew Dillon 



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

NSS Project update

[Oscar Bonilla]

After collecting a bunch of emails from the list, this is the
approach I'll be taking:

1. use the existing nsdispatch code obtained from NetBSD as a base
   for parsing the /etc/nsswitch.conf file.

2. Make the C library nsdispatch aware. The dtab[] array will be
   filled dynamicaly from the contents of /etc/nsswitch.conf.
   I'm still not sure if this has to be done "whithin" the C library
   or if nsdispatch should fill the dtab[] array itself and not relay
   on the caller (i.e. drop the dtab[] parameter). It seems to me at
   this point that the easiest approach is to have nsdispatch fill the
   dtab array itself.
3. Move the current implementation of the get*ent and get*by* from the
   C library to three dynamically loaded modules, namely: nss_files.so,
   nss_nis.so, and nss_dns.so
4. Add more nss_*.so modules for things like LDAP, etc.

once again: comments, suggestions.

Someone mentioned that we should still be able to produce statically linked
binaries for things like /stand and /sbin. I suggest making the nsdispatch
(or get* functions) revert to files if everything else fails (not the
modules themselves, but the loading of the modules). How does this sound?

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

no getkerninfo() man page (docs/12220)

[Nik Clayton]

-hackers,

As docs/12220 points out;

We want to extract routing information by specifying a particular 
destination IP address.  The man page on Route and Rtentry mention 
that this information can be acquired using getkerninfo command.  But 
there is no such man page.  Is it possible to get the information as 
how to use this command.  Or if there is any other method of acquiring 
this information.

Can anyone oblige with a getkerninfo() man page?

Cheers,

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
-- Tom Christiansen in <37514...@cs.colorado.edu>


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: TCP stack hackers take a bow

[Nik Clayton]

On Tue, Aug 03, 1999 at 07:52:26PM -0400, Bill Fumerola wrote:
> On Tue, 3 Aug 1999, Ted Faber wrote:
> 
> > http://www.sciencedaily.com/releases/1999/08/990802072727.htm
> 
> The Duke release credits one Andrew Gallatin for a couple quotes.
> 
> Not only FreeBSD in the news, but one of our own committers. Cool.

I've submitted this to /., we'll see what happens.

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
-- Tom Christiansen in <37514...@cs.colorado.edu>


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Building a new kernel

[Warner Losh]

I have a freebsd-stable system.  I can't build a kernel for
freebsd-current on that system unless I upgrade my compiler to egcs.
Will this cause problems for our upgrade proceedure?

gcc 2.7.2.3 doesn't like i386/include/atomic.h.  It complains about
bad assmbler contraints.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Building a new kernel

[David Scheidt]

On Wed, 4 Aug 1999, Warner Losh wrote:

> 
> I have a freebsd-stable system.  I can't build a kernel for
> freebsd-current on that system unless I upgrade my compiler to egcs.
> Will this cause problems for our upgrade proceedure?
> 
> gcc 2.7.2.3 doesn't like i386/include/atomic.h.  It complains about
> bad assmbler contraints.

I upgraded a -STABLE system to -CURRENT using source a month or two 
ago.  The first step is to build the new toolchain, so you shouldn't 
ever be compiling a new kernel with an old compiler.  

David



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Building a new kernel

[Osokin Sergey]

On Wed, 4 Aug 1999, Warner Losh wrote:

> 
> I have a freebsd-stable system.  I can't build a kernel for
> freebsd-current on that system unless I upgrade my compiler to egcs.
> Will this cause problems for our upgrade proceedure?
> 
> gcc 2.7.2.3 doesn't like i386/include/atomic.h.  It complains about
> bad assmbler contraints.
try to cvsup your source tree to 4.0, then rebuild your system
with simply make world procedure.

Rgdz,
Sergey Osokin aka oZZ,
o...@etrust.ru



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Results of investigating optimizing calloc()...

[Wilko Bulte]

As Dag-Erling Smorgrav wrote ...
> "Kelly Yancey"  writes:
> > [...]
> 
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of clearing pages "manually". This
> assumes your disk supports DMA, of course.

Wow.. I once saw this used, ages ago on a Uniflex machine running on
a Motorola 6809 cpu. They used a slightly different approach by doing dma
to a non-existent piece of hardware (memory is dim here...) that resulted
in zeros being read from the databus. The fact that TSC (the makers
of Uniflex) did this was discovered when Uniflex was ported over to 
a slightly different set of hardware that used inverting databuffers ;-)

Wilko
-- 
|   / o / /  _   Arnhem, The Netherlands- Powered by FreeBSD -
|/|/ / / /( (_) BulteWWW  : http://www.tcja.nl  http://www.freebsd.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Building a new kernel

[Warner Losh]

In message
 David
Scheidt writes: 
: I upgraded a -STABLE system to -CURRENT using source a month or two 
: ago.  The first step is to build the new toolchain, so you shouldn't 
: ever be compiling a new kernel with an old compiler.  

In the past, we've given advise to build a new kernel, then reboot and
do a make upgrade or make world (depending on if you were branch
jumping or not).  Also, as part of the aout-to-elf target, a kernel is
built...

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Building a new kernel

[Warner Losh]

In message  Osokin 
Sergey writes:
: try to cvsup your source tree to 4.0, then rebuild your system
: with simply make world procedure.

I can't do that.  This system *MUST* be a 3.2-stable system.  I was
building the kernel to test to see if a nasty NFS bug I've found in
-stable is present in the exact same environment but with a -current
kernel rather than a -stable one.

I was just noting this for people in the future.  It is something that
I've tradtionally been able to do and I couldn't do it in this case.
Others less worldly surely will hit the problem over time...  Likely
near the time we release 4.0 if the compiler situation remains the
same.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: no getkerninfo() man page (docs/12220)

[Jonathan Lemon]

In article 
 
you write:
>-hackers,
>
>As docs/12220 points out;
>
>We want to extract routing information by specifying a particular 
>destination IP address.  The man page on Route and Rtentry mention 
>that this information can be acquired using getkerninfo command.  But 
>there is no such man page.  Is it possible to get the information as 
>how to use this command.  Or if there is any other method of acquiring 
>this information.
>
>Can anyone oblige with a getkerninfo() man page?

getkerninfo() is depreciated, we use sysctl() instead.  In fact, most of
the information provided by getkerninfo() is implemented in terms of 
sysctl().

At the moment, sysctl() will only provide a dump of all routes, there
doesn't appear be a way to limit the output to a specific address.  In 
order to get a specific route, you'd have to query the routing socket
directly with RTM_GET, this is documented in the route(4) manpage.

The route(4) manpage says:

 User processes can obtain information about the routing entry to a spe-
 cific destination by using a RTM_GET message, or by reading the /dev/kmem
 device, or by issuing a getkerninfo(2) system call.

IMHO, the above sentence should probably be altered by replacing the
first comma with a period, and throwing away the rest of it.
--
Jonathan


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Building a new kernel

[David Scheidt]

On Wed, 4 Aug 1999, Warner Losh wrote:

> In message
>  David
> Scheidt writes: 
> : I upgraded a -STABLE system to -CURRENT using source a month or two 
> : ago.  The first step is to build the new toolchain, so you shouldn't 
> : ever be compiling a new kernel with an old compiler.  
> 
> In the past, we've given advise to build a new kernel, then reboot and
> do a make upgrade or make world (depending on if you were branch
> jumping or not).  Also, as part of the aout-to-elf target, a kernel is
> built...

Read the docs?  Who me?  It sounds like the 3.X to 4.0-RELEASE documentation
should say not to do this.  Unless, of course, gcc-2.95 is imported before
t hen.  

David



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Results of investigating optimizing calloc()...

[Peter Jeremy]

Dag-Erling Smorgrav  wrote:
>Which reminds me - has anyone thought of using DMA for zeroing pages,
This sounds reasonable.  Some DMA engines support filling regions
and memory-memory copies, but I'm not sure about what can be done
with the DMA engine(s) in PCs.

> The idea is to keep a chunk of zeroes on disk and DMA it into memory
Have you looked at disk latencies recently?  A modern CPU could zero-
fill a decent fraction of its RAM in the time taken to fetch a page of
zeroes from the platter.  And if it was accessed frequently enough to
keep the zeroed page in disk cache, you've just moved the bottleneck
into that disk controller (and you've reduced the effective size of the
disk's cache by a page).

Peter


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Building a new kernel

[Warner Losh]

In message
 David
Scheidt writes: 
: Read the docs?  Who me?  It sounds like the 3.X to 4.0-RELEASE documentation
: should say not to do this.  Unless, of course, gcc-2.95 is imported before
: t hen.  

Give me a F*ing break.  No such documetation exists and the more that
we change in how things traditionally the more problem's we'll have.

gcc 2.95 is the same thing as egcs, so that wouldn't matter...

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: NSS Project

[Peter Jeremy]

Assar Westerlund  wrote:
>Peter Jeremy  writes:
>> We need to be able to build an application that has no dynamically
>> loaded code for recovery purposes (/stand and /sbin) as well as for
>> security.
>
>Isn't that the same problem as with PAM?

Quite probably PAM has the same problem.  I haven't bumped into it
with PAM, so I can't be sure.  I definitely wouldn't like to get into
the situation where init can fail to load (or be unable to validate
the single-user password for a secure console) because the appropriate
encryption library is on a partition that isn't mounted yet (or has
been corrupted somehow).

The idea of being able to dynamically add new password encrytion
schemes (PAM) or database access methods (NSS) is generally good.
The problems appear when you try to marry these schemes with the
system security and initialisation/recovery tools (which need to
rely on and trust a minimal subset of the system).

Peter


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

memory leak in the routing table ?

[jayanth]

Were there any issues related to a memory leak in the routing table ?
I am running freebsd-stable.
After a few days vmstat -m shows the memory used by routing table to be
very high and log messages  "arpresolve: cant allocate llinfo for
a.b.c.d"
"arplookup a.b.c.d failed could not allocate llinfo" , keep repeating
for
every ip address that requires an arp entry to be created.

I turned on "route -v monitor" and started getting the following
messages
"RTM_MISS: Lookup failed on this address" for most addresses.

"netstat -arn" revealed routes that had a refcnt 0 zero but were not
being freed. However, I think the UP flag was on for each of the routes.

The machine was rebooted.
It seems there is a memory leak in the routing table.

thanks
Jayanth




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

ignoretime in login.conf??

[Doug]

I'm doing some research on resource limits and I can't find any
information at all on the ignoretime capability that's in
/usr/src/etc/login.conf. A 'grep -iR ignoretime *' in /usr/src didn't
return any hits outside of the login.conf files in /usr/src/etc and the
picobsd stuff. Does anyone have any information on what this is or what
it's used for? If not, perhaps it should be removed from the examples?

Also, the 'boolean' option is essentially undocumented in the
login.conf man page. It's mentioned once, but there is no example of how
it works or the fact that the @ sign is the symbol for it. The info is in
login_cap(3), but it's hard to decipher for a non-programmer. I'll put
this on my list if no one else wants to take it, and submit a PR.

Doug
-- 
On account of being a democracy and run by the people, we are the only
nation in the world that has to keep a government four years, no matter
what it does.
-- Will Rogers



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

netstat broken for -N -M?

[Warner Losh]

I'm seeing on a -stable system that netstat will always print values
obtained from sysctl rather than from the core file specified.  Can
anybody confirm this?  It doesn't seem like feature to me...

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Daniel O'Connor]

On 04-Aug-99 Matthew Dillon wrote:
>  I kinda like the second choice the best but the first choice is what
>  most
>  other system calls use.

That doesn't make it right =)

The second avoids the 'the data is different but the size is the same' problem
which would seem to be not too uncommon..

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


pgpFOORb26UPR.pgp
Description: PGP signature

Re: NSS Project update

[Boris Popov]

On Wed, 4 Aug 1999, Oscar Bonilla wrote:

[skip]
> 2. Make the C library nsdispatch aware. The dtab[] array will be
>filled dynamicaly from the contents of /etc/nsswitch.conf.
>I'm still not sure if this has to be done "whithin" the C library
>or if nsdispatch should fill the dtab[] array itself and not relay
>on the caller (i.e. drop the dtab[] parameter). It seems to me at
>this point that the easiest approach is to have nsdispatch fill the
>dtab array itself.

dtab[] array *should* be filled in nsdispatch, otherwise how will
you keep me from writing an empty get*() function ?

[skip]
> 
> Someone mentioned that we should still be able to produce statically linked
> binaries for things like /stand and /sbin. I suggest making the nsdispatch
> (or get* functions) revert to files if everything else fails (not the
> modules themselves, but the loading of the modules). How does this sound?

Sounds reasonable. If functions that works with local files
compiled statically we also not loose perfomance with plain setup.

--
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: Results of investigating optimizing calloc()...

[Arun Sharma]

On Wed, Aug 04, 1999 at 01:20:59PM +0200, Dag-Erling Smorgrav wrote:
> "Kelly Yancey"  writes:
> > [...]
> 
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of clearing pages "manually". This
> assumes your disk supports DMA, of course.

On a Pentium III, you can use the new instructions to do page zero'ing
without allocating cache lines.

-Arun



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Results of investigating optimizing calloc()...

[John-Mark Gurney]

Dag-Erling Smorgrav scribbled this message on Aug 4:
> "Kelly Yancey"  writes:
> > [...]
> 
> Which reminds me - has anyone thought of using DMA for zeroing pages,
> to avoid cache invalidation? The idea is to keep a chunk of zeroes on
> disk and DMA it into memory instead of clearing pages "manually". This
> assumes your disk supports DMA, of course.

has anyone looked at using two dma channels tied together to do memory
copies?  I haven't studied the DMA specs, but from what I know of the
dma on x86 machines is that you could tie two dma channels together one
to feed the other, and this would allow you to copy memory w/o using the
processor...

w/ dma channels, we can just make a copy of the base zero page...

-- 
  John-Mark Gurney  Voice: +1 541 684 8449
  Cu Networking   P.O. Box 5693, 97405

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: NSS Project

[John Polstra]

In article <99aug5.074611est.40...@border.alcanet.com.au>,
Peter Jeremy   wrote:
> Assar Westerlund  wrote:
> >Peter Jeremy  writes:
> >> We need to be able to build an application that has no dynamically
> >> loaded code for recovery purposes (/stand and /sbin) as well as for
> >> security.
> >
> >Isn't that the same problem as with PAM?
> 
> Quite probably PAM has the same problem.  I haven't bumped into it
> with PAM, so I can't be sure.

When you're not sure, it's really best to find out or keep quiet
on the mailing list.  As it is, you've just created a dozen or so
new people all over the world who will go around saying, "Hmm, I
seem to remember reading that PAM doesn't work in statically-linked
executables" -- which is false.  It works fine.  It is implemented
using a linker set approach which you are encouraged to investigate in
the sources.

> the situation where init can fail to load (or be unable to validate
> the single-user password for a secure console) because the appropriate
> encryption library is on a partition that isn't mounted yet

If that happened, it would have to be considered a severe design
error.

> (or has been corrupted somehow).

Many things can get corrupted to make the system unrecoverable.  For
example: the kernel, init itself, entries in the /dev directory, and
various combinations of cp, fsck, newfs, restore, ...

> The idea of being able to dynamically add new password encrytion
> schemes (PAM) or database access methods (NSS) is generally good.
> The problems appear when you try to marry these schemes with the
> system security and initialisation/recovery tools (which need to
> rely on and trust a minimal subset of the system).

Well, dynamic linking is here to stay, and that enlarges the scope
of "minimal subset" somewhat.  But nothing would be qualitatively
different if we went to an all-dynamic scheme (which I hope we will do
some day).  In any case, your system has to be working to a certain
degree to be recovered, or else you have to use external media such as
the fixit disk.

John
-- 
  John Polstra   j...@polstra.com
  John D. Polstra & Co., Inc.Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."-- Nora Ephron


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: NSS Project

[Peter Jeremy]

John Polstra  wrote:
>Peter Jeremy   wrote:
>> Assar Westerlund  wrote:
>> >Peter Jeremy  writes:
>> >> We need to be able to build an application that has no dynamically
>> >> loaded code for recovery purposes (/stand and /sbin) as well as for
>> >> security.
>> >
>> >Isn't that the same problem as with PAM?
>> 
>> Quite probably PAM has the same problem.  I haven't bumped into it
>> with PAM, so I can't be sure.
>
>When you're not sure, it's really best to find out or keep quiet
>on the mailing list.

Maybe I should have worded it differently:  In order to build statically
linked applications, both PAM and NSS have to solve a similar problem.
If it can or has been solved for PAM (which I wasn't sure about), the
same (or a very similar) solution will work for NSS.

> PAM doesn't work in statically-linked
>executables" -- which is false.  It works fine.

I apologize if I gave anyone the impression that you couldn't build
statically linked executables with libpam.

>  It is implemented
>using a linker set approach which you are encouraged to investigate in
>the sources.

A similar approach should work for NSS, though a case could probably
be made for having statically linking mean `only rely on local files'.

>> the situation where init can fail to load ...  because the appropriate
>> encryption library is on a partition that isn't mounted yet

I should also point out that init doesn't use PAM at present, so this
problem can't occur.  (The downside if that if the root password
doesn't use the default encryption method, init won't be able to
validate it).

>  But nothing would be qualitatively
>different if we went to an all-dynamic scheme (which I hope we will do
>some day).
I recall having a similar static-vs-dynamic discussion with you a couple
of years ago.  My position was (and still is) that for most purposes
dynamic linking is a definite advantage, but we should continue to
permit static linking for applications that want it (which Sun doesn't).

Peter


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: no getkerninfo() man page (docs/12220)

[Nik Clayton]

On Wed, Aug 04, 1999 at 03:59:00PM -0500, Jonathan Lemon wrote:
> getkerninfo() is depreciated, we use sysctl() instead.  In fact, most of
> the information provided by getkerninfo() is implemented in terms of 
> sysctl().



> The route(4) manpage says:
> 
>  User processes can obtain information about the routing entry to a spe-
>  cific destination by using a RTM_GET message, or by reading the /dev/kmem
>  device, or by issuing a getkerninfo(2) system call.
> 
> IMHO, the above sentence should probably be altered by replacing the
> first comma with a period, and throwing away the rest of it.

Sounds fair enough.  I'll allow 24 hours for objections, and then commit
based on that, OK?

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
-- Tom Christiansen in <37514...@cs.colorado.edu>


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Doug Rabson]

On Wed, 4 Aug 1999, Brian F. Feldman wrote:

> On Tue, 3 Aug 1999, Mike Smith wrote:
> 
> > > 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...
> 
> Actually, the structure shouldn't change size because it should be
> using a sockaddr.

The argument for versioning is not simply because the size of ip_number
might change (it should be a sockaddr) but because other fields might be
added or removed. To avoid allocating a new syscall whenever this happens,
the structure should be versioned.

Putting sizeof(whatever) at the beginning of the structure works
surprisingly well as a versioning system.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

[Fwd: Please support FreeBSD 3.x as host OS]

[Niall Smart]

Olivia Cheriton wrote:
> 
> Niall,
> 
> VMware will support FreeBSD as a guest operating system, but unfortunately
> we currently do not have plans to support FreeBSD as a host operating
> system.  I have noted your request of FreeBSD host support in case we review
> this in the future.
> 
> Best regards,
> 
> Olivia Cheriton
> VMware, Inc.
> 
> - Original Message -
> From: Niall Smart <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Saturday, July 24, 1999 11:09 AM
> Subject: Please support FreeBSD 3.x as host OS
> 
> > Hi.
> >
> > I'd like to see FreeBSD 3.x supported as a host OS, I'll
> > certainly be buying a copy of VMware if this happens.
> >
> > Regards,
> >
> > Niall Smart
> > Senior Software Developer
> > Trinity Commerce


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 ?

[Vince Vielhaber]

On Wed, 4 Aug 1999, Biju Susmer wrote:

> 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?

You have the CD connected as the secondary slave and no secondary master.
That's the problem.  It's an illegal configuration as the IDE controller
is actually on the drive itself.  Move the jumper on the CD to master and
it'll be recognized.

Vince.
-- 
==
Vince Vielhaber -- KA8CSH   email: [EMAIL PROTECTED]   flame-mail: /dev/null
   # includeTEAM-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: BSD voice synthesis

[Ville-Pertti Keinonen]

[EMAIL PROTECTED] (Wes Peters) writes:

> available for "home" computers decades ago.  (Anyone else here ever use
> SAM "the Software Automated Mouth" for the Atari 800 or Commodore 64?)

Yes.

It's almost surprising how little speech synthesis has improved, at
least judging from the festival demos (it is, of course, better than
SAM, but apparently the data and processing requirements are several
orders of magnitude greater).  I haven't downloaded all of the
required stuff, yet, so I don't know how good or bad it actually might
be.

I certainly don't expect any of the available voices to be able to
pronounce Finnish names correctly, even with phonetic specifications.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Solution for mail pseudo-users?

[Markus Stumpf]

On Tue, Aug 03, 1999 at 02:22:17PM -0700, Alex Zepeda wrote:
> > 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. 

With your setup that would hold, too.
But with my setup the effective user doesn't have to be root, so if there
is an exploit the intruder doesn't gain root privileges the first place
and it reduces the possibilities that e.g. the whole subnet is compromised
by sniffing or the like.

> > 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. 

A e.g. database isn't a flat text file. Nobody said that one should use a
linear search on a flat text file. You're free to plug in whatever
backend you want (Berkley DB, SQL database, cdb, ...), but you don't
have to rebuild the whole database, but just the record modified.

Queuing changes is IMHO not an option.
When a user changes his password, he want it to be effective
immediately, not after 5, 10, 15 oder 30 minutes.

\Maex

-- 
SpaceNet GmbH |   http://www.Space.Net/   | Yeah, yo mama dresses
Research & Development| mailto:[EMAIL PROTECTED] | you funny and you need
Joseph-Dollinger-Bogen 14 |  Tel: +49 (89) 32356-0| a mouse to delete files
D-80807 Muenchen  |  Fax: +49 (89) 32356-299  |


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Onstream?

[Vince Vielhaber]

Out of curiousity, have there been any successes in the drivers for
the OnStream tape drives (SCSI or IDE)?

Vince.
-- 
==
Vince Vielhaber -- KA8CSH   email: [EMAIL PROTECTED]   flame-mail: /dev/null
   # includeTEAM-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: Onstream?

[Soren Schmidt]

It seems Vince Vielhaber wrote:
> 
> Out of curiousity, have there been any successes in the drivers for
> the OnStream tape drives (SCSI or IDE)?

Working on it (for IDE that is), support is planned for, but I have
no release date yet... I know that there is work done on the SCSI
end too...


-Søren


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

[Mike Pritchard]

> At 8:01 PM +0200 8/3/99, Robert Nordier wrote:
> 
> > > - If I select 3.2 at the PowerBoot menu, it comes up
> > >   with two messages about "invalid partition", [...]
> > >   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.

I have my main machine setup to boot 3 different operating systems all
on one harddisk.  My disk is paritioned into 4 fdisk partitions, as follows:

1:  Win98 (ugh, but I need to have it to play games :-) (bootable)
2:  extended dos partition (non-bootable)
3:  FreeBSD 3.2-stable (bootable)
4:  FreeBSD 4.0 -current (bootable)

Here is my file system layout when running 4.0:

/dev/wd0s4a on / (local, soft-updates, writes: sync 16 async 14249)
/dev/wd0s3a on /root32 (local, writes: sync 2 async 44)
/dev/wd0s3e on /root32/usr (local, writes: sync 2 async 7099)
/dev/wd0s4f on /usr (local, soft-updates, writes: sync 2 async 8148)
/dev/wd0s4h on /shared (local, soft-updates, writes: sync 1963 async 263656)
/dev/wd0s3f on /root32/var (local, writes: sync 2 async 40)
/dev/wd0s4g on /var (local, soft-updates, writes: sync 4604 async 69441)
(along with a wd0s4b swap partition, which is shared between both
FreeBSD versions)

When I first tried this, I couldn't boot the 4.0 version because 
the 4.0 root device was named wd0s4e by my initial 3.2 sysinstall.  I had 
to run disklabel and change the partition name to wd0s4a.  After doing 
that, both versions would boot no problem.  I just hit F3 for 3.2-stable, 
or F4 for 4.0-current.

All of my boot blocks were orignally written out with 3.2-stable,
but I've since re-written them with 4.0-current boot blocks.

-Mike
-- 
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSD voice synthesis

[Dag-Erling Smorgrav]

Ville-Pertti Keinonen <[EMAIL PROTECTED]> writes:
> I certainly don't expect any of the available voices to be able to
> pronounce Finnish names correctly, even with phonetic specifications.

If the software were *designed* to speak Finnish, I'd expect it to
cope with Finnish much better than it currently does with English,
seeing as you guys have nearly phonetic spelling.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Assar Westerlund]

"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> On Tue, 3 Aug 1999, Mike Smith wrote:
> > 
> > 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...
> 
> Actually, the structure shouldn't change size because it should be
> using a sockaddr.

No, because sizeof(struct sockaddr) < sizeof(struct sockaddr_in6).
This is kind of bad but that's the way it is.  It would make sense to
use a `struct sockaddr_storage' but I still think it's worthwhile and
better to have a version number.

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Results of investigating optimizing calloc()...

[Dag-Erling Smorgrav]

"Kelly Yancey" <[EMAIL PROTECTED]> writes:
> [...]

Which reminds me - has anyone thought of using DMA for zeroing pages,
to avoid cache invalidation? The idea is to keep a chunk of zeroes on
disk and DMA it into memory instead of clearing pages "manually". This
assumes your disk supports DMA, of course.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Tekram DC-390U2W support (80Mb/sec operation)

[Kevin]

Hey all, I purchased a Tekram DC-390U2W scsi controller to use with a
FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) chipset(s). I
see that ncr.c supports the NCR 53c8xx family of chipsets..
which the controller is seen as having a 53c895, which only supports
40Mb/sec operation(?)


 {NCR_895_ID, 0x00, "ncr 53c895 fast40 wide scsi",  7, 31, 7,
 FE_WIDE|FE_ULTRA2|FE_QUAD|FE_CACHE_SET|FE_DFS|FE_LDSTR|FE_PFEN|FE_RAM}


I am assuming that it only supports 40Mb/sec operation.. could someone
prove me wrong? I just want to get 80Mb/sec operation (would I need to have
support for the 53c141 driver? are there any out there, is it in the
works?). Tekram has FreeBSD drivers on their site but they say it is
supported in 3.0, I can't find anything newer. They are working on a new
one.. They already have support for the DC-390U2W on various Linux's of
course :(

Could anyone *please* enlighten me? I would be grateful.

Please reply to my email address, as I am not subsribed to these lists.

Thanks a lot,

Kevin



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: NSS Project

[Alfred Perlstein]

On Wed, 4 Aug 1999, Peter Jeremy wrote:

> Oscar Bonilla <[EMAIL PROTECTED]> wrote:
> >If anyone has any comments, suggestions, etc. I would appreciate it.
> 
> Overall, I like the idea of NSS.  But, having worked on Solaris 2.x
> for some time, we need to avoid some of the blunders Sun made: The
> biggest problem with Sun's NSS implementation is that it's no longer
> possible to statically link an application that uses any of the
> get...byname() functions that have NSS backends.
> 
> We need to be able to build an application that has no dynamically
> loaded code for recovery purposes (/stand and /sbin) as well as for
> security.

well you could just link in the shared nss object statically into
it...?

-Alfred



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: BSD voice synthesis

[Ville-Pertti Keinonen]

[EMAIL PROTECTED] (Dag-Erling Smorgrav) writes:

> Ville-Pertti Keinonen <[EMAIL PROTECTED]> writes:
> > I certainly don't expect any of the available voices to be able to
> > pronounce Finnish names correctly, even with phonetic specifications.

> If the software were *designed* to speak Finnish, I'd expect it to
> cope with Finnish much better than it currently does with English,
> seeing as you guys have nearly phonetic spelling.

Festival is basically language-independent, each voice is associated
with a specific language, so with a Finnish voice it should be able to
pronounce Finnish reasonably.

Since the English voices have dictionaries for pronunciation, anyhow,
a Finnish voice wouldn't necessarily do a better job in terms of
pronunciation, although a Finnish voice should require fewer distinct
phonemes.

Creating voices does seem to involve quite a bit of work, though.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Alfred Perlstein]

On Wed, 4 Aug 1999, Niall Smart wrote:

> Olivia Cheriton wrote:
> > 
> > Niall,
> > 
> > VMware will support FreeBSD as a guest operating system, but unfortunately
> > we currently do not have plans to support FreeBSD as a host operating
> > system.  I have noted your request of FreeBSD host support in case we review
> > this in the future.
> > 
> > Best regards,
> > 
> > Olivia Cheriton
> > VMware, Inc.
> > 
> > - Original Message -
> > From: Niall Smart <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Saturday, July 24, 1999 11:09 AM
> > Subject: Please support FreeBSD 3.x as host OS
> > 
> > > Hi.
> > >
> > > I'd like to see FreeBSD 3.x supported as a host OS, I'll
> > > certainly be buying a copy of VMware if this happens.
> > >

I heard they have released the source to the kernel modules needed
to run it.

why not port them over? :)

-Alfred




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Tekram DC-390U2W support (80Mb/sec operation)

[Stuart Henderson]

> Hey all, I purchased a Tekram DC-390U2W scsi controller to use with 
> a FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) 
> chipset(s). I see that ncr.c supports the NCR 53c8xx family of 
> chipsets.. which the controller is seen as having a 53c895, which 
> only supports 40Mb/sec operation(?)

http://www.freebsd.org/cgi/search.cgi?words=53c895+80mbps&max=25&sort=score&source=freebsd-scsi


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: Tekram DC-390U2W support (80Mb/sec operation)

[Nigel Roles]

The 53c141 is an auto-sensing single-ended/LVDS terminator, permitting
you to connect single-ended and LVDS drives to the same cable. It is
transparent.

If you want 80mbps you need

1. a wide LVDS (aka Ultra2 or fast40) drive
2. a wide LVDS terminator

The 40 in the portion of ncr.c you quote is MHz not megabytes. By having a
wide
(16 bit) drive (and bus) you get 16bits * 40MHz or 80mbps. 

What makes you think you haven't got 80mbps? How would you tell?

-Original Message-
From: Kevin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 04, 1999 12:42 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Tekram DC-390U2W support (80Mb/sec operation)


Hey all, I purchased a Tekram DC-390U2W scsi controller to use with a
FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) chipset(s). I
see that ncr.c supports the NCR 53c8xx family of chipsets..
which the controller is seen as having a 53c895, which only supports
40Mb/sec operation(?)


 {NCR_895_ID, 0x00, "ncr 53c895 fast40 wide scsi",  7, 31, 7,
 FE_WIDE|FE_ULTRA2|FE_QUAD|FE_CACHE_SET|FE_DFS|FE_LDSTR|FE_PFEN|FE_RAM}


I am assuming that it only supports 40Mb/sec operation.. could someone
prove me wrong? I just want to get 80Mb/sec operation (would I need to have
support for the 53c141 driver? are there any out there, is it in the
works?). Tekram has FreeBSD drivers on their site but they say it is
supported in 3.0, I can't find anything newer. They are working on a new
one.. They already have support for the DC-390U2W on various Linux's of
course :(

Could anyone *please* enlighten me? I would be grateful.

Please reply to my email address, as I am not subsribed to these lists.

Thanks a lot,

Kevin



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-scsi" 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

[Graham Wheeler]

Robert Nordier wrote:
> 
> 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.

Hmmm. This sounds a good plan. Would the following then work
(I'm using `partition' to refer to a fdisk partition, and `file
system' to refer to a BSD partition):

* I partition my drive into 4 equal partitions (rather than 2;
this gives me more future flexibility)

* I install 2.2.8 in the first partition.

* I change the type to something other than FreeBSD

* I install 3.2 into the second partition

* I change the type of the first partition back to FreeBSD

* I install os-bs or some other boot selector

* And now, hopefully, I can simply boot either from the boot
selector menu?


-- 
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

double vfs_object_create in open syscall?

[Alfred Perlstein]

Why does open() at "sys/kern/vfs_syscalls.c" line 1023 call
vfs_object_create() when vnopen() ("sys/kern/vfs_vnops.c" line 174)
already does so?

vfs_object_create checks for this and doesn't leak, but it looks
funny to me.

-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: Tekram DC-390U2W support (80Mb/sec operation)

[Stuart Henderson]

> What makes you think you haven't got 80mbps? How would you tell?

Something like this in your dmesg/boot output.
da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing
Enabled


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Assar Westerlund]

Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I heard they have released the source to the kernel modules needed
> to run it.
> 
> why not port them over? :)

I started looking at the kernel modules and porting them, however, I
must confess that I don't fully understand exactly what the linux
kernel module does, which makes it somewhat harder to implement the
same functionality on FreeBSD :-)

/assar


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

[Graham Wheeler]

Graham Wheeler wrote:
> 
> Robert Nordier wrote:
> >
> > 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.
> 
> Hmmm. This sounds a good plan. Would the following then work
> (I'm using `partition' to refer to a fdisk partition, and `file
> system' to refer to a BSD partition):
> 
> * I partition my drive into 4 equal partitions (rather than 2;
> this gives me more future flexibility)
> 
> * I install 2.2.8 in the first partition.
> 
> * I change the type to something other than FreeBSD
> 
> * I install 3.2 into the second partition
> 
> * I change the type of the first partition back to FreeBSD
> 
> * I install os-bs or some other boot selector
> 
> * And now, hopefully, I can simply boot either from the boot
> selector menu?

I tried this, and the installation went through fine. But after 
installing 3.2, I get a `Missing operating system' when I try to
boot the second partition (the first still has its type set to 
something other than FreeBSD, so it won't boot either).

Robert, you seem quite knowledgeable about all this, and seem to have
had considerable success. How do I get this right? I want to install
2.2.8 in one partition and 3.2 in another. If I don't change the 
fdisk partition type after installing 2.2.8, then sysinstall won't
allow me to install the second OS (it complains when I try to make the 
root BSD partition that the boot loader can't handle it). If I do
change the fdisk partition type first, the install is fine, but I can't
boot afterwards, as described above.

-- 
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: [Fwd: Please support FreeBSD 3.x as host OS]

[Soren Schmidt]

It seems Assar Westerlund wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> > 
> > why not port them over? :)
> 
> I started looking at the kernel modules and porting them, however, I
> must confess that I don't fully understand exactly what the linux
> kernel module does, which makes it somewhat harder to implement the
> same functionality on FreeBSD :-)

If you provide an URL to those files, I'd give them a look...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Alfred Perlstein]

On 4 Aug 1999, Assar Westerlund wrote:

> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I heard they have released the source to the kernel modules needed
> > to run it.
> > 
> > why not port them over? :)
> 
> I started looking at the kernel modules and porting them, however, I
> must confess that I don't fully understand exactly what the linux
> kernel module does, which makes it somewhat harder to implement the
> same functionality on FreeBSD :-)

a quick scan of the vmware site didn't reveal where the kernel
mods are.  are they available freely? can i have a url please?

-Alfred



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

[Robert Nordier]

> > > 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.
> > 
> > Hmmm. This sounds a good plan. Would the following then work
> > (I'm using `partition' to refer to a fdisk partition, and `file
> > system' to refer to a BSD partition):
> > 
> > * I partition my drive into 4 equal partitions (rather than 2;
> > this gives me more future flexibility)
> > 
> > * I install 2.2.8 in the first partition.
> > 
> > * I change the type to something other than FreeBSD
> > 
> > * I install 3.2 into the second partition
> > 
> > * I change the type of the first partition back to FreeBSD
> > 
> > * I install os-bs or some other boot selector
> > 
> > * And now, hopefully, I can simply boot either from the boot
> > selector menu?
> 
> I tried this, and the installation went through fine. But after 
> installing 3.2, I get a `Missing operating system' when I try to
> boot the second partition (the first still has its type set to 
> something other than FreeBSD, so it won't boot either).
> 
> Robert, you seem quite knowledgeable about all this, and seem to have
> had considerable success. How do I get this right? I want to install
> 2.2.8 in one partition and 3.2 in another. If I don't change the 
> fdisk partition type after installing 2.2.8, then sysinstall won't
> allow me to install the second OS (it complains when I try to make the 
> root BSD partition that the boot loader can't handle it). If I do
> change the fdisk partition type first, the install is fine, but I can't
> boot afterwards, as described above.

"Missing operating system" indicates that the first sector of the
OS bootstrap (boot1 in the FreeBSD case) isn't flagged bootable:
that is, it doesn't have the bytes 0x55 and 0xaa right at the end.

Almost invariably, the cause of this is a mismatch between the disk
geometry the BIOS is using, and what FreeBSD thought the geometry
was during the install.  (So the wrong sector is read by the MBR
code.)

The first partition is less sensitive to geometry mismatches than
the others, since it has a starting CHS value of 0,1,1.  That relies
only on "sectors per track" and not "number of heads".

Because most modern BIOSes do CHS translation, the BIOS geometry is
not always evident from the geometry reported by the drive, and
FreeBSD may get this wrong, particularly if no existing partitions
are defined.

Since you are installing to a drive with no pre-existing non-FreeBSD
partitions, I suspect sysinstall got the geometry wrong.  Probably
you should re-install and use the 'G' command in sysinstall's fdisk,
after determining what geometry the BIOS is actually using.

The best way to determine BIOS geometry in FreeBSD is to boot -v
(but it should be from the old "boot:" prompt, not from loader(8)
in 3.2R) and then check using dmesg(8) for "BIOS Geometries"
information.

-- 
Robert Nordier


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

fetch: default to passive mode?

[Chuck Youse]

I have a really strong urge to submit a PR to make fetch default to passive
mode, instead of requiring a command-line switch ...

In this day and age, with firewalls and NAT abound, it's a bit odd that such
a change has not already been made.  Am I missing something?  Is there a
reason we haven't done this yet?

Chuck Youse
Director of Engineering
CyberSites, Inc.





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Milan Kopacka]

On Wed, 4 Aug 1999, Alfred Perlstein wrote:

> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
> 
> a quick scan of the vmware site didn't reveal where the kernel
> mods are.  are they available freely? can i have a url please?

Source code is included in the distribution. They have modules precompiled
only for certain versions of Linux kernel. You may have to compile them
yourself when you are running some other version. 

  Milan Kopacka

--
... a koho system nachyta na procesoru, tomu snizi prioritu.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Alfred Perlstein]

On Wed, 4 Aug 1999, Milan Kopacka wrote:

> On Wed, 4 Aug 1999, Alfred Perlstein wrote:
> 
> > > I started looking at the kernel modules and porting them, however, I
> > > must confess that I don't fully understand exactly what the linux
> > > kernel module does, which makes it somewhat harder to implement the
> > > same functionality on FreeBSD :-)
> > 
> > a quick scan of the vmware site didn't reveal where the kernel
> > mods are.  are they available freely? can i have a url please?
> 
> Source code is included in the distribution. They have modules precompiled
> only for certain versions of Linux kernel. You may have to compile them
> yourself when you are running some other version. 

so one must purchase the program to get the kernel mods, is there
an evaluation that can be downloaded?

-Alfred



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Fwd: Please support FreeBSD 3.x as host OS]

[Milan Kopacka]

On Wed, 4 Aug 1999, Alfred Perlstein wrote:

> so one must purchase the program to get the kernel mods, is there
> an evaluation that can be downloaded?

They have all described on website. The program is key-protected, you can
buy a key, or ask for evaluation key, which will work one month.

You need the key to run the virtual machine, archive unpacking and
installation can be done without the key.

  Milan Kopacka

--
... a koho system nachyta na procesoru, tomu snizi prioritu.



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

[Graham Wheeler]

Robert Nordier wrote:
> 
> Because most modern BIOSes do CHS translation, the BIOS geometry is
> not always evident from the geometry reported by the drive, and
> FreeBSD may get this wrong, particularly if no existing partitions
> are defined.
> 
> Since you are installing to a drive with no pre-existing non-FreeBSD
> partitions, I suspect sysinstall got the geometry wrong.  Probably
> you should re-install and use the 'G' command in sysinstall's fdisk,
> after determining what geometry the BIOS is actually using.
> 
> The best way to determine BIOS geometry in FreeBSD is to boot -v
> (but it should be from the old "boot:" prompt, not from loader(8)
> in 3.2R) and then check using dmesg(8) for "BIOS Geometries"
> information.

Hmmm - perhaps it isn't possible then to do what I want (without 
losing most of the drive). The drive is 17Gb, consisting of 
33416 cyls, 16 heads and 63 sectors. The BIOS reports 1023 cyls, 255
heads and 63 sectors - which is approximately 8Gb. This doesn't change
if I change the BIOS mode between normal, large or LBA, nor if I make
the disk type in the BIOS user defined and enter the real parameters
(the BIOS is an Award BIOS v4.51PG, probably from about 1996).

I assume that if I set the gemoetry in fdisk to be the BIOS figures,
that I will lose the other half of the disk?

-- 
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: Jail syscalls

[Brian F. Feldman]

On 4 Aug 1999, Assar Westerlund wrote:

> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > On Tue, 3 Aug 1999, Mike Smith wrote:
> > > 
> > > 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...
> > 
> > Actually, the structure shouldn't change size because it should be
> > using a sockaddr.
> 
> No, because sizeof(struct sockaddr) < sizeof(struct sockaddr_in6).
> This is kind of bad but that's the way it is.  It would make sense to
> use a `struct sockaddr_storage' but I still think it's worthwhile and
> better to have a version number.

As I read it, sockaddr is a transparent type (overloaded, as it were).
So we would use something like:
struct jail {
...
struct sockaddr;
char [SOCK_MAXADDRLEN - sizeof(struct sockaddr)];
char [sizeof(int) - SOCK_MAXADDRLEN % sizeof(int)];/* padding */
...
}

> 
> /assar
> 
> 
> 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: Jail syscalls

[Brian F. Feldman]

On Wed, 4 Aug 1999, Doug Rabson wrote:

> The argument for versioning is not simply because the size of ip_number
> might change (it should be a sockaddr) but because other fields might be
> added or removed. To avoid allocating a new syscall whenever this happens,
> the structure should be versioned.

Ahh, okay. If we plan on changing it, I agree.

> 
> Putting sizeof(whatever) at the beginning of the structure works
> surprisingly well as a versioning system.

Or a version field at a set offset, like in struct ip :)

> 
> --
> Doug Rabson   Mail:  [EMAIL PROTECTED]
> Nonlinear Systems Ltd.Phone: +44 181 442 9037
> 
> 
> 

 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: [Fwd: Please support FreeBSD 3.x as host OS]

[Assar Westerlund]

Soren Schmidt <[EMAIL PROTECTED]> writes:
> > I started looking at the kernel modules and porting them, however, I
> > must confess that I don't fully understand exactly what the linux
> > kernel module does, which makes it somewhat harder to implement the
> > same functionality on FreeBSD :-)
> 
> If you provide an URL to those files, I'd give them a look...

Try .  To run it you
need to get an `evaluation key' but the tarboll itself is just
downloadable.  Then you want to look at driver-only.tar and
vmnet-only.tar that are included in the outer tarboll.

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Jail syscalls

[Assar Westerlund]

"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> As I read it, sockaddr is a transparent type (overloaded, as it were).
> So we would use something like:
>   struct jail {
>   ...
>   struct sockaddr;
>   char [SOCK_MAXADDRLEN - sizeof(struct sockaddr)];
>   char [sizeof(int) - SOCK_MAXADDRLEN % sizeof(int)];/* padding */
>   ...
>   }

Yes, that would work, as would:

union {
struct sockaddr sa;
struct sockaddr_storage ss;
} u;

I was just trying to say that not all socket addresses fit into a
`struct sockaddr' but they should fit into a `struct
sockaddr_storage'.

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: NSS Project

[Assar Westerlund]

Peter Jeremy <[EMAIL PROTECTED]> writes:
> We need to be able to build an application that has no dynamically
> loaded code for recovery purposes (/stand and /sbin) as well as for
> security.

Isn't that the same problem as with PAM?

/assar


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

[Robert Nordier]

> > Because most modern BIOSes do CHS translation, the BIOS geometry is
> > not always evident from the geometry reported by the drive, and
> > FreeBSD may get this wrong, particularly if no existing partitions
> > are defined.
> > 
> > Since you are installing to a drive with no pre-existing non-FreeBSD
> > partitions, I suspect sysinstall got the geometry wrong.  Probably
> > you should re-install and use the 'G' command in sysinstall's fdisk,
> > after determining what geometry the BIOS is actually using.
> > 
> > The best way to determine BIOS geometry in FreeBSD is to boot -v
> > (but it should be from the old "boot:" prompt, not from loader(8)
> > in 3.2R) and then check using dmesg(8) for "BIOS Geometries"
> > information.
> 
> Hmmm - perhaps it isn't possible then to do what I want (without 
> losing most of the drive). The drive is 17Gb, consisting of 
> 33416 cyls, 16 heads and 63 sectors. The BIOS reports 1023 cyls, 255
> heads and 63 sectors - which is approximately 8Gb. This doesn't change
> if I change the BIOS mode between normal, large or LBA, nor if I make
> the disk type in the BIOS user defined and enter the real parameters
> (the BIOS is an Award BIOS v4.51PG, probably from about 1996).

1023/255/63 as the BIOS geometry is OK.  It means that only about
half the drive will be accessible through the BIOS CHS interface,
but there is an "8.4GB" CHS limit anyway.

The BIOS CHS interface is mainly needed only for booting.  Some OSes
support booting using a more recent BIOS LBA interface, which doesn't
(effectively) have a size limit.  Windows 9x and FreeBSD can do that,
provided your BIOS LBA support isn't broken.

Because not many OSes (or boot managers) support BIOS LBA, how you
set up your partitions, and what OSes you choose to install in which
partitions, needs some thought.

Personally, for maximum flexibility, I'd use FreeBSD's boot0 (or some
commercial boot manager that also supports LBA).  And I'd install 2.2.8
in partition 4, but using the boot blocks from -current.  I'd also
suggest ending partition 2 about 32-64M below cylinder 1024.

So it isn't completely straightforward, but you can make use of the
whole disk.

> I assume that if I set the gemoetry in fdisk to be the BIOS figures,
> that I will lose the other half of the disk?

Use 2096/255/63 in sysinstall.

-- 
Robert Nordier


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message