On Thu 1999-12-09 (02:46), Robert Watson wrote:
Once we get into boot2 land, I recognize the FreeBSD-specific loading
code, etc. What I don't know much about is those first three 512-byte
chunks of code. Boot0 appears to be booteasy, but given some ignorance
about the i386 boot process, I'm
On Thu, 9 Dec 1999, Neil Blakey-Milner wrote:
On Thu 1999-12-09 (02:46), Robert Watson wrote:
Once we get into boot2 land, I recognize the FreeBSD-specific loading
code, etc. What I don't know much about is those first three 512-byte
chunks of code. Boot0 appears to be booteasy, but
I've got a port of the most recent LinuxThreads (glibc-linuxthreads-2.1.2)
running, but ran into a couple of minor problems integrating with our libc.
LinuxThreads redefines a number of functions in order to make them either
support thread cancellation or work correctly.
The following functions
dcs suggests that the correct answer is:
mbr is a replacement for boot0, without the OS choices. This seems to
make sense, so I'll go with that unless someone has a better idea :-). We
assume that you would never, therefore, use both mbr and boot0, explaining
why there doesn't need to be an
Jason Evans wrote:
I've got a port of the most recent LinuxThreads (glibc-linuxthreads-2.1.2)
running, but ran into a couple of minor problems integrating with our libc.
LinuxThreads redefines a number of functions in order to make them either
support thread cancellation or work correctly.
Hi
I´m sitting behind a firewall consisting av FreeBsd and Squid. My mail program is
Popper. I can mail to (and from) every adress I´ve tried - except freebsd.org. Here´s
the error.
The original message was received at Wed, 8 Dec 1999 16:40:08 +0100 (CET)
from [192.168.1.2]
- The
Ralph Utbult wrote:
Hi
I´m sitting behind a firewall consisting av FreeBsd and Squid. My mail program is
Popper. I can mail to (and from) every adress I´ve tried - except freebsd.org. Here´s
the error.
The original message was received at Wed, 8 Dec 1999 16:40:08 +0100 (CET)
from
On Thu, Dec 09, 1999 at 12:35:17AM -0800, Jason Evans wrote:
I've got a port of the most recent LinuxThreads (glibc-linuxthreads-2.1.2)
running,
Great!
but ran into a couple of minor problems integrating with our libc.
LinuxThreads redefines a number of functions in order to make them
The recent discussion about route table leaks led me to check some
of my systems. On one of them I got this:
bash-2.03$ uname -srm
FreeBSD 3.2-RELEASE i386
bash-2.03$ uptime
7:45AM up 28 days, 12:38, 3 users, load averages: 0.61, 0.50, 0.43
bash-2.03$ vmstat -m | grep routetbl | grep K
Greetings Seniors.
I am interested in establishing the sequence of events from a source code
perspective from when the PC is switched on, to the login prompt. I am
specifically interested in the setting up of lower level stuff like the drivers.
memory etc.
Can anyone please take a moment and
We're seeing it with our ppp link, which uses the kernel level ppp
code. Since it doesn't happen for me often, it is hard to diagnose.
You could set up a 486 (386?) and have it chew on a tonne of ipfw rules.
If it is due to ipfw load, you should be able to force the problem to be
I just upgraded my laptop to use a fresh current from this morning
(fresh checkout with empty /usr/obj).
The machine is an IBM ThinkPad 760XD with 88Mb RAM.
Now when the ep driver attaches my 3COM 3C574 it reports the following
mac address:
ep0: 3Com 3C574 at port 0x240-0x25f irq 10 slot 0 on
http://news.excite.com/news/r/991209/09/tech-veritas-linux
Veritas Software Now Shipping With Linux
MOUNTAIN VIEW, Calif. (Reuters) Veritas Software
Corp. (VRTS.O) said on Thursday its software used to backup
data on computer systems is being shipped with Red Hat
Inc.'s Linux 6.1 Delux product.
Alfred Perlstein [EMAIL PROTECTED] wrote:
(regarding Hoard: http://www.cs.utexas.edu/users/emery/hoard)
This allocator is pretty much what the Dynix allocator is, it wouldn't be
difficult to clean-room implement this with a BSD license.
They should have given credit to Dynix or at least
your ip address 62.20.54.54 is not in DNS, you must have your
address in DNS. we do not accept email from machines that do not have
entries in DNS. amny spammer use addresses that do not appear in DNS
jmb
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Mailer:
On Thu, 9 Dec 1999, Robert Watson wrote:
loaderloadedbyfunction
mbr BIOSwhatever, maybe a couple of lines
/boot/mbr is a copy of the classic DOS MBR code. Used by fdisk. Simply
loads the partition marked as 'active' (flag
On Thu, Dec 09, 1999 at 06:42:56AM -0600, Richard Seaman, Jr. wrote:
In this case, you'd want, for example, an _lseek(), _libc_lseek(),
and _seek().
I meant "and lseek()", not _seek().
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone:
Yes- this also concerned and annoyed the folks at Legato. It puts *me* in
a bit of a bind because I have had business ties to both companies (I
still do (at a very slow rate) Legato NetWorker client packages for *BSD
and non-Intel Linux).
On Thu, 9 Dec 1999, Charles Randall wrote:
This message was sent from Geocrawler.com by "Alex" [EMAIL PROTECTED]
Be sure to reply to that address.
Hello,
I use printf() function from my KLD for
debugging. Always, when the kernel call printf, I
see two same line, like :
Dec 9 15:40:10 techno /kernel: message
Dec 9 15:40:10 techno
On Thu, Dec 09, 1999 at 06:42:56AM -0600, Richard Seaman, Jr. wrote:
On Thu, Dec 09, 1999 at 12:35:17AM -0800, Jason Evans wrote:
The problem with cancellation points, libc and linuxthreads has been
that you need to wade through libc and replace instances of, for
example, write() with
Alex writes:
This message was sent from Geocrawler.com by "Alex" [EMAIL PROTECTED]
Be sure to reply to that address.
Hello,
I use printf() function from my KLD for
debugging. Always, when the kernel call printf, I
see two same line, like :
Dec 9 15:40:10 techno /kernel: message
Dec
Jason Evans wrote:
On Thu, Dec 09, 1999 at 06:42:56AM -0600, Richard Seaman, Jr. wrote:
On Thu, Dec 09, 1999 at 12:35:17AM -0800, Jason Evans wrote:
The problem with cancellation points, libc and linuxthreads has been
that you need to wade through libc and replace instances of, for
On Thu, 9 Dec 1999, Etienne De Bruin wrote:
Greetings Seniors.
I am interested in establishing the sequence of events from a source code
perspective from when the PC is switched on, to the login prompt. I am
specifically interested in the setting up of lower level stuff like the
On Thu, Dec 09, 1999 at 12:57:45PM -0800, Jason Evans wrote:
On Thu, Dec 09, 1999 at 06:42:56AM -0600, Richard Seaman, Jr. wrote:
On Thu, Dec 09, 1999 at 12:35:17AM -0800, Jason Evans wrote:
The problem with cancellation points, libc and linuxthreads has been
that you need to wade
The documentation in /usr/src/sys/boot/i386 seems a little scant, and that
still hanging out in /usr/src/sys/i386/boot is clearly outdated. Was
wondering if someone could point me at docs, and/or post a short summary
something in the form of:
This message was sent from Geocrawler.com by "Alex" [EMAIL PROTECTED]
Be sure to reply to that address.
Hello,
I use printf() function from my KLD for
debugging. Always, when the kernel call printf, I
see two same line, like :
Dec 9 15:40:10 techno /kernel: message
Dec 9 15:40:10
We are having a similar problem at the job I just started. A box meeting
the exact specifications that Mike said caused the problem is essentially
having the crap beat out of it as far as disk access and network activity
(it might help to also say that this company is rather large in the scheme
Richard Seaman, Jr. wrote:
Actually, I don't think all that many apps use pthread_cancel().
Its kind of messy to use. Most can get along without it, which
is why there have only been a limited number of complaints about
the lack of pthread_cancel() in libc_r (until recently). BTW,
I
On Thu, Dec 09, 1999 at 05:41:09PM -0500, Daniel Eischen wrote:
Richard Seaman, Jr. wrote:
Actually, I don't think all that many apps use pthread_cancel().
Its kind of messy to use. Most can get along without it, which
is why there have only been a limited number of complaints about
the
On Thu, 9 Dec 1999, Richard Seaman, Jr. wrote:
On Thu, Dec 09, 1999 at 05:41:09PM -0500, Daniel Eischen wrote:
Richard Seaman, Jr. wrote:
Actually, I don't think all that many apps use pthread_cancel().
Its kind of messy to use. Most can get along without it, which
is why there have
What is the plan (if any) for including crypto stuff in the kernel?
As time goes on this will be more and more needed, eg. for IPSec
and other VPN applications.
It would be nice if we had a /usr/src/sys/crypt directory, plus whatever
export-controlled firewalling silliness is necessary.
On Thu, 9 Dec 1999 17:01:38 -0800 (PST)
Archie Cobbs [EMAIL PROTECTED] wrote:
What is the plan (if any) for including crypto stuff in the kernel?
As time goes on this will be more and more needed, eg. for IPSec
and other VPN applications.
At NetBSD, we already solved this problem with
On Tue, Dec 07, 1999 at 10:13:34PM -0500, C. Stephen Gunn wrote:
I'll send-pr the recipe, and post a reference here when I document
how I worked around some of the magnicomp guys's kludged
makefiles/includes.
I've send-pr'd my attempt at getting this ready for import. (bin/15390)
You can
What is the plan (if any) for including crypto stuff in the kernel?
As time goes on this will be more and more needed, eg. for IPSec
and other VPN applications.
The KAME/IPv6 guys have already brought this up; the agreement was
that...
It would be nice if we had a /usr/src/sys/crypt
34 matches
Mail list logo
