kobject_rename(9) [centos man page]

KOBJECT_RENAME(9)						   Driver Basics						 KOBJECT_RENAME(9)

NAME

       kobject_rename - change the name of an object

SYNOPSIS

       int kobject_rename(struct kobject * kobj, const char * new_name);

ARGUMENTS

       kobj
	   object in question.

       new_name
	   object's new name

DESCRIPTION

       It is the responsibility of the caller to provide mutual exclusion between two different calls of kobject_rename on the same kobject and to
       ensure that new_name is valid and won't conflict with other kobjects.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							 KOBJECT_RENAME(9)

lurename(1M)						  System Administration Commands					      lurename(1M)

NAME

       lurename - change the name of a boot environment

SYNOPSIS

       /usr/sbin/lurename -e BE_name -n new_name [-l error_log] [-o outfile] [-X]

DESCRIPTION

       The  lurename  command  is  part  of  a	suite  of commands that make up the Live Upgrade feature of the Solaris operating environment. See
       live_upgrade(5) for a description of the Live Upgrade feature.

       The lurename command renames the boot environment (BE) BE_name to new_name.

       The string new_name must not exceed 30 characters in length and must consist only of alphanumeric characters  and  other  ASCII	characters
       that  are not special to the Unix shell. See the "Quoting" section of sh(1). The BE name can contain only single-byte, 8-bit characters. It
       cannot contain whitespace characters. Also, new_name must be unique on the system.

       A BE must have the status "complete" before you rename it. Use lustatus(1M) to determine a BE's status. Also, you cannot rename a  BE  that
       has file systems mounted with lumount(1M) or mount(1M).

       Renaming  a  BE	is  often  useful  when you upgrade the BE from one Solaris release to another. For example, following an operating system
       upgrade, you might rename the BE solaris7 to solaris8.

       The lurename command requires root privileges.

OPTIONS

       The lurename command has the options listed below.

       -e BE_name	       Name of the BE whose name you want to change.

       -l error_log	       Error and status messages are sent to error_log, in addition to where they are sent in your current environment.

       -n new_name	       New name of the BE. new_name must be unique on a given system.

       -o outfile	       All command output is sent to outfile, in addition to where it is sent in your current environment.

       -X		       Enable XML output. Characteristics of XML are defined in  DTD,  in  /usr/share/lib/xml/dtd/lu_cli.dtd.<num>,  where
			       <num> is the version number of the DTD file.

EXIT STATUS

       The following exit values are returned:

       0	Successful completion.

       >0	An error occurred.

FILES

       /etc/lutab

	   list of BEs on the system

       /usr/share/lib/xml/dtd/lu_cli.dtd.<num>

	   Live Upgrade DTD (see -X option)

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWluu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       lu(1M),	luactivate(1M),  lucancel(1M),	lucompare(1M),	lucreate(1M),  lucurr(1M),  ludelete(1M),  ludesc(1M),	lufslist(1M),  lumake(1M),
       lumount(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)

SunOS 5.10							    24 Jan 2002 						      lurename(1M)