![]() This article on adding users on Arch Linux was helpful. During the initial installation I set up a root user, but no regular users, so my first step was to give myself a … um, me. Setting up users was an odd exercise in reminding me that I’d forgotten what life was like before sudo. ![]() I thought I wouldn’t need to since I already had grub on my machine from the previous Ubuntu install but in the end it didn’t work without going through the GRUB install process Toward the end of the installation it tells you to install a bootloader. Eventually I got it to work when I installed NetworkManager and enabled rvice, which in turn only made sense to me after I’d read about start/enable and realised that “starting” a service sets it running in the background now, and “enabling” it means it will start automatically on startup. The network configuration step gave me some grief. It took me three tries to get a working installation, because I missed some subtle thing (e.g., the first time I didn’t have the bootable USB booting in UEFI mode, because obviously I would have thought of that at the beginning… sigh).Įverything became easier once I started feeling comfortable using pacman. ![]() The installation guide ( ) is good but dense, and I had to read a lot of the documents it links to in order to make progress. What I am going to do, however, is jot down my notes to myself on the process. My point is I have no business whatsoever in trying to guide anyone else through the installation process. The only reason any of this happened is that I happened to have a spare laptop 2 and couldn’t think of anything better to do with it. Top of that list is that I am a complete amateur when it comes to Arch and I have no idea whatsoever what I’m doing. You may wish to add an alias to ~/.I have absolutely no intention of writing a “how to install Arch” guide, for many excellent reasons. Likewise, the same can be done for any other user (e.g. Thus, administrators should generally use su as follows:Īn identical result is produced by adding the username root: That is, the current directory and environment will be changed to what would be expected if the new user had actually logged on to a new session (rather than just taking over an existing session). Such as their ~/.bashrc, and possibly other dot files, for a bash shell. Changes the environmental variables to those of the new user, as dictated by their preferred shell settings.Switches from the current directory to the home directory of the new user (e.g., to /root in the case of the root user) by logging in as that user.Thus, it is advisable that administrative users, as well as any other users that are authorized to use su (and it is suggested that there be very few, if any) acquire the habit of always running the su command with the -l/ -login option. For instance, a program could be installed that could give the ordinary user power to accidentally damage the system or gain unauthorized access to certain data. While inadvertently using an ordinary user's shell account, root could install a program or make other changes to the system that would not have the same result as if they were made while using the root account. However, in many situations it is not desirable, or it can even be dangerous, for the root user to be operating from an ordinary user's shell account and with that account's environmental variables rather than from its own.In particular, occasionally the most efficient way to solve a user's problem is to log into that user's account in order to reproduce or debug the problem. It sometimes can be advantageous for a system administrator to use the shell account of an ordinary user rather than its own.Note the following important contrasting considerations: The default behavior of su is to remain within the current directory and to maintain the environmental variables of the original user (rather than switch to those of the new user). If no username is passed, su assumes the root user, and the password for which you are prompted will be that of root. When running su as root, no password is required. To assume the login of another user, pass the username that you want to become to su, as in:īy default, when running as a regular user, you will be prompted for the password of the user you are attempting to become. See PAM for ways to configure su's behavior. The su core utility (substitute user) is used to assume the identity of another user on the system, root by default. List of applications/Security#Privilege elevation.
0 Comments
Leave a Reply. |