Re: How to read a file from a device driver?

2000-03-17 Thread Mark Newton

On Fri, Mar 17, 2000 at 11:00:08PM -0500, Gary T. Corcoran wrote:

 > Can someone please tell me how I can read a file from a device driver
 > in FreeBSD?  I need to download 2 or 3 relatively-large code files to
 > my device, choosing from amongst several different files depending on
 > which mode I'm operating in.  Therefore compiling-in the code is not
 > a reasonable choice.
 
Defer the initialization of the device until a user-mode process opens
it and performs an ioctl() on it.  The ioctl should take a (void *) to
a buffer containing a structure which says how long the code is, followed
by the code itself.  That avoids the whole problem of reading a file from
your driver, you can do it with a user-mode helper process.

 > If you can either tell me how to be able to read a file from my driver,
 > or point me to an example driver which does this, I would appreciate it.

I think the Stallion serial port drivers do something kinda similar.

- mark

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


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



Re: How to read a file from a device driver?

2000-03-17 Thread Matthew N. Dodd

On Sat, 18 Mar 2000, Gary T. Corcoran wrote:
> Ugh.  This isn't the answer I was looking for...  :-( ;-) I can do
> this in Windows (the original driver), I can do this in Linux (our new
> port) via a slight kluge which temporarily fiddles with the segment
> pointers (via standard system routines) to make it seem as if our
> driver's buffer is in user space so that the standard system read()
> can be called.

Again, your best bet is to look at how the QUOTA stuff works; it reads and
writes to the quota files.

Heres the problem though;

If you compile your kernel in, the root filesystem isn't mounted until
after your drivers probe/attach routines have been called.

It would be better if you made your firmware a KLD so that it can be
loaded by the loader or demand loaded by the kernel linker when your
driver is loaded.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



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



Re: How to read a file from a device driver?

2000-03-17 Thread Alfred Perlstein

* Gary T. Corcoran <[EMAIL PROTECTED]> [000317 21:46] wrote:
> 
> "Matthew N. Dodd" wrote:
> > 
> > On Fri, 17 Mar 2000, Gary T. Corcoran wrote:
> > > I'm trying to initialize a network device, and I'm trying to download
> > > code *into* my device from some binary system files.  There is no
> > > "user space" or user process, for that matter, to deal with at this
> > > point. I just want to (at this step) open a file(s) directly from my
> > > device driver, read the file(s), and download the relevant parts to my
> > > device.
> > 
> > There isn't really any clean way of doing this so most drivers that need
> > to load firmware usually compile them in.  :/
> 
> Ugh.  This isn't the answer I was looking for...  :-(   ;-)
> I can do this in Windows (the original driver), I can do this in Linux
> (our new port) via a slight kluge which temporarily fiddles with the segment
> pointers (via standard system routines) to make it seem as if our driver's
> buffer is in user space so that the standard system read() can be called.
> 
> You mean I really can't do a relatively simple thing like read a file
> (which the _kernel_ really does, if you think about it) in my favorite
> operating system??  There's gotta be a way for a driver to do a read(),
> isn't there? :)  BTW, I did a search on the email archives, and Mike Smith
> implied that there *is* a way to read a file from a driver, but he only
> made a vague reference to a driver that did same, and I wasn't able to
> find any example code to give me a clue...

You're just going to have to grovel through the code somewhat,
sendfile is sort of useful but you must have an already open file
handle.  There's other code you can get to do that, like the quota
system (i'm pretty sure).

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]


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



Re: How to read a file from a device driver?

2000-03-17 Thread Gary T. Corcoran


"Matthew N. Dodd" wrote:
> 
> On Fri, 17 Mar 2000, Gary T. Corcoran wrote:
> > I'm trying to initialize a network device, and I'm trying to download
> > code *into* my device from some binary system files.  There is no
> > "user space" or user process, for that matter, to deal with at this
> > point. I just want to (at this step) open a file(s) directly from my
> > device driver, read the file(s), and download the relevant parts to my
> > device.
> 
> There isn't really any clean way of doing this so most drivers that need
> to load firmware usually compile them in.  :/

Ugh.  This isn't the answer I was looking for...  :-(   ;-)
I can do this in Windows (the original driver), I can do this in Linux
(our new port) via a slight kluge which temporarily fiddles with the segment
pointers (via standard system routines) to make it seem as if our driver's
buffer is in user space so that the standard system read() can be called.

You mean I really can't do a relatively simple thing like read a file
(which the _kernel_ really does, if you think about it) in my favorite
operating system??  There's gotta be a way for a driver to do a read(),
isn't there? :)  BTW, I did a search on the email archives, and Mike Smith
implied that there *is* a way to read a file from a driver, but he only
made a vague reference to a driver that did same, and I wasn't able to
find any example code to give me a clue...

Thanks,
Gary


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



Re: How to read a file from a device driver?

2000-03-17 Thread Wes Peters

"Gary T. Corcoran" wrote:
> 
> I'm trying to initialize a network device, and I'm trying to download
> code *into* my device from some binary system files.  There is no
> "user space" or user process, for that matter, to deal with at this point.
> I just want to (at this step) open a file(s) directly from my device
> driver, read the file(s), and download the relevant parts to my device.

Can you repackage the binary as a data-only kld, with a couple of public
symbols wrapping the beginning and end of the binary, or a couple of
symbols with start and length?  You could then have the loader pre-
load the .ko at boot time.

The only other way is to wait until the system is up and load the code
into your driver through an ioctl.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


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



Re: How to read a file from a device driver?

2000-03-17 Thread Alfred Perlstein

* Matthew N. Dodd <[EMAIL PROTECTED]> [000317 21:22] wrote:
> On Fri, 17 Mar 2000, Gary T. Corcoran wrote:
> > I'm trying to initialize a network device, and I'm trying to download
> > code *into* my device from some binary system files.  There is no
> > "user space" or user process, for that matter, to deal with at this
> > point. I just want to (at this step) open a file(s) directly from my
> > device driver, read the file(s), and download the relevant parts to my
> > device.
> 
> There isn't really any clean way of doing this so most drivers that need
> to load firmware usually compile them in.  :/

Now that I think about it, with FreeBSD's ability to dynamically load
and unload modules it would seem like using anything else would be
pretty annoying unless there's something else we don't understand here.

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]


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



Re: How to read a file from a device driver?

2000-03-17 Thread Kenneth D. Merry

On Fri, Mar 17, 2000 at 23:59:28 -0500, Matthew N. Dodd wrote:
> On Fri, 17 Mar 2000, Gary T. Corcoran wrote:
> > I'm trying to initialize a network device, and I'm trying to download
> > code *into* my device from some binary system files.  There is no
> > "user space" or user process, for that matter, to deal with at this
> > point. I just want to (at this step) open a file(s) directly from my
> > device driver, read the file(s), and download the relevant parts to my
> > device.
> 
> There isn't really any clean way of doing this so most drivers that need
> to load firmware usually compile them in.  :/

True enough.  The Alteon Tigon driver (sys/pci/if_ti.c) decides which one
of its firmware images (sys/pci/{ti_fw,ti_fw2}.h) based on the chip
revision.

So that's one possible example to look at.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


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



Re: AMD Athlon and booting

2000-03-17 Thread Annelise Anderson

Just FYI, my Athlon K7-700 with the ASUS motherboard won't boot
with an old IBM keyboard unless the reset button is pressed; the
screen remains blank.  The ASUS web page says this happens in
certain combinations of keyboards and ATX power supplies.  With
another keyboard it's fine.

Annelise

On Fri, 17 Mar 2000, Mike Smith wrote:

