Learning to Live with UAC - InfoWorld

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Learning to Live with UAC - InfoWorld
# 1  
Old 07-11-2007
Learning to Live with UAC - InfoWorld

Learning to Live with UAC
InfoWorld, CA - 19 minutes ago
Running as "root" (to use a UNIX/Linux term) was simply bad policy. You're all but asking for some malicious script or rogue executable to have its way with ...

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. What is on Your Mind?

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates" The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
Login or Register to Ask a Question
lucurr(1M)																lucurr(1M)

NAME
lucurr - display the name of the active boot environment SYNOPSIS
/usr/sbin/lucurr [-l error_log] [-m mount_point] [-o outfile] [-X] DESCRIPTION
The lucurr 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 lucurr command displays the name of the currently running boot environment (BE). If no BEs are configured on the system, lucurr dis- plays the message "No Boot Environments are defined". Note that lucurr reports only the name of the current BE, not the BE that will be active upon the next reboot. Use lustatus(1M) or luactivate(1M) for this information. The lucurr command requires root privileges. OPTIONS
The lucurr command has the following options: -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -m mount_point Returns the name of the BE that owns mount_point, where mount_point is the mount point of a BE's root file system. This can be a mount point of the current BE or the mount point of a BE other than the current BE. If the latter, the file system of the BE must have been mounted with lumount(1M) or mount(1M) before entering this option. -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), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure- name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 lucurr(1M)