Can you put a QNX partition in a extended partition?
I have piece of software that logs data and I want put it in it’s own
partition and put a couple other directories as there own partition.
However I only have 1 partition left. If I could make a “extended
partition” I could put multiple parts in it.
I didn’t see anyway to do this with fdisk.
Any Ideas?
Bob Smith <bobsmith@home.com> wrote:
Can you put a QNX partition in a extended partition?
I have piece of software that logs data and I want put it in it’s own
partition and put a couple other directories as there own partition.
However I only have 1 partition left. If I could make a “extended
partition” I could put multiple parts in it.I didn’t see anyway to do this with fdisk.
Any Ideas?
No. However, you can play tricks. Make an extended DOS partition (using
someone else’s fdisk) and make a big file in that partition and format the
file as QNX4fs and mount the file. Heck, you might even just be able to
use the fat file system directly.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Bob Smith <bobsmith@home.com> wrote:
Can you put a QNX partition in a extended partition?
I didn’t see anyway to do this with fdisk.
The filesystem does handle extended partitions, but the tools
(fdisk) don’t. So you can’t make them, but if you could, you’d
be able to use them. I’m not happy saying this, but you could
use fdisk from another OS to do the partitioning … :-/
Uh…
I have QNX, and windows…
If I can’t do it QNX, do you know of a 3rd party fdisk like utility that
will let me put QNX partition types in a extended partition?
I know I can make extended parts in windows, but it won’t let me put QNX
types in the partition table.
“John Garvey” <jgarvey@qnx.com> wrote in message
news:bi6701$ok$1@nntp.qnx.com…
Bob Smith <> bobsmith@home.com> > wrote:
Can you put a QNX partition in a extended partition?
I didn’t see anyway to do this with fdisk.The filesystem does handle extended partitions, but the tools
(fdisk) don’t. So you can’t make them, but if you could, you’d
be able to use them. I’m not happy saying this, but you could
use fdisk from another OS to do the partitioning … :-/
Bob Smith <bobsmith@home.com> wrote:
If I can’t do it QNX, do you know of a 3rd party fdisk like utility that
will let me put QNX partition types in a extended partition?
I know I can make extended parts in windows, but it won’t let me put QNX
types in the partition table.
Does it matter what the type is? Nothing (except “diskboot”) cares,
you can dinit and mount anything as anything. You could “spatch”
the partition table if you cared. But, from re-reading your original
post I don’t see why you need real partitions? For your log file,
is it to limit the size or to specify different mount options or … ?
As as been suggested, consider using the filesystem-in-a-file trick:
You now have a /mypart filesystem to store things in, the space is
limited to the specified size, you can mount with specific options,
you can backup the filesystem by copying the .img file, ,make as
many container filesystems as you want of whatever size (<2GB), etc
(almost all the benefits of the partition without the limitations).
The log file is for fairly large quantities binary data being collected in
real time. If the guys collecting data are not careful they can, and have,
completely fill the partition. I need to reconfigure a system that is
already in use and would like to use some space that is not currently being
used. I would like to at least make the partitions invisible in Windows
mode, that prevents someone from doing something to them by accident.
“John Garvey” <jgarvey@qnx.com> wrote in message
news:bie2t9$bsl$1@nntp.qnx.com…
Bob Smith <> bobsmith@home.com> > wrote:
If I can’t do it QNX, do you know of a 3rd party fdisk like utility that
will let me put QNX partition types in a extended partition?
I know I can make extended parts in windows, but it won’t let me put QNX
types in the partition table.Does it matter what the type is? Nothing (except “diskboot”) cares,
you can dinit and mount anything as anything. You could “spatch”
the partition table if you cared. But, from re-reading your original
post I don’t see why you need real partitions? For your log file,
is it to limit the size or to specify different mount options or … ?
As as been suggested, consider using the filesystem-in-a-file trick:touch mypart.img
dinit -S4m mypart.img
mount -tqnx4 mypart.img /mypart
You now have a /mypart filesystem to store things in, the space is
limited to the specified size, you can mount with specific options,
you can backup the filesystem by copying the .img file, ,make as
many container filesystems as you want of whatever size (<2GB), etc
(almost all the benefits of the partition without the limitations).