Skip to main content

Archlinux installation notes


Introduction

I switched to Arch Linux, a totally new distribution for me, and these are some tips I had to perform in order the make things work.

Installation

The installation guide page is quite clear. It's a step by step set of instruction an intermediate Linux user may blindly follow.
The only thing I missed is the syntax of "/etc/vconsole.conf", in order to get my french keyboard considered. Instead of having it on another page, I'd rather it would be in this page.

Pidgin

At work we need Pidgin with the support of Sametime. I had to recompile it from ABS, and compile the "meanwhile" utilities from AUR.
The Pidgin wiki page misses the indication that libpurple-meanwhile has to be installed with meanwhile.

Modem

I choosed to have my network managed with NetworkManager.
As described on the guide, the installation instructions miss the step to enable the NetworkManager service at boot.
I had my EVDO ZTE Modem unrecognized until the service was started.
There is also a problem with the version of NetworkManager I installed: when you connect to a secured WiFi network, it doesn prompt for the key. I had to enter it manually by configuring the connection.

Conclusion

For the moment, I just used it for a week. That is not enough to get a decent conclusion. Let's see within 3 months.

Comments

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href
When building an Angular application, people usually use "ng" and pass arguments to that invocation.
Typically, when wanting to hard code "base-href" in "index.html", one will issue:

ng build --base-href='https://ngx.rktmb.org/foo'


I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin.
I got the habit to build the application with "npm run build" before deploying it.

But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter.

npm run build --base-href='https://ngx.rktmb.org/foo


did not set the base href in indext.html

After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says:
You need to use −− to pass arguments to npm scripts. This did the job!
The command to issue is then:

npm run build -- --base-href='https://ngx.rktmb.org/foo'

dockerfile multiline to file

Outputing a multiline string from Dockerfile
I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian.
But I also have a local mirror and would like to use it for packages installation.

Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file.

Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write.
Here you are:

RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 " >>…

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…