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.

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&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "