David O'Brien writes :
Access to ftp.internat.freebsd.org from the USA (and presumably
elsewhere) is an abomination. Isn't there *anyone* with an permanate FTP
server that could officially mirror the crypto bits from
ftp.internat.freebsd.org?
Part of the reason for the poor access is that
On Thu, Apr 06, 2000 at 12:05:48PM -0700, David O'Brien wrote:
On Thu, Apr 06, 2000 at 02:16:15PM +0200, Jesper Skriver wrote:
elsewhere) is an abomination. Isn't there *anyone* with an permanate FTP
server that could officially mirror the crypto bits from
I'm glad we are discussing specific technical issues now. Perhaps
we should move this discussion to freebsd-i18n once it's created?
You, Kazutaka YOKOTA, were spotted writing this on Fri, Apr 07, 2000 at 12:13:14PM
+0900:
I have suggested adding Unicode support in the keyboard driver and the
On Fri, Apr 07, 2000 at 03:31:07PM +0100, Koster, K.J. wrote:
Not trying to push this idea one way or the other, I'm just
curious as to WHY so many people think this is a "bad idea"
I can think of four things real quick:
1) Disks are much slowere, and controllers actually have time
Type [enter]
You should then be at a "#" sign
Type " fsck -y "
when it gets done Type 'exit'
It should continue booting.
hi :
when loading the kernel , i have the following error :
**
the following file system had an
Alfred Perlstein wrote:
Some archs (such as i386) allow the OS to set page protections and
io permission bitmaps that effectively can pretect against problems
with drivers touching incorrect IO ranges, however...
Worse yet: What about hardware buggy devices?
This could case the
[...]
Worse yet: What about hardware buggy devices?
This could case the entiry system to crash, isn't it ?
Yes, incorrectly programmed hardware either by firmware (on
chip/board) or by drivers can cause crashes and hardware damage.
[...]
This design, would not let a system
I don't think that's quite true. I've seen microkernels crash because of
bad drivers. I think no matter what, even in a microkernel the drivers
have to interface directly to the kernel. I could be wrong but I thought
that in a microkernel, drivers were loaded as kernel modules.
"Yevmenkin, Maksim N, CSCIO" wrote:
only one :-) performance :-) context switch is a slow operation.
Thanks,
emax
Excuse me gentleman, who said that ?
Take time to visit this site: http://www.qnx.com/iat/download/index.html
You'll be introduced to a hard-real time OS (with a very modular
Gustavo V G C Rios wrote:
Why not starting a microkernel arch?
IMHO the microkernel is the emperor's new clothes (so is OOP, but that,
I suspect, I won't
get quite so much agreement on).
Context switching has been mentioned, but in addition to that, the real
problem is that it
really doesn't
On Fri, 7 Apr 2000, Gustavo V G C Rios wrote:
What all you think about that ?
I think you need to do a literature search for, oh, say, six months and
get back to us. You'll need to read ca. 256-512 or so articles. I'm not
kidding. You should start reading papers from the 1960s.
And oh yes,
Nick Sayer wrote:
Gustavo V G C Rios wrote:
Why not starting a microkernel arch?
IMHO the microkernel is the emperor's new clothes (so is OOP, but that,
I suspect, I won't
get quite so much agreement on).
Context switching has been mentioned, but in addition to that, the real
[...]
only one :-) performance :-) context switch is a slow operation.
Excuse me gentleman, who said that ?
Well, Intel does :)
Take time to visit this site:
http://www.qnx.com/iat/download/index.html
I know this OS. It looks great. Perhaps, it is a good choice for embeded OS.
A good
Not necessarily a bad idea, but certainly incomplete. Being able to
detect and run with bad RAM is only about halfway there. The other half
is being able to remove and replace the bad RAM without taking the
machine down. Like some of the old mainframes (ie TOPS-10, I think).
This not only
Gustavo V G C Rios wrote:
Alfred Perlstein wrote:
Some archs (such as i386) allow the OS to set page protections and
io permission bitmaps that effectively can pretect against problems
with drivers touching incorrect IO ranges, however...
Worse yet: What about hardware buggy
Thanks for the fast reply.. :)
Needless to say the machine has been rebooted since the last time it
died, but I'll try and keep an eye on it and next time it locks if I can
get to the console I'll see if I can grab a snapshot at that time. If a
current running snapshot is of any use
In message [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
: Maybe I'm mis-understanding something, but isn't this situation
: analagous to bad sectors on a hard drive? Isn't this similar, at
: least in theory, to remapping dead sectors and continuing to use the
: drive? (except that the disk's
In message [EMAIL PROTECTED] Gustavo V G C Rios writes:
: All other tasks would run in like any other user process, like a fyle
: system daemon, process daemon , internet daemon (not inetd), and, of
: course, device drivers programs.
This still won't stop you from wedging the machine absoltely
On Fri, Apr 07, 2000 at 04:04:23PM -0600, Warner Losh wrote:
In message [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
: Maybe I'm mis-understanding something, but isn't this situation
: analagous to bad sectors on a hard drive? Isn't this similar, at
: least in theory, to remapping dead
What's the proper ordering for the hardware listed in HARDWARE.TXT?
What's the right way to list drivers that are generally only available
on embedded hardware (eg the crystal semiconductor 89x0 based hardware
isn't listed in the supported section, even though it appears on many
embedded
On Fri, Apr 07, 2000 at 03:19:07PM -0700, Brooks Davis wrote:
On Fri, Apr 07, 2000 at 04:04:23PM -0600, Warner Losh wrote:
In message [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
: Maybe I'm mis-understanding something, but isn't this situation
: analagous to bad sectors on a hard drive?
Gustavo V G C Rios wrote:
"Yevmenkin, Maksim N, CSCIO" wrote:
only one :-) performance :-) context switch is a slow operation.
Thanks,
emax
Excuse me gentleman, who said that ?
Take time to visit this site: http://www.qnx.com/iat/download/index.html
You'll be introduced to a
In message [EMAIL PROTECTED], Ugen Antsilevitch writes:
Gustavo V G C Rios wrote:
"Yevmenkin, Maksim N, CSCIO" wrote:
only one :-) performance :-) context switch is a slow operation.
Thanks,
emax
Excuse me gentleman, who said that ?
Take time to visit this site:
rohrbach@filepile:/ftp/.vol/vol1$ du -sk FreeBSD
22975903FreeBSD
rohrbach@filepile:/ftp/.vol/vol1$ date
Sat Apr 8 01:17:30 CEST 2000
...eek!
/k
Jesper Skriver([EMAIL PROTECTED])@Thu, Mar 30, 2000 at 05:11:43PM +0200:
On Thu, Mar 30, 2000 at 09:42:42AM -0500, Patrick Gardella wrote:
I apologize profusely for the delay of this, but lockd-0.2 is out.
The URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2.tar.gz
A couple of notes on this release:
1) the statd hooks to lockd are not yet done (or started)
2) you need a patched libc (for XDR64 types). I have included the
"Yevmenkin, Maksim N, CSCIO" wrote:
only one :-) performance :-) context switch is a slow operation.
Thanks,
emax
Excuse me gentleman, who said that ?
Take time to visit this site: http://www.qnx.com/iat/download/index.html
You'll be introduced to a hard-real time OS (with a
David Holloway wrote:
In message [EMAIL PROTECTED], Ugen Antsilevitch writes:
Gustavo V G C Rios wrote:
QNX is great and all the power to it. This is FreeBSD and it is unix and BSD
and as such it is what it is. If it would take a QNX approach then it would
not be FreeBSD but something
27 matches
Mail list logo
