On 05/30/12 07:59, Jan Damborsky wrote:
Hello caimaniacs,
I am currently evaluating following net text install bug (which is
in fact regression I caused when fixing 7162079):
7172606 Network text install fails trying to download /etc/shadow
I have some idea how it could be addressed, but since this particular
issue seems to reveal more generic kind of problem, I would like to
verify if approach I am considering seems reasonable. Concurrently
I am working on related code changes in order to find out if that approach
is feasible or not.
Please see proposal below.
Thank you very much,
Jan
Background
==========
In cases when CPIO transfer method is used for populating installation
target, there are files which need to be reverted to their
pristine state on target (shadow(4) being one of examples).
Those files are stored within dedicated "save area" during process
of media construction. Then during installation they are transferred
to appropriate places by CleanupCPIOInstall ICT task.
In case of media boot (text installer, GUI installer), those files reside
under /.cdrom/save directory while in case of network boot (text installer
only) they are downloaded file-by-file from AI server to /tmp/ directory,
then copied to the target.
Problem statement
=================
In general, "save area" may contain files with restrictive combination
of ownership/permissions. That turned out to be problematic in case
of net boot when files are transferred one by one by webserver running
under webservd user. In particular, webserver currently fails to
transfer shadow(4) file, since it's root readable only.
Proposed solution
=================
Since "save area" may contain files webserver may not be able to access
directly, I am wondering if instead transferring those files separately,
if it may make sense to transfer them in form of archive, then unarchive
them on target.
In particular, I am thinking if "save area" may be delivered by
existing solarismisc.zlibarchive. /.cdrom/save would be just symlink
to perhaps /mnt/misc/save directory which would contain populated
"save area".
Advantages of this approach:
- solarismisc.zlibis standard archive delivered in all scenarios.
Thus, consistent approach could be used for all types of installations,
no need to distinguish between net boot and media boot. Related pros:
- simplified code
- simplified test matrix
Yes, I was thinking you'd have to put them in an archive somehow in
order to meet the requirements, this seems like the least change. I
would suggest, though, that we go for slightly more change and not leave
a /.cdrom/save symlink behind; the number of consumers here should be
small enough to make your proposal a straight move to /mnt/misc/save
without undue risk.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
