Hey Joe,
> usr/src/cmd/beadm/beadm.py > > I will assume you have the correct message formate and fields... > Sure. > > usr/src/cmd/beadm/messages.py > > Please just check/confirm: > > Do we want to suggest becoming super user? If it acceptable to suggest > this should the wording be "become root"? I chose superuser after looking at su(1M) which mentions superuser in its NAME section. It also just seemed more appropriate then "root" since "root" seems less specific and is used in more contexts while superuser can only mean one thing. Thanks Joe! Tim > > > usr/src/lib/libbe/be_create.c > > Looks good. > > Joe > > > > Tim Knitter wrote: >> Hello, >> >> Could Ethan and/or Evan or anyone else for that matter review this >> snap2 project fix which is against the snap_upgrade WS? I'm sending >> this out as a separate review since this is a bug found during the >> system test phase of the project and it isn't covered in the main >> webrev (3686) >> >> http://cr.opensolaris.org/~tsk/3734/ >> This was tested on opensolaris bld 88. The test revealed the following >> output when the user was non-privaleged: >> >> os% beadm destroy be2 >> Are you sure you want to destroy be2? This action cannot be >> undone(y/[n]): y >> Unable to destroy be2. >> You don't have enough permissions to execute this command. >> Either use 'pfexec' to execute the command or become superuser. >> >> Thanks >> Tim >> >> Jack Schwartz wrote: >>> Hi everyone. >>> >>> My push of: >>> 3340 bootroot auto size >>> is a minor flag day for those using Distro-Constructor: >>> - with their own finalizer scripts >>> - with their own custom bootroot >>> >>> If you use DC in one of these ways, please read on... >>> >>> *** If you write your own finalizer scripts: *** >>> >>> Please note that now there are 5 arguments automatically passed to >>> them (in addition to any specified in the manifest for a particular >>> script). These arguments are: >>> 1) Manifest Reader Socket: Passed to ManifestRead to get manifest >>> data >>> 2) Package Image Path: Path to the package image area where IPS >>> packages are loaded to create a system image >>> 3) Temporary Directory: Used during the building process >>> 4) Bootroot Build Area: Area where bootroot is built >>> 5) Media Directory: Area where finished media are deposited. >>> >>> *** If you create your own custom bootroot: *** >>> >>> Please note that the bootroot is now autosized. The manifest >>> contains a new entry: >>> img_params/output_image/bootroot/size_pad_mb >>> which specifies a number of extra megabytes to add to the bootroot's >>> automatically-determined size. The default is 10Mb. >>> >>> Note also that the file system into which the bootroot is set no >>> longer sets aside the UFS default of 10% of space for system use >>> only. The entire file system is available to all users. This may >>> lower the ultimate size requirements of the bootroot (the / file >>> system on the live system), depending on applications supported by >>> the live system. >>> >>> Please send any questions to caiman-discuss. >>> >>> Thanks, >>> Jack >>> >>> _______________________________________________ >>> caiman-discuss mailing list >>> caiman-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
