On Tue, Jan 24, 2006 at 03:49:54AM +, [EMAIL PROTECTED] wrote:
and I never messed with an initrd. My understanding is that the purpose
of an initrd is to provide an image of a RAMdisk containing the modules
the kernel needs to access the root file system; but if the hardware and
On Mon, Jan 23, 2006 at 05:46:48PM -0500, Robert Isaac wrote:
You could even save yourself some effort and install Yaird from backports.org
:)
It wasn't there when I did it. :)
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Tue, Jan 24, 2006 at 03:49:54AM +, [EMAIL PROTECTED] wrote:
OK, I have a dumbass question: why is yaird necessary at all? Or more
accurately, why is an initrd necessary at all? Is it something about
2.6.x kernels? Back when I built 2.4.x kernels for my Athlon XP machine,
I follwed
Lennart Sorensen wrote:
On Sun, Jan 22, 2006 at 09:09:23AM -0500, [EMAIL PROTECTED] wrote:
It worked beautifully.
A day or two ago, the URL seems to have changed.
http://tinyplanet.ca/~lsorense/amd64/
works now.
I didn't know port 81 had ever worked on that machine. It is run by one
On Tue, Jan 24, 2006 at 12:21:10PM -0600, Ken Bloom wrote:
The package may have been renamed to linux-image-* instead of
kernel-image-*.
It certainly would have been. :)
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On 1/22/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Sun, Jan 15, 2006 at 09:49:41PM -0500, [EMAIL PROTECTED]
wrote: On Sun, Jan 15, 2006 at 10:50:22PM +, Jo Shields wrote: [EMAIL PROTECTED] wrote: I haven't accepted the new AMD-64 box the computer store has
built for me, because I
On Sun, Jan 22, 2006 at 09:09:23AM -0500, [EMAIL PROTECTED] wrote:
It worked beautifully.
A day or two ago, the URL seems to have changed.
http://tinyplanet.ca/~lsorense/amd64/
works now.
I didn't know port 81 had ever worked on that machine. It is run by one
of my friends.
I now have
Upgrading past 2.6.12 requires getting yaird or initramfstools installed
on sarge somehow. It can be done however. Yaird is not too hard to
backport.
You could even save yourself some effort and install Yaird from backports.org :)
Robert Isaac wrote:
Upgrading past 2.6.12 requires getting yaird or initramfstools installed
on sarge somehow. It can be done however. Yaird is not too hard to
backport.
You could even save yourself some effort and install Yaird from backports.org
:)
OK, I have a dumbass question:
On Sun, Jan 15, 2006 at 09:49:41PM -0500, [EMAIL PROTECTED] wrote:
On Sun, Jan 15, 2006 at 10:50:22PM +, Jo Shields wrote:
[EMAIL PROTECTED] wrote:
I haven't accepted the new AMD-64 box the computer store has
built for me, because I can't get it to run in 64-bit mode.
I provided
On Sun, Jan 15, 2006 at 09:55:15PM -0500, [EMAIL PROTECTED] wrote:
Sorry to sound terminally stupid, but I don't know how to translate a
URL like
http://debian.csail.mit.edu/debian-amd64/debian-amd64/pool/main/
into a deb line for /etc/apt/sources.list
And how does aptitude figure out which
[EMAIL PROTECTED] wrote:
I haven't accepted the new AMD-64 box the computer store has
built for me, because I can't get it to run in 64-bit mode.
I provided the sarge net-install CD's for both AMD-64 and the older
386 architectures.
The netinstall for AMD64 went fine up to a point (except it
On Sun, Jan 15, 2006 at 01:52:19PM -0900, Greg Madden wrote:
I use debian.csail.mit.edu.
Sorry to sound terminally stupid, but I don't know how to translate a
URL like
http://debian.csail.mit.edu/debian-amd64/debian-amd64/pool/main/
into a deb line for /etc/apt/sources.list
And how does
13 matches
Mail list logo
