On 19.07.2011 1:22, Scott Long wrote:
Btw, I *HATE* the chip and card identifiers used in pciconf. Can we
change it to emit
the standard (sub)vendor/(sub)device terminology?
Oh, yeah. I hate that too. Would you want them as 4 separate entities or
to just rename the
labels to 'devid'
On Mon, Jul 18, 2011 at 4:41 PM, Jeremy Chadwick
free...@jdc.parodius.com wrote:
On Mon, Jul 18, 2011 at 03:50:15PM -0700, Kevin Oberman wrote:
I just want to check on the status of 4K sector support in FreeBSD. I read
a long thread on the topic from a while back and it looks like I might hit
On 19/07/2011 07:56, Andrey V. Elsukov wrote:
On 19.07.2011 1:22, Scott Long wrote:
Btw, I *HATE* the chip and card identifiers used in pciconf. Can we change
it to emit
the standard (sub)vendor/(sub)device terminology?
Oh, yeah. I hate that too. Would you want them as 4 separate entities
On Monday, July 18, 2011 5:22:26 pm Scott Long wrote:
On Jul 18, 2011, at 3:14 PM, John Baldwin wrote:
On Monday, July 18, 2011 5:06:40 pm Scott Long wrote:
On Jul 18, 2011, at 12:02 PM, John Baldwin wrote:
On Friday, July 15, 2011 6:07:31 pm Mark McConnell wrote:
Dear folks,
I
Hi,
I've just noticed and tracked down a regression in x86/cpufreq/powernow.c
(on amd64) which was first mentioned here:
http://lists.freebsd.org/pipermail/freebsd-current/2011-March/023509.html
although no followup seems to have occurred.
Symptoms are that powerd stops working because the
On Jul 19, 2011, at 7:31 AM, John Baldwin wrote:
If we're going to change it, might as well break it down into 4 fields.
Maybe
we retain the old format under a legacy switch and/or env variable for users
that have tools that parse the output (cough yahoo cough).
The only reason it might
On Tuesday 19 July 2011 07:20 am, Callum Gibson wrote:
Hi,
I've just noticed and tracked down a regression in
x86/cpufreq/powernow.c (on amd64) which was first mentioned here:
http://lists.freebsd.org/pipermail/freebsd-current/2011-March/02350
9.html
although no followup seems to have
On Tue, Jul 19, 2011 at 6:31 AM, John Baldwin j...@freebsd.org wrote:
The only reason it might be nice to stick with two fields is due to the line
length (though the first line is over 80 cols even in the current format).
Here
are two possible suggestions:
old:
hostb0@pci0:0:0:0:
On Jul 18, 2011, at 11:04 PM, Kevin Oberman wrote:
I just wish FreeBSD had some decent documentation on such a fundamental
operation. Fortunately there are some pretty good articles folks have
written, but they did leave me with several questions.
Is there something in FreeBSD which is
On 19.7.2011. 19:54, Chuck Swiger wrote:
On Jul 18, 2011, at 11:04 PM, Kevin Oberman wrote:
I just wish FreeBSD had some decent documentation on such a fundamental
operation. Fortunately there are some pretty good articles folks have
written, but they did leave me with several questions.
Is
On Jul 19, 2011, at 12:29 PM, Ivan Voras wrote:
Is there something in FreeBSD which is preventing you from using the drive's
native DEV_BSIZE of 4096 bytes, or is it that the drive claims to have a
physical block size of 512 bytes when it is really 4k?
Nope, only that.
:-)
It's nice to
On Mon, 18 Jul 2011 16:41:24 -0700 Jeremy Chadwick
free...@jdc.parodius.com wrote:
But the currently known method is to use gnop(8). Here's an
example:
http://www.leidinger.net/blog/2011/05/03/another-root-on-zfs-howto-optimized-for-4k-sector-drives/
Now, that's for ZFS, but I'm under
On 2011-Jul-19 10:54:38 -0700, Chuck Swiger cswi...@mac.com wrote:
Unix operating
systems like SunOS 3 and NEXTSTEP would happily run with a DEV_BSIZE
of 1024 or larger-- they'd boot fine off of optical media using
2048-byte sectors,
Actually, Sun used customised CD-ROM drives that faked
On Tue, Jul 19, 2011 at 1:41 PM, Alexander Leidinger
alexan...@leidinger.net wrote:
On Mon, 18 Jul 2011 16:41:24 -0700 Jeremy Chadwick
free...@jdc.parodius.com wrote:
But the currently known method is to use gnop(8). Here's an
example:
On Tue, Jul 19, 2011 at 02:33:27PM -0700, Kevin Oberman wrote:
On Tue, Jul 19, 2011 at 1:41 PM, Alexander Leidinger
alexan...@leidinger.net wrote:
On Mon, 18 Jul 2011 16:41:24 -0700 Jeremy Chadwick
free...@jdc.parodius.com wrote:
But the currently known method is to use gnop(8). ?Here's
On Jul 19, 2011, at 2:10 PM, Peter Jeremy wrote:
On 2011-Jul-19 10:54:38 -0700, Chuck Swiger cswi...@mac.com wrote:
Unix operating
systems like SunOS 3 and NEXTSTEP would happily run with a DEV_BSIZE
of 1024 or larger-- they'd boot fine off of optical media using
2048-byte sectors,
On Tue, Jul 19, 2011 at 2:49 PM, Jeremy Chadwick
free...@jdc.parodius.com wrote:
On Tue, Jul 19, 2011 at 02:33:27PM -0700, Kevin Oberman wrote:
On Tue, Jul 19, 2011 at 1:41 PM, Alexander Leidinger
alexan...@leidinger.net wrote:
On Mon, 18 Jul 2011 16:41:24 -0700 Jeremy Chadwick
Quoting Peter Ross peter.r...@bogen.in-berlin.de:
Quoting Scott Sipe csco...@gmail.com:
On Wed, Jul 6, 2011 at 4:21 AM, Peter Ross
peter.r...@bogen.in-berlin.dewrote:
Quoting Peter Ross peter.r...@bogen.in-berlin.de**:
Quoting Peter Ross peter.r...@bogen.in-berlin.de**:
Quoting Jeremy
On 19Jul11 12:04, Jung-uk Kim wrote:
}On Tuesday 19 July 2011 07:20 am, Callum Gibson wrote:
} I've just noticed and tracked down a regression in
} x86/cpufreq/powernow.c (on amd64) which was first mentioned here:
}
} http://lists.freebsd.org/pipermail/freebsd-current/2011-March/02350
}9.html
}
}
On Tue, 19 Jul 2011, Chuck Swiger wrote:
Is there something in FreeBSD which is preventing you from using the
drive's native DEV_BSIZE of 4096 bytes, or is it that the drive claims
to have a physical block size of 512 bytes when it is really 4k?
Are there any 4K-block drives that are honest
Chuck Swiger cswi...@mac.com wrote:
On Jul 19, 2011, at 2:10 PM, Peter Jeremy wrote:
On 2011-Jul-19 10:54:38 -0700, Chuck Swiger cswi...@mac.com wrote:
Unix operating systems like SunOS 3 and NEXTSTEP would happily
run with a DEV_BSIZE of 1024 or larger-- they'd boot fine off
of optical
On Wed, Jul 20, 2011 at 02:39:28AM -0700, per...@pluto.rain.com wrote:
Chuck Swiger cswi...@mac.com wrote:
On Jul 19, 2011, at 2:10 PM, Peter Jeremy wrote:
On 2011-Jul-19 10:54:38 -0700, Chuck Swiger cswi...@mac.com wrote:
Unix operating systems like SunOS 3 and NEXTSTEP would happily
On Jul 19, 2011, at 8:14 PM, Jeremy Chadwick wrote:
On Wed, Jul 20, 2011 at 02:39:28AM -0700, per...@pluto.rain.com wrote:
IIRC, Plextor (and maybe some others) had a switch to select 512 or
2048 as the default transfer size, precisely so that they could be
used as boot devices with systems
23 matches
Mail list logo
