Low Cost Term Life Insurance H
Term Quotes Life Insurance Companies Since 1996, term life insurance rates have been reduced by as much as 70% 40 year old male - $250,000 - 10 year level termAs low as $10.44 per month! At TermQuotes Life Insurance Companies of America, we will survey the top life insurance companies for you and provide you with the best rates available. The quote is free. There is no obligation to buy. Compare the rates and see for yourself. Fill out this quick form below for further information. Results of computer survey 07-09-01Sample Annual Premiums* 10 Year Level Premium Term Rates * Age $250,000 $500,000 $1,000,000 35 $115 $175 $305 45 $210 $375 $670 55 $500 $935 $1,370 65 $1,305 $2,550 $4,920 70 $2,265 $4,480 $7,510*Above rates guaranteed to remain level for 10 yearsRates based on male preferred class 1 non-smoker Policies are guaranteed renewable to age 95Policies with 15, 20, 25, and 30 year level premiums also available Attention All Smokers,you may qualify for special reduced smoker rates! Universal Life, Second-to-Die and Estate Planning products also provided. Submit This Form for a Free Term Insurance Quote! Name Insured: Amount of Coverage: $250,000$300,000$400,000$500,000$600,000$700,000$800,000$900,000$1,000,000 Date of Birth: Month 010203040506070809101112 Day 01020304050607080910111213141516171819202122232425262728293031 Year Sex: Male Female Height: FT in Weight: lbs. Occupation: xxx Have You Ever Had: High Blood Pressure Yes No Heart Attack or Stroke Yes No Cancer Yes No Diabetes Yes No Mother, Father, Sister, Brother Diagnosed or Died of Cancer or Cardiovascular DiseaseBefore Age 60 Yes No Have You Smoked Within the Last 12 Months Yes No xxx Person Completing Request: Mailing Address: City: State Zip Daytime Phone: Evening Phone: Email Address: Best time to contact: Morning After noon Evening Weekend When you click submit it may start your spell check, so please click Ignore if it does. YOUR INTERNET ADVERTISING CopyrightÿA92000-2001 . All Rights Reserved This could be your ad! Email Uswith your name and a good phone number to reach you. If you think, that you will not benefit from this correspondence, please click here. To Unsubscribe: send mail to [EMAIL
Re: I will be in Europe and the UK from Nov 5th through Nov 14th.
On Mon, Oct 29, 2001 at 05:53:05PM -0800, Jordan Hubbard wrote: JFYI, Brett Halle (the director of CoreOS engineering for Apple) and I will be speaking at the NLUUG's Autumn Conference in Ede, The Netherlands on November 8th and then travelling on to BSDCon Europe in Brighton, UK immediately thereafter (the 9th) and staying in the UK until November 14th. JOKE To be exact, the subject should say ... in the Netherlands and the UK... since the UK is a part of Europe. Or, even better, in the Continent and the UK :-) :-) /JOKE Cheers, JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
pxe booting problem
I posted some of this info last friday but haven't had any responses. I'm hoping someone out there knows what the problem is. Here's the details: I saw Alfred Perlsteins page on how to setup FreeBSD installs unsing PXE. The problem I'm having now is when I follow Alfred's directions to create the PXE loader (using 4.4R) It bombs out. It's my understanding the I just need to stick 'pxeldr' into the root of the TFTP server directory and tell the machine to execute this by specifying it as the boot file in the DHCP configuration. I also understand that I have to create a subdirectory called 'boot' under the TFTP root directory with the file 'loader.rc' in it. Can someone verify if this is the case? Alfred's instructions can be found here: http://people.freebsd.org/~alfred/pxe/ This is the console output that insues when I try and build pxeldr as per Alfred's instructions: auadwesm1203280# make === ficl Warning: Object directory not changed from original /usr/src/sys/boot/ficl === i386 === i386/mbr Warning: Object directory not changed from original /usr/src/sys/boot/i386/mbr === i386/boot0 Warning: Object directory not changed from original /usr/src/sys/boot/i386/boot0 === i386/kgzldr Warning: Object directory not changed from original /usr/src/sys/boot/i386/kgzld r === i386/btx === i386/btx/btx Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/b tx === i386/btx/btxldr Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/b txldr === i386/btx/lib Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/l ib === i386/boot2 Warning: Object directory not changed from original /usr/src/sys/boot/i386/boot2 === i386/libi386 Warning: Object directory not changed from original /usr/src/sys/boot/i386/libi3 86 cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i 386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT= 0x3f8 -DCOMSPEED=9600 -I/usr/src/sys/boot/i386/libi386/../../../../lib/libstand/ -DTERM_EMU -mpreferred-stack-boundary=2 -c pxe.c -o pxe.o pxe.c:41: net.h: No such file or directory pxe.c:42: netif.h: No such file or directory pxe.c:43: nfsv2.h: No such file or directory pxe.c:44: iodesc.h: No such file or directory pxe.c:46: bootp.h: No such file or directory pxe.c:84: warning: `struct netif' declared inside parameter list pxe.c:84: warning: its scope is only this definition or declaration, which is pr obably not what you want. pxe.c:85: warning: `struct netif' declared inside parameter list pxe.c:86: warning: `struct iodesc' declared inside parameter list pxe.c:88: warning: `struct iodesc' declared inside parameter list pxe.c:89: warning: `struct iodesc' declared inside parameter list pxe.c:90: warning: `struct netif' declared inside parameter list pxe.c:100: elements of array `pxe_ifs' have incomplete type pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:102: invalid use of undefined type `struct netif_stats' pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:102: warning: excess elements in struct initializer pxe.c:102: warning: (near initialization for `pxe_ifs[0]') pxe.c:103: invalid use of undefined type `struct netif_dif' pxe.c:105: variable-size type declared outside of any function pxe.c:107: variable `pxenetif' has initializer but incomplete type pxe.c:108: warning: excess elements in struct initializer pxe.c:108: warning: (near initialization for `pxenetif') pxe.c:109: warning: excess elements in struct initializer pxe.c:109: warning: (near initialization for `pxenetif') pxe.c:110: warning: excess elements in struct initializer pxe.c:110: warning: (near initialization for `pxenetif') pxe.c:111: warning: excess elements in struct initializer pxe.c:111: warning: (near initialization for `pxenetif') pxe.c:112: warning: excess elements in struct initializer pxe.c:112: warning: (near initialization for `pxenetif') pxe.c:113: warning: excess elements in struct initializer pxe.c:113: warning: (near initialization for `pxenetif') pxe.c:114: warning: excess elements in struct initializer pxe.c:114: warning: (near initialization for `pxenetif') pxe.c:115: warning: excess elements in struct initializer pxe.c:115: warning: (near initialization for `pxenetif') pxe.c:117: warning: excess elements in struct initializer pxe.c:117: warning: (near initialization for `pxenetif') pxe.c: In function `pxe_open': pxe.c:256: `FNAME_SIZE' undeclared (first use in this function) pxe.c:256: (Each undeclared identifier is reported only once pxe.c:256: for each function it appears in.) pxe.c:276: `rootip' undeclared (first use in this function) pxe.c:283: `BOOTP_PXE' undeclared (first use in this function) pxe.c:286:
RE: pxe booting problem
On 30-Oct-01 Paul Jansen wrote: I posted some of this info last friday but haven't had any responses. I'm hoping someone out there knows what the problem is. Here's the details: I saw Alfred Perlsteins page on how to setup FreeBSD installs unsing PXE. The problem I'm having now is when I follow Alfred's directions to create the PXE loader (using 4.4R) It bombs out. It's my understanding the I just need to stick 'pxeldr' into the root of the TFTP server directory and tell the machine to execute this by specifying it as the boot file in the DHCP configuration. I also understand that I have to create a subdirectory called 'boot' under the TFTP root directory with the file 'loader.rc' in it. Can someone verify if this is the case? Alfred's instructions can be found here: http://people.freebsd.org/~alfred/pxe/ This is the console output that insues when I try and build pxeldr as per Alfred's instructions: You need pxeboot (not pxeldr, pxeldr is part of pxeboot). Do you have the sources for libstand (src/lib/libstand) installed? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use 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: pxe booting problem
Le Mardi 30 Octobre 2001 14:30, vous avez écrit :
I posted some of this info last friday but haven't had
any responses. I'm hoping someone out there knows
what the problem is. Here's the details:
I saw Alfred Perlsteins page on how to setup
FreeBSD installs unsing PXE.
The problem I'm having now is when I follow Alfred's
directions to create the PXE loader (using 4.4R) It
bombs out. It's my understanding the I just need to
stick 'pxeldr' into the root of the TFTP server
directory and tell the machine to execute this by
specifying it as the boot file in the DHCP
configuration. I also understand that I have to
create a subdirectory called 'boot' under the TFTP
root directory with the file 'loader.rc' in it. Can
someone verify if this is the case?
Alfred's instructions can be found here:
http://people.freebsd.org/~alfred/pxe/
This is the console output that insues when I try and
build pxeldr as per Alfred's instructions:
You can find pxeboot (instead of pxeldr) if /boot.
Just copy it into /tftpboot, and add the following in the dhcpd config file
(for isc-dhcp version 3):
option space PXE;
option PXE.mtftp-ipcode 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
class pxeclients {
match if substring (option vendor-class-identifier, 0, 9) =
PXEClient;
option vendor-class-identifier PXEClient;
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
next-server X.X.X.X;
server-name X.X.X.X;
server-identifier X.X.X.X;
option root-path /path/to/FreeBSD/CDROM;
filename pxeboot;
}
where X.X.X.X is the IP address of the tftp boot server.
Henri.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Vinum problem with JBOD on a 3ware?
I be stumped: newsfeed-inn# uname -a FreeBSD newsfeed-inn.meganews.com 4.4-STABLE FreeBSD 4.4-STABLE #0: Mon Oct 29 15:08:57 PST 2001 [EMAIL PROTECTED]:/n/FreeBSD/RELENG_4-2001-10-29/src/sys/compile/NEWSFEED-INN i386 Diskcontroller is a 3ware 7800, with 4 maxtor 20GB IDE's on it, which have all been scanned 1x with the maxblast software for a quick verification. newsfeed-inn# disklabel -r twed0 # /dev/twed0c: type: ESDI disk: twed0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 2490 sectors/unit: 40017852 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 400178520unused0 0 # (Cyl.0 - 2490*) d: 40016828 1024 vinum# (Cyl.0*- 2490*) newsfeed-inn# cat /root/vinum.config drive d1 device /dev/twed0d newsfeed-inn# vinum vinum - create -f /root/vinum.config 1: drive d1 device /dev/twed0d ** 1 Can't initialize drive d1: Operation not supported by device 0 drives: 0 volumes: 0 plexes: 0 subdisks: vinum - quit It gets weirder: newsfeed-inn# newfs -v /dev/twed0d newfs: /dev/twed0d: `d' partition is unavailable newsfeed-inn# newfs -v /dev/twed0c newfs: /dev/twed0c: `c' partition is unavailable newsfeed-inn# newfs /dev/twed0c Warning: Block size and bytes per inode restrict cylinders per group to 22. Warning: 68 sector(s) in last cylinder unallocated /dev/twed0c:40017852 sectors in 9770 cylinders of 1 tracks, 4096 sectors 19540.0MB in 445 cyl groups (22 c/g, 44.00MB/g, 10944 i/g) super-block backups (for fsck -b #) at: 32, 90144, 180256, 270368, 360480, 450592, 540704,^C newsfeed-inn# newfs /dev/twed0d Warning: Block size and bytes per inode restrict cylinders per group to 22. Warning: 1092 sector(s) in last cylinder unallocated /dev/twed0d:40016828 sectors in 9770 cylinders of 1 tracks, 4096 sectors 19539.5MB in 445 cyl groups (22 c/g, 44.00MB/g, 10944 i/g) super-block backups (for fsck -b #) at: 32, 90144, 180256, 270368, 360480, 450592, 540704,^C (A little surprised that newfs will newfs a non 4.2BSD/UFS labeled volume, but oh well). So I can newfs it, but I can't vinum it. I've tried zeroing out the label, and using sysinstall to put on the disklabel's, and using just disklabel -w -r auto. Can't get it to work. Note that if I uncomment d1-d4, they all fail in the same way. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: pxe booting problem
* Paul Jansen [EMAIL PROTECTED] [011030 08:31] wrote: I posted some of this info last friday but haven't had any responses. I'm hoping someone out there knows what the problem is. Here's the details: I saw Alfred Perlsteins page on how to setup FreeBSD installs unsing PXE. The problem I'm having now is when I follow Alfred's directions to create the PXE loader (using 4.4R) It bombs out. It's my understanding the I just need to stick 'pxeldr' into the root of the TFTP server directory and tell the machine to execute this by specifying it as the boot file in the DHCP configuration. I also understand that I have to create a subdirectory called 'boot' under the TFTP root directory with the file 'loader.rc' in it. Can someone verify if this is the case? Alfred's instructions can be found here: http://people.freebsd.org/~alfred/pxe/ This is the console output that insues when I try and build pxeldr as per Alfred's instructions: [snip] I'm not seeing this problem when I build from a full copy of the source tree. Perhaps you only have a subset? I also moved my obdir out of the way (mv /usr/obj /usr/obj.tmp) and did a make clean before make. good luck, -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: I will be in Europe and the UK from Nov 5th through Nov 14th.
On Tue, Oct 30, 2001 at 03:05:40PM +0100, Jose M. Alcaide wrote: On Mon, Oct 29, 2001 at 05:53:05PM -0800, Jordan Hubbard wrote: JFYI, Brett Halle (the director of CoreOS engineering for Apple) and I will be speaking at the NLUUG's Autumn Conference in Ede, The Netherlands on November 8th and then travelling on to BSDCon Europe in Brighton, UK immediately thereafter (the 9th) and staying in the UK until November 14th. JOKE To be exact, the subject should say ... in the Netherlands and the UK... since the UK is a part of Europe. Or, even better, in the Continent and the UK :-) :-) /JOKE I grant you that most of .nl is below sealevel, but we are _on_ the Continent :) [back to our regular scheduled time_t bikeshed now] -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: A question about multithreaded server
The typical solution is to create a pipe, and write a byte to it in order to wake up the manager thread. Jason To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
MPSAFE KLD syscall
Is there a correct way to mark a syscall as MPSAFE when loading it as a KLD? -- Chad David[EMAIL PROTECTED] ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: dummynet pipe show problem
On Tue, Oct 30, 2001 at 10:47:33AM -0800, rick norman wrote:
Hi,
I have enclosed a short piece of code that seems to
reproduce the problem after 5 to 10 minutes.
I am running 4.3 freebsd off the release cd's.
Pretty much the generic kernel except for the
addition of dummynet and ipfw. My platform
is a dell dimension 4100 with 1ghz p3, though
I doubt that is relevant. To reproduce the problem,
compile and run the enclosed code in one window.
In another window su to root and run ping -s 1024 -f 127.0.42.1.
As you will see, the code reports the gowing byte count as one
would expect. Walk away for 5 to 10 minutes and when you come
back you should see the state I'm talking about. The flood ping stream
It _might_ be a locking problem due to the frequent
reconfigurations of the pipe -- i think there was some
fix of this kind related to ipfw commands between 4.3 and 4.4.
I will see if i can reproduce the problem locally (but i have
4.4).
You are using dummynet in a very peculiar way:
more precisely, your pipe does not introduce any delay,
and this excludes the scheduler which is part of dummynet.
Also you are using the same pipe for icmp requests
and replies, which are generated within the kernel, so
the behaviour should be quite deterministic in this
respect.
thanks for the report
luigi
Thanks,
Rick
--cut
main() {
int i;
restart:
system(ifconfig lo0 -alias 127.0.42.1);
system(ifconfig lo0 alias 127.0.42.1 netmask 255.255.255.0);
system(ipfw -f flush);
system(ipfw pipe 1 delete);
system(ipfw add pipe 1 ip from 127.0.42.0/24 to any in);
for(i=0;i5;i++) {
system(ipfw pipe 1 config queue 2048Bytes);
sleep(1);
system(ipfw pipe 1 show);
}
goto restart;
}
cut--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: jail's /proc
This is fixed in 5.0-CURRENT, but the architectural improvements to support the fix have not been merged, since they're still in flux. My general advice is to not mount procfs on systems with untrusted users. It's almost possible to not lose functionality in doing that -- I understand DES has patches to truss to make it use ptrace(), which is the last remaining instance I can think of. (actually, I think ps -e requires procfs still) Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Mon, 29 Oct 2001, opr wrote: Hello, i really have no clue if i should mail this to you guys, but we've found some issue's in de jail's /proc. We were able to find information about processes running outside the jail, or running in other jails. eg. when i run sshd in the host system, and it has PID 655, i can login on the jail, and by execution ls -l /proc/665/file i can see what binary is running on pid 655. So any user of the jail system can see what processes you run on that server. I'm running FreeBSD 4.4-RELEASE on a i386. greetz, Pieter Danhieux Proof of concept shellscript: #!/bin/sh _COUNT=0; while [ $_COUNT -le 65000 ]; do if [ -f /proc/$_COUNT/file ]; then _USER=`/bin/ls -l /proc/$_COUNT/file | cut -d -f4`; _PROC=`/bin/ls -l /proc/$_COUNT/file | cut -d -f14`; echo PID= $_TELLER USER= $_USERPROC= $_PROC; fi _COUNT=`expr $_COUNT + 1`; done - [www.bsdaemon.be] - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
debugging question
Hi I suspect that there is some endless loop somewhere in my kernel (-CURRENT). I can escape to ddb but a trace ofcourse only goes back to spot where the ddb gets called from the keyboard. How can I see in what piece of the kernel it is looping? (I know about where it is, but not exactly) I hope that there is another way then to place printf's everywhere. Thanks Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging question
On Tue, 30 Oct 2001, Mark Santcroos wrote: :How can I see in what piece of the kernel it is looping? :(I know about where it is, but not exactly) : Use ddb to set a break -- you may need to do this upon boot (boot -d) *-. | Andrew R. Reiter | [EMAIL PROTECTED] | It requires a very unusual mind | to undertake the analysis of the obvious -- A.N. Whitehead To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging question
when the system is looping, hit CTLALTESC to drop into the debugger. On Tue, 30 Oct 2001, Andrew R. Reiter wrote: On Tue, 30 Oct 2001, Mark Santcroos wrote: :How can I see in what piece of the kernel it is looping? :(I know about where it is, but not exactly) : Use ddb to set a break -- you may need to do this upon boot (boot -d) *-. | Andrew R. Reiter | [EMAIL PROTECTED] | It requires a very unusual mind | to undertake the analysis of the obvious -- A.N. Whitehead To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
[Fwd: NSF Trusted Computing program]
Hi guys, maybe this is of interest for some in the FreeBSD community. Contract value is $4-6m. -- Andre [Forwarded from RISKS DIGEST 21.72] Date: Thu, 25 Oct 2001 14:56:01 -0400 From: Landwehr, Carl E. [EMAIL PROTECTED] Subject: NSF Trusted Computing program [Carl Landwehr, erstwhile security guru at the U.S. Naval Research Lab and more recently at Mitretek, is now on a one-year leave at the National Science Foundation, as Director of the Trusted Computing program. NSF is a good source of funding, and this procurement should be of interest to many RISKS readers. As always, I recommend that we focus on developing TRUSTWORTHY systems, not just UNTRUSTWORTHY systems that have to be TRUSTED because we have no alternative. PGN] The initial announcement for the new Trusted Computing program is at: http://www.nsf.gov/pubs/2001/nsf01160/nsf01160.html The deadline for proposals is 5 Dec 2001; if you are in a position to conduct research in this area, I encourage you to consider submitting a proposal. NSF focuses on funding research at universities and not-for-profit organizations. I also hope you will consider helping me staff the review panels for the proposals that are submitted. My new contact information is provided below; please use this e-mail address for future correspondence. Carl E. Landwehr, Program Director, Trusted Computing, CISE/CCR, Suite 1175 National Science Foundation, 4201 Wilson Blvd., Arlington, VA 22230 e-mail: [EMAIL PROTECTED] phone: 703-292-8936 fax: 703-292-9059 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Vinum problem with JBOD on a 3ware?
On Tuesday, 30 October 2001 at 8:26:14 -0800, Jaye Mathisen wrote: I be stumped: newsfeed-inn# uname -a FreeBSD newsfeed-inn.meganews.com 4.4-STABLE FreeBSD 4.4-STABLE #0: Mon Oct 29 15:08:57 PST 2001 [EMAIL PROTECTED]:/n/FreeBSD/RELENG_4-2001-10-29/src/sys/compile/NEWSFEED-INN i386 Diskcontroller is a 3ware 7800, with 4 maxtor 20GB IDE's on it, which have all been scanned 1x with the maxblast software for a quick verification. newsfeed-inn# cat /root/vinum.config drive d1 device /dev/twed0d newsfeed-inn# vinum vinum - create -f /root/vinum.config 1: drive d1 device /dev/twed0d ** 1 Can't initialize drive d1: Operation not supported by device Currently Vinum has to know about each kind of disk device before it will use it. It doesn't know about twed. I'll send you a patch. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Driver help
The company I work for is willing to pay for someone to write a Compaq Fibe Channel driver for FreeBSD. Please write me personally if you are interested. Nick Rogness [EMAIL PROTECTED] - Keep on Routing in a Free World... FreeBSD: The Power to Serve! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [Fwd: NSF Trusted Computing program]
Unfortunately, NSF is really interested in academic institutions and non-profits. NAI Labs, due to its association with NAI, counts as a for-profit entity, and is likely not to be applicable for this grant. With an appropriate academic or non-profit partner acting as the prime contractor, we could act as a sub-contractor and be applicable for funds, and there are a variety of useful activities this could cover relating to FreeBSD. Obviously, we would be interested in hearing from institutions that are appropriately qualified and interested in such a partnership. Interesting questions would include whether or not the FreeBSD Foundation is qualified. This is an opportunity we should not miss--if we don't get these funds, someone else will. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Wed, 31 Oct 2001, Andre Oppermann wrote: Hi guys, maybe this is of interest for some in the FreeBSD community. Contract value is $4-6m. -- Andre [Forwarded from RISKS DIGEST 21.72] Date: Thu, 25 Oct 2001 14:56:01 -0400 From: Landwehr, Carl E. [EMAIL PROTECTED] Subject: NSF Trusted Computing program [Carl Landwehr, erstwhile security guru at the U.S. Naval Research Lab and more recently at Mitretek, is now on a one-year leave at the National Science Foundation, as Director of the Trusted Computing program. NSF is a good source of funding, and this procurement should be of interest to many RISKS readers. As always, I recommend that we focus on developing TRUSTWORTHY systems, not just UNTRUSTWORTHY systems that have to be TRUSTED because we have no alternative. PGN] The initial announcement for the new Trusted Computing program is at: http://www.nsf.gov/pubs/2001/nsf01160/nsf01160.html The deadline for proposals is 5 Dec 2001; if you are in a position to conduct research in this area, I encourage you to consider submitting a proposal. NSF focuses on funding research at universities and not-for-profit organizations. I also hope you will consider helping me staff the review panels for the proposals that are submitted. My new contact information is provided below; please use this e-mail address for future correspondence. Carl E. Landwehr, Program Director, Trusted Computing, CISE/CCR, Suite 1175 National Science Foundation, 4201 Wilson Blvd., Arlington, VA 22230 e-mail: [EMAIL PROTECTED] phone: 703-292-8936 fax: 703-292-9059 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
/etc/ld.so.preload?
Is there anything in FreeBSD that gives this functionality? My reading of src/libexec/rtld-elf/rtld.c in both -stable and -current seems to indicate that there isn't any such functionality (i need the global functionality that LD_PRELOAD doesn't give me). I'd be willing to write a patch for it, but I'd need some guidance on what would be a proper way to fix it. I'm thinking of a patch to ldconfig to get /etc/ld.so.preload into the hints file and then to hack gethints() in rtld.c to take an argument indicating which path you want to return. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
ACPI CA updated
I've just updated the ACPI CA subsystem to the Intel 20011018 snapshot. This primarily fixes a couple of bugs in the ACPI interpreter; see the changelog at http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt for full details. These changes may fix some situations where: - Devices had wrong or invalid resources. - The interpreter failed to communicate with BIOS SMI code. - The system would fault on certain AML code. - Debugging output was incorrect. Please report any problems with this update to the ACPI list at [EMAIL PROTECTED] Regards, Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [PBS-USERS] Re: DRM standard API [was: SC2001 technical papers online]
Don't get me wrong. I am not against companies making money from selling products (even close source software), but I care how they market their products. I hope you still remember what M$ said about Linux+Apahce, and how it carefully set up the benchmark that showed Linux+Apache suck. If you want more information about what Platform people said, please go to: http://www.sun.com/software/gridware/support.html Technical Forums - Compute Farms - some comments overheard by Platform Computing rep. -Ron --- Richard Reigh [EMAIL PROTECTED] wrote: What I wanted to say was that there are a lot of companies aggressively making money, they don't really care about the technology. Let's not forget that Veridian is also in the business of making money. I've seen quite a few suggestions from their employees that the solution to a user's problem is to upgrade to PBS Pro. You may not like Platform's business practices, but at least their software doesn't suck like M$. ** Richard Reigh Systems Administrator II Human Genome Sequencing Center N1419 One Baylor Plaza Baylor College of Medicine Houston, TX 77030 -- Voice: 713.798.8086 FAX: 713.798.6977 ** __ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Driver help
On Tue, Oct 30, 2001 at 06:04:16PM -0600, Nick Rogness wrote: There is the isp(4) driver, by Matt Jacob, that supports Qlogic FC HBAs. The company I work for is willing to pay for someone to write a Compaq Fibe Channel driver for FreeBSD. Please write me personally if you are interested. Nick Rogness [EMAIL PROTECTED] - Keep on Routing in a Free World... FreeBSD: The Power to Serve! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message ---end of quoted text--- -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: /etc/ld.so.preload?
Well, here's a short patch to add the necessarily functionality to
/var/run/ld-elf.so.hints and /usr/libexec/ld-elf.so.1. If this is
acceptable, /sbin/ldconfig would need to be patched.
Looks like the major bug is that if you preload libraries globally you
break linux binary compatibility.
On Tue, 30 Oct 2001, Lamont Granquist wrote:
Is there anything in FreeBSD that gives this functionality? My reading of
src/libexec/rtld-elf/rtld.c in both -stable and -current seems to indicate
that there isn't any such functionality (i need the global functionality
that LD_PRELOAD doesn't give me). I'd be willing to write a patch for it,
but I'd need some guidance on what would be a proper way to fix it.
I'm thinking of a patch to ldconfig to get /etc/ld.so.preload into the
hints file and then to hack gethints() in rtld.c to take an argument
indicating which path you want to return.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--- include/elf-hints.h~Tue Oct 30 18:29:57 2001
+++ include/elf-hints.h Tue Oct 30 18:31:47 2001
@@ -40,7 +40,10 @@
u_int32_t dirlist;/* Offset of directory list in
string table */
u_int32_t dirlistlen; /* strlen(dirlist) */
- u_int32_t spare[26]; /* Room for expansion */
+ u_int32_t preloadlist;/* Offset of preload list in
+ string table */
+ u_int32_t preloadlistlen; /* strlen(preloadlist) */
+ u_int32_t spare[24]; /* Room for expansion */
};
#define ELFHINTS_MAGIC 0x746e6845
--- libexec/rtld-elf/rtld.c~Tue Oct 30 18:28:00 2001
+++ libexec/rtld-elf/rtld.c Tue Oct 30 21:06:39 2001
@@ -52,8 +52,10 @@
#include debug.h
#include rtld.h
-#define END_SYM_end
-#define PATH_RTLD /usr/libexec/ld-elf.so.1
+#define END_SYM_end
+#define PATH_RTLD /usr/libexec/ld-elf.so.1
+#define HINT_LIBRARY_PATH 0x01
+#define HINT_PRELOAD 0x02
/* Types. */
typedef void (*func_ptr_type)();
@@ -80,7 +82,7 @@
static void errmsg_restore(char *);
static char *errmsg_save(void);
static char *find_library(const char *, const Obj_Entry *);
-static const char *gethints(void);
+static char *gethints(int);
static void init_dag(Obj_Entry *);
static void init_dag1(Obj_Entry *root, Obj_Entry *obj, DoneList *);
static void init_rtld(caddr_t);
@@ -91,7 +93,7 @@
static void linkmap_add(Obj_Entry *);
static void linkmap_delete(Obj_Entry *);
static int load_needed_objects(Obj_Entry *);
-static int load_preload_objects(void);
+static int load_preload_objects(char *);
static Obj_Entry *load_object(char *);
static void lock_check(void);
static Obj_Entry *obj_from_addr(const void *);
@@ -359,7 +361,9 @@
sym_zero.st_shndx = SHN_ABS;
dbg(loading LD_PRELOAD libraries);
-if (load_preload_objects() == -1)
+if (load_preload_objects(ld_preload) == -1)
+ die();
+if (load_preload_objects(gethints(HINT_PRELOAD)) == -1)
die();
preload_tail = obj_tail;
@@ -805,7 +809,7 @@
if ((refobj != NULL
(pathname = search_library_path(name, refobj-rpath)) != NULL) ||
(pathname = search_library_path(name, ld_library_path)) != NULL ||
- (pathname = search_library_path(name, gethints())) != NULL ||
+ (pathname = search_library_path(name, gethints(HINT_LIBRARY_PATH))) != NULL ||
(pathname = search_library_path(name, STANDARD_LIBRARY_PATH)) != NULL)
return pathname;
@@ -873,18 +877,20 @@
* necessary. Returns NULL if there are problems with the hints file,
* or if the search path there is empty.
*/
-static const char *
-gethints(void)
+static char *
+gethints(int hintflag)
{
-static char *hints;
+static char *preload;
+static char *library_path;
-if (hints == NULL) {
+if ((library_path == NULL) || (preload == NULL)) {
int fd;
struct elfhints_hdr hdr;
char *p;
/* Keep from trying again in case the hints file is bad. */
- hints = ;
+ library_path = ;
+ preload = ;
if ((fd = open(_PATH_ELF_HINTS, O_RDONLY)) == -1)
return NULL;
@@ -901,10 +907,25 @@
close(fd);
return NULL;
}
- hints = p;
+ library_path = p;
+ p = xmalloc(hdr.preloadlistlen + 1);
+ if (lseek(fd, hdr.strtab + hdr.preloadlist, SEEK_SET) == -1 ||
+ read(fd, p, hdr.preloadlistlen + 1) != hdr.preloadlistlen + 1) {
+ free(p);
+ close(fd);
+ return NULL;
+ }
+ preload = p;
close(fd);
}
-return hints[0] != '\0' ? hints : NULL;
+switch (hintflag) {
+ case HINT_LIBRARY_PATH:
+ return library_path[0]
Re: pxe booting problem
Le Mardi 30 Octobre 2001 17:17, vous avez écrit : configuration. I also understand that I have to create a subdirectory called 'boot' under the TFTP root directory with the file 'loader.rc' in it. Can someone verify if this is the case? Sorry. Forget this part. This is the content my /path/to/FreeBSD/CDROM : - The entire content of the original CDROM - A custom mfsroot with install.cfg - A custom kernel with 'options MD_ROOT' - A directory called 'boot' with the following files (from /boot): boot1 boot2 loader loader.rc Henri To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging question
Thats what I already said in my email :) I was hoping that there is some way to dump the codepath of the kernel. Or is it maybe possible from ddb to move the context of a certain process and trace from there? Mark ps. I have narrowed it down already a bit more and hope to come with a bug report on -current in the coming days. On Tue, Oct 30, 2001 at 03:38:45PM -0800, Julian Elischer wrote: when the system is looping, hit CTLALTESC to drop into the debugger. On Tue, 30 Oct 2001, Andrew R. Reiter wrote: On Tue, 30 Oct 2001, Mark Santcroos wrote: :How can I see in what piece of the kernel it is looping? :(I know about where it is, but not exactly) : Use ddb to set a break -- you may need to do this upon boot (boot -d) *-. | Andrew R. Reiter | [EMAIL PROTECTED] | It requires a very unusual mind | to undertake the analysis of the obvious -- A.N. Whitehead To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Simple pthread question
How do I suspend one particular thread without suspending the whole process? I can not use sleep or usleep can I? TIA Arjan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