> > > "Mike" == Mike Smith <[EMAIL PROTECTED]> writes:
> > 
> > Mike> This has nothing to do with Athlon processors and everything to do with 
> > Mike> buggy BIOS code that doesn't set the "extended keyboard present" bit.  
> > Mike> Feel free to check the (very simple) code in boot2 that performs keyboard 
> > Mike> detection, and if you've got any better ideas on how to make this work 
> > Mike> properly, we're all ears. 8)
> > 
> > This is untrue, at least in general.  It is a timing problem at least
> > on some Athlon boards.  On the MSI 6195, if you increase the timing
> > parameters in probe_keyboard.c, the keyboard will get detected just fine.
> 
> I don't know what you're smoking, but there is no "probe_keyboard.c" 
> involved in this.  The keyboard probe code is in boot2.c, and it looks 
> like this:
> 
>313  if (opts & 1 << RBX_PROBEKBD) {
>314  i = *(uint8_t *)PTOV(0x496) & 0x10;
>315  printf("Keyboard: %s\n", i ? "yes" : "no");
>316  if (!i)
>317  opts |= 1 << RBX_DUAL | 1 << RBX_SERIAL;
>318  opts &= ~(1 << RBX_PROBEKBD);
>319  }
> 
> There aren't any timing parameters there either.  Either bit 4 in the 
> byte at 0x400:96 is set, or it's not.
> 
> -- 
> \\ Give a man a fish, and you feed him for a day. \\  Mike Smith
> \\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]
> 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
> 



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



Re: How to read a file from a device driver?

2000-03-17 Thread Matthew N. Dodd

On Fri, 17 Mar 2000, Gary T. Corcoran wrote:
> I'm trying to initialize a network device, and I'm trying to download
> code *into* my device from some binary system files.  There is no
> "user space" or user process, for that matter, to deal with at this
> point. I just want to (at this step) open a file(s) directly from my
> device driver, read the file(s), and download the relevant parts to my
> device.

There isn't really any clean way of doing this so most drivers that need
to load firmware usually compile them in.  :/

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



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



Re: How to read a file from a device driver?

2000-03-17 Thread Alfred Perlstein

* Gary T. Corcoran <[EMAIL PROTECTED]> [000317 20:54] wrote:
> 
> Alfred,
> 
> > > Can someone please tell me how I can read a file from a device driver
> > > in FreeBSD?  I need to download 2 or 3 relatively-large code files to
> > > my device, choosing from amongst several different files depending on
> > > which mode I'm operating in.  Therefore compiling-in the code is not
> > > a reasonable choice.
> > >
> > > If you can either tell me how to be able to read a file from my driver,
> > > or point me to an example driver which does this, I would appreciate it.
> > >
> > > I'm running FreeBSD 3.4.
> > >
> > > (not subscribed to this list, please always CC: me on replies)
> > 
> > I hope i'm not advocating abusing an interface here, but here's what
> > comes to mind...
> > 
> > Use an ioctl in your driver to pass in a pointer to your user
> > address space which depending on the ioctl request the size of the
> > file be written to the pointer, or that the pointer is where the
> > device should copyout() or use one of the functions from STORE(9)
> > to dump into the user address space.
> 
> Sorry, but either I'm not understanding what you're suggesting, or
> I didn't explain my need clearly...  ;-)

I had an inverted sense of what you wanted to accomplish, i thought
you had several different chunks of data that needed to be downloaded
from the driver.

> 
> I'm trying to initialize a network device, and I'm trying to download
> code *into* my device from some binary system files.  There is no
> "user space" or user process, for that matter, to deal with at this point.
> I just want to (at this step) open a file(s) directly from my device
> driver, read the file(s), and download the relevant parts to my device.
> 
> Does that change your answer?  :-)

Yes, in a couple of ways:

a) you can use a userland program to copy the data in like I suggested
   above, but you'll obviously be using 'fubyte' or 'copyin' instead of
   subyte or copyout (easiest)
b) you can make the datafiles into some sort of kernel loadable module (so so)
   you can load your module via the loader or once the system is up.
c) you can look at NAMEI and the fs code to figure out how this is done,
   one subsystem that manipulates files from kernel space is the quota
   system.
d) ? :)

good luck,
-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]


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



Re: How to read a file from a device driver?

2000-03-17 Thread Gary T. Corcoran


Alfred,

