Re: Shutdown failure and empty boot.log with encrypted system

--qMm9M+Fa2AknHoGS
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Frederick Gazerblezeebe <[email protected]> wrote:

> I have two issues:  The first is since encrypting /, the file
> /var/log/boot.log is no longer written.  Is this a problem with my
> /specific setup or is this how it behaves for everyone else?

Is /var already mounted when boot.log is being written? Search init
scripts for boot.log (usually it's just a dmesg > file)


> Ideas?  Can I provide other information that would be helpful with
> troubleshooting?

Idea: I'd guess it's one more script issue, and dig through fedora's
shutdown scripts and adapt them so that /var and /usr are unmounted
at last, right before the actual sync; reboot; magic


--=20
left blank, right bald
loop-AES FAQ: http://mareichelt.de/pub/texts.loop-aes.php#faq
--qMm9M+Fa2AknHoGS
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkrSWWcACgkQLMyTO8Kj/uQAkgCfd2kzLFHPWAsF8ZsZz16PzVDa
DW0An2LP3dfChb3JjBAdMADWu5uYkQzf
=4Cne
-----END PGP SIGNATURE-----

--qMm9M+Fa2AknHoGS--

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/