Quoting Garrett Cooper <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
Quoting RW <[EMAIL PROTECTED]>:
On Thu, 28 Jun 2007 10:12:39 -0500
[EMAIL PROTECTED] wrote:
What I am trying to do is compile an amd64 kernel, install it and
see what happens ;) I can always go back to the generic kernel
[EMAIL PROTECTED] wrote:
Quoting RW <[EMAIL PROTECTED]>:
On Thu, 28 Jun 2007 10:12:39 -0500
[EMAIL PROTECTED] wrote:
What I am trying to do is compile an amd64 kernel, install it and
see what happens ;) I can always go back to the generic kernel
compiled in sys/i386.
amd64 and i386 are dif
Quoting Erik Trulsson <[EMAIL PROTECTED]>:
On Thu, Jun 28, 2007 at 10:12:39AM -0500, [EMAIL PROTECTED] wrote:
Quoting RW <[EMAIL PROTECTED]>:
>On Wed, 27 Jun 2007 14:54:52 -0500
>[EMAIL PROTECTED] wrote:
>
>>I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
>>686-class CPU)
Quoting RW <[EMAIL PROTECTED]>:
On Thu, 28 Jun 2007 10:12:39 -0500
[EMAIL PROTECTED] wrote:
What I am trying to do is compile an amd64 kernel, install it and
see what happens ;) I can always go back to the generic kernel
compiled in sys/i386.
amd64 and i386 are different platforms in the sa
On Thu, 28 Jun 2007 10:12:39 -0500
[EMAIL PROTECTED] wrote:
> What I am trying to do is compile an amd64 kernel, install it and
> see what happens ;) I can always go back to the generic kernel
> compiled in sys/i386.
amd64 and i386 are different platforms in the same sense that sparc64
and ppc
On Thu, Jun 28, 2007 at 10:12:39AM -0500, [EMAIL PROTECTED] wrote:
> Quoting RW <[EMAIL PROTECTED]>:
>
> >On Wed, 27 Jun 2007 14:54:52 -0500
> >[EMAIL PROTECTED] wrote:
> >
> >>I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
> >>686-class CPU) into a new box with an AMD Athlon
Quoting RW <[EMAIL PROTECTED]>:
On Wed, 27 Jun 2007 14:54:52 -0500
[EMAIL PROTECTED] wrote:
I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
686-class CPU) into a new box with an AMD Athlon(tm) 64 Processor
3800+ (2387.78-MHz 686-class CPU). I am still building a daily
ker
On Wed, 27 Jun 2007 14:54:52 -0500
[EMAIL PROTECTED] wrote:
> I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
> 686-class CPU) into a new box with an AMD Athlon(tm) 64 Processor
> 3800+ (2387.78-MHz 686-class CPU). I am still building a daily
> kernel with the old configu
Quoting Roland Smith <[EMAIL PROTECTED]>:
On Wed, Jun 27, 2007 at 02:50:30PM -0500, [EMAIL PROTECTED] wrote:
I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
686-class CPU) into a new box with an AMD Athlon(tm) 64 Processor 3800+
(2387.78-MHz 686-class CPU). I am still b
On Wed, Jun 27, 2007 at 02:50:30PM -0500, [EMAIL PROTECTED] wrote:
> I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
> 686-class CPU) into a new box with an AMD Athlon(tm) 64 Processor 3800+
> (2387.78-MHz 686-class CPU). I am still building a daily kernel with the
> ol
I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
686-class CPU) into a new box with an AMD Athlon(tm) 64 Processor
3800+ (2387.78-MHz 686-class CPU). I am still building a daily kernel
with the old configuration and all is well. Of course the old
configuration was/is i
I have just stuck the disks from an old AMD Athlon(tm) (1333.39-MHz
686-class CPU) into a new box with an AMD Athlon(tm) 64 Processor
3800+ (2387.78-MHz 686-class CPU). I am still building a daily kernel
with the old configuration and all is well. Of course the old
configuration was/is i
12 matches
Mail list logo