Tag Info

Hot answers tagged

4

Considering the diversity above, what is the most accepted approach for naming configs? Whatever you want to call them. File extensions don't matter much beyond letting an admin know what the file probably is. A human is probably going to know that *.cfg and *.conf are both probably config files. The *.cnf I've only ever seen with MySQL which is a ...


3

xinput controls input settings. It has the same role for input that xrandr has for the display. Run xinput list to list devices. Each device has a name and a numerical ID. You can use either this name or this ID to list properties of the corresponding device. Device IDs can depend on the order in which the devices are detected, so to target a specific ...


2

Possible locations for the configuration file are /etc/asound.conf for all users, or ~/.asoundrc for a single user. The file ~/.asoundrc.asoundconf is a file created by the asoundconf tool, and should not be edited by hand.


1

I was answering similar question on Superuser.com, but after the responses I am not longer sure if it is right. In short, I believe that it is currently not possible and even openssh-7.0 is out, but these bugs were not fixed so we will have to urge upstream. Also there is alternative answer with positive feedback, but I guess this is the way how you are ...


1

As you mentioned that it should be an automated shell script, at least for the two yum commands you would need to add -y so yum will assume an answer of "yes" for all questions it will ask. See the yum man page, relevant excerpt: -y, --assumeyes Assume yes; assume that the answer to any question which would be asked is yes. ...


1

You have several pieces to your question, and I can't claim familiarity with all of the commands you run, but here's my take: Either run the whole script as root (directly) or via sudo. That way, you won't need to run sudo in the script itself. If you require sudo for a particular step, then you'll either need to set your ID up with a NOPASSWD flag in ...


1

Assuming you have root access to the machine, you could write an installation routine. I made a few assumptions, as the availability of apt-get #script, saved local, executed on ssh server: #install tools: apt-get -y install tool1 tool2 #be careful with the -y option, though #new zsh tools: #load standard .zshrc file echo . /home/user/.zshrc > ...


1

Did something happen back in the day that divided the dev crowd into ... camps ...? You may be looking at the chronology backwards.  "Back in the day" the "Unix dev crowd" was all at AT&T Bell Laboratories.  (If you provide enough power to the flux capacitor, you may be able to go back to a time when the "Unix dev crowd" was two people, and they may ...


1

It's a way to organise your config into logical files. It's generally easier to find ssl.conf instead of parsing through 1000 lines of httpd.conf for the ssl section. On centos, conf/httpd.conf will include conf.d/*.conf. This is probably loaded in same order the shell globs *.conf which basically amounts to alphabetical order (but I've never checked the ...


1

Yes, /etc/inet/hosts (or /etc/hosts) and /etc/inet/ipnodes should be updated manually, they are relative to the network stack and not the hostname of the machine.



Only top voted, non community-wiki answers of a minimum length are eligible