Mike Smith wrote:
>
> > anybody got some reliable, tested, known-good code for getting back to
> > real mode? I'm to the point where I have a working GDT, and paging is
> > turned off, but the last step -- turning off protection enable -- is not
> > working for me.
>
> You want to be more explic
Narvi wrote:
>
> See LINT on details of how to wire down scsi devices...
>
> Your proposal doesn't take adding a second scsi card into account.
UnixWare has a kind od solution for this: when they create
the VTOC table (an analog of the BSD disk label) on the disk
they have a field in it that co
Julian Elischer wrote:
>
> Has anyone looked at netscape Communicator 4.7 for FreeBSD???
>
> I just installed it.
> the binary is 13234176 bytes long!!
> yes folks, that's 13 MB!
>
> stripped!
> With shared libraries!
>
> It runs but it's quite easy to make your xserver run out of memory (or
>
This wouldn't seem -hackers worthy, except I offfered to try to port
it to freebsd-current.
I thought that this would be interesting to people and that I might be able
to get some advice from around here. Following is the email thread that
happened between Scott Draeker (president of Loki) and S
No response on -current and I have an update. After moving to
-current source via cvs -D (1999//D99.08.28.21.00.00) the servers are
infinitely more stable, running continuously for three days, and showing
no signs of dying. I get sockname errors once in a great while, and only
one at a tim
[EMAIL PROTECTED] wrote:
} > > That's an interesting argument on the part of a few people. The
} > > commercial UNIX I first adminned had wired down, short names for disks
} > > (rz0, rz1, rz2, ... ). This was very nice.
} >
} > This one does not resolve the controller problem either as
} > [EM
According to Brett Taylor:
> That's about 1/2 the size and if you're not using the composer, news
> reader or mailer you might as well toss Communicator in favor of
> Navigator.
Yes but with the navigator, you can't even mail a link or a page...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve
Dag-Erling Smorgrav wrote:
>
> Jaakko Salomaa <[EMAIL PROTECTED]> writes:
>
> > Hey, how am I supposed to fetch directory listing with ftpio(3) or
> > fecth(3)? ftpio doesn't seem to contain necessary functions for it, and
> > fetch's ones aren't implemented.
>
> Type 'man 3 fetch', scroll down
If memory serves me right, [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
> } Well...I personally prefer the short names. On systems with multiple
> } controllers, the commercial UNIX I used (Ultrix) just continued its
> } numbering with rz0, rz1, rz2, ..., rz6, rz7, rz8, ... FreeBSD let
If memory serves me right, [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
> > If memory serves me right, [EMAIL PROTECTED] wrote:
> > > > See LINT on details of how to wire down scsi devices...
> > > >
> > > > Your proposal doesn't take adding a second scsi card into account.
> > >
> > > We
The following is copied from the comments of FFS code:
"Block devices associated with filesystems may have new I/O requests
posted for them even if the vnode is *locked*, so no amount of trying will
get them clean. Thus we give block devices a good effort, then just give
up. For all other file t
The following is copied from the comments of FFS code:
"Block devices associated with filesystems may have new I/O requests
posted for them even if the vnode is *locked*, so no amount of trying will
get them clean. Thus we give block devices a good effort, then just give up.
For all other file
[EMAIL PROTECTED] wrote...
> > On Fri, 1 Oct 1999 [EMAIL PROTECTED] wrote:
> >
> > > Current FreeBSD SCSi disk naming mechanism is problem for using more than
> > > one disks in the chain during the disk failure.
> > >
> > > The problem is that the name is not fixed with is SCSI ID. e.g.,
> > >
Hey is this a bug ?
I downloaded the code for radix.c and radix.h and was trying to get a
tree that looks
like the one in TCP/IP Illustrated V.2 page 563 A.K.A "the book". I set
up a test program to put the same data into the tree, page 560 and
noticed a couple of differences. This is a copy of
It seems Stefan Lindgren wrote:
> Thanks for the help Soren,
>
> The disk is a Seagate Medalist 6.2 GB UDMA
> But now I have tested all PIO modes(0 - 4 and auto) and disabled udma.
> It still doesn't work.
> I get different results when I change PIO. Once I got some message like:
> Page fault: Co
[EMAIL PROTECTED] wrote:
> If memory serves me right, [EMAIL PROTECTED] wrote:
> > > See LINT on details of how to wire down scsi devices...
> > >
> > > Your proposal doesn't take adding a second scsi card into account.
> >
> > Well, I did not mean that has to be da0, da1, etc., but similar thin
Thanks for the help Soren,
The disk is a Seagate Medalist 6.2 GB UDMA
But now I have tested all PIO modes(0 - 4 and auto) and disabled udma.
It still doesn't work.
I get different results when I change PIO. Once I got some message like:
Page fault: Couldn't init disk...(something)
Any clue?
/st
Nate Williams wrote:
> In short, it's a netscape bug
maybe not - i recently received buckets of these on a system i was
experimenting with overclocking on - an upgraded heatsink fixed it.
I've also seen it when I tweak the BIOS settings a bit too
aggresively...
--
Dave Cornejo - Dogwood Med
On Fri, 1 Oct 1999 [EMAIL PROTECTED] wrote:
> Current FreeBSD SCSi disk naming mechanism is problem for using more than
> one disks in the chain during the disk failure.
>
> The problem is that the name is not fixed with is SCSI ID. e.g.,
> if one disk is presented in the chain, regardless its
If memory serves me right, [EMAIL PROTECTED] wrote:
> > See LINT on details of how to wire down scsi devices...
> >
> > Your proposal doesn't take adding a second scsi card into account.
>
> Well, I did not mean that has to be da0, da1, etc., but similar thing
> like dac0t0d0, dac0t1d0, ... dac3
Hi Julian,
On Thu, 30 Sep 1999, Julian Elischer wrote:
> Has anyone looked at netscape Communicator 4.7 for FreeBSD???
>
> I just installed it. the binary is 13234176 bytes long!!
Is this much bigger than before? I usually use Navigator instead as I
don't want all the bloat. The 4.61 version
See LINT on details of how to wire down scsi devices...
Your proposal doesn't take adding a second scsi card into account.
On Fri, 1 Oct 1999 [EMAIL PROTECTED] wrote:
> Current FreeBSD SCSi disk naming mechanism is problem for using more than
> one disks in the chain during the disk failure.
>
Jaakko Salomaa <[EMAIL PROTECTED]> writes:
> Hey, how am I supposed to fetch directory listing with ftpio(3) or
> fecth(3)? ftpio doesn't seem to contain necessary functions for it, and
> fetch's ones aren't implemented.
Type 'man 3 fetch', scroll down to the BUGS section, and see the
light. Next
Guido van Rooij wrote:
>
> I know about the 1024 cylinder limit, however I would expect loader
> to be able to work beyond that limit..
Loader uses BIOS and, thus, has all of BIOS limits.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Rule 69: Do
Current FreeBSD SCSi disk naming mechanism is problem for using more than
one disks in the chain during the disk failure.
The problem is that the name is not fixed with is SCSI ID. e.g.,
if one disk is presented in the chain, regardless its SCSI ID, it is
always named "da0";
if two disks are ins
> See LINT on details of how to wire down scsi devices...
>
> Your proposal doesn't take adding a second scsi card into account.
Well, I did not mean that has to be da0, da1, etc., but similar thing
like dac0t0d0, dac0t1d0, ... dac3t4d0, etc. which is much clear what
disk is.
A few people does n
On Thu, Sep 30, 1999 at 10:57:42PM -0700, Julian Elischer wrote:
> I just installed it.
> the binary is 13234176 bytes long!!
> yes folks, that's 13 MB!
That's an improvement from 4.61!
$ ls -l /usr/local/lib/netscape/communicator-4.61.bin
-r-xr-xr-x 1 root wheel 13271040 Jun 10 10:00
/usr/
27 matches
Mail list logo
