Lines Matching refs:order
1382 >0xc byte 00 \b, DOS 3.3 sector order
1385 >0xc byte 01 \b, ProDOS sector order
1442 # that I could find. The 1 and 2 really mean "order in which you defined
1454 # row- or column-order recalculation; the A or M means automatic or manual
1697 # byte order as the machine running "file" with "cpio archive", and
1698 # to indicate archives produced on machines with the opposite byte order
1719 # They were written with binary values in host byte order, and
3488 # "VAX-order" and "VAX-order2"?
3492 0 short 03401 VAX-order 68K Blit (standalone) executable
3495 0 short 03001 VAX-order 68k Blit mpx/mux executable
4005 # XXX - what byte order does the Clipper use?
4240 # This magic number is byte-order-independent.
4245 # byte-order independent, and one of which is byte-order dependent?
4901 # Hash 1.85/1.86 databases store metadata in network byte order.
4902 # Btree 1.85/1.86 databases store the metadata in host byte order.
4903 # Hash and Btree 2.X and later databases store the metadata in host byte order.
4910 >>4 belong >0 (Hash, version %d, native byte-order)
4924 >>4 belong >0 (Hash, version %d, native byte-order)
4927 >4 long >0 (Btree, version %d, native byte-order)
4934 >16 long >0 (Hash, version %d, native byte-order)
4941 >16 long >0 (Btree, version %d, native byte-order)
4948 >16 long >0 (Queue, version %d, native byte-order)
4956 >16 long >0 (Log, version %d, native byte-order)
5532 # We specify both byte orders in order to recognize byte-swapped dumps.
5713 # We have to check the byte order flag to see what byte order all the
5904 >5 byte 0 invalid byte order
5936 # XXX - needs to have the byte order specified (NS32K was little-endian,
8586 # All new-style FreeBSD magic numbers are in host byte order (i.e.,
8702 # 28: low order byte of the current PTD entry, always 0 since the
9781 # XXX - somebody should figure out whether any byte order needs to be
9792 # practice in order to avoid collisions.
9813 # The "misc" stuff needs a byte order; the archives look suspiciously
9823 0 long 01203604016 TML 0123 byte-order format
9824 0 long 01702407010 TML 1032 byte-order format
9825 0 long 01003405017 TML 2301 byte-order format
9826 0 long 01602007412 TML 3210 byte-order format
10076 # Unfortunately, HP-UX uses corehead blocks without specifying the order
10082 # The only observed order in real core files is KERNEL, EXEC, FORMAT, PROC
10083 # but we include all 6 variations of the order of the first 3, and
11813 # "long" magic is a better practice in order to avoid collisions.
12326 # yes, this is separate from the low-order magic number bit
13396 # XXX - byte order?
13429 # XXX - byte order?
14757 >>0x400A string \0\0\0\0\0\0 MSX MegaROM with nonstandard page order
14765 >>0x800A string \0\0\0\0\0\0 MSX MegaROM with nonstandard page order
14773 >0x3C008 string \0\0\0\0\0\0\0\0 MSX MegaROM with nonstandard page order
14939 # All new-style magic numbers are in network byte order.
15328 # We have to check the byte order flag to see what byte order all the
15353 >5 byte 0 invalid byte order
15366 >>18 leshort 1 AT&T WE32100 - invalid byte order,
15367 >>18 leshort 2 SPARC - invalid byte order,
15369 >>18 leshort 4 Motorola 68000 - invalid byte order,
15370 >>18 leshort 5 Motorola 88000 - invalid byte order,
15373 >>18 leshort 8 MIPS R3000_BE - invalid byte order,
15374 >>18 leshort 9 Amdahl - invalid byte order,
15376 >>18 leshort 11 RS6000 - invalid byte order,
15377 >>18 leshort 15 PA-RISC - invalid byte order,
15399 >>18 beshort 3 Intel 80386 - invalid byte order,
15402 >>18 beshort 6 Intel 80486 - invalid byte order,
15406 >>18 beshort 10 MIPS R3000_LE - invalid byte order,
15810 # XXX - byte order?
15920 >4 byte >0 (net-order %d)
15988 # XXX - byte order? Paging Hokey....
16185 # XXX - byte order?
16875 # XXX - byte order?
17600 # XXX - byte order?
18350 # XXX - byte order for screen images?