> > Can someone please tell me how I can read a file from a device driver
> > in FreeBSD?  I need to download 2 or 3 relatively-large code files to
> > my device, choosing from amongst several different files depending on
> > which mode I'm operating in.  Therefore compiling-in the code is not
> > a reasonable choice.
> >
> > If you can either tell me how to be able to read a file from my driver,
> > or point me to an example driver which does this, I would appreciate it.
> >
> > I'm running FreeBSD 3.4.
> >
> > (not subscribed to this list, please always CC: me on replies)
> 
> I hope i'm not advocating abusing an interface here, but here's what
> comes to mind...
> 
> Use an ioctl in your driver to pass in a pointer to your user
> address space which depending on the ioctl request the size of the
> file be written to the pointer, or that the pointer is where the
> device should copyout() or use one of the functions from STORE(9)
> to dump into the user address space.

Sorry, but either I'm not understanding what you're suggesting, or
I didn't explain my need clearly...  ;-)

I'm trying to initialize a network device, and I'm trying to download
code *into* my device from some binary system files.  There is no
"user space" or user process, for that matter, to deal with at this point.
I just want to (at this step) open a file(s) directly from my device
driver, read the file(s), and download the relevant parts to my device.

Does that change your answer?  :-)

Thanks,
Gary


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



Re: How to read a file from a device driver?

2000-03-17 Thread Alfred Perlstein

* Gary T. Corcoran <[EMAIL PROTECTED]> [000317 20:16] wrote:
> 
> Can someone please tell me how I can read a file from a device driver
> in FreeBSD?  I need to download 2 or 3 relatively-large code files to
> my device, choosing from amongst several different files depending on
> which mode I'm operating in.  Therefore compiling-in the code is not
> a reasonable choice.
> 
> If you can either tell me how to be able to read a file from my driver,
> or point me to an example driver which does this, I would appreciate it.
> 
> I'm running FreeBSD 3.4.
> 
> (not subscribed to this list, please always CC: me on replies)

I hope i'm not advocating abusing an interface here, but here's what
comes to mind...

Use an ioctl in your driver to pass in a pointer to your user
address space which depending on the ioctl request the size of the
file be written to the pointer, or that the pointer is where the
device should copyout() or use one of the functions from STORE(9)
to dump into the user address space.

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]


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



How to read a file from a device driver?

2000-03-17 Thread Gary T. Corcoran


Can someone please tell me how I can read a file from a device driver
in FreeBSD?  I need to download 2 or 3 relatively-large code files to
my device, choosing from amongst several different files depending on
which mode I'm operating in.  Therefore compiling-in the code is not
a reasonable choice.

If you can either tell me how to be able to read a file from my driver,
or point me to an example driver which does this, I would appreciate it.

I'm running FreeBSD 3.4.

(not subscribed to this list, please always CC: me on replies)

Thanks,
Gary Corcoran


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



Re: Why not gzip iso images?

2000-03-17 Thread Andy

"Daniel C. Sobral" wrote:

At this point, I'd just like to see the iso available, I don't care if
it is compressed or not. :P

> To ALL PEOPLE complaining about the size:

-- 

|  Andy   | e-mail  |  web   |
| | [EMAIL PROTECTED] | www.lewman.com |

You will remember, Watson, how the dreadful business of the
Abernetty family was first brought to my notice by the depth which the
parsley had sunk into the butter upon a hot day.
-- Sherlock Holmes
 S/MIME Cryptographic Signature


Re: Why not gzip iso images?

2000-03-17 Thread Daniel C. Sobral

To ALL PEOPLE complaining about the size:

Paul Robinson wrote:
> 
> If you save 20Mb, over a reliable 56Kb modem, you've saved them somewhere
> in the region of one and a half hours... I think you guys are too used to
> your broadband... :)

If you don't want to download 650 Mb, DON'T DOWNLOAD THE ISO IMAGE!!!
Download the two 1.44 Mb floppy disk images, and INSTALL FROM FTP.
You'll get to select what bits you want, and thus save A LOT of time.

Why ISO images, then? Because some people download these images from
work/university, where they have broadband access, to install them at
home. For these people, the darned 20 Mb out of 650 won't matter.

This is a classic case of much ado about nothing. Go take reality check
pills, everyone.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone bind them.


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



Re: AMD Athlon and booting

