search for: 470mb

...he shipped version (I used the DATE= option to make as required). I was using the simple menu system, but reverted to the old boot: command-line system to remove the simple menu system code. The only thing I can see that is different is that I have exceeded the old size for my ISO. Now I am about 470MB instead of just under 450MB. Is there some requirement to boot from some low block (like hard disks needed to boot from cylinders<1024). I am beginning to think I need to use the almost never used -sort option to mkisofs to force my /isolinux directory to be earlier on the disk. After burnin...

I recently got some checksum errors on my btrfs filesystem that seem "interesting". This is on a F18 kernel (3.6.0-3.fc18.x86_64) with the filesystem on a single INTEL SSDSA2CW16 disk (ssd). Its my workstation, so i do normal development on it, i.e. its not a server. Recently I have been doing some virt work, so I''ve been running qemu a lot. I also for some time had a near full

without going into actual source code yet, here is the general scenario: i''ve pulled down a project from svn that a friend has been developing on a linux box... i''m on a windows box. if i run "ruby script/server", i get one line of output: => Booting WEBrick... then it dies and goes back to command prompt with no error messages. ...however, if i pull down the

Hi everyone, I'm trying to rsync a large directory. After pondering on the list-of-files, it's now more or less doing nothing. It's running for over 4 hours now, not doing anything except eating CPUtime on the destination for over half an hour. I don't know what it was doing before that. The stdout of the rsync reported: 4675350 files to consider (which is about right)

forgive me if this has been resolved already... I have an app that is using sendfile to return large files to customers. We can''t use regular Apache to handle this static content since the files are what the customers are paying for - so it wouldn''t be cool for anyone else to get access to them. The issue is that the mongrel mem footprint gets bloated when the files are

Under Solaris 10 on a 4 core Sun Ultra 40 with 20GB RAM, I am setting up a Sun StorageTek 2540 with 12 300GB 15K RPM SAS drives and connected via load-shared 4Gbit FC links. This week I have tried many different configurations, using firmware managed RAID, ZFS managed RAID, and with the controller cache enabled or disabled. My objective is to obtain the best single-file write performance.