[haiku-bugs] Re: [Haiku] #9547: Building Haiku x86_64 on Haiku x86_64 issues
- From: "Luposian" <trac@xxxxxxxxxxxx>
- Date: Thu, 21 Mar 2013 06:59:14 -0000
#9547: Building Haiku x86_64 on Haiku x86_64 issues
-------------------------+----------------------------
Reporter: Luposian | Owner: xyzzy
Type: bug | Status: assigned
Priority: normal | Milestone: R1
Component: - General | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: x86-64
-------------------------+----------------------------
Comment (by Luposian):
Ok, the revision of the nightly Haiku x86_64 I am using, is hrev45362.
Now this next thing doesn't make any sense...
I decided to "mess around" and delete everything out of the mounted Haiku
image, by dragging it to the trash. It copies to the trash fine. In
fact, upon emptying the trash, the 300Mb Haiku image file was now
completely empty! Even after a reboot! But, the weird thing was... I was
able to INSTALL to that 300Mb image file (it errored because it ran out of
room)! And, upon trying to copy one of the files in it, it copied
perfectly fine!
So, the question is... are the files, themselves, corrupted and CAN'T be
copied? But how does that explain being able to copy them from within
Haiku32?
Does the image file need to be large enough (sufficiently larger than it's
contents) to have room to copy it's files elsewhere (or install from)
properly? Assuming, it uses some of the image's space for temp use or
something?
Grasping at straws here, but hoping something makes sense.
Now gotta recreate a new Haiku.image file... my current one is now no
longer valid, as it's been completely messed up by my tinkering! HA!
I'm gonna make the image file larger, this time, to see if that helps.
I'll enclose a Syslog with my next reply.
--
Ticket URL: <http://dev.haiku-os.org/ticket/9547#comment:6>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