2000-03-17 Thread Mike Smith

> > "Mike" == Mike Smith <[EMAIL PROTECTED]> writes:
> 
> Mike> This has nothing to do with Athlon processors and everything to do with 
> Mike> buggy BIOS code that doesn't set the "extended keyboard present" bit.  
> Mike> Feel free to check the (very simple) code in boot2 that performs keyboard 
> Mike> detection, and if you've got any better ideas on how to make this work 
> Mike> properly, we're all ears. 8)
> 
> This is untrue, at least in general.  It is a timing problem at least
> on some Athlon boards.  On the MSI 6195, if you increase the timing
> parameters in probe_keyboard.c, the keyboard will get detected just fine.

I don't know what you're smoking, but there is no "probe_keyboard.c" 
involved in this.  The keyboard probe code is in boot2.c, and it looks 
like this:

   313  if (opts & 1 << RBX_PROBEKBD) {
   314  i = *(uint8_t *)PTOV(0x496) & 0x10;
   315  printf("Keyboard: %s\n", i ? "yes" : "no");
   316  if (!i)
   317  opts |= 1 << RBX_DUAL | 1 << RBX_SERIAL;
   318  opts &= ~(1 << RBX_PROBEKBD);
   319  }

There aren't any timing parameters there either.  Either bit 4 in the 
byte at 0x400:96 is set, or it's not.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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



procmap - Where does it belong?

2000-03-17 Thread Jason Evans

A couple of months ago I was doing some work on guard pages in libc_r and
discovered that using 'cat' to view the VM map for a process is
unreliable.  This fact is documented in the proc code, and there is even an
explanation of how to reliably read the map files.  However, I could find
no program that actually does this, so I wrote one.

The program is attached (yes, it needs a man page if it is to be imported),
but my question is whether it belongs in the source tree, and if so, where?

Thanks,
Jason


/*
 * Copyright (C) 2000 Jason Evans <[EMAIL PROTECTED]>.
 * All rights reserved.
 * 
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *notice(s), this list of conditions and the following disclaimer as
 *the first lines of this file unmodified other than the possible
 *addition of one or more copyright notices.
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice(s), this list of conditions and the following disclaimer in
 *the documentation and/or other materials provided with the
 *distribution.
 * 
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER(S) ``AS IS'' AND ANY
 * EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDER(S) BE
 * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
 * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
 * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
 * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
 * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 * $FreeBSD$
 */

#include 
#include 
#include 

#define MAXPATH 18
#define MINBUF 4096

int
main(int argc, char ** argv)
{
char * buf;
char path[MAXPATH] = "/proc/"; /* Big enough for "/proc/curproc/map". */
int mfd, bytes, size = MINBUF;

if (argc != 2) {
fprintf(stderr, "usage: procmap { | curproc}\n");
exit(1);
} else if (strlen(argv[1]) > 7) {
fprintf(stderr, "procmap:  too long.\n");
fprintf(stderr, "usage: procmap { | curproc}\n");
exit(1);
}

/* Open the map file. */
snprintf(path, MAXPATH, "/proc/%s/map", argv[1]);
mfd = open(path, O_RDONLY);
if (mfd < 0) {
fprintf(stderr, "Unable to open() %s: %s\n",
path, strerror(errno));
exit(1);
}

/*
 * Start out with a MINBUF byte buffer, and double the buffer size until
 * it's big enough to read the whole map at once.
 */
buf = (char *) malloc(size);
if (buf == NULL) {
fprintf(stderr, "malloc() error\n");
exit(1);
}
bzero(buf, size);

while (1) {
if (lseek(mfd, 0, SEEK_SET) < 0) {
fprintf(stderr, "lseek() error: %s\n",
strerror(errno));
exit(1);
}
/* Leave space for a NULL terminator at the end of buf. */
if (bytes = read(mfd, buf, size - 1) < 0) {
if (errno == EFBIG) {
/* Buffer to small; try again. */
size <<= 1;
buf = (char *) realloc(buf, size);
if (buf == NULL) {
fprintf(stderr, "realloc() error\n");
exit(1);
}
bzero(buf, size);
} else {
fprintf(stderr, "read() error: %s\n",
strerror(errno));
exit(1);
}
} else {
/* Success.  The results are in buf. */
break;
}
}

/*
 * Write out a header.
 *
 * format: start, end, resident, private resident, cow, access, type.
 */
printf("start end resident priv_res cow access type\n");
printf("%s", buf);

return 0;
}



