Date: Wed, 25 Feb 2004 10:11:36 -0800 (PST) From: Andrew Reisse <areisse@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 47635 for review Message-ID: <200402251811.i1PIBa4R083457@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=47635 Change 47635 by areisse@areisse_ibook on 2004/02/25 10:11:23 talk about verbose mode hanging tell them how do enable enforcing mode Affected files ... .. //depot/projects/trustedbsd/sedarwin/bootstrap_instructions.txt#27 edit Differences ... ==== //depot/projects/trustedbsd/sedarwin/bootstrap_instructions.txt#27 (text+ko) ==== @@ -8,6 +8,11 @@ forward to 10.2.8. Currently, Panther and older Jaguar releases are not supported. + The instructions assume that / is the root of the system that + will have SEdarwin installed. Boot into that partition before + continuing, so that absolute paths and 'make install' targets + will be in the right place. + Step 2: Check out TrustedBSD/SEDarwin source tree In our environment, this requires installing and configuring the @@ -271,7 +276,10 @@ variables, or press Command-Option-P-R to clear the PRAM in the event of serious problems. Finally, you may want to set the boot-args flag to "-v" to get a text-based boot with console messages, rather than the - pretty but less informative Apple logo, etc. + pretty but less informative Apple logo, etc. If the system hangs during + verbose mode startup (whether running sedarwin or not), try using normal + boot options, as we have experienced unpredictable hangs with verbose + boots. We've found that boot-time failure modes with Darwin are a bit hard to diagnose, and problems booting a new kernel frequent result in a @@ -342,3 +350,8 @@ Missing this step will result in login attempts failing, or the entire system not working if enforcing mode is enabled. + + If you want to run in enforcing mode, you can use the "kenv_sebsd_enforce" + OF variable. Set it with: + + # nvram kenv_sebsd_enforce=1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402251811.i1PIBa4R083457>