>
> --VbJkn9YxBvnuCH5J
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> In our last exciting episode, Danny Braniss (da...@cs.huji.ac.il) said:
> > I guess it's time to fix this.
> &
>
> --ikeVEW9yuYc//A+q
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> I'm running into some odd headaches regarding what looks like iSCSI initiat=
> ors
> going to sleep for approximately 30 seconds before returning to
> At 1:25 PM -0600 10/17/05, M. Warner Losh wrote:
> >In message: <[EMAIL PROTECTED]>
> > Gary Kline <[EMAIL PROTECTED]> writes:
> >:vi was the first screen/cursor-based editor in computer
> >:history.
> >
> >Are you sure about this? I was using screen oriented editors over a
>
hi danny
you are asking too many questions :-), but w/r to netapp:
same computer, 1gbE, NFS is about 50% slower than FC.
btw, iSCSI (still beta) is only slightly faster than NFS
(note NFS is UDP, iSCSI is TCP).
as to reliability, the netapp is worth avery penny (actualy K$ :-), had only
o
> On Thu, Aug 04, 2005 at 11:00:46AM +0300, Danny Braniss wrote:
> > this 11k lines of fortran compile and run under Linux,
> > on FreeBSD 5.4, compiling with f77 produces a binary, apparently without
> > errors, but
> > executing it, inmediately gives
hi,
this 11k lines of fortran compile and run under Linux,
on FreeBSD 5.4, compiling with f77 produces a binary, apparently without
errors, but
executing it, inmediately gives 'Abort', ldd gives signal 6
ktrace is not very helpful :-)
36372 ktrace RET ktrace 0
36372 ktrace
> All,
>
> I was wondering what people thought of iSCSI and FreeBSD. Is it a viable
> option for creating SANs?
>
refrase question.
> I want to move away from tape backups, and have numerous production
> FreeBSD machines that I need to back up data from.
>
for one, it depends on how deep are
