Re: Xquartz: xterm hangs with trimenable command
Re: Xquartz: xterm hangs with trimenable command
- Subject: Re: Xquartz: xterm hangs with trimenable command
- From: René J.V. Bertin <email@hidden>
- Date: Sun, 13 Sep 2015 10:11:46 +0200
On Saturday September 12 2015 18:02:52 Jeremy Huddleston Sequoia wrote:
>It isn't a boot parameter. It's stored in nvram, but not as a boot parameter. You need to boot into recovery mode to modify the setting.
In fact, this makes me curious. How exactly does that work with booting from external disks? Is it pervasive over all boot disks once you've modified it, as the nvram storage suggests? Does one have to jump through the hoops for each boot disk? Or after cloning the boot disk to another one? I can hardly imagine that a token is stored on disk to tell the kernel to take the nvram parameter into account or not.
Is it possible to store the parameter into nvram from an earlier OS X version, or with the tools VM hosts like Parallels provide to provide a simulated nvram to guests?
Oh, and does this all really mean that one can no longer edit /etc/hosts, /etc/hosts.{allow,deny} etc. without wizardry?
Also,
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden