>>>>> " " == Rogier Wolff <R.E.Wolff@BitWizard.nl> writes:
> B. Galliart wrote:
>> Partition check: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8
>> sdb9 sdb10 sdb11 sdb12 sdb13 sdb 14 sdb15 >
> If you absolutely cannot do the work that Andries pointed out,
> you could "manually" setup a bunch of loop devices, to select
> the other partitions.
So the right[tm] way is to use the devfs filesystem and allocate
major/minor numbers on the fly while scanning the partition table.
> As I've proven on my DVD RAM drive, you can setup loop devices
> directly on a device. You'd need to make a script that parses
> the partition table, and creates the right loop devices.
You will get problems with ioctrls, like the one for reparsing the
partition table. The loop devices won't change accordingly. Also
theres a big risk of miscalculating some offset and overwriting data.
> (Hmm. Can loop handle offsets larger than 32 bits? That's going
> to be a big setback if it doesn't!)
Hmm, loop should use off_t or maybe size_t, so on any decent 64 Bit
Linux thats 64Bit. Sorry, couldn't resist. :))
AAAARRRRRGGGGHHHHH!!!!!!
/usr/include/linux/loop.h:
struct loop_device {
int lo_number;
struct dentry *lo_dentry;
int lo_refcnt;
kdev_t lo_device;
int lo_offset;
int lo_encrypt_type;
...
int lo_offset means 32 Bit offsets. Which id*** wrote that. What do we
have off_t for?
Looks like someone has to check the loopdevices for BIG FILE support.
May the Source be with you.
Goswin
PS: Did anyone ever _try_ to mount a 5GB loopback file?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:23 EST