Another installation on the same disk
Filippo
there. It could be another Slackware or Zenwalk, to do some tests. I also
have a ntfs and a fat32 partition. And lilo does double boot between
Slackware 10.2 and WinXP.
The question: do I risk to erase or do some damage if I install one of those
systems?
Are there some precautions that I should take?
Douglas Mayne
> I have a free reiserfs 4GB partition, and I would like to install another OS
> there. It could be another Slackware or Zenwalk, to do some tests. I also
> have a ntfs and a fat32 partition. And lilo does double boot between
> Slackware 10.2 and WinXP.
> The question: do I risk to erase or do some damage if I install one of those
> systems?
Do you mean windows? ;-) The best way to avoid damaging something else
which may be on your disk is to be careful. Know what you're doing and
know your intended target. Missing a target can be hazardous to your
system.
> Are there some precautions that I should take?
>
Note: comment inline.
The first thing /* I */ would do is switch to the grub loader. Then you
will be able to do your multiboot tricks. Install grub at the mbr. Then
when you install new OS, create a new grub stanza manually.
You can also test that the grub loader install succeeded before you add
anything else. Caution: make a bootfloppy beforehand, or otherwise have a
fallback position to avoid locking yourself out.
--
Russell: You're not gonna report this or anything, are you?
Louise: I'm gonna treat it like a UFO sighting.
"I saw something, but I'm not quite sure what it was."
http://us.imdb.com/title/tt0083131/
Stanislaw Flatto
> I have a free reiserfs 4GB partition, and I would like to install another OS
> there. It could be another Slackware or Zenwalk, to do some tests. I also
> have a ntfs and a fat32 partition. And lilo does double boot between
> Slackware 10.2 and WinXP.
> The question: do I risk to erase or do some damage if I install one of those
> systems?
> Are there some precautions that I should take?
Nothing special. This IS Linux after all, a simple, obedient creature
that does exactly as ordered.
Now to the story:
you want to install another Linux distro on the 4Gb slice on your hard
disk. The file system on this slice has no importance as most installs
re-initialise the intended partition during install.
You have LILO as booting manager, put in your existing /etc/lilo.conf a
stanza calling "guest" distro from the intended partition, and when
installing the "guest" tell its LILO to install itself _on partition_.
In this configuration you don't have to do anything to your native
distro and can install different "guest(s)" which will be booted in the
same manner.
Have fun
Stanislaw
Slack user from Ulladulla.
Grant
>The first thing /* I */ would do is switch to the grub loader. Then you
>will be able to do your multiboot tricks. Install grub at the mbr. Then
>when you install new OS, create a new grub stanza manually.
Do you run grub with multi-boot windoze + linux?
Because there's a problem with some windoze tools that may overwrite
the grub second stage (somebody wrote it was grub stage 1.5) --> you
seen this and have a way to avoid?
'cos I stay with lilo, nobody's convinced grub good for anything yet ;)
I have a box with windoze dual-boot to play with and sort this out if
only to clarify the lilo / grub argument... Maybe they fixed it...
Grant.
--
Memory fault -- brain fried
Douglas Mayne
> On Fri, 31 Mar 2006 11:52:09 -0700, Douglas Mayne <do...@localhost.localnet> wrote:
>
>>The first thing /* I */ would do is switch to the grub loader. Then you
>>will be able to do your multiboot tricks. Install grub at the mbr. Then
>>when you install new OS, create a new grub stanza manually.
>
> Do you run grub with multi-boot windoze + linux?
>
> Because there's a problem with some windoze tools that may overwrite
> the grub second stage (somebody wrote it was grub stage 1.5) --> you
> seen this and have a way to avoid?
I haven't seen it stop working without a reason to stop working. Do you have
a specific reminder of an app that breaks the loader. I remember seeing
something about something (Windows or an app) writing in unclaimed space
in the first cylinder. That is where grub 1.5 lives. So if the loader
stops working suddenly (with grub at the MBR), then that is a "canary in
the coal mine," telling you something is overwritten. But IME, the OS
_should_ boot with a simple link using chainloader.
One way to avoid getting locked out of your system is to have a recovery CD.
If you have a copy of my project CD, then you can use it to test without
installing grub. Just boot the CD and press "c" for a command line. Then
something like this:
grub> rootnoverify (hd0,0)
grub> makeactive
grub> chainloader +1
grub> boot
I have seen the Windows loader to fail to work with some discs with large
partition sizes (on NT4 and >8G). The way around that is (usually) to
keep a primary partition <8G (doesn't have to be partition 1) where ntldr,
ntdetect.com, and boot.ini live. This partition can also be used mainly
for windows swap. Also, install the bootsector code using mkbt.
http://www.nu2.nu/mkbt/
Then chainload to that partition instead of the larger partition. The
windows loader is much like grub, in the fact that it is fully
functional and working if it gets to the stage where the menu can be
displayed. The difference is grub gives you the option of dynamically
entering commands to control the boot (above).
>
> 'cos I stay with lilo, nobody's convinced grub good for anything yet ;)
>
> I have a box with windoze dual-boot to play with and sort this out if
> only to clarify the lilo / grub argument... Maybe they fixed it...
>
> Grant.
>
Note: comments inline.
The thing I have seen with discussions about multiboot is that people swear
by the method they know. I know there is more than one way to multiboot, but
for me it's easiest to setup a dual boot machine using grub, installed at the
MBR.
I use the grub loader multiboot with Windows: NT, 2k, and XP (with limited
experience.) I know if you install Windows after Linux, then the MBR is
overwritten and needs to be fixed. IME, grub can be reinstalled and will
boot all of the OSs present. I did some tests (strictly with Linux and
filesystems (jfs, xfs, reiserfs, ext2) which showed it works best if grub
is installed at the MBR. My tests showed some problems with chainloader.
Also, some later tests (which I need to complete and document) showed that
chainloader works a little better under grub v0.96 than v0.97. I want to
confirm that for a fact, though- so don't quote me.
I also stumbled into the site for the RIP CD: recovery is possible. He
is using a patched version of grub which can read from NTFS- which is
something new.
If you have a system to test, then try it out.
Just one more thing. I really think VMWare is superior to dual booting.
The idea is to fire up a virtual machine using Slackware as the host
whenever a Windows computer is required. You can download a 30 day free
trial of VMWare. It really does save time rebooting. I just keep a
Windows machine running on suspend within VMWare, and when I need it I
press resume. It is ready in 5-10 seconds. I still keep machines dual boot
for users who are not ready to switch to GNU/Linux. The dual boot
environment gives the platform for a complete backup of windows or a
complete virus scan.
--
Douglas Mayne
Grant
>On Sat, 01 Apr 2006 09:29:35 +1100, Grant wrote:
...
Firstly, I do find I'm dual booting much less these days, main box is
winxp for desktop, 'net browsing and music; project development, GNU/Linux
downloads with wget or rsync is over PuTTY terminals to slack boxen.
Only laptop and two fastest boxen have dual-boot, I have an old p100 laptop
with Win98 and the rest are mid (hell, make that low)-range boxen CPU speeds
266..500MHz.
>I haven't seen it stop working without a reason to stop working. Do you have
>a specific reminder of an app that breaks the loader. I remember seeing
>something about something (Windows or an app) writing in unclaimed space
>in the first cylinder. That is where grub 1.5 lives.
PowerQuest, virtual floppy boot overwrites first cylinder 2..63 area
(and fails on large drives... ho hum), as does winxp (I've read, but
zeroing sectors 2..63 does not break winxp boot, so I suspect the place
is used as scratch, sometimes --> guess it might be winxp recovery or
optional chkdsk prior to system boot.
> So if the loader
>stops working suddenly (with grub at the MBR), then that is a "canary in
>the coal mine," telling you something is overwritten.
I let windoze keep the MBR, then all I need do is change active primary,
which can be done from windoze or linux. Main point is to know how to
regain control with one's preferred bootloader, not claiming a 'best',
though I do claim convenience ;)
I used to always install a small FAT first primary on a PC, for win98 or
DOS boot to CLI. Weaned off that habit by using slack's syslinux install
boot on one box sans CDROM. Forgot who, someone suggested it here months
ago -- saves the three floppy boot.
> But IME, the OS
>_should_ boot with a simple link using chainloader.
Agree, as same principle allows me to boot FreeBSD too, not that I ever
spent much time in there. I have an account on an IRIX box if I feel
the need for fooling around in a 'foreign' unix environment ;)
>
>One way to avoid getting locked out of your system is to have a recovery CD.
...
Sure - that is where I feel a win, being able to recover with either OS +
lilo ;) Beyond that, I have the slack boot cdrom to fallback to.
>I have seen the Windows loader to fail to work with some discs with large
>partition sizes (on NT4 and >8G).
I ran NT4 for years, there's a fix for that, a replacement <something>.exe
for installer, after sp6 came out.
...
>http://www.nu2.nu/mkbt/
similar thing?: http://www.winimage.com/bootpart.htm
>Then chainload to that partition instead of the larger partition.
I sometimes use a small FAT primary to skip over early disk area and
run WinNT from a logical partition, give linux fastest disk area when
it was main OS. Those techniques mean much less now with faster drives
and larger memory for disk caching
> The
>windows loader is much like grub, in the fact that it is fully
>functional and working if it gets to the stage where the menu can be
>displayed.
Yep, they both (grub, WinNT) enumerate visible partitions at boot time,
whereas lilo lays down the 'map' track at install time, which is
basically a simple list of sectors to read into memory.
> The difference is grub gives you the option of dynamically
>entering commands to control the boot (above).
Which is about where I'd be booting a rescue cd instead ;)
...
>The thing I have seen with discussions about multiboot is that people swear
>by the method they know.
It is important to have confidence in one preferred bootloader --> but
trying to convince others is pointless, unless they're faced with a
requirement specifically addressed by one or other method.
> I know if you install Windows after Linux, then the MBR is
>overwritten and needs to be fixed.
Or, one may sidestep that issue with the 'active' flag, leave MBR to
windoze ;)
> I did some tests (strictly with Linux and
>filesystems (jfs, xfs, reiserfs, ext2) which showed it works best if grub
>is installed at the MBR.
Agree, grub does not like running from elsewhere -- which is the only
place I've tested it --> trying to install ubuntu and similar that
strongly demand grub in MBR... Funniest was a trial last ubuntu install
on /dev/sdb3 --> it booted ubuntu kernel but loaded OS root from /dev/sda3,
which was the slackware install!
>I also stumbled into the site for the RIP CD: recovery is possible. He
>is using a patched version of grub which can read from NTFS- which is
>something new.
I download the RIP image 'just in case' -- can't remember using it.
> I really think VMWare is superior to dual booting.
A friend's been telling me that for years, and this box running winxp is
the intended target. Just not got around tuit yet --> built this box
mid 2003... Me slow. One day?
Thing is, while I stumble along and things sort of run okay I don't
care so much. Good to keep up the options though. Trouble with
vmware is they require frequent relicensing fees, but hell, they got
to stay in business. On the good side, a guy from vmware contributes
hypervisor (support for virtualisation) code to linux-kernel, so the
company is better than some.
Where does slack's installer (setup) program live?
Thanks,
Thomas Overgaard
Grant wrote :
> Where does slack's installer (setup) program live?
When you run the 'pkgtool' command you'll find all the setup scripts in
the menu.
--
Thomas O.
This area is designed to become quite warm during normal operation.
Grant
>
>Grant wrote :
>
>> Where does slack's installer (setup) program live?
>
>When you run the 'pkgtool' command you'll find all the setup scripts in
>the menu.
Sorry, I don't see installer in here, the one that goes through
setup swap, select partitions, packages, install...
+-------------Slackware Package Tool (pkgtool version 10.2)---------------+
Ś Ś
Ś Welcome to the Slackware package tool. Ś
Ś Ś
Ś Which option would you like? Ś
Ś +---------------------------------------------------------------------+ Ś
Ś Ś Current Install packages from the current directory Ś Ś
Ś Ś Other Install packages from some other directory Ś Ś
Ś Ś Floppy Install packages from floppy disks Ś Ś
Ś Ś Remove Remove packages that are currently installed Ś Ś
Ś Ś View View the list of files contained in a package Ś Ś
Ś Ś Setup Choose Slackware installation scripts to run again Ś Ś
Ś Ś Exit Exit Pkgtool Ś Ś
Ś +---------------------------------------------------------------------+ Ś
+-------------------------------------------------------------------------Ś
Ś < OK > <Cancel> Ś
+-------------------------------------------------------------------------+
+-------------------SELECT SYSTEM SETUP SCRIPTS----------------------+
Ś Please use the spacebar to select the setup scripts to run. Hit Ś
Ś enter when you are done selecting to run the scripts. Ś
Ś +----------------------------------------------------------------+ Ś
Ś Ś[ ] 70.install-kern Install a Linux kernel from a bootdisk Ś Ś
Ś Ś[ ] 80.make-bootdis Create a Linux boot floppy Ś Ś
Ś Ś[ ] 90.modem-device Select modem device Ś Ś
Ś Ś[ ] liloconfig Set up LILO to boot Linux (and other OSes) fŚ Ś
Ś Ś[ ] mouse Configure the console mouse support (GPM). Ś Ś
Ś Ś[ ] netconfig Configure basic network settings Ś Ś
Ś Ś[ ] services Select/deselect system daemons (services) Ś Ś
Ś Ś[ ] timeconfig Select your timezone Ś Ś
Ś Ś[ ] xwmconfig Choose a default window manager for X Ś Ś
Ś +----------------------------------------------------------------+ Ś
+--------------------------------------------------------------------Ś
Ś < OK > <Cancel> Ś
+--------------------------------------------------------------------+
Grant.
--
Momento mori ( remember that you must die... )
Thomas Overgaard
Grant wrote :
> Sorry, I don't see installer in here, the one that goes through
> setup swap, select partitions, packages, install...
Why are you asking for "setup" when its the "installer" you want? :)
OK. The installer is "nowhere" to be found because it only exist in the
ramdisk that is loaded when you boot from the Slackware install CD-1.
Douglas Mayne
> On Fri, 31 Mar 2006 16:34:42 -0700, Douglas Mayne <do...@localhost.localnet> wrote:
>
>>On Sat, 01 Apr 2006 09:29:35 +1100, Grant wrote:
> ...
> Firstly, I do find I'm dual booting much less these days, main box is
> winxp for desktop, 'net browsing and music; project development, GNU/Linux
> downloads with wget or rsync is over PuTTY terminals to slack boxen.
> Only laptop and two fastest boxen have dual-boot, I have an old p100 laptop
> with Win98 and the rest are mid (hell, make that low)-range boxen CPU speeds
> 266..500MHz.
>
<snip>
>
> I ran NT4 for years, there's a fix for that, a replacement <something>.exe
> for installer, after sp6 came out.
> ...
>>http://www.nu2.nu/mkbt/
> similar thing?: http://www.winimage.com/bootpart.htm
I think it is the same. If you have a working Windows setup, you can
extract the code which is written to the BPB (partition superblock) when
the partition is formatted NTFS. This information is going obsolete
fast, as no more patches are being issued for NT4 (and this applied
mostly to that.)
>
<snip>
>
> A friend's been telling me that for years, and this box running winxp is
> the intended target. Just not got around tuit yet --> built this box
> mid 2003... Me slow. One day?
I have some hardware projects on the back burner, too.
>
> Thing is, while I stumble along and things sort of run okay I don't care
> so much. Good to keep up the options though. Trouble with vmware is
> they require frequent relicensing fees, but hell, they got to stay in
> business. On the good side, a guy from vmware contributes hypervisor
> (support for virtualisation) code to linux-kernel, so the company is
> better than some.
>
If Xen offered a similar alternative, I'd use it. The thing that has some
potential is saving heat and electricity in the server room. That is,
replacing some older less powerful equipment with virtual servers. The
problem it introduces is the need for centralized disk storage, i.e. a
SAN.
> Where does slack's installer (setup) program live?
Do you mean in VMWare? In VMWare you setup a virtual machine with virtual
hardware. Some of the hardware is virtual and some maps to real devices.
So, if the Slackware setup program is on CD- you would setup a virtual
cdrom mapped to an actual device. When the virtual hardware is defined,
you hit the "power" button, which begins the boot for the virtual
computer. The BIOS posts just like a real machine, and has a BIOS boot
order, etc. VMWare has licensed the BIOS code from a BIOS
manufacturer, Phoenix I think.
>
> Thanks,
> Grant.
Note: Comments inline.
--
Douglas Mayne
Wha...@1yahoo.com
ages 3 to 12, to play on. It has XP Pro and PCLinuxOS-p92 from
http://pclinuxos.com
Recommend it highly for kids, noobs!
Douglas Mayne
> Douglas Mayne wrote:
>>
<snip>
>
> Have a AMD XP2.0 ( 1.667Mhz ) system that dual boots, just for the kids,
Where did you get it? You know, the first PC computer that I had ran at
4.77MHz. How long does it take to boot? A 486-33 MHz will take about 5
minutes to boot. Okay, I think you meant GHz.
> ages 3 to 12, to play on. It has XP Pro and PCLinuxOS-p92 from
> http://pclinuxos.com
>
> Recommend it highly for kids, noobs!
>
Okay. But why are you telling me? What is the context in this thread that
you are commenting on?
--
Douglas Mayne
Grant
>Why are you asking for "setup" when its the "installer" you want? :)
'cos I have a lousy memory ;) Until your reply I was trying to remember
what 'pkgtool' was called... Otherwise I would have said, 'not pkgtool'.
>OK. The installer is "nowhere" to be found because it only exist in the
>ramdisk that is loaded when you boot from the Slackware install CD-1.
That's the one! But it should be visible somewhere, outside of booting
the installer? (Source?) Or has P.V. buried it to reduce problems by
people using it on a running system?
Thanks,
cashmir
> That's the one! But it should be visible somewhere, outside of booting
> the installer? (Source?) Or has P.V. buried it to reduce problems by
> people using it on a running system?
>
> Thanks,
> Grant.
you're looking for /disk1/isolinux/initrd.img
to view contents :
-rename to initrd.gz
-gunzip
-mount on a loop dev.
...all just starts with /etc/rc.d/rc.S as usual.
cashmir
Grant
>Op Sun, 02 Apr 2006 07:23:35 +1000, schreef Grant:
[where is slack installer?]
>you're looking for /disk1/isolinux/initrd.img
>
>to view contents :
>
>-rename to initrd.gz
>-gunzip
>-mount on a loop dev.
>...all just starts with /etc/rc.d/rc.S as usual.
Thank you, that's the recipe I was after ;)