[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Fresh Install From Nightly Compose desktop-x86_64-20091002.15.iso

On Mon, 2009-10-05 at 15:16 -0400, Robert L Cochran wrote:
> On 10/05/2009 03:04 PM, James Laska wrote:
> > Hey Robert,
> >
> > On Mon, 2009-10-05 at 14:47 -0400, Robert L Cochran wrote:
> >    
> >> To make it clearer what I really want: I already have a Fedora 12 system
> >> up and running but it does not appear to be encrypted.
> >>
> >> If I follow the instructions below (at
> >> http://docs.fedoraproject.org/install-guide/f12/en-US/html/apcs04.html  )
> >>
> >> will my Fedora 12 system be preserved, or will it be destroyed in the
> >> encryption process? I get the feeling the answer is it will be destroyed
> >> -- I need to encrypt a filesystem first and then install Fedora 12
> >> within that.
> >>      
> > Good question, sorry if that wasn't clear.  To my understanding, you
> > cannot encrypt an already unencrypted partition.  I believe you'd need
> > to back-up the data to another location, and then follow the procedures
> > in the install-guide (either during anaconda or from an already
> > installed system).
> >
> > Thanks,
> > James
> >    
> Hey James,
> I did think this might be the case. I might try another (newer) nightly 
> compose and see if I can get the encryption to work. Only this time I'll 
> install the live system only and not add or subtract software to it 
> until I'm sure the important basics are working. I really like having 
> encryption to guard my privacy.
> During yesterday's install attempt, Anaconda does not seem to have 
> encrypted my file system as part of the installation process, but this 
> might be because I was trying to replace an existing Fedora 12 system 
> with a brand new one and the older system was encrypted, and perhaps 
> that confuses Anaconda.

It certainly should honor your partitioning requests.  If you have any
luck reproducing the issue, any screenshots (and log files from the
install '/tmp/*log*') would help identify the root cause.

Thanks for testing!

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]