#delay in s before booting default
title
root=(hd0,4)
kernel=/vmlinuz2.8.39 root=(hd0,0) ro
Save this file, then run
grub-install
Where can be expressed either in grubian language or in
fstabese language.
As seen in 8), I prefer to have each system equ
ocate if = source disk, of = destination disk with
bs=512! That was in the BACKUP section, so that one could return to
the status quo ante in case of shit | fan.
Interesting point: what's in bytes 447 and 448?
BR from SpamHog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
I have multiple Debian installs on 2 IDE HDs on the same channel.
I want to turn the SLAVE into MASTER & viceversa.
Here's my planned checklist - am I missing anything?
For ease of changing things around, I keep a simple, self-installing
graphic boot _selector_ (GAG) in the MBR of /dev/hda, and
mentaldisasters.cds.merseine.nu
Nice pics! The end of the world is not that far, after all. Yuckkk!
Thanks again...
Filippo / SpamHog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
John Summerfield <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
>> Grub is Grand
And I thought that "Grand Unified Bootloader" was hubristic!
Until recently I used automatically installed lilo or grub rather
indifferently, both as bootloaders and bootselectors. This way I could
what else?
- What are the implications?
- Is one stuck with vulns for now? If so, till when?
Preemptive Gratitude from the SpamHog!
http://filippo.ru.ru
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
n't work anymore. As a result i386 kernels
cannot be exchanged, but for most other architectures this is
possible. <<< /quote
So I still wonder if ALL i386 kernels contain such vendor-provided
modules.
You say compliling everything from source will take care of the binary
API misma
> Since net-install can give you a minimal base system without a network
> then yes, all base debs will be there. You could just look at the list
> of debs supplied on the netinst.iso.
Thank you Douglas!
I did just that, and the following few lines distill the difference
between the debs list o
Thank you again Douglas!
I'll look at all the packages you find objectionable. Some are rarely
used, of course, but my goal is to put together a rather complete but
fully standard Debian stable CLI-only rescue install, mostly because I
didn't find one, and I generally find such a separate on-spind
On Feb 5, 3:30 pm, "Douglas A. Tutty" <[EMAIL PROTECTED]> wrote:
> What's wrong with just GRML?
What's wrong with MS-DOS?
What's wrong with AOL?
:-)
For starters, grml medium wasn't even out of beta last time I checked,
and came with a nice big proviso.
The usual other criticisms apply. Or d
On Feb 5, 3:30 pm, "Douglas A. Tutty" <[EMAIL PROTECTED]> wrote:
> What's wrong with just GRML?
What's wrong with MS-DOS?
What's wrong with AOL?
:-)
For starters, grml medium wasn't even out of beta last time I checked,
and came with a nice big proviso.
The usual other criticisms apply. Or d
On my boxes I install a small Debian stable on its own partition for
service and rescue purposes, an alternative to the many live-CD
distros.
I've been looking for a Custom Debian Distributions or package list or
metapackage which would pull in plenty of CLI-only admin - rescue -
network - securit
On Jan 17, 12:50 pm, Martin Marcher <[EMAIL PROTECTED]> wrote:
>
> i'm also open to suggestions
Hmmm, I'll readup on metapackages.
Never maintained anything, but how hard would it be to prepare
ONE dummy .deb that pulls all the CLI admin/rescue tools I want?.
After a standard net-install one would
Interesting stuff all this!
Joseph: your metapackage is a great starting point.
I'll see if I understand it enough to hack it up for needs.
Thanks to all.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I am selecting a set of add-on packages
for a small "service & rescue" install.
I would like to know what is
already included in the base install,
and in general I'd like to see
the latest version of this list of thigs.
My guess is that it might not be included
in the minimal net-install boot imag
I am cloning a 1-partition system (3.1/i386)
from /dev/hda5 to /dev/hda6,
and intend to install grub in that partition.
No need to change drivers, etc. - *only* the root device.
I already did the following:
- copied all files in the / tree to a filesystem on /dev/hda6
- amended /etc/fstab to m
Thank you Hugo, but I am not really going to use Mondo instead of
understanding what the issue is. :-) Are you sure it rebuilds
initrd.img to fit a new root partition?? (I use and like Mondo though,
and might try it in a Serious Cloning Emergency - ...)
Thank you too Mike, but I have already tr
Thank you for clarifying!
I'll never again root =(hdx,x) after a kernel.
Yet, there must be something else munching up this boot.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Thank you for clarifying!
I'll never again root =(hdx,x) after a kernel.
Yet, there must be something else munching up this boot.
Whence the hda5 reference comes is not explained even by a missing
SECOND specification of hda6 as running root. Nothing anywhere
specifies hda5.
--
To UNSUBSCRIB
Mike,
I promise you, I never meant to touch the MBR! Once you bide grub
(either interactively or from any boot sector of any partition)
root (hdx,y)
you overrule the spell in the MBR.
You can install several distros and have each recognize all the
preexisting ones during the instal, an
?!?! Solved it isn't, but this workaround is FAST :
1 - boot the original system (say, on hda8), get root
2 - get into the cloned system (say, on hda10)
mkdir /mnt/hda10
mount /dev/hda10 /mnt/hda10
3 - fix /dev/hda10 /mnt/etc/fstab and /dev/hda10 /mnt/grub/menu.lst as
described in pr
On a couple of i-386 test machines I am noticing install problems that
appear to change over time. I use floppies, and therefore download the
install package from a repository every time.
I know that if video card recognition works, then fail, then works
again, this has noting to do with D-I prope
22 matches
Mail list logo
