Translate

Image of Linux Kernel Development (3rd Edition)
Image of Android Wireless Application Development
Image of Modern Operating Systems (3rd Edition)
Image of Beginning Google Maps API 3

Blocking Specific Commands and Utilities in Sudo

Sudo is a mechanism that enables a system administrator to give regular users permission to execute certain commands that they would normally not be allowed to use. Which user can do what is defined by the contents of /etc/sudoers. Typically you should use visudo to edit this file. So how do you prevent a user from using sudo to run specific commands in a subdirectory like /usr/bin but allow the user to run other commands in that same directory? Here is one way of doing it: # list of commands alice may not run Cmnd_Alias BANNED = /usr/bin/su, /usr/bin/ksh, usr/bin/zsh

UEFI Shell Help Text

There are two common UEFI Shells available. The first is the older EFI Shell (see the TianoCore EdkShellBinPkg) and the second is the UEFI 2.0 Shell (See theTianoCore ShellBinPkg.) Most current UEFI implementations seem to use the older shell. In the EFI Shell, you invoke “help utility” to get help text for a particular utility. You can also do “help utility -b” to display the help text screen by screen. Just using “help” produces a sorted list of all available shell commands. In the UEFI Shell 2.0, when you invoke “help utility” to get help text for a particular utility,

Gmail – Not Receiving Copy of Email Sent To Mailing List

Not receiving email from groups or mailing lists you are subscribed to? According to Gmail FAQ: When you send mail to any group or mailing list you subscribe to, Gmail automatically skips your inbox and archives the message to save you time and prevent clutter. The message will appear in your inbox if someone responds to it or if there is an error delivering the message. If you’d like to view your message, you can find it in Sent Mail or All Mail. Aaagh!

Problems With UEFI Shell Options

The (U)EFI Shell has been around one form or another for nearly 15 years. Recenly I looked at Shell startup options and found that the relevant code in the Shell was badly broken and could never have worked. This post details my findings and solutions.

Fedora /etc/os-release

Fedora 17 added support for /etc/os-release. Here is the contents of that file: # cat /etc/os-release NAME=Fedora VERSION=”17 (Beefy Miracle)” ID=fedora VERSION_ID=17 PRETTY_NAME=”Fedora 17 (Beefy Miracle)” ANSI_COLOR=”0;34″ CPE_NAME=”cpe:/o:fedoraproject:fedora:17″ A number of fields are specified, some mandatory, some optional. CPE_NAME is a stylized name for the operating system, following the proposed Common Platform Enumeration specification. This field is optional. This file is part of the generic-release-17-1.noarch package.