> I'm using the last dev version of catalyst, r9. When my .iso was >There has't been a -r9 of catalyst in a long time, if ever. If you're referring >to _pre9, that's not the latest.
Very acute. I'll check if in the last week there were other updates. >It's also package.mask'd, Well, I tried the current stable release. When I got to livecd-stage2, in the livecd/rm section, it deleted files in my filesystem instead of the livecd. I ended up loosing everything. So I tried the masked package, which didn't give this problem. > I found that it was a bug, but I lost the link now. >A bug in what? It is similar to this: http://unixadmintalk.com/f11/re-cd-burnt-sid-unreadable-windows-111555/ I found it also in bugs.gentoo.org, but I cannot find it now. I noticed in the catalyst log that it said something about wrong Joliet extensions. > Catalyst? cdrkit/cdrtools? That's why I ask if somebody encountered a similar problem. And since I am a catalyst newbee, I asked what packages catalyst uses. cdrtools? I don't have that installed, so I guess it's something else. genisoimage? mkisofs? > Are we supposed to track it down for you? You are welcome, if you are a catalyst developer. I'm not. Just trying to figure out things. >The only error report we've seen recently that's somewhat recently was on this >mailing list. The ISO image was rejected by Nero when it was larger than 700MB. I didn't use Nero for burning. As I said, I can burn it fine. I just can read the CD and the iso only from linux (I do have the ext2 driver in windows, and I can read other livecds produced by other versions of catalyst). Best, Fabrizio -- [email protected] mailing list
