search for: 1kib

...same file twice, using the same settings and same OS, never results in identical files (checked using 'diff'). I know that a randomly generated serial number is put it, but it gets better: a diff (- a -u0) between these two encodings is ~120KiB. Umm... why? Should the diff be around 1KiB, at the most? Also, I've compiled by own libao, libogg, etc. (in Linux 2.4.17) and one of the files I've encoded using these utils has a bitrate 2 bits lower than the same track encoded in Windows 95. Why is this? Is there some way to find out whether my compiler (gcc 2.95.3) is crea...

...know I'm missing something, but I'm not sure what. Another thing I tried was to copy the mbr.img to the disk, but that didn't help. Some details hde: SanDisk SDCFB-512, CFA DISK drive ide2 at 0x3100-0x3107,0x310e on irq 19 hde: max request size: 128KiB hde: 1000944 sectors (512 MB) w/1KiB Cache, CHS=993/16/63 hde: hde1 [root at tyr Murano]# cat extlinux.conf default Murano prompt 1 timeout 40 label Murano kernel /vmlinux append init=/linuxrc root=/dev/hda1 Any help would be appreciated. Thanks.

...n my own plugin. I want to insert and delete some large metadata (>4KiB). It seems, that the delete in a second call of my plugin smashes the file dovecot.dict in users dir: 1st call: *dovecot.dict is empty -delete metadata 1 -delete metadata 2 -insert metadata 1 ~8KiB -insert metadata 2 <1KiB *dovecot.dict contains two entries 2nd call: -delete metadata 1 -delete metadata 2 -insert metadata 1 ~8KiB -insert metadata 2 <1KiB *dovecot.dict contains the two entries + some waste If all eight steps are called together (in the same plugin context) the file dovecot.dict seems to be ok. I...

Hello What is the largest file size that can be created on Linux ? is there any limitation ? Thanks

Hi, I am not an engineer or linux expert but I have been using syslinux to boot live disk filesets (extracted from iso's) residing on fat32 and NTFS volumes. In FAT32 there has been no problem going with larger cluster sizes up to the nominal maximum of 64K however, with NTFS it has not been possible to exceed the cluster size of 4096. With NTFS formatted using clusters of 8192 or larger,

...menting the function. The old comment mentioned the 'human*' interface from gnulib; we can't use that for licensing reasons; so my rewrite is done from scratch. In particular, I know that gnulib's code accepts 'M' as a synonym for '1M'; treats '1k' and '1kiB' as 1024 but '1kB' as 1000, and so on, which I didn't bother to implement here. The unit test can now be adjusted to cover the cases that are now handled correctly. Signed-off-by: Eric Blake <eblake@redhat.com> --- src/test-utils.c | 20 ++++++------ src/utils.c | 95 +...

Take two, this time split into two patches. I liked Rich's suggestion of unit-testing src/ files directly in src/, and automake is a lot happier with this than with my v1 attempt that tried to compile .c files across directories. It's still enough of a change that I'm not pushing it right away. Eric Blake (2): build: Add unit-testing of internal files utils: Revamp

...; as useful for NTFS as in FAT32, > > if not more so. > > > > I stand by prepared for immediate testing of win32 > syslinux versions as early as 4.06 which contain > > modifications to include this property > > -- > -Gene > > search terms: 0.5 kiB, 1kiB, 2kiB, 4kiB 8kiB; half k, 1k, > 2k, 4k, 8k; > 0.5kB, 1kB, 2kB, 4kB, 8kB

This patchset expands traditional CFQ scheduler in order to support cgroups, and improves old version. Improvements are as following. * Modularizing our new CFQ scheduler. The expanded CFQ scheduler is registered/unregistered as new I/O elevator scheduler called "cfq-cgroups". By this, the traditional CFQ scheduler, which does not handle cgroups, and our new CFQ

This patchset expands traditional CFQ scheduler in order to support cgroups, and improves old version. Improvements are as following. * Modularizing our new CFQ scheduler. The expanded CFQ scheduler is registered/unregistered as new I/O elevator scheduler called "cfq-cgroups". By this, the traditional CFQ scheduler, which does not handle cgroups, and our new CFQ