er 14, 2004 5:38 PM
To: Macy, Kip
Cc: Danny Braniss; [EMAIL PROTECTED]; Peter Blok
Subject: Re: My project wish-list for the next 12 months
On Tue, 14 Dec 2004 17:05:25 -0800 (PST), Kip Macy <[EMAIL PROTECTED]>
wrote:
> > Hardware-based iSCSI HBAs solve this by having their own memory a
let me start by a local saying:
Q- What's a camel
A- It's a horse designed by a committee.
BTW, the camel is a very efficient piece of equipment.
If I would plan a 24/7 life support system I would not use iSCSI.
(having to rely on packets traveling the Internet, DOS, etc, is not go
> Hardware-based iSCSI HBAs solve this by having their own memory and
> TCP stack separate from the OS. Software-only iSCSI initiators such
> as linux-iscsi usually just hope it doesn't happen, and that's why I
> don't usually recommend software-only iSCSI initiators to anyone.
How is that any be
On Tue, 14 Dec 2004 17:05:25 -0800 (PST), Kip Macy <[EMAIL PROTECTED]> wrote:
> > Hardware-based iSCSI HBAs solve this by having their own memory and
> > TCP stack separate from the OS. Software-only iSCSI initiators such
> > as linux-iscsi usually just hope it doesn't happen, and that's why I
> >
On Tue, 14 Dec 2004 22:02:40 +, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>
> Note that this isn't different from any sufficiently complex HBA driver,
> except that the code that can operate under these conditions is more
> complex for iscsi.
I don't understand why you think the situation
On Tue, Dec 14, 2004 at 01:47:15PM -0600, Scott M. Ferris wrote..
> On Tue, 14 Dec 2004 09:29:19 +0200, Danny Braniss <[EMAIL PROTECTED]> wrote:
> > Great!, we seem to be on the same wavelength, im now writing (at about one
> > char a minute) the login user program, and somehow - to be discovered -
On Tue, 14 Dec 2004 09:29:19 +0200, Danny Braniss <[EMAIL PROTECTED]> wrote:
> Great!, we seem to be on the same wavelength, im now writing (at about one
> char a minute) the login user program, and somehow - to be discovered -, the
> socket will be passed to the kernel.
> my main efford, at the mo
Great!, we seem to be on the same wavelength, im now writing (at about one
char a minute) the login user program, and somehow - to be discovered -, the
socket will be passed to the kernel.
my main efford, at the moment, is a) to &^%$$## understand the RFC (i think
they used a scrambler) and b) defi
er 12, 2004 9:05 AM
To: Peter Blok
Cc: [EMAIL PROTECTED]
Subject: Re: My project wish-list for the next 12 months
> Hi Danny,
>
> Great! I am still in a design proof-of-concept phase, but I appreciate
your
> help. I'll keep you posted.
>
> Peter
hi Peter,
re-readi
> Hi Danny,
>
> Great! I am still in a design proof-of-concept phase, but I appreciate your
> help. I'll keep you posted.
>
> Peter
hi Peter,
re-reading your email, i realize you are interested in the target
side of iSCSI, and me more on the initiator side, so i decided to bite
the bulle
On Wed, 01 Dec 2004 15:02:40 -0700
Scott Long <[EMAIL PROTECTED]> wrote:
> All,
>
> I know that I said last month that we were going to stop promising
> specific features for the next major release. However, I'd like to
> throw out a list of things that would be really nice to have in the
> futu
How about some form of streamlined video input support?
I realize Linux's v4l model doesn't fit too well here, but what
they have done there provides support for all sorts of common video
devices, and makes them all available to pretty much any program that
wants video input.
FreeBSD is far behin
On Thu, Dec 02, 2004 at 06:41:53PM +0100, Andre Oppermann typed:
:: Data redundancy would require a UFS/FFS redesign. I'm 'only' talking
:: about enhancing UFS/FFS but keeping anything ondisk the same (plus
:: some more elements).
Well, from my point of view, I would see this as some strong
geom
El Viernes, 3 de Diciembre de 2004 13:29, Devon H. O'Dell escribió:
> Jose M Rodriguez wrote:
> > El Jueves, 2 de Diciembre de 2004 02:23, Peter Kieser escribió:
> >>Scott Long wrote:
[ ... ]
> > Also, I can remenber, al last, other previous try. Please, use a
> > safe path. As a reference, Mandr
Anaconda is also GPLed and also requires a good few changes for most
of it to run under FreeBSD. I haven't made any of these changes, but
we looked into using Anaconda in DragonFly before we started on our
own installer, and it would have just been too much work for the
deadline we had (our 1.
Jose M Rodriguez wrote:
El Jueves, 2 de Diciembre de 2004 02:23, Peter Kieser escribió:
Scott Long wrote:
2. New installer. I know some people still consider this a joke,
but the reality is that sysinstall is no longer state of the art.
It's fairly good at the simple task that it does, but it's
El Jueves, 2 de Diciembre de 2004 02:23, Peter Kieser escribió:
> Scott Long wrote:
> > 2. New installer. I know some people still consider this a joke,
> > but the reality is that sysinstall is no longer state of the art.
> > It's fairly good at the simple task that it does, but it's becoming
>
El Jueves, 2 de Diciembre de 2004 00:19, Scott Long escribió:
> Kris Kennaway wrote:
> > On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote:
> >>Another issue I had with the dfly installer was one point I believe
> >> needs to be central to any next-gen installer.
> >> Internationalisatio
Peter Wemm wrote:
On Wednesday 01 December 2004 05:17 pm, Foxfair Hu wrote:
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
All,
[]
1. Keyboard multiplexer. We are running into problems with making
ps/2 and USB/bluetooth keyboards work together and work with KVMs.
Having a virtua
On Wednesday 01 December 2004 05:17 pm, Foxfair Hu wrote:
> On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
> > All,
>
> []
>
> > 1. Keyboard multiplexer. We are running into problems with making
> > ps/2 and USB/bluetooth keyboards work together and work with KVMs.
> > Having a v
Scott Long wrote:
Stephan Uphoff wrote:
On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote:
The holy grail of course is to mount
the same filesystem 'rw' on more than one box, preferrably more than
two.
This requires some more involved synchronization and locking on top
of the
cache invalidation.
Stephan Uphoff wrote:
On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote:
Scott Long wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerf
Stephan Uphoff wrote:
On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote:
Scott Long wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerf
> >> 4. Journaled filesystem.
> >
> > The stage of the current implementation is, as I said, read-only.
> > Further, it's currently i386 only.
>
> In theory, it shouldn't be tied to i386, but I never tested it somewhere
> else unfortunately.
>
Got that from the reiserfs port which says it doesn
On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote:
> Scott Long wrote:
> > 5. Clustered FS support. SANs are all the rage these days, and
> > clustered filesystems that allow data to be distributed across many
> > storage enpoints and accessed concurrently through the SAN are very
> > powerful.
On Thu, Dec 02, 2004 at 10:47:36PM +0200, Valentin Nechayev wrote:
> Wed, Dec 01, 2004 at 15:02:40, scottl wrote about "My project wish-list for
> the next 12 months":
>
> [...]
> > 2. New installer. I know some people still consider this a joke, but
> > th
Wed, Dec 01, 2004 at 15:02:40, scottl wrote about "My project wish-list for
the next 12 months":
[...]
> 2. New installer. I know some people still consider this a joke, but
> the reality is that sysinstall is no longer state of the art. It's
> fairly good at the
> 4. Journaled filesystem. While we can debate the merits of speed and
> data integrety of journalling vs. softupdates, the simple fact remains
> that softupdates still requires a fsck run on recovery, and the
> multi-terabyte filesystems that are possible these days make fsck a very
> long and u
On Wed, Dec 01, 2004 at 04:37:59PM -0700, Scott Long wrote..
> Jason C. Wells wrote:
> >--On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long
> ><[EMAIL PROTECTED]> wrote:
> >
> >>5. Clustered FS support. SANs are all the rage these days, and
> >>clustered filesystems that allow data to be
On Thu, 2004-Dec-02 07:55:30 +0100, Miguel Mendez wrote:
>On Thu, 02 Dec 2004 10:44:32 +0530
>"Kamal R. Prasad" <[EMAIL PROTECTED]> wrote:
>> I find X windows to be a bit too compute intensive. Maybe something
>> like apple's interface would be a good alternative [for those who
>> don't need X-wind
Andre Oppermann wrote:
Sam wrote:
On Thu, 2 Dec 2004, Andre Oppermann wrote:
Scott Long wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
pow
Sam wrote:
On Thu, 2 Dec 2004, Andre Oppermann wrote:
Scott Long wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful. RedHat recently
On Thu, 2 Dec 2004, Andre Oppermann wrote:
Scott Long wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful. RedHat recently bought Sis
Scott Long wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful. RedHat recently bought Sistina and re-opened the GFS source
code, so
On Thu, 2 Dec 2004, Brad Knowles wrote:
It's interesting that you mention this. I've been giving some
thought to how I might be able to dive in and start seriously working on
building my UltraSPARC cluster (based on the four U10 clones I have already,
plus as many U5s as I can throw into the m
> As far as the iSCSI stuff, I have the Lucent stuff and am trying to use it
> as a reference to build an iSCSI target. I have been experimenting a bit.
>
> The design goal is to have the negotiation stuff running in a user daemon,
> while the target data handling is completely in the kernel. I wa
[Cc list trimmed]
< said:
> The lack of speed in some apps can be blamed mostly on the toolkits.
I'll second that.
> GTK+ 1.2 was a speed demon, GTK+ 2.x is a lot slower.
And either one is an enormous hog compared to Athena widgets. (This
is something of an accomplishment, since people have b
At 3:38 PM -0800 2004-12-01, Kris Kennaway quoted Jason C. Wells:
This sounds very close to OpenAFS. I don't know what distinguishes a SAN
from other types of NAS. OpenAFS does everything you mentioned in the
above paragraph. OpenAFS _almost_ works on FreeBSD right now.
I'd be very intereste
On Wed, 1 Dec 2004, Scott Long wrote:
> 2. New installer. [... sysinstall] is fairly good at the simple
> task that it does [ ... ]
I'll put my bugmeister-hat on and simply say that query-pr suggests
otherwise. I have not spent sufficient time examining each of the
PRs to figure out what the b
< said:
> This sounds very close to OpenAFS. I don't know what distinguishes a SAN
> from other types of NAS. OpenAFS does everything you mentioned in the
> above paragraph. OpenAFS _almost_ works on FreeBSD right now.
AFS's consistency model is wholly unsuitable for clustering.
-GAWollman
--On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long
<[EMAIL PROTECTED]> wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful.
On Wednesday, 1. December 2004 23:14, Andre Oppermann wrote:
> Scott Long wrote:
> > All,
> >
> > I know that I said last month that we were going to stop promising
> > specific features for the next major release. However, I'd like to
> > throw out a list of things that would be really nice to ha
Cc: [EMAIL PROTECTED]
Subject: My project wish-list for the next 12 months
All,
I know that I said last month that we were going to stop promising
specific features for the next major release. However, I'd like to
throw out a list of things that would be really nice to have in the
future, whe
In message <[EMAIL PROTECTED]>, Scott Long writes:
>All,
>
>I know that I said last month that we were going to stop promising
>specific features for the next major release. However, I'd like to
>throw out a list of things that would be really nice to have in the
>future, whether its 6.0 or 7.0 or
> "Scott" == Scott Long <[EMAIL PROTECTED]> writes:
Hi,
Scott> 1. Keyboard multiplexer. We are running into problems with
Scott> making ps/2 and USB/bluetooth keyboards work together and work
Scott> with KVMs. Having a virtual keyboard device that multiplexes the
Scott> various real keybo
Ryan Sommers wrote:
Scott Long said:
2. New installer. I know some people still consider this a joke, but
the reality is that sysinstall is no longer state of the art. It's
fairly good at the simple task that it does, but it's becoming harder
and harder to fix bugs and extend functionality in it
On Thu, 02 Dec 2004 10:44:32 +0530
"Kamal R. Prasad" <[EMAIL PROTECTED]> wrote:
[Please don't top-post]
> I find X windows to be a bit too compute intensive. Maybe something
> like apple's interface would be a good alternative [for those who
> don't need X-windows' powerful graphic features].
Wh
In message: <[EMAIL PROTECTED]>
John Hay <[EMAIL PROTECTED]> writes:
: > > 1. Keyboard multiplexer.
: >
: > I actually fail to stop thinking about a complete syscons and pcvt
: > replacement. You know, the one and only console implementation that
: > makes all others obsolete. Big pla
> >
> > 1. Keyboard multiplexer.
>
> I actually fail to stop thinking about a complete syscons and pcvt
> replacement. You know, the one and only console implementation that
> makes all others obsolete. Big plans, little time, yada yada yada...
It would be nice if one would still be able to use
I find X windows to be a bit too compute intensive. Maybe something like
apple's interface would be a good alternative [for those who don't need
X-windows' powerful graphic features].
regards
-kamal
Scott Long wrote:
Jason C. Wells wrote:
--On Wednesday, December 01, 2004 3:02 PM -0700 Scott Lon
In message: <[EMAIL PROTECTED]>
Scott Long <[EMAIL PROTECTED]> writes:
: 1. Keyboard multiplexer. We are running into problems with making
: ps/2 and USB/bluetooth keyboards work together and work with KVMs.
: Having a virtual keyboard device that multiplexes the various real
: keyboa
Foxfair Hu wrote:
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
All,
[]
1. Keyboard multiplexer. We are running into problems with making
ps/2 and USB/bluetooth keyboards work together and work with KVMs.
Having a virtual keyboard device that multiplexes the various real
keyboar
Scott Long wrote:
2. New installer. I know some people still consider this a joke, but
the reality is that sysinstall is no longer state of the art. It's
fairly good at the simple task that it does, but it's becoming harder
and harder to fix bugs and extend functionality in it. It's also
fairly
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
> All,
>
[]
>
> 1. Keyboard multiplexer. We are running into problems with making
> ps/2 and USB/bluetooth keyboards work together and work with KVMs.
> Having a virtual keyboard device that multiplexes the various real
> keyboard
Marcel Moolenaar wrote:
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
1. Keyboard multiplexer.
I actually fail to stop thinking about a complete syscons and pcvt
replacement. You know, the one and only console implementation that
makes all others obsolete. Big plans, little time, ya
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
>
> 1. Keyboard multiplexer.
I actually fail to stop thinking about a complete syscons and pcvt
replacement. You know, the one and only console implementation that
makes all others obsolete. Big plans, little time, yada yada yada...
>
In the last episode (Dec 01), Jason C. Wells said:
> --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long
> <[EMAIL PROTECTED]> wrote:
>
> >5. Clustered FS support. SANs are all the rage these days, and
> >clustered filesystems that allow data to be distributed across many
> >storage enpo
Jason C. Wells wrote:
--On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long
<[EMAIL PROTECTED]> wrote:
5. Clustered FS support. SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the S
On Wed, Dec 01, 2004 at 03:29:10PM -0800, Jason C. Wells wrote:
> --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long
> <[EMAIL PROTECTED]> wrote:
>
> >5. Clustered FS support. SANs are all the rage these days, and
> >clustered filesystems that allow data to be distributed across many
>
Kris Kennaway wrote:
On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote:
Another issue I had with the dfly installer was one point I believe needs
to be central to any next-gen installer. Internationalisation.
Careful not to pile on so many wishes that achieving anything becomes
impossi
On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote:
> Another issue I had with the dfly installer was one point I believe needs
> to be central to any next-gen installer. Internationalisation.
Careful not to pile on so many wishes that achieving anything becomes
impossible. Our current
Scott Long said:
> 2. New installer. I know some people still consider this a joke, but
> the reality is that sysinstall is no longer state of the art. It's
> fairly good at the simple task that it does, but it's becoming harder
> and harder to fix bugs and extend functionality in it. It's als
Scott Long wrote:
All,
I know that I said last month that we were going to stop promising
specific features for the next major release. However, I'd like to
throw out a list of things that would be really nice to have in the
future, whether its 6.0 or 7.0 or whatever. Most of these tasks are
not
All,
I know that I said last month that we were going to stop promising
specific features for the next major release. However, I'd like to
throw out a list of things that would be really nice to have in the
future, whether its 6.0 or 7.0 or whatever. Most of these tasks are
not trivial, but I hop
64 matches
Mail list logo