Re: SendMail

2000-03-17 Thread Leif Neland

Which server do you get that message from?
Your own?
Your isp?
A complete stranger, you are trying to use as smarthost?

- Original Message - 
From: "Rafael Gomez" <[EMAIL PROTECTED]>
To: "FreeBSD Hackers" <[EMAIL PROTECTED]>
Sent: Thursday, March 16, 2000 7:42 PM
Subject: SendMail


> Everytime i try to send an email out of my server the answer is "Relaying
> Denied".
> 
> Can any of yuo help me in order to fix this error or let me know where I can
> find out the solution?
> 
> Thanks in advance
> 
> Rafael Gomez
> [EMAIL PROTECTED]
> Pager: [EMAIL PROTECTED]
> Charter Communications International Venezuela
> 
> Tel: 58-2-576.60.80
> Fax: 58-2-572.43.43
> 
> 
> 
> 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: T/TCP friendly inetd change?

2000-03-17 Thread David Malone

> I like T/TCP (I use it on some of my networked apps for the same reasons you
> describe), but I don't think that it should be added to a program like inetd
> which has two default settings that would need to be changed before the
> T/TCP extensions would ever provide any benefit.

The changes I've suggested don't actually require T/TCP to be useful,
they just make inetd friendlier to T/TCP connections if they come in.
When T/TCP isn't used they just put the FIN for the TCP connection on
the last data packet, instead of on a seperate packet, so saving one
packet.

David.


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



RE: kERNEL

2000-03-17 Thread Alton, Matthew

What on Earth are you talking about?

> -Original Message-
> From: Rafael Gomez [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, March 17, 2000 07:10
> To:   FreeBSD Hackers
> Subject:  kERNEL
> 
> Can any of you send me a copy of a text kernel file?
> 
> Rafael Gomez
> [EMAIL PROTECTED]
> Pager: [EMAIL PROTECTED]
> Charter Communications International Venezuela
> 
> Tel: 58-2-576.60.80
> Fax: 58-2-572.43.43 
> 
> 
> 
> 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



Bootable CD Question

2000-03-17 Thread Chad David


I have a custom kernel that I need to have boot from a cd across as many
machines as possible.  I currently build the cd using scripts adapted from
what is in src/release, (I now owe Poul-Henning more than one beer), and
it boots every time in the lab, but people testing are reporting that it
will not boot on even newer machines.  I realize that having a cd boot in
the PC world is an ify proposition, but does anybody have any tips on how
how to burn a more "reliable" bootable cd.

I am using mkisofs 1.12 with the following flags:
mkisofs -b floppies/boot.flp -c floppies/boot.catalog -d -N -D -R -T -l -V
'"Test"' -P '"Copyright"' -o ${BASE}/../../isoimages/image.iso ${BASE}

and cdrecord 1.8 with the following flags:
cdrecord speed=4 -v -data -multi dev=0,4,0 image.iso


I realize this might be more apropriate on questions, but if I don't solve
or at least have a better story about this problem very soon there may be
one less application available for FreeBSD, and I am working very hard
trying to prevent that :).

Thanks.

Chad



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



Netbooting FreeBSD 4.0/Intel?

2000-03-17 Thread Matthew Zahorik

This was originally posted to freebsd-questions, but I didn't get a
response.  I'm hoping that someone in here has successfully netbooted a
FreeBSD 4.0-RELEASE box on Intel EtherExpress Pro 100+ cards and can share
their story.

Since I wrote this message, I have tried etherboot 4.4.5.  Still no go.

- Matt

