Yes, it's start position inside the file, so all are starting at the beginning - 0.
On 12.4.2016 21:50, [email protected] wrote: > Thanks again. > > One final question: > > /mnt/tables/gsm/100.ins 100 0 > /mnt/tables/gsm/100.ins 108 0 > . > . > . > /mnt/tables/gsm/100.ins 500 0 > > > OR > > > /mnt/tables/gsm/100.ins 100 0 > /mnt/tables/gsm/100.ins 108 1 > . > . > . > /mnt/tables/gsm/100.ins 500 49 > > I think these are the start positions of independent files and not a raw > disk, so I guess the first option.. Correct? > > Regards, > Spørgeren > > > On 2016-04-12 00:34, Jan Hrach wrote: >> I'm not sure about the "Table:" beginning of the line (maybe there is >> no prefix at all), but definitely the rest is >> /mnt/tables/gsm/100.ins 100 0 >> >> On 11.4.2016 21:02, [email protected] wrote: >>> Thanks Jan. >>> >>> Furthermore, could you tell me which of the following given below is the >>> correct format for tables.conf? >>> >>> #Settings A: >>> #============================ >>> Tables: /mnt/tables/gsm/100.ins 100 0 >>> Tables: /mnt/tables/gsm/108.ins 108 0 >>> . >>> . >>> Tables: /mnt/disk2/gsm/500.ins 500 0 >>> #============================ >>> >>> >>> OR >>> >>> #Settings B: >>> #============================ >>> Tables: /mnt/tables/gsm/100.ins 100 1 >>> Tables: /mnt/tables/gsm/108.ins 108 1 >>> . >>> . >>> Tables: /mnt/disk2/gsm/500.ins 500 1 >>> #============================ >>> >>> OR >>> >>> #Settings C: >>> #============================ >>> Table: 0 100 0 >>> Table: 1 108 0 >>> Table: 2 116 0 >>> . >>> . >>> Table: 39 500 0 >>> #============================ >>> >>> Which one of the above has the correct syntax? A,B,C OR none ! >>> Note that some of the tables are on a separate disk :( >>> >>> Regards, >>> Spørgeren >>> >>> >>> On 2016-04-09 18:31, Jan Hrach wrote: >>>> The offset is meant to be used when you are converting multiple tables >>>> to raw device without filesystem. >>>> You definitely want all tables to start at offset 0 when you have them in >>>> files. >>>> >>>> Offset :1 would mean 4096 from the beginning, which makes no sense. If >>>> you were to put it to the device, you will have to see how many blocks >>>> were written and then set the offset to that (maybe +1). These offsets >>>> are expected to be around 10000000. >>>> >>>> On 9.4.2016 12:50, [email protected] wrote: >>>>> Dear all, >>>>> >>>>> While manually converting dlt files to idx and inx using: >>>>> >>>>> ./TableConvert di /media/tables/a51_table_100.dlt /media/GSM/100.ins:0 >>>>> /media/GSM/100.idx >>>>> >>>>> Do I keep the offset the same for all remaining files as well? >>>>> >>>>> Example: >>>>> >>>>> ./TableConvert di /media/tables/a51_table_268.dlt /media/GSM/268.ins:0 >>>>> /media/GSM/268.idx >>>>> >>>>> OR >>>>> >>>>> Does the offset (ins:0) change or increment in a pattern to ins:1 ins:2 >>>>> .. etc. ? >>>>> >>>>> Regards, >>>>> Spørgeren >>>>> _______________________________________________ >>>>> A51 mailing list >>>>> [email protected] >>>>> https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51 >>> >>> _______________________________________________ >>> A51 mailing list >>> [email protected] >>> https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51 > > _______________________________________________ > A51 mailing list > [email protected] > https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51 -- Jan Hrach | http://jenda.hrach.eu/ GPG CD98 5440 4372 0C6D 164D A24D F019 2F8E 6527 282E _______________________________________________ A51 mailing list [email protected] https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51
