site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com - Kevin On May 31, 2005, at 10:07 AM, Stéphane Thiell wrote: Hi, Thanks for your help, Stéphane Thiell _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... The --setBoot argument (which used to be called --setOF) does not change the on-disk representation at all, but instead changes the boot-device open firmware variable (`nvram boot-device`). It's not possible (as far as I know) to modify an open firmware variable on a machine that is in target disk mode. Thus, I don't think your problem has any relation to the bootx.bootinfo file, but instead is due to the open firmware variable not being set on the PowerBook (until you set it via the option key and clicking the icon at boot). I encounter a little problem with a PowerBook Titanium which is mounted in target mode on a G5 system. My goal is to clone a partition of the G5 to the Titanium's unique partition so that it can then boot on the Titanium. The copy works but doesn't boot on the Titanium. Actually, it's quite understandable as the bless command takes the bless of the G5 bootable partition, which is probably different. After booting on a OS X Install DVD on the Titanium and setting the right boot partition, the clone works well. But before doing that — the volume is then probably correctly blessed —, even when booting with 'option' (alt), the volume doesn't appear. My question is, is there a way to generate a sort of generic bootx.bootinfo so that it'll be seen as a boot volume on the Titanium? or should I use a bootx.bootinfo taken on a working system of the Titanium (specific) ? This email sent to site_archiver@lists.apple.com