on 26/06/2012 15:50 Andrey V. Elsukov said the following:
3. ZFS code now uses new API and probing on the systems with many disks
should be greatly increased:
zfs/zfs.c
i386/loader/main.c
First of all, it's hard to parse the above sentence. probing ... should be
greatly
On 16.07.2012 14:23, Andriy Gapon wrote:
on 26/06/2012 15:50 Andrey V. Elsukov said the following:
3. ZFS code now uses new API and probing on the systems with many disks
should be greatly increased:
zfs/zfs.c
i386/loader/main.c
First of all, it's hard to parse the above
on 16/07/2012 13:57 Andrey V. Elsukov said the following:
On 16.07.2012 14:23, Andriy Gapon wrote:
on 26/06/2012 15:50 Andrey V. Elsukov said the following:
3. ZFS code now uses new API and probing on the systems with many disks
should be greatly increased:
zfs/zfs.c
On 16.07.2012 15:05, Andriy Gapon wrote:
2. I am not sure if I like the approach of moving partition tasting code
into
common ZFS code (zfs.c). On one hand, it now makes sense because the new
partition iteration code is machine-independent. On the other hand, the
reason
that I added
on 16/07/2012 14:14 Andrey V. Elsukov said the following:
On 16.07.2012 15:05, Andriy Gapon wrote:
2. I am not sure if I like the approach of moving partition tasting code
into
common ZFS code (zfs.c). On one hand, it now makes sense because the new
partition iteration code is
On 16.07.2012 15:31, Andriy Gapon wrote:
Yes. It should work as before.
Well, but it's obvious that zfs_probe_dev would be attempting to do some
unneeded
stuff (trying to treat partitions as disks) for that case. To me this is a
clear
indication zfs_probe_dev is not optimal for
On Mon, Jul 16, 2012 at 04:00:49PM +0400, Andrey V. Elsukov wrote:
On 16.07.2012 15:31, Andriy Gapon wrote:
Yes. It should work as before.
Well, but it's obvious that zfs_probe_dev would be attempting to do some
unneeded
stuff (trying to treat partitions as disks) for that case. To
On 07/05/12 02:03, Doug Barton wrote:
On 07/05/2012 01:28, Peter Jeremy wrote:
On 2012-Jul-05 09:22:25 +0200, Jonathan McKeown
j.mcke...@ru.ac.za wrote:
As for the idea that Linux refugees need extra help to migrate,
that's the sort of thinking that led to things like:
alias dir=ls
Whilst
On Mon, Jul 16, 2012 at 2:41 PM, Dave Hayes d...@jetcafe.org wrote:
Why not create a command wtf(1)?
When you type it, it detects the shell you are using, looks at the last
command you typed, and provides all sorts of arbitrarily verbose and usable
documentation and suggestions as to what
On 07/16/12 15:16, David Brodbeck wrote:
I suspect you meant this as a sarcastic suggestion, but I actually
like it. It reminds me of AmigaDOS's why command, which would give
a detailed explanation of why the previous command failed.
Actually I meant this as a real suggestion, though I'll
Why not create a command wtf(1)?
there are really lot of good features that can be made in FreeBSD.
actually good, instead of that crap
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
11 matches
Mail list logo