--
Matthew Zahorik  Director of Systems and Networking - BiznessOnline.com
[EMAIL PROTECTED]  President of AlbanyNet Inc. - a BiznessOnline subsidiary
[EMAIL PROTECTED]Voice: (518) 292-1001  Fax: (518) 626-0793
- Original Message -
From: "Matthew Zahorik" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 16, 2000 1:40 PM
Subject: Netbooting FreeBSD 4.0/Intel?


: Does anyone have a howto on netbooting FreeBSD 4.0/Intel with Etherboot?
:
: I've easily managed to netboot my FreeBSD 4.0/Alpha boxes with the
included
: Alpha SRM netboot utility.  I really like the bootp/NFS solution used by
: netboot.  It's quite clean, especially since I'm mounting root from this
: same box.
:
: My Intel boxes are proving to be more difficult.
:
: Netboot is depreciated on Intel, and doesn't even seem to compile on
FreeBSD
: 4.0.  Either way, it doesn't support the Intel Pro/100+ cards (82559
based)
: I have in my Intel boxes.  No bootp/NFS for the Intel boxes. :-(
:
: So I turned to Etherboot as suggested in many Usenet postings and the list
: archives.
:
: I hand compiled the latest, etherboot 4.4.4.  That didn't work.  (see
below)
:
: I used ports to install etherboot 4.2.13.  (Had to change the Makefile
since
: it specifies 4.2.11, which isn't available anymore)  This too didn't work.
:
: In both cases, I wrote floppyload.bin and eepro100.lzrun to a floppy.
: Etherboot starts, gets its IP address from bootp, TFTP's the kernel,
quickly
: says "Loading Segment 1", "Loading Segment 2", "Loading Segment 3", and
then
: promptly reboots the machine.
:
: The kernel is compiled with all the option BOOTP.* bits - it should work.
I've even
: tried the generic kernel that I used to boot the server, knowing it would
crash when trying
: to mount root, but at least I'd see *something*.  No go.
:
: So, if anyone has any pointers or a list of things you did to get this
work,
: I'd appreciate it.
:
: Thanks!
:
: - Matt
:
: --
: Matthew Zahorik  Director of Systems and Networking - BiznessOnline.com
: [EMAIL PROTECTED]  President of AlbanyNet Inc. - a BiznessOnline subsidiary
: [EMAIL PROTECTED]Voice: (518) 292-1001  Fax: (518) 626-0793




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



Re: kERNEL

2000-03-17 Thread Kelly Yancey

On Fri, 17 Mar 2000, Rafael Gomez wrote:

> Can any of you send me a copy of a text kernel file?
> 

  I can't quite parse what exactly you are looking for. The kernel itself
is binary executable code. However, kernel config files are text files
that indicate the config(8) what bits to compile into the kernel. If you
have the FreeBSD kernel sources installed, you should have kernel config
files in /sys/i386/conf. If you don't have the kernel sources installed,
then having a kernel config file is quite useless.

  Kelly

--
Kelly Yancey  -  [EMAIL PROTECTED]  -  Richmond, VA
Analyst / E-business Development, Bell Industries  http://www.bellind.com/
Maintainer, BSD Driver Database   http://www.posi.net/freebsd/drivers/
Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/



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



Re: AMD Athlon and booting

2000-03-17 Thread Michael Sperber [Mr. Preprocessor]

> "Mike" == Mike Smith <[EMAIL PROTECTED]> writes:

Mike> This has nothing to do with Athlon processors and everything to do with 
Mike> buggy BIOS code that doesn't set the "extended keyboard present" bit.  
Mike> Feel free to check the (very simple) code in boot2 that performs keyboard 
Mike> detection, and if you've got any better ideas on how to make this work 
Mike> properly, we're all ears. 8)

This is untrue, at least in general.  It is a timing problem at least
on some Athlon boards.  On the MSI 6195, if you increase the timing
parameters in probe_keyboard.c, the keyboard will get detected just fine.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla


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



kERNEL

2000-03-17 Thread Rafael Gomez

Can any of you send me a copy of a text kernel file?

Rafael Gomez
[EMAIL PROTECTED]
Pager: [EMAIL PROTECTED]
Charter Communications International Venezuela

Tel: 58-2-576.60.80
Fax: 58-2-572.43.43 



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