1MB is a magic number. It works with advanced format disks, traditional disks,
some odd SSD and most raid configurations.
Lucas Holt
On Sep 21, 2011, at 4:26 AM, "Thomas Mueller" wrote:
>> From "Matthew D. Fuller" :
>
>> I've been meaning to mention this, but we really should document
>> som
* Garrett Cooper , 20110921 04:34:
> I'd unpack a tarball from the most recent release. It's the easiest
> way to fix things :)..
Well, sometimes this is sufficient:
cd /usr/src/include
make install clean
That way you'll at least get the default system h
Forgot to add this for reference earlier:
http://msdn.microsoft.com/en-us/library/dd758814%28v=sql.100%29.aspx
"Valid Starting Partition Offsets" has some justification for the 1M
offset.
___
freebsd-current@freebsd.org mailing list
http://lists.freeb
On Wed, 21 Sep 2011, Thomas Mueller wrote:
From "Matthew D. Fuller" :
I've been meaning to mention this, but we really should document
somewhere that it has a _MAXIMUM_ size.
I setup a system a few weeks back with GPT, and figured I'd just make
the first 'real' partition start at the 1 meg
On 19 August 2011 05:07, Garrett Cooper wrote:
> Hi,
> I've periodically seen the following LOR when trying to repro a
> panic after restarting my network configuration:
>
> :lock order reversal:
> 1st 0xc4142f1c rtentry (rtentry) @ /usr/src/sys/net/routec:362
> 2nd 0xc3d08604 if_afdata (if_a
On 21/09/2011 04:34, Garrett Cooper wrote:
> On Sep 20, 2011, at 6:19 PM, Kevin Oberman wrote:
>> To build a new system, you have to start with something. You build the
>> toolcain and gcc. Those have to be built first with the existing compiler
>> and toolchain which uses the existing system in
>From "Matthew D. Fuller" :
> I've been meaning to mention this, but we really should document
> somewhere that it has a _MAXIMUM_ size.
> I setup a system a few weeks back with GPT, and figured I'd just make
> the first 'real' partition start at the 1 meg mark. And make
> everything before tha
On Tue, 20 Sep 2011 00:27:22 +0300, Kostik Belousov wrote:
KB> Could you, please, test the change below ? For me, I still can truss(1)
KB> or debug with gdb after the change applied. Does truss work for you
KB> with only this change, without resetting SIGTRAP handler in truss process ?
KB>
KB> com
