Printable View
It COULD be caused by bad data on the cd. Did you check the md5checksum on the iso after downloading? It happened me too often that I had a bad image downloaded (and sometimes I just found out after burning and (trying to) install).
Maybe you can use bittorrent, it checks its data. a downloaded bittorrent file is always ok, thats why I use it for big files... (on the anouncement-forumpage you can find a bittorrent-link)
Try removing common.dpkg-tmp not kenolaba.
I can't even touch or enter the kenolaba directory. Since the common--- folder is inside kenolaba, there's nothing I can do about it it seems.Quote:
Originally Posted by rickenbacherus
The ISO passed the MD5 check before i burned it. I'm not asking that, I'm asking if there are any flaws or reasons why the file copy would corrupt or produce a bad copy. As in no error checking or something like that. The CD is from January, and it's not scratched up. It of course has small scratches, but aren't CDs supposed to last at least a year?
if the md5 was ok, I guess there is just a very small chance the cd whould be corrupt. after a year, a cd should be readable. but it is possible you where just unlucky...
Well....IIRC I have never not been able to delete something before. I would do it like so:
sudo rm -rf /name/of/directory