Cyberuben wrote:Hey,
I created an account for myself, with the name "ruben". It was ruben and not Ruben or something else.
I am really sure, that my password was right, 2 times, but, can it have an @ or something?
Because I reinstalled because my useraccount wasn't working, so I was wondering, maybe you guys know the answer.
Ruben
Hi Ruben!
I believe it is best to discover whom are the users currently recognized within your system. This is done by invoking the user command which lists users recognized in YDL (or any Linux/Unix system).
- Code: Select all
[gandalf@middleearth ~]$ users
gandalf gandalf
[gandalf@middleearth ~]$
In order to change the password I previously entered for the user ID known as gandalf, use the passwd command which allows me to change the password. Note that I switched from user to root mode which means that I have and recall the distinct and different password for root! Notice also that I needed to enter the root password after invoking the superuser (su) command. The root, also known as the System Administrator password, which is established usually during the first boot or installation procedure of YDL (or any Linux), if memory serves me well.
The sequence "su -", without the quotes, is a special invocation of the su command which allows access to all commands available within YDL regardless where the command is located within the directory tree (which means some commands may be located in /usr/bin and others in /usr/local/bin). If I did not use the special invocation I would have to know exactly where in which directory that specific command is located, in order to actually use that particular command.
- Code: Select all
[gandalf@middleearth ~]$ su -
Password:
[root@middleearth ~]# passwd gandalf
Changing password for user gandalf.
New UNIX password:
Retype new password:
passwd: all authentication tokens updated successfully.
[root@middleearth ~]#
Regarding your query regarding the @. I believe that you are perhaps referring to having something like an email address like
gandalf@middleearth.org which brings us to a bit of long discussion regarding the hostname command. I recommend that you access information regarding the hostname command on your own system by doing:
- Code: Select all
man hostname
or
- Code: Select all
info hostname
You can use either man or info to learn about any installed Linux command so that you can learn something regarding it.
Returning to the hostname command, you'll notice an explanation regarding something called dnsdomainname and nisdomainname. These commands are related to assigning your server an officially listed and recognized web address recognized everywhere on planet earth. There is a formal application process (which is not free) involved with one or more web agencies which allow you to complete this application process legally so that only you have the name you choose and no one else. Once the application process is completed this means that anytime that name is entered on the web into a Universal Resource Locator (URL) it will bring that person to your server's website/webpage. Note the word "server", this is not merely an email address like
sillyname@gmail.com or
sillyname@yahoo.com which points to the servers owned by gmail and yahoo. The server that you are registering which will be on permanently during and after the registration process will be that computer which has that name you are registering. You'll also be responsible for keeping it virus/spam free and a list of other server "best practice" standards so that your server doesn't become a spam/virus server, infecting everyone else and risking being black-listed.
The hostname command allows you to establish the name of the computer, which is the server I am running YDL on, which up to that point is identified as localhost. Doing so allows the computer to be identified as mine is which is:
[gandalf@middleearth ~]$
There is no way to send me an email from anywhere on the web to me using this because I did not register this server formally and I block the web from any access to this name. I will however receive internal messages from the system itself reporting boot problems, errors etc. registered from middleearth directed to root@middleearth. This can be changed so that these messages are directed via internal mail to gandalf@middleearth instead but that process is a different topic.
I recommend that you acquire a reference text on Linux System Administration to learn more details such as modifying YDL so that it is changed from a single user system into a multiuser system for multiple users with multiple login accounts, in the event that making this change interests you. The command to do this is fairly straightforward, what is not easy however is controlling the users you allow on your system. Here is a list of questions every professional System Administrator must consider and which you will have to consider if you proceed along the direction of switching to a multi-user YDL (or any Linux) system.
- What applications and commands will users be allowed to use?
- What shell will users be logged into by default?
Keep in mind that the ksh shell also has the ability to restrict specific users to a sub-shell known as rsh which is so limited that users cannot use any applications or commands not defined or approved by the System Administrator, also these shells report any attempted violations back to the System Administrator. Commercial Linux and Unix systems have these shells by default; ksh can be installed into YDL as well.
There are other concerns and responsibilities of the System Administrator such as building a strong firewall, protecting the system and more. The responsibilities and duties of the job can fill several University class libraries so I invite you to start with one reference work which makes sense to you and proceed expand your learning from there.
All the best...