It’s kind of impossible latetly to buy a small HDD.
All I could hind was 20GB, so I had to split it into two partitions
/dev/hd0t77 (bootable) and /dev/hd0t78 (mounted as /).
What is the minimum set of files for /dev/hd0t77?
Is it enough to just have the .boot and .altboot there?
Tony.
Tony <mts.spb.suxx@mail.ru> wrote:
It’s kind of impossible latetly to buy a small HDD.
All I could hind was 20GB, so I had to split it into two partitions
/dev/hd0t77 (bootable) and /dev/hd0t78 (mounted as /).
What is the minimum set of files for /dev/hd0t77?
Is it enough to just have the .boot and .altboot there?
Why not just do a full install on t77?
In fact, the minimum to have on t77 is a /.boot file. (And you probably
also want a /.altboot.) If in your boot script, you mount t78 as /
(instead of t77) everything else can be on t78.
David Gibbs
QNX Training Services
dagibbs@qnx.com
On Thu, 16 Jun 2005 19:50:41 +0400, David Gibbs <dagibbs@qnx.com> wrote:
Why not just do a full install on t77?
It’s not “kewl enough” for a QNX4-master as me!
Seriously - wouldn’t it infringe the License to have two installations for
the same set of licenses?
And I’d like not to waste HDD space no matter how huge it might be…
I want to create a one-cylinder partition and put there not a byte over
what is absolutely nesessary.
Tony.
PS
I was wrong (in some my previous post) regarding the way to hide the
…licenses file. It does not work if I hide it in the t77 and do the t78 my
“/”. It’s a pity.
Please consider returning to the old-style licenses (in /etc/licenses).
Tony wrote:
I want to create a one-cylinder partition and put there not a byte over
what is absolutely nesessary.
cylinders, Cylinders! CYLINDERS!!! &$*&^$&^%@#@! The PC and it’s bloody cylinders, I’ll beat your cylinders right through that there BIOS!
Ahhh… and feeling relaxed …
David Gibbs wrote:
Why not just do a full install on t77?
very dangerous
in qnx4 when you install new image (eg: cp new_image .boot) and the
partition is spanning over first 1024 cylinders (8 GB) on the disk then
you risk that the image end up on cylinders with higher address than
1024, thus making the system not bootable
it is better to create a separate boot partition spanning under first
1024 cylinders (eg: start at cylinder 0 and end at cylinder 0 (size 8
MB)) and install the image in there and in the image mount the second
(big) partition as filesystem root
On Fri, 17 Jun 2005 12:37:57 +0400, Stepan Hejny <sh@aveco.com> wrote:
it is better to create a separate boot partition spanning under first
1024 cylinders (eg: start at cylinder 0 and end at cylinder 0 (size 8MB))
That is exactly what I’m doing.
Tony.
We’ve been doing sort of the same thing for years, except we have a
“system partition” and a “user partition”. The system partition (t77)
holds all the QNX installed packages and can be over written with a
fresh install or update any time one is needed. It only needs to be
about 110M to hold a full install (we do 200M just to be safe 
. The
user partition holds all our persistent data and custom applications…
and can be whatever size is needed.
That schema has worked just fine (since could it be? '93?)… but, then
we switched over to RAID based SCSI 160 disk systems for all our QNX4
nodes… and QNX4 won’t boot off the RAID, period. So what we’ve done
is install IDE Flash drives as our boot devices(16M or 32M works fine,
if you can still find them that small). All that’s on the flash drives
is the boot loader, .boot and .altboot. The .boot just starts
Fsys.aha8scsi and mounts the t77 & t78 partitions on the RAID drives.
We don’t even bother to fire up Fsys.eide unless we need access to a CD
drive or want to install a new boot image.
-Rob
Tony wrote:
On Fri, 17 Jun 2005 12:37:57 +0400, Stepan Hejny <> sh@aveco.com> > wrote:
it is better to create a separate boot partition spanning under first
1024 cylinders (eg: start at cylinder 0 and end at cylinder 0 (size 8MB))
That is exactly what I’m doing.Tony.
Tony <mts.spb.suxx@mail.ru> wrote:
On Thu, 16 Jun 2005 19:50:41 +0400, David Gibbs <> dagibbs@qnx.com> > wrote:
Why not just do a full install on t77?
It’s not “kewl enough” for a QNX4-master as me!
Ok, then as I suggested, you can’t get smaller than just .boot (and
…altboot) on the t77 partition.
Seriously - wouldn’t it infringe the License to have two installations for
the same set of licenses?
IANAL, nor can I officially answer a licensing question for QNX Software
Systems, but I don’t think so. You’ll only be running one of those
installs at any particular time, and they are on the same machine (even
if different partitions) so I don’t think there would be any problem
with that setup at all.
And I’d like not to waste HDD space no matter how huge it might be…
I want to create a one-cylinder partition and put there not a byte over
what is absolutely nesessary.
Dunno how big one cylinder is on your disk – but you’ll need about
1.3M – two < 640K images, and a bit of filesystem data.
I was wrong (in some my previous post) regarding the way to hide the
.licenses file. It does not work if I hide it in the t77 and do the t78 my
“/”. It’s a pity.
Please consider returning to the old-style licenses (in /etc/licenses).
I don’t think that is going to happen.
David Gibbs
QNX Training Services
dagibbs@qnx.com
How are you guys mounting the large partition as root ‘/’?
What do typically use for the boot partition mount point?
I have an 8 GB boot partition as root ‘/’.
Then I have a second larger partition with all our data that I call ‘/p1’.
Then I need to make some symbolic links to make all work…
I wish there was a simple way to set the large partition as root ‘/’.
TIA
Augie
“Rob Hem” <rob@spamyourself.com> wrote in message
news:d8upnp$qpm$1@inn.qnx.com…
We’ve been doing sort of the same thing for years, except we have a
“system partition” and a “user partition”. The system partition (t77)
holds all the QNX installed packages and can be over written with a fresh
install or update any time one is needed. It only needs to be about 110M
to hold a full install (we do 200M just to be safe >
partition holds all our persistent data and custom applications… and can
be whatever size is needed.That schema has worked just fine (since could it be? '93?)… but, then we
switched over to RAID based SCSI 160 disk systems for all our QNX4
nodes… and QNX4 won’t boot off the RAID, period. So what we’ve done is
install IDE Flash drives as our boot devices(16M or 32M works fine, if you
can still find them that small). All that’s on the flash drives is the
boot loader, .boot and .altboot. The .boot just starts Fsys.aha8scsi and
mounts the t77 & t78 partitions on the RAID drives. We don’t even bother
to fire up Fsys.eide unless we need access to a CD drive or want to
install a new boot image.-Rob
Tony wrote:
On Fri, 17 Jun 2005 12:37:57 +0400, Stepan Hejny <> sh@aveco.com> > wrote:it is better to create a separate boot partition spanning under first
1024 cylinders (eg: start at cylinder 0 and end at cylinder 0 (size
8MB))
That is exactly what I’m doing.Tony.
Augie <augiehenriques@hotmail.com> wrote:
How are you guys mounting the large partition as root ‘/’?
What do typically use for the boot partition mount point?
I have an 8 GB boot partition as root ‘/’.
Then I have a second larger partition with all our data that I call ‘/p1’.
Then I need to make some symbolic links to make all work…I wish there was a simple way to set the large partition as root ‘/’.
It’s not that hard. You can mount any partition you want as root.
In my buildfile I have:
/bin/mount
$ 1000 mount -p /dev/hd0 /dev/hd0t79 /
Boot that image from any partition, or even a floppy or network, and it
will mount partition t79 as /.
David Gibbs
QNX Training Services
dagibbs@qnx.com
How about /dev/hd0t77?
TIA
Augie
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:d8usaf$rtb$2@inn.qnx.com…
Augie <> augiehenriques@hotmail.com> > wrote:
How are you guys mounting the large partition as root ‘/’?What do typically use for the boot partition mount point?
I have an 8 GB boot partition as root ‘/’.
Then I have a second larger partition with all our data that I call
‘/p1’.
Then I need to make some symbolic links to make all work…I wish there was a simple way to set the large partition as root ‘/’.
It’s not that hard. You can mount any partition you want as root.
In my buildfile I have:
/bin/mount
$ 1000 mount -p /dev/hd0 /dev/hd0t79 /Boot that image from any partition, or even a floppy or network, and it
will mount partition t79 as /.-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Augie <augiehenriques@hotmail.com> wrote:
How about /dev/hd0t77?
As in, if you boot from t77, but want to mount t79, sure that works. Or as in,
to mount t77? Again, no problem – make the obvious change:
/bin/mount
$ 1000 mount -p /dev/hd0 /dev/hd0t77 /
David Gibbs
QNX Training Services
dagibbs@qnx.com
David,
I’m getting confused…
Can you please post both correct mounts for the boot partition and the large
partition (/)?
Also…
Is the /home directory created in the boot partition or the large partition?
TIA
Augie
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:d8v0fm$291$1@inn.qnx.com…
Augie <> augiehenriques@hotmail.com> > wrote:
How about /dev/hd0t77?As in, if you boot from t77, but want to mount t79, sure that works. Or as
in,
to mount t77? Again, no problem – make the obvious change:/bin/mount
$ 1000 mount -p /dev/hd0 /dev/hd0t77 /-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Augie <augiehenriques@hotmail.com> wrote:
David,
I’m getting confused…
Can you please post both correct mounts for the boot partition and the large
partition (/)?
Let’s assume you have a minimal partition for boot images, t77.
You have a big partition, with a full install and everything t78.
In your buildfile:
/bin/mount
$ 1000 mount -p /dev/hd0 /dev/hd0t78 /
Then, in your sysinit you would add:
mount /dev/hd0t77 /boot
If you wanted access to your .boot and .altboot files. To change
your bootable image, you would modify /boot/.boot or /boot/.altboot.
Also…
Is the /home directory created in the boot partition or the large partition?
You’d want it in the large partition. Or, you might even choose to have
it on a partition of it’s own. Say, t80.
mount /dev/hd0t80 /home
Or, on a seperate disk:
mount -p /dev/hd1
mount /dev/hd1t78 /home
Again, everything but the / partition would generally be mounted in
the sysinit, rather than the boot file – more flexible, easier to
debug, better control of what is happening.
David Gibbs
QNX Training Services
dagibbs@qnx.com
David,
How would the install from the CD be done for this?
Or do I do the regular install and then teak the system?
See bellow…
TIA
Augie
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:d8v4nk$50c$1@inn.qnx.com…
Augie <> augiehenriques@hotmail.com> > wrote:
David,I’m getting confused…
Can you please post both correct mounts for the boot partition and the
large
partition (/)?Let’s assume you have a minimal partition for boot images, t77.
You have a big partition, with a full install and everything t78.In your buildfile:
/bin/mount
$ 1000 mount -p /dev/hd0 /dev/hd0t78 /
What does the 1000 do before the mount?
Then, in your sysinit you would add:
mount /dev/hd0t77 /boot
If you wanted access to your .boot and .altboot files. To change
your bootable image, you would modify /boot/.boot or /boot/.altboot.Also…
Is the /home directory created in the boot partition or the large
partition?You’d want it in the large partition. Or, you might even choose to have
it on a partition of it’s own. Say, t80.mount /dev/hd0t80 /home
Or, on a seperate disk:
mount -p /dev/hd1
mount /dev/hd1t78 /homeAgain, everything but the / partition would generally be mounted in
the sysinit, rather than the boot file – more flexible, easier to
debug, better control of what is happening.-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Augie wrote:
David,
How would the install from the CD be done for this?
Or do I do the regular install and then teak the system?
See bellow…
TIA
Augie
During the install create both partitions. Install to the larger
partition. After the install, boot from the CD again (as you wont be
able to boot from the hard disk as the partition cross 1024 cylinders).
From the install open a terminal, start the Filesystem driver mounting
your second partition as ‘/’ (or mount as anything and prefix it to /).
Now you will have access to all the QNX utilities. You can then dinit
the small partition and create your OS image, modify your sysinit file
and make the small partition bootable (w/ fdisk).
Regards,
Joe
Joe,
Thanks.
I will give this a try.
It would be super for the install to be able to do this… Or have at least
an option for this…
TIA
Augie
“Joe Mammone” <hw@qnx.com> wrote in message news:d8v8un$858$1@inn.qnx.com…
Augie wrote:
David,How would the install from the CD be done for this?
Or do I do the regular install and then teak the system?
See bellow…
TIA
Augie
During the install create both partitions. Install to the larger
partition. After the install, boot from the CD again (as you wont be able
to boot from the hard disk as the partition cross 1024 cylinders). From
the install open a terminal, start the Filesystem driver mounting your
second partition as ‘/’ (or mount as anything and prefix it to /). Now you
will have access to all the QNX utilities. You can then dinit the small
partition and create your OS image, modify your sysinit file and make the
small partition bootable (w/ fdisk).Regards,
Joe
On Fri, 17 Jun 2005 11:35:48 +0400, Evan Hillas <evanh@clear.net.nz> wrote:
cylinders, Cylinders! CYLINDERS!!! &$*&^$&^%@#@!
Seems - the winter is getting you!
You sound like someone at M$.
Tony.
Tony wrote:
You sound like someone at M$.
Not likely. Although they may have very little to do with IDE and it’s CHS crap, I do very much blame M$ for the lack of partition slot entries.
Evan
On Sat, 18 Jun 2005 04:15:05 +0400, Evan Hillas <evanh@clear.net.nz> wrote:
Not likely.
Remember: “Developers! Developers!!!..”?
Tony.