public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: help with hd problem.
Date: Thu, 21 Jun 2007 22:15:30 -0500	[thread overview]
Message-ID: <002701c7b47b$96feb340$ab00a8c0@tenstac> (raw)
In-Reply-To: <1182468805.17350.31.camel@ubuntu1>

Cody Hurst wrote:
you cannot mix hd installs with other machines because when you install
linux, it is compiled and molded to that particular system and no other
systems I have the same issue when I do it. Do a clean install on the
machine you want to run it on.

Say what? This is not true, I have done it dozens of times. I have in 
fact set up machines as build machines for others. The only thing that
is "molded" is the kernel. As said in recent thread, what you need is 
a generic kernel, not pentium or amd specific. To be more clear, in 
the kernel config, you want 386 processor:

Subarchitecture Type
PC-compatible  (CONFIG_X86_PC)

Processor family 
386  (CONFIG_M386) 

A 386 kernel will boot on anything. You also want generic chipset
stuff, not anything specific to the original hardware. The easiest way
to achieve this is to get one of the already made generic kernels, 
the ones that boot when you run an install. On slackware that is 
called bare.i, it will boot on anything! Equivalents are available on 
other distros. And repeating what I said before: if a kernel will 
not boot on any system, boot with floppy or cd, load the kernel
from that media but use the root= parameter to boot into the 
root on the hard drive. This has never failed for me unless the
drive is toast. You need to catch the boot: prompt and do 
something like 

boot: bare.i root=/dev/hda1 noinitrd ro 

where bare.i is the name of your generic kernel. You should
be able to find a generic kernel for debian. Once you have 
booted from the CD or floppy, with the root= to your hard
drive, you have a running system, build a kernel on the target
and then update bootloader. It is definitely possible to move 
drives from one machine to another. 

  -- Doug




  parent reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Littlefield, Tyler
 ` Cody Hurst
   ` Littlefield, Tyler
   ` Doug Sutherland [this message]
     ` Littlefield, Tyler
       ` Gregory Nowak
         ` Littlefield, tyler
           ` Gregory Nowak
             ` Littlefield, tyler
         ` Re[2]: " Farhan
           ` Gregory Nowak
         ` Alex Snow
 ` Ralph W. Reid
   ` Littlefield, tyler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002701c7b47b$96feb340$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).