I think the only limitation you’re going to run into is the boot image one,
where the boot image must be below the 2G mark. If you want to access all of
the disk, I’d suggest making a small boot partition (as low as 400MB will work
wonderfully) with a partition type of 77 (hd0t77), then make the rest of the
disk one great big type 78 partition (hd0t78). When your system boots from
hd0t77, you just add to your sysinit file “mount /dev/hd0t78 /u” or whatever
you want to call it besides /u. Then away you go…
One thing we do, to make upgrading the O.S. easy (which looks like it’s
thwarted in the standard QNX6 install), is to put all of our “permanent” or
application data on a separate disk which is mounted as /u in our systems. We
have a smallish universal sysinit file which mounts the /u partition then execs
/u/etc/config/sysinit.<node#> which creates namespace prefixes to things like
/etc/passwd, and so on. What this allows us to do is shut down a machine,
yoink the boot/os drive which is in a Kingston removeable crive carrier, shove
in a pre-fabbed newer O.S. boot drive, and turn the machine back on. We’ve got
one machine that we keep up to date with build files, boot images and whatnot
for each node, and that’s what we build the o.s. drives from. It sure has made
our lives a lot easier.
“Magaly Azevedo” <email@example.com> wrote in message
| I have to install Qnx 4.23A in a 13 gig HD - does anyone know exactly how
| many gigabytes Qnx4.23A can “see” ?? The system actually needs less than 1
| gig - it is an old installation, but you can’t buy “small” HD today. Do I
| have to type in manually the number of cylinders ??
| Thanks !