Charles Curley | 3 Sep 2002 14:29
Favicon

Booting tomsrtbt from Mess-DOS

Has anyone gotten tomsrtbt to boot directly from Mess-DOS without
building a floppy?

I have a laptop with no floppy drive and it doesn't boot to the
CD-ROM, so that leaves a Mess-DOS boot.

--

-- 

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://w3.trib.com/~ccurley     / \    No M$ Word docs in email
Warren Doney | 3 Sep 2002 21:07
Picon

Re: Booting tomsrtbt from Mess-DOS

On Wed, 04 Sep 2002 00:29, Charles Curley wrote:
> Has anyone gotten tomsrtbt to boot directly from Mess-DOS without
> building a floppy?
>
> I have a laptop with no floppy drive and it doesn't boot to the
> CD-ROM, so that leaves a Mess-DOS boot.

If it won't, it would be trivial to get it to. IIRC tomsrtbt loads into 
RAM - will be much faster to load it off a HDD with Loaadlin than a 
floppy. You could use the CD-ROM version with the extras too. Google 
"ramfloppy" to see how someone else has done it.
--

-- 
-WBD.

ronin2 | 4 Sep 2002 03:14

2.0.103 /bin/sh bad interpreter

I'm running Debian 3.0 (Woody), and kernel 2.4.18.

The following is the result of trying to execute install.s:

sirius:/home/kjmck/files/software/toms/tomsrtbt-2.0.103# ./install.s
su: ./install.s: /bin/sh: bad interpreter: Permission denied

I've tried logging in as root instead of su-ing to root, with the same
results.

I found the series of messages from Jan-Feb, in which Tom recommended
executing the script from a higher-level directory. I worked my way all
the way back up to /, without success.

I tried changing the first line of the script to point to /bin/bash
instead of /bin/sh (OK, I was getting desperate). Same problem.

Can you recommend something else to try?

--

-- 
Kevin McKinley

Tom Oehser | 4 Sep 2002 04:31
Favicon

Re: 2.0.103 /bin/sh bad interpreter


Dunno, something like "#!/bin/sh" seems pretty hard to mess up.

The thing with running from a higher level directory should only
apply to buildit.s or maybe unpack.s, but not to install.s.

Go ahead and manually superformat or fdformat the diskette and
manually dd the image to it.  The install.s just formats it to
1722 and dds the image, there really isn't anything fancy.

-Tom

On Tue, 3 Sep 2002 ronin2 <at> bellatlantic.net wrote:

> Date: Tue, 3 Sep 2002 21:14:37 -0400
> From: ronin2 <at> bellatlantic.net
> To: tomsrtbt <at> toms.net
> Subject: [tomsrtbt] 2.0.103 /bin/sh bad interpreter
>
> I'm running Debian 3.0 (Woody), and kernel 2.4.18.
>
> The following is the result of trying to execute install.s:
>
> sirius:/home/kjmck/files/software/toms/tomsrtbt-2.0.103# ./install.s
> su: ./install.s: /bin/sh: bad interpreter: Permission denied
>
> I've tried logging in as root instead of su-ing to root, with the same
> results.
>
> I found the series of messages from Jan-Feb, in which Tom recommended
(Continue reading)

Warren Doney | 4 Sep 2002 09:53
Picon

Re: Booting tomsrtbt from Mess-DOS

On Wed, 04 Sep 2002 07:07, you wrote:
> On Wed, 04 Sep 2002 00:29, Charles Curley wrote:
> > Has anyone gotten tomsrtbt to boot directly from Mess-DOS without
> > building a floppy?
> >
> > I have a laptop with no floppy drive and it doesn't boot to the
> > CD-ROM, so that leaves a Mess-DOS boot.
>
> If it won't, it would be trivial to get it to. IIRC tomsrtbt loads
> into RAM - will be much faster to load it off a HDD with Loaadlin
> than a floppy. You could use the CD-ROM version with the extras too.
> Google "ramfloppy" to see how someone else has done it.

I had to see if it would work.

bunzip2 tomsrtbt-2.0.103.ElTorito.288.img.bz2
mount -o loop tomsrtbt-2.0.103.ElTorito.288.img /mnt/foo
mkdir /mnt/dos/rtbt
cp /mnt/foo/bz2bzImage /mnt/dos/rtbt/rtbt
cp /mnt/foo/initrd.bz2 ~/initrd.bz2
bunzip2 ~/initrd.bz2
(might not need to, I don't recall wether or not the kernel can handle a 
bzip2 image, it can handle a gzipped one though. Anyhow once it's 
bunzip2ed, you can mount it on loopback & copy over any add-ons you 
want to the appropriate place - there's 1700 odd KB of spare space)

cp ~/initrd /mnt/dos/rtbt/
cp loadlin.exe /mnt/dos/rtbt/

Boot DOS.
(Continue reading)

rmy | 4 Sep 2002 12:08
Picon
Favicon

Re: 2.0.103 /bin/sh bad interpreter

Kevin,

You wrote:
>The following is the result of trying to execute install.s:
>
>sirius:/home/kjmck/files/software/toms/tomsrtbt-2.0.103# ./install.s
>su: ./install.s: /bin/sh: bad interpreter: Permission denied

Does ./install.s have execute permission?  This is the sort of non-intuitive
error you'd get if it didn't.

Or is the filesystem mounted noexec (which is implied by the mount options
user or users)?

In either case it should work if you do 'sh ./install.s'.

Ron

Charles Curley | 5 Sep 2002 05:34
Favicon

Re: Booting tomsrtbt from Mess-DOS

On Wed, Sep 04, 2002 at 07:53:18PM +1200, Warren Doney wrote:
> On Wed, 04 Sep 2002 07:07, you wrote:
> > On Wed, 04 Sep 2002 00:29, Charles Curley wrote:
> > > Has anyone gotten tomsrtbt to boot directly from Mess-DOS without
> > > building a floppy?
> > >
> > > I have a laptop with no floppy drive and it doesn't boot to the
> > > CD-ROM, so that leaves a Mess-DOS boot.
> >
> > If it won't, it would be trivial to get it to. IIRC tomsrtbt loads
> > into RAM - will be much faster to load it off a HDD with Loaadlin
> > than a floppy. You could use the CD-ROM version with the extras too.
> > Google "ramfloppy" to see how someone else has done it.
> 
> I had to see if it would work.
> 
> bunzip2 tomsrtbt-2.0.103.ElTorito.288.img.bz2
> mount -o loop tomsrtbt-2.0.103.ElTorito.288.img /mnt/foo
> mkdir /mnt/dos/rtbt
> cp /mnt/foo/bz2bzImage /mnt/dos/rtbt/rtbt
> cp /mnt/foo/initrd.bz2 ~/initrd.bz2
> bunzip2 ~/initrd.bz2
> (might not need to, I don't recall wether or not the kernel can handle a 
> bzip2 image, it can handle a gzipped one though. Anyhow once it's 
> bunzip2ed, you can mount it on loopback & copy over any add-ons you 
> want to the appropriate place - there's 1700 odd KB of spare space)

You don't need to bunzip2 it; the kernel will do that for you at boot.

> 
(Continue reading)

Warren Doney | 5 Sep 2002 08:52
Picon

Re: Booting tomsrtbt from Mess-DOS

On Thu, 05 Sep 2002 15:34, Charles Curley wrote:
> On Wed, Sep 04, 2002 at 07:53:18PM +1200, Warren Doney wrote:
> > On Wed, 04 Sep 2002 07:07, you wrote:
> > > On Wed, 04 Sep 2002 00:29, Charles Curley wrote:
> > > > Has anyone gotten tomsrtbt to boot directly from Mess-DOS
> > > > without building a floppy?
> > > >
> > > > I have a laptop with no floppy drive and it doesn't boot to the
> > > > CD-ROM, so that leaves a Mess-DOS boot.
[........]

From the front page of the wiki:

"I recommend using a bootable CD rescue distribution if you have a 
bootable CDROM drive available. Why limit yourself to tomsrtbt if you 
can have a full GUI and 650 MegaBytes of tools?" -- TomOehser.

The same could be said of having a few  100MB free on your DOS 
partition. Why not just use zipslak, or tar a minimal install of your 
favorite rpm/deb based distribution & extract it to a Loopback Root 
Filesystem & boot it with loadlin? About all you'd have to do is edit 
fstab, unless there is some problem with distros that boot with an 
initrd.

The Loopback Root Filesystem HOWTO:
http://www.tux.org/pub/people/kent-robotti/looplinux/loop-root-fs.txt

BTW, if you have tweakui installed in M$, there is an option in it to 
boot to a menu, rather than the GUI.

(Continue reading)

BzF | 18 Sep 2002 23:34
Picon
Favicon

kernel patches

Hello,
I'd like to ask which patches were applied to kernel (and where I can
download them). I tried to look in
http://toms.net/tomsrtbt-sources/part2/rb/v2/in-rb-src/
there is bz2.diff, but there was used at least another one patch for ext3.

Thanks
BzF

BzF | 18 Sep 2002 23:48
Picon
Favicon

joining and extracting archive

Hello,
if I have tar.gz archive divided into severeal pieces with split and put
each on floppy disk, then I can use this command:

( while mount -o ro -t vfat /dev/fd0 /fl; do cat /fl/x*;
echo -n 'Insert next' >&2; umount /fl; read; done ) | gzip -d | tar -xf -

on my "big" distribution to unpack it on-the-fly (without creating
big temporary file by joining all pieces together).

But it doesn't work on tomsrtbt - after inserting second floppy and
pressing a key I got this error:

Segmentation fault
gzip: invalid compressed data--format violated
gzip: invalid compressed data--crc error
gzip: invalid compressed data--length error
tar: Ready for volume 2
tar: Type "go" when ready to proceed (or "quit" to abort):

Is there a way how to unpack this files without joining them somewhere?
(I plan to use it with cd-roms, and on the target harddisk probably won't be
enough space to join the files)

Thanks
BzF


Gmane