updated articles translations
This commit is contained in:
parent
57f4c8b596
commit
5b1a36b92c
@ -2,6 +2,7 @@ Author: Jesús E.
|
|||||||
Category: Seguridad
|
Category: Seguridad
|
||||||
Date: 2019-05-18 12:17
|
Date: 2019-05-18 12:17
|
||||||
Image: 2019/05/core-thread-sched-state-diagram.png
|
Image: 2019/05/core-thread-sched-state-diagram.png
|
||||||
|
Lang: es
|
||||||
Slug: ataque-mds
|
Slug: ataque-mds
|
||||||
Tags: Intel, Ataque a procesadores Intel
|
Tags: Intel, Ataque a procesadores Intel
|
||||||
Title: Vulnerabilidad MDS en procesadores Intel
|
Title: Vulnerabilidad MDS en procesadores Intel
|
||||||
|
@ -0,0 +1,128 @@
|
|||||||
|
Author: Megver83
|
||||||
|
Category: GNU/Linux
|
||||||
|
Date: 2017-05-18 06:35
|
||||||
|
Image: /2017/05/xmpp.png
|
||||||
|
Lang: en
|
||||||
|
Save_as: connect-xmpp-with-whatsapp-using-yowsup-and-transWhat/index.html
|
||||||
|
URL: connect-xmpp-with-whatsapp-using-yowsup-and-transWhat/
|
||||||
|
Slug: conectar-xmpp-con-whatsapp-usando-yowsup-y-transwhat
|
||||||
|
Tags: xmpp
|
||||||
|
Title: Connect XMPP with WhatsApp using yowsup and transWhat
|
||||||
|
|
||||||
|
Hasn't it happened to you that communication with your friends,
|
||||||
|
family, etc. is made difficult by the simple fact of not using
|
||||||
|
WhatsApp? Sure, it's a quick, easy, and cross-platform solution,
|
||||||
|
but it doesn't respect the freedoms and rights of users.
|
||||||
|
I know many people in the world of free software who have been
|
||||||
|
forced to install it because there is no other way to communicate
|
||||||
|
with those who need to do it (be it for work, school work, or
|
||||||
|
simply keep in touch with their loved ones). However,
|
||||||
|
with [yowsup][yowsupGIT] and [transWhat][transWhatGIT] that is over.
|
||||||
|
With both, you can chat with WhatsApp users, be in their groups
|
||||||
|
and more, using the best-known decentralized instant messaging
|
||||||
|
network: XMPP.
|
||||||
|
|
||||||
|
## What are yowsup and transWhat?
|
||||||
|
|
||||||
|
Yowsup is a python library that allows you to create applications
|
||||||
|
that use the WhatsApp service. Yowsup has been used to create an
|
||||||
|
unofficial WhatsApp Nokia N9 client through the
|
||||||
|
[Wazapp][WazappGIT] project that was in use by 200K + users,
|
||||||
|
as well as another completely unofficial client for Blackberry 10.
|
||||||
|
On the other hand, transWhat is a gateway to link between XMPP
|
||||||
|
and WhatsApp instant messaging networks.
|
||||||
|
|
||||||
|
## Brilliant! How do I start?
|
||||||
|
|
||||||
|
The basic requirements are:
|
||||||
|
|
||||||
|
- Have [pip][pipweb] installed.
|
||||||
|
- Create an XMPP account (if you don't have one) with support for
|
||||||
|
the transWhat gateway. For example, [JabJab.de][jabjabsite]
|
||||||
|
- Have a mobile phone number.
|
||||||
|
- Have an advanced XMPP client, for example Gajim, with the XMPP
|
||||||
|
account to be used configured.
|
||||||
|
|
||||||
|
## So, get to work!
|
||||||
|
|
||||||
|
From a terminal, install the yowsup2 package with pip as root.
|
||||||
|
|
||||||
|
# pip install yowsup2
|
||||||
|
|
||||||
|
After you have installed it, make sure that in the file
|
||||||
|
/usr/lib/python3.6/site-packages/yowsup/env/env.py in
|
||||||
|
DEFAULT variable it says "Android" (including the quotes),
|
||||||
|
read this [comment][comment] from an issue from yowsup's
|
||||||
|
GitHub repository.
|
||||||
|
|
||||||
|
## Make account
|
||||||
|
|
||||||
|
To create an account with yowsup, you must run the following command:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
$ yowsup-cli registration -E s40 -r sms -p <phone_number> -C <country_code> -m <country_mobile_code> -n <network_mobile_code>
|
||||||
|
```
|
||||||
|
|
||||||
|
So, as Jack the Ripper said, let's go part.
|
||||||
|
|
||||||
|
- `<phone_number>` it must be the complete telephone number, with the country code, except for the `+` sign
|
||||||
|
- `<country_code>` corresponds to the country code, if you do not know yours, see it [here][netlist].
|
||||||
|
- `<country_mobile_code>` It is the MCC that you can find [here][MCC].
|
||||||
|
- `<network_mobile_code>` It is the MNC that you can also find on the same page as `<country_mobile_code>`
|
||||||
|
|
||||||
|
If everything works, something like this should appear at the end of the command,
|
||||||
|
you should receive a text message with the code to register, similarly write:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
$ yowsup-cli registration -E s40 -p <phone_number> -C <country_code> -m <country_mobile_code> -n <network_mobile_code> -R <sms_code>
|
||||||
|
```
|
||||||
|
|
||||||
|
Where `<sms_code>` corresponds to the code you received on your cell
|
||||||
|
phone.
|
||||||
|
The output of the command, near the end, you should get something like:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
INFO:yowsup.common.http.warequest:b'{"status":"ok","login":"<phone_number>","type":"existing","pw":"FBmvgZs8UUbSX2ZHeVyxc7G7g4s=","expiration":4444444444.0,"kind":"free","price":"US$0.99","cost":"0.99","currency":"USD","price_expiration":1497967560}\n' status: b'ok' login: b'<phone_number>' pw: b'<password>' type: b'existing' expiration: 4444444444.0 kind: b'free' price: b'US$0.99' cost: b'0.99' currency: b'USD' price_expiration: 1497967560
|
||||||
|
```
|
||||||
|
|
||||||
|
What interests us here is what is blackened. It will show you your
|
||||||
|
phone number and password, which we will now use to connect XMPP
|
||||||
|
with WhatsApp. Note that the letters "b" and the apostrophes are
|
||||||
|
not blackened.
|
||||||
|
|
||||||
|
## Connecting XMPP and WhatsApp with transWhat
|
||||||
|
|
||||||
|
So now that we have the number and password, it's time for action.
|
||||||
|
If you use Gajim, go to **Actions>Discover services>using the
|
||||||
|
account jabjab.de** (or the one you use with transWhat support).
|
||||||
|
In the "Transport" section select "transWhat" and then click
|
||||||
|
"Subscribe", it will ask for the number and password that you
|
||||||
|
obtained with yowsup.
|
||||||
|
|
||||||
|
Ready! You already have a functional XMPP account with WhatsApp.
|
||||||
|
To add WhatsApp contacts you have to add them with the address
|
||||||
|
`<phone number>@domain.of.transport>`
|
||||||
|
|
||||||
|
**Note:**
|
||||||
|
|
||||||
|
`<telephone number>`: it must be the complete number but without the `+` sign,
|
||||||
|
the same as when you registered.
|
||||||
|
|
||||||
|
## To end
|
||||||
|
|
||||||
|
We hope this tutorial has helped you, share it with your friends, on social
|
||||||
|
networks and you have derived from this article if you wish, remember that
|
||||||
|
Conocimientos Libres is about that (o˘◡˘o)
|
||||||
|
|
||||||
|
I thank [trinux][u-trinux], who was the person who taught me how to
|
||||||
|
connect XMPP and WhatsApp.
|
||||||
|
|
||||||
|
[yowsupGIT]: https://github.com/tgalal/yowsup
|
||||||
|
[transWhatGIT]: https://github.com/stv0g/transwhat
|
||||||
|
[WazappGIT]: https://github.com/tgalal/wazapp
|
||||||
|
[pipweb]: https://pip.pypa.io/
|
||||||
|
[jabjabsite]: https://jabjab.de/
|
||||||
|
[comment]: https://github.com/tgalal/yowsup/issues/1952#issuecomment-284212268
|
||||||
|
[netlist]: http://www.ipipi.com/networkList.do
|
||||||
|
[MCC]: https://en.wikipedia.org/wiki/Mobile_country_code
|
||||||
|
[u-trinux]: https://trisquel.info/en/users/trinux
|
@ -2,6 +2,7 @@ Author: Megver83
|
|||||||
Category: GNU/Linux
|
Category: GNU/Linux
|
||||||
Date: 2017-05-18 06:35
|
Date: 2017-05-18 06:35
|
||||||
Image: /2017/05/xmpp.png
|
Image: /2017/05/xmpp.png
|
||||||
|
Lang: es
|
||||||
Slug: conectar-xmpp-con-whatsapp-usando-yowsup-y-transwhat
|
Slug: conectar-xmpp-con-whatsapp-usando-yowsup-y-transwhat
|
||||||
Tags: xmpp
|
Tags: xmpp
|
||||||
Title: Conectar XMPP con WhatsApp usando yowsup y transWhat
|
Title: Conectar XMPP con WhatsApp usando yowsup y transWhat
|
||||||
@ -60,7 +61,7 @@ $ yowsup-cli registration -E s40 -r sms -p <nº_de_teléfono> -C <código_del_pa
|
|||||||
Entonces, como dijo Jack el destripador, vamos por parte.
|
Entonces, como dijo Jack el destripador, vamos por parte.
|
||||||
|
|
||||||
|
|
||||||
- `<nº_de_teléfono>` debe ser el número de teléfono completo, con el código del país, exceptuando el signo +
|
- `<nº_de_teléfono>` debe ser el número de teléfono completo, con el código del país, exceptuando el signo `+`
|
||||||
- `<código_del_país>` corresponde al código del país, si no te sabes el tuyo, míralo [aquí][netlist].
|
- `<código_del_país>` corresponde al código del país, si no te sabes el tuyo, míralo [aquí][netlist].
|
||||||
- `<código_móvil_del_país>` Es el MCC que lo puedes encontrar [aquí][MCC].
|
- `<código_móvil_del_país>` Es el MCC que lo puedes encontrar [aquí][MCC].
|
||||||
- `<código_móvil_de_la_red>` Es el MNC que también lo puedes encontrar en la misma página que `<código_móvil_del_país>`
|
- `<código_móvil_de_la_red>` Es el MNC que también lo puedes encontrar en la misma página que `<código_móvil_del_país>`
|
||||||
@ -93,7 +94,8 @@ añadirlos con la dirección `<nº_de_teléfono>@dominio.del.transporte>`
|
|||||||
|
|
||||||
**Nota:**
|
**Nota:**
|
||||||
|
|
||||||
`<nº_de_teléfono>`: tiene que ser el número completo pero sin el **signo +**, igual que cuando te registraste.
|
`<nº_de_teléfono>`: tiene que ser el número completo pero sin el signo `+`,
|
||||||
|
igual que cuando te registraste.
|
||||||
|
|
||||||
## Para finalizar
|
## Para finalizar
|
||||||
|
|
||||||
@ -109,5 +111,5 @@ Le agradezco a [trinux][u-trinux], quien fue la persona que me enseñó como con
|
|||||||
[jabjabsite]: https://jabjab.de/
|
[jabjabsite]: https://jabjab.de/
|
||||||
[comment]: https://github.com/tgalal/yowsup/issues/1952#issuecomment-284212268
|
[comment]: https://github.com/tgalal/yowsup/issues/1952#issuecomment-284212268
|
||||||
[netlist]: http://www.ipipi.com/networkList.do
|
[netlist]: http://www.ipipi.com/networkList.do
|
||||||
[MCC]: https://en.wikipedia.org/wiki/Mobile_country_code
|
[MCC]: https://es.wikipedia.org/wiki/Mobile_country_code
|
||||||
[u-trinux]: https://trisquel.info/es/users/trinux
|
[u-trinux]: https://trisquel.info/es/users/trinux
|
||||||
|
230
content/articles/crear-parches-con-git.en.md
Normal file
230
content/articles/crear-parches-con-git.en.md
Normal file
@ -0,0 +1,230 @@
|
|||||||
|
Author: Megver83
|
||||||
|
Category: GNU/Linux
|
||||||
|
Date: 2017-07-08 10:02
|
||||||
|
Image: 2018/04/git-diff.png
|
||||||
|
Lang: en
|
||||||
|
Save_as: make-patches-with-git/index.html
|
||||||
|
URL: make-patches-with-git/
|
||||||
|
Slug: crear-parches-con-git
|
||||||
|
Tags: git, diff, patch
|
||||||
|
Title: Make patches with Git
|
||||||
|
|
||||||
|
Many times it happens, especially when working in code development,
|
||||||
|
that we modify software (eg something as simple as a script or
|
||||||
|
several files from the source code of a program) and we want to
|
||||||
|
share that modification or just save it to have that "differentiation"
|
||||||
|
in the form of a plain text file for later application when the
|
||||||
|
program on which we are based is updated.
|
||||||
|
Well that's the role patches play.
|
||||||
|
|
||||||
|
Wikipedia says the following about patches:
|
||||||
|
|
||||||
|
>A patch is a set of changes to a computer program or its supporting
|
||||||
|
>data designed to update, fix, or improve it. This includes fixing
|
||||||
|
>security vulnerabilities and other bugs, with such patches usually
|
||||||
|
>being called bugfixes or bug fixes, and improving the functionality,
|
||||||
|
>usability or performance.
|
||||||
|
|
||||||
|
Well there are several methods to create patches, the most used
|
||||||
|
are `diff` and `git diff`. In this tutorial the use of `git diff`
|
||||||
|
will be taught, as it is more complete.
|
||||||
|
|
||||||
|
## First step: create directories
|
||||||
|
This is a very important step, that most of the tutorials skip,
|
||||||
|
why will be explained later.
|
||||||
|
|
||||||
|
If you look closely, in Git, every time a commit is made a
|
||||||
|
patch is created, and when it shows a modified file the
|
||||||
|
command `diff --git a/path/to/file/modified.sh b/path/to/file/modified.sh`
|
||||||
|
where `modified.sh` is, in this case, a script that was modified (.❛ ᴗ ❛.)
|
||||||
|
|
||||||
|
So, to modify our script, text or source code, we must first
|
||||||
|
create the directory `a` and `b`
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
mkdir a b
|
||||||
|
|
||||||
|
In directory `a` we will put the unmodified file or files,
|
||||||
|
and in directory `b` the modified one.
|
||||||
|
|
||||||
|
## Step two: create patch
|
||||||
|
Run:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
git diff --no-prefix --no-index --no-renames --binary a b > patched.patch
|
||||||
|
```
|
||||||
|
|
||||||
|
+ --no-prefix: Do not show any source or destination prefix.
|
||||||
|
+ --no-index: It is used to compare the two paths given in the file system.
|
||||||
|
+ --no-remanes: Turn off file renaming detection.
|
||||||
|
+ --binary: Create a binary diff that can be applied with git apply.
|
||||||
|
|
||||||
|
You have your patch ready. Simple, right? Well, now is the time to try it.
|
||||||
|
|
||||||
|
## Step three: apply patch
|
||||||
|
Once we have our patch as a `.diff` or `.patch` file (although in general any
|
||||||
|
extension can be used), we will apply it with `patch` or `git apply`
|
||||||
|
depending on the case.
|
||||||
|
|
||||||
|
1. Plain text only: If your patch only modifies plain text, such as scripts,
|
||||||
|
C/C ++ source files, Python, Pascal, Javascript, PHP, HMTL, etc.
|
||||||
|
then we will use this command:
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
patch -p1 -i /ruta/del/parche.diff
|
||||||
|
|
||||||
|
2. With binary files: That is, things like already compiled executable programs,
|
||||||
|
PNG images, JPEG, Gif, etc. other than plain text. In general you will be able
|
||||||
|
to identify when a binary is patched when in patch it says something like
|
||||||
|
"GIT binary patch". In this case we will apply the patch as follows:
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
git apply -v /ruta/del/parche.diff
|
||||||
|
|
||||||
|
## The issue with diff and not making directories a and b
|
||||||
|
Now, going back to what I said earlier about why this is important,
|
||||||
|
it is because in many guides, wikis, etc. I have found that instead
|
||||||
|
of creating these directories, they create a file (eg) `script.sh`
|
||||||
|
and `script.sh.new` and then based on that they run
|
||||||
|
`diff -u scripts.sh script.sh.new`.
|
||||||
|
It turns out that there are two problems in this:
|
||||||
|
|
||||||
|
+ By doing that, in the patch instead of saying something like
|
||||||
|
`diff --options a/path/to/file/modified.sh b/path/to/file/modified.sh`
|
||||||
|
says (in this case) `diff --options script.sh script.sh.new`,
|
||||||
|
but it turns out that you want to patch `b/script.sh`,
|
||||||
|
not `script.sh.new` (because inside `b/` are the modified files).
|
||||||
|
|
||||||
|
+ If `diff` is used, when it detects a file that didn't originally exist in `a/`
|
||||||
|
(surely because you created one in `b/`), it won't add it in the patch,
|
||||||
|
and if you deleted one inside the original tree, it won't remove that file either.
|
||||||
|
|
||||||
|
+ `diff` cannot patch binaries.
|
||||||
|
|
||||||
|
To better understand it, I will exemplify each case with two examples.
|
||||||
|
In the first one, I will create the files that I put as an example
|
||||||
|
(worth the redundancy) and I will use diff:
|
||||||
|
|
||||||
|
**script.sh:**
|
||||||
|
|
||||||
|
```bash
|
||||||
|
#!/bin/bash
|
||||||
|
echo "Hello world"
|
||||||
|
```
|
||||||
|
|
||||||
|
**script.sh.new:**
|
||||||
|
|
||||||
|
```bash
|
||||||
|
#!/bin/sh
|
||||||
|
echo "Hello world"
|
||||||
|
echo "This is a patched file :D"
|
||||||
|
```
|
||||||
|
Now we will do what most internet tutorials tell you to do:
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
diff -u script.sh script.sh.new
|
||||||
|
|
||||||
|
And it looks like this:
|
||||||
|
|
||||||
|
```diff
|
||||||
|
--- script.sh 2018-03-16 15:52:49.887087539 -0300
|
||||||
|
+++ script.sh.new 2018-03-16 15:53:02.490420209 -0300
|
||||||
|
@@ -1,2 +1,3 @@
|
||||||
|
-#!/bin/bash
|
||||||
|
+#!/bin/sh
|
||||||
|
echo "Hello world"
|
||||||
|
+echo "This is a patched file :D"
|
||||||
|
```
|
||||||
|
Everything apparently fine, but now let's apply that patch
|
||||||
|
|
||||||
|
```bash
|
||||||
|
$ diff -u script.sh script.sh.new | patch -p1 -i /dev/stdin
|
||||||
|
```
|
||||||
|
|
||||||
|
```diff
|
||||||
|
can't find file to patch at input line 3
|
||||||
|
Perhaps you used the wrong -p or --strip option?
|
||||||
|
The text leading up to this was:
|
||||||
|
--------------------------
|
||||||
|
|--- script.sh 2018-03-16 15:52:49.887087539 -0300
|
||||||
|
|+++ script.sh.new 2018-03-16 15:53:02.490420209 -0300
|
||||||
|
--------------------------
|
||||||
|
File to patch:
|
||||||
|
```
|
||||||
|
It fails being that I am in the same directory as `script.sh{.new}`,
|
||||||
|
so this is fixed using the create directories `a/` and `b/` hack.
|
||||||
|
However, this does not turn out point 2 and 3. Let's go for it.
|
||||||
|
|
||||||
|
Suppose we have this inside `a/` and `b/`:
|
||||||
|
|
||||||
|
a:
|
||||||
|
script.sh
|
||||||
|
|
||||||
|
b:
|
||||||
|
binary_file.bin script.sh
|
||||||
|
|
||||||
|
Okay, now let's make the patch with diff:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
$ diff -ur a b
|
||||||
|
```
|
||||||
|
|
||||||
|
```diff
|
||||||
|
Sólo en b: binary_file.bin
|
||||||
|
diff -ur a/script.sh b/script.sh
|
||||||
|
--- a/script.sh 2018-03-16 15:37:27.513802777 -0300
|
||||||
|
+++ b/script.sh 2018-03-16 15:41:17.717123987 -0300
|
||||||
|
@@ -1,2 +1,3 @@
|
||||||
|
-#!/bin/bash
|
||||||
|
+#!/bin/sh
|
||||||
|
echo "Hello world"
|
||||||
|
+echo "This is a patched file :D"
|
||||||
|
```
|
||||||
|
And what is said in point 2 is true, it does not put the new file,
|
||||||
|
it tells you "Only in b" or if there is a file that is in `a/` but not in `b/`
|
||||||
|
(that is to say, surely you removed it from your fork), you will
|
||||||
|
get the message "Only in a" instead of deleting or creating it.
|
||||||
|
If we apply this patch it will only affect the plain text files,
|
||||||
|
and even if it did its job and created this new file it would not
|
||||||
|
work because `binary_file.bin` is a binary, which is not supported
|
||||||
|
by `diff` but it is supported by `git` which leads us to third point.
|
||||||
|
See what happens if I use `git` instead of `diff`:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
$ git diff --no-prefix --no-index --no-renames --binary a b
|
||||||
|
```
|
||||||
|
|
||||||
|
```diff
|
||||||
|
diff --git b/binary_file.bin b/binary_file.bin
|
||||||
|
new file mode 100644
|
||||||
|
index 0000000000000000000000000000000000000000..1ce3c1c596d7a7f400b0cc89bda5a41eed2780c5
|
||||||
|
GIT binary patch
|
||||||
|
literal 73
|
||||||
|
pcmd-HXHZUIU{c}EWl|AfLZWk+R0P|Ad@#)bSHb~R0-{lr003gr3L5|b
|
||||||
|
|
||||||
|
literal 0
|
||||||
|
HcmV?d00001
|
||||||
|
|
||||||
|
diff --git a/script.sh b/script.sh
|
||||||
|
index da049c4..3d351f5 100644
|
||||||
|
--- a/script.sh
|
||||||
|
+++ b/script.sh
|
||||||
|
@@ -1,2 +1,3 @@
|
||||||
|
-#!/bin/bash
|
||||||
|
+#!/bin/sh
|
||||||
|
echo "Hello world"
|
||||||
|
+echo "This is a patched file :D"
|
||||||
|
```
|
||||||
|
Now I did consider the non-existent binary file in `a/` but tangible in `b/`.
|
||||||
|
Note that in this particular case, as I explained earlier, when dealing with
|
||||||
|
binary files that only git supports (see the message "GIT binary patch") you
|
||||||
|
must use `git apply`. But I recommend using it only when it is mandatory,
|
||||||
|
not always (in general, not many binaries are used in software that is
|
||||||
|
100% free, unless they are cases such as firmware for the kernel or
|
||||||
|
precompiled libraries, but free software blobbeado It usually has proprietary
|
||||||
|
binaries in its code, although just because it's binary doesn't necessarily
|
||||||
|
mean it's proprietary.)
|
||||||
|
|
||||||
|
If you have doubts about the use of `diff` and `git diff` or patch and `git apply`,
|
||||||
|
remember that you can leave them in the comments, as well as read their **manpages**
|
||||||
|
and consult their web pages for more information.
|
@ -2,6 +2,7 @@ Author: Megver83
|
|||||||
Category: GNU/Linux
|
Category: GNU/Linux
|
||||||
Date: 2017-07-08 10:02
|
Date: 2017-07-08 10:02
|
||||||
Image: 2018/04/git-diff.png
|
Image: 2018/04/git-diff.png
|
||||||
|
Lang: es
|
||||||
Slug: crear-parches-con-git
|
Slug: crear-parches-con-git
|
||||||
Tags: git, diff, patch
|
Tags: git, diff, patch
|
||||||
Title: Crear parches con Git
|
Title: Crear parches con Git
|
||||||
|
@ -2,6 +2,7 @@ Author: Jesús E.
|
|||||||
Category: GNU/Linux
|
Category: GNU/Linux
|
||||||
Date: 2018-05-29 08:57
|
Date: 2018-05-29 08:57
|
||||||
Image: 2018/05/curso-hyperbola-gnu-linux.png
|
Image: 2018/05/curso-hyperbola-gnu-linux.png
|
||||||
|
Lang: es
|
||||||
Slug: curso-de-instalacion-de-hyperbola
|
Slug: curso-de-instalacion-de-hyperbola
|
||||||
Tags: hyperbola, linux, linux-libre, parabola
|
Tags: hyperbola, linux, linux-libre, parabola
|
||||||
Title: Curso de Instalación de Hyperbola
|
Title: Curso de Instalación de Hyperbola
|
||||||
|
677
content/articles/guia-de-instalacion-de-hyperbola.en.md
Normal file
677
content/articles/guia-de-instalacion-de-hyperbola.en.md
Normal file
@ -0,0 +1,677 @@
|
|||||||
|
Author: Jesús E.
|
||||||
|
Category: tutorials
|
||||||
|
Date: 2019-11-11 08:41
|
||||||
|
Image: 2019/11/hyperbola-base.jpg
|
||||||
|
Lang: en
|
||||||
|
Save_as: hyperbola-installation-guide/index.html
|
||||||
|
URL: hyperbola-installation-guide/
|
||||||
|
Slug: guia-de-instalacion-de-hyperbola
|
||||||
|
Tags: hyperbola, guia
|
||||||
|
Title: Hyperbola installation guide [Legacy/MBR-DOS mode]
|
||||||
|
|
||||||
|
[TOC]
|
||||||
|
|
||||||
|
First we must build a Hyperbola installation device,
|
||||||
|
it can be on a [USB][usb-boot]{:target='_blank' rel='noopener noreferrer'}
|
||||||
|
memory or [CD][cd-boot]{:target='_blank' rel='noopener noreferrer'}.
|
||||||
|
|
||||||
|
There is also an [installation video][video-guide]{:target='_blank' rel='noopener noreferrer'}
|
||||||
|
that will be updated.
|
||||||
|
|
||||||
|
### First steps
|
||||||
|
|
||||||
|
We check if there is an Internet connection
|
||||||
|
|
||||||
|
# ping -c 3 gnu.org
|
||||||
|
|
||||||
|
Partition disk
|
||||||
|
|
||||||
|
# cfdisk
|
||||||
|
|
||||||
|
- In case of the partition chosen as **swap** go to "Type" option and select **82 (Linux swap)** from list.
|
||||||
|
- In case of the partition chosen as **/boot**, select **"bootable"**
|
||||||
|
|
||||||
|
example:
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
sda1=/boot
|
||||||
|
sda2=/
|
||||||
|
sda3=/home
|
||||||
|
sda4=swap
|
||||||
|
|
||||||
|
Recommendations:
|
||||||
|
/boot = 300MB
|
||||||
|
/ = 40GB
|
||||||
|
/home = customized
|
||||||
|
swap = equivalent to RAM
|
||||||
|
|
||||||
|
#### Wi-fi connection
|
||||||
|
|
||||||
|
`wifi` detect
|
||||||
|
|
||||||
|
# iw dev
|
||||||
|
|
||||||
|
Enable device of network
|
||||||
|
|
||||||
|
# ip link set <device-name> up
|
||||||
|
|
||||||
|
Enable Internet with `wpa_supplicant`
|
||||||
|
|
||||||
|
# wpa_supplicant -B -i <device-name> -c <(wpa_passphrase "ssid" "psk")
|
||||||
|
|
||||||
|
Renew IPv4 with `dhcpcd`
|
||||||
|
|
||||||
|
# dhcpcd <device-name>
|
||||||
|
|
||||||
|
### Partition Formatting
|
||||||
|
|
||||||
|
- `/boot`, **ext4** will be used
|
||||||
|
|
||||||
|
# mkfs -t ext4 /dev/sda1
|
||||||
|
|
||||||
|
- `/`, **ext4** will be used
|
||||||
|
|
||||||
|
# mkfs -t ext4 /dev/sda2
|
||||||
|
|
||||||
|
- `/home`, **ext4** will be used
|
||||||
|
|
||||||
|
# mkfs -t ext4 /dev/sda3
|
||||||
|
|
||||||
|
- `swap`, **mkswap** will be used
|
||||||
|
|
||||||
|
# mkswap /dev/sda4
|
||||||
|
|
||||||
|
- Enable swap partition
|
||||||
|
|
||||||
|
# swapon /dev/sda4
|
||||||
|
|
||||||
|
### Organization of Partitions
|
||||||
|
|
||||||
|
- Mount root in /mnt
|
||||||
|
|
||||||
|
# mount /dev/sda2 /mnt
|
||||||
|
|
||||||
|
- Make directories of other partitions
|
||||||
|
|
||||||
|
- boot
|
||||||
|
|
||||||
|
# mkdir /mnt/boot
|
||||||
|
|
||||||
|
- home
|
||||||
|
|
||||||
|
# mkdir /mnt/home
|
||||||
|
|
||||||
|
- Mount other partitions
|
||||||
|
|
||||||
|
- Mount boot
|
||||||
|
|
||||||
|
# mount /dev/sda1 /mnt/boot
|
||||||
|
|
||||||
|
- Mount home
|
||||||
|
|
||||||
|
# mount /dev/sda3 /mnt/home
|
||||||
|
|
||||||
|
### Base System Installation
|
||||||
|
|
||||||
|
Update keys of hyperiso:
|
||||||
|
|
||||||
|
# pacman -Sy hyperbola-keyring
|
||||||
|
|
||||||
|
Install base packages:
|
||||||
|
|
||||||
|
# pacstrap /mnt base base-devel grub-bios wpa_supplicant iw kernel-firmware ldns xenocara-input-synaptics
|
||||||
|
|
||||||
|
> Install `xenocara-input-synaptics` only on laptops
|
||||||
|
|
||||||
|
### Main Configuration
|
||||||
|
|
||||||
|
- Generate fstab file
|
||||||
|
|
||||||
|
# genfstab -U -p /mnt >> /mnt/etc/fstab
|
||||||
|
|
||||||
|
- Inside chroot and configure base system
|
||||||
|
|
||||||
|
# arch-chroot /mnt
|
||||||
|
|
||||||
|
- Set hostname, to edit `/etc/hostname` file:
|
||||||
|
|
||||||
|
Example:
|
||||||
|
|
||||||
|
# echo hyperpc > /etc/hostname
|
||||||
|
|
||||||
|
- Set localtime
|
||||||
|
|
||||||
|
# ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime
|
||||||
|
|
||||||
|
- Update system time to UTC (Optional)
|
||||||
|
|
||||||
|
# hwclock --systohc --utc
|
||||||
|
|
||||||
|
- Enable our location, uncomment
|
||||||
|
|
||||||
|
# sed -e 's/^#en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/g' -i /etc/locale.gen
|
||||||
|
|
||||||
|
- Set location preferences
|
||||||
|
|
||||||
|
# echo LANG=en_US.UTF-8 > /etc/locale.conf
|
||||||
|
|
||||||
|
- Generate location
|
||||||
|
|
||||||
|
# locale-gen
|
||||||
|
|
||||||
|
- If you need to change keymap, configure in `/etc/conf.d/keymaps` file
|
||||||
|
|
||||||
|
# sed -e 's/^keymap="us"/keymap="uk"/g' -i /etc/conf.d/keymaps
|
||||||
|
|
||||||
|
- Install Grub
|
||||||
|
|
||||||
|
# grub-install --target=i386-pc --recheck /dev/sda
|
||||||
|
|
||||||
|
- Create grub.cfg file
|
||||||
|
|
||||||
|
# grub-mkconfig -o /boot/grub/grub.cfg
|
||||||
|
|
||||||
|
- Edit ramdisk
|
||||||
|
|
||||||
|
# nano -w /etc/mkinitcpio.conf
|
||||||
|
-----------------------------
|
||||||
|
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
|
||||||
|
|
||||||
|
- Generate ramdisk
|
||||||
|
|
||||||
|
# mkinitcpio -p linux-libre-lts
|
||||||
|
|
||||||
|
- Set root user password
|
||||||
|
|
||||||
|
# passwd
|
||||||
|
|
||||||
|
- Configure [wpa_supplicant][wpa_link]{:target='_blank' rel='noopener noreferrer'}
|
||||||
|
|
||||||
|
# nano -w /etc/wpa_supplicant/wpa_supplicant.conf
|
||||||
|
|
||||||
|
and inside:
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
ctrl_interface=/var/run/wpa_supplicant
|
||||||
|
ctrl_interface_group=wheel
|
||||||
|
update_config=1
|
||||||
|
|
||||||
|
network = {
|
||||||
|
ssid="lynx"
|
||||||
|
psk="your-pass"
|
||||||
|
}
|
||||||
|
|
||||||
|
Add to service by default
|
||||||
|
|
||||||
|
# rc-update add wpa_supplicant default
|
||||||
|
|
||||||
|
- [DHCPCD][dhcpcd_link]{:target='_blank' rel='noopener noreferrer'}
|
||||||
|
|
||||||
|
Add to service by default
|
||||||
|
|
||||||
|
# rc-update add dhcpcd default
|
||||||
|
|
||||||
|
- Close chroot
|
||||||
|
|
||||||
|
# exit
|
||||||
|
|
||||||
|
- Unmount partitions
|
||||||
|
|
||||||
|
# umount '/mnt/{boot,home,}'
|
||||||
|
|
||||||
|
- Reboot
|
||||||
|
|
||||||
|
# reboot
|
||||||
|
|
||||||
|
### Adding a user
|
||||||
|
|
||||||
|
- Create user group, for example: `libre`
|
||||||
|
|
||||||
|
# groupadd libre
|
||||||
|
|
||||||
|
- Create user `freedom` and add it to basic groups
|
||||||
|
|
||||||
|
# useradd -m -G audio,disk,games,http,input,lp,network,optical,power,scanner,storage,sys,video,wheel -g libre -s /bin/bash freedom
|
||||||
|
|
||||||
|
- Assign password
|
||||||
|
|
||||||
|
# passwd freedom
|
||||||
|
|
||||||
|
- Edit `/etc/sudoers` file
|
||||||
|
|
||||||
|
# sed -i /etc/sudoers -e 's/^# %whell ALL=(ALL) ALL/%whell ALL=(ALL) ALL/g'
|
||||||
|
|
||||||
|
- Reboot pc
|
||||||
|
|
||||||
|
# reboot
|
||||||
|
|
||||||
|
- Upgrade system
|
||||||
|
|
||||||
|
$ sudo pacman -Syu
|
||||||
|
|
||||||
|
### BASE graphical interface
|
||||||
|
|
||||||
|
#### Install video package (depending trademark of your video card)
|
||||||
|
|
||||||
|
Check video trademark:
|
||||||
|
|
||||||
|
# lspci | grep -e VGA
|
||||||
|
|
||||||
|
Install one, depending of trademark:
|
||||||
|
|
||||||
|
AMD:
|
||||||
|
|
||||||
|
# pacman -S xorg-video-amdgpu
|
||||||
|
|
||||||
|
Ati:
|
||||||
|
|
||||||
|
# pacman -S xenocara-video-ati
|
||||||
|
|
||||||
|
Intel:
|
||||||
|
|
||||||
|
# pacman -S xorg-video-intel
|
||||||
|
|
||||||
|
Nvidia:
|
||||||
|
|
||||||
|
# pacman -S xorg-video-nouveau
|
||||||
|
|
||||||
|
Vesa (generic):
|
||||||
|
|
||||||
|
# pacman -S xenocara-video-vesa
|
||||||
|
|
||||||
|
#### Xenocara components
|
||||||
|
|
||||||
|
# pacman -S xenocara-server xenocara-xinit xenocara
|
||||||
|
|
||||||
|
#### Mesa demos
|
||||||
|
|
||||||
|
# pacman -S mesa mesa-demos
|
||||||
|
|
||||||
|
#### Setting in keyboard language for Xenocara
|
||||||
|
|
||||||
|
Syntax of X configuration files is explained in
|
||||||
|
[Xenocara#Configuration][xe-conf]{:target='_blank' rel='noopener noreferrer'}.
|
||||||
|
Method creates configuration for entire system, which is
|
||||||
|
maintained after reboot.
|
||||||
|
|
||||||
|
Here's an example:
|
||||||
|
|
||||||
|
# nano -w /etc/X11/xorg.conf.d/00-keyboard.conf
|
||||||
|
|
||||||
|
and inside write:
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
Section "InputClass"
|
||||||
|
Identifier "system-keyboard"
|
||||||
|
MatchIsKeyboard "on"
|
||||||
|
Option "XkbLayout" "us,uk"
|
||||||
|
Option "XkbModel" "pc105"
|
||||||
|
Option "XkbVariant" "deadtilde,dvorak"
|
||||||
|
Option "XkbOptions" "grp:alt_shift_toggle"
|
||||||
|
EndSection
|
||||||
|
|
||||||
|
XkbOptions can receive various parameters for example:
|
||||||
|
|
||||||
|
`"grp:alt_shift_toggle,compose:rwin,lv3:ralt_switch,numpad:pc"`
|
||||||
|
|
||||||
|
We have 2 keyboard layouts: English US (us) and English UK (uk),
|
||||||
|
and to go from one to the other just use the `ALT+SHIFT`
|
||||||
|
key combination.
|
||||||
|
|
||||||
|
- Check keyboard settings:
|
||||||
|
|
||||||
|
# setxkbmap -print -verbose 10
|
||||||
|
|
||||||
|
- Typefaces
|
||||||
|
|
||||||
|
# pacman -S ttf-liberation ttf-bitstream-vera ttf-dejavu ttf-droid
|
||||||
|
|
||||||
|
Next, we will proceed to create the personal folders.
|
||||||
|
In case you have planned to install **GNOME** or **PLASMA KDE**
|
||||||
|
as a desktop environment, skip this step, since the
|
||||||
|
**GNOME** or **PLASMA KDE** installation automatically
|
||||||
|
generates this directories.
|
||||||
|
|
||||||
|
- Directory generator installation:
|
||||||
|
|
||||||
|
# pacman -S xdg-user-dirs
|
||||||
|
|
||||||
|
- Automatic directory creation:
|
||||||
|
|
||||||
|
# xdg-user-dirs-update
|
||||||
|
|
||||||
|
#### Audio support
|
||||||
|
|
||||||
|
Install `pulseadio`
|
||||||
|
|
||||||
|
# pacman -S pulseaudio pulseaudio-alsa alsa-utils pavucontrol
|
||||||
|
|
||||||
|
Add audio service to default
|
||||||
|
|
||||||
|
# rc-update add alsasound default
|
||||||
|
|
||||||
|
#### Configure pulseaudio
|
||||||
|
|
||||||
|
# sed -e 's/^; autospawn = yes/autospawn = yes/g' -i /etc/pulse/client.conf
|
||||||
|
|
||||||
|
### Officially supported desktop environments
|
||||||
|
|
||||||
|
#### Install MATE
|
||||||
|
|
||||||
|
MATE desktop environment is the continuation of GNOME 2 (Based on Gnome 2).
|
||||||
|
It provides an intuitive and attractive environment. MATE is actively being
|
||||||
|
developed to add support for new technologies, while preserving the
|
||||||
|
traditional desktop experience.
|
||||||
|
|
||||||
|
- Installation
|
||||||
|
|
||||||
|
# pacman -S mate mate-extra
|
||||||
|
|
||||||
|
Where:
|
||||||
|
|
||||||
|
+ mate: contains basic desktop environment and applications necessary for the standard MATE experience.
|
||||||
|
+ mate-extra: contains a set of packages and optional tools, like a screensaver, a calculator,
|
||||||
|
an editor and other non-problematic applications that go well with the MATE desktop.
|
||||||
|
|
||||||
|
#### Install XFCE
|
||||||
|
|
||||||
|
Xfce is a lightweight desktop environment for UNIX-like systems.
|
||||||
|
Its goal is to be fast and use few system resources, while
|
||||||
|
remaining visually attractive and easy to use.
|
||||||
|
|
||||||
|
- Installation
|
||||||
|
|
||||||
|
# pacman -S xfce4 xfce4-goodies
|
||||||
|
|
||||||
|
Where:
|
||||||
|
|
||||||
|
+ xfce4: is basic group of xfce4 packages.
|
||||||
|
+ xfce4-goodies: is a group of additional packages, such as panel plugins,
|
||||||
|
notifications and other system tools.
|
||||||
|
|
||||||
|
#### Install LXDE
|
||||||
|
|
||||||
|
LXDE is a free desktop environment. Abbreviation means
|
||||||
|
«Lightweight X11 Desktop Environment»
|
||||||
|
|
||||||
|
- Installation
|
||||||
|
|
||||||
|
# pacman -S lxde
|
||||||
|
|
||||||
|
#### Install KDE Plasma
|
||||||
|
|
||||||
|
KDE is a software project that currently comprises a
|
||||||
|
desktop environment known as Plasma, a collection of
|
||||||
|
libraries and frameworks (KDE Frameworks) and also a
|
||||||
|
large number of applications (KDE Applications).
|
||||||
|
|
||||||
|
The desktop environment created by KDE primarily for GNU/Linux systems,
|
||||||
|
KDE Plasma 5, is successor to KDE Plasma Workspaces and is primarily
|
||||||
|
released on July 15, 2014.
|
||||||
|
|
||||||
|
- Installation
|
||||||
|
|
||||||
|
# pacman -S plasma kde-applications plasma-wayland-session
|
||||||
|
|
||||||
|
Where:
|
||||||
|
|
||||||
|
+ plasma: contains group of packages to install desktop. with some basic applications and tools.
|
||||||
|
+ kde-applications: installs all KDE applications contained in group (kcal, amarok, etc).
|
||||||
|
+ plasma-wayland-session: enable support for Wayland in Plasma.
|
||||||
|
|
||||||
|
#### How to start Xenocara?
|
||||||
|
|
||||||
|
- Write a `~/.xinitrc` file (option 1)
|
||||||
|
|
||||||
|
Uncomment your desktop installed, example file `~/.xinitrc`:
|
||||||
|
|
||||||
|
:::bash
|
||||||
|
#!/bin/sh
|
||||||
|
#
|
||||||
|
# ~/.xinitrc
|
||||||
|
#
|
||||||
|
# Executed by startx (run your window manager from here)
|
||||||
|
#
|
||||||
|
# exec enlightenment_start
|
||||||
|
# exec i3
|
||||||
|
# exec mate-session
|
||||||
|
# exec xmonad
|
||||||
|
# exec startlxqt
|
||||||
|
# exec startlxde
|
||||||
|
# exec awesome
|
||||||
|
# exec bspwm
|
||||||
|
# exec gnome-session
|
||||||
|
# exec gnome-session --session=gnome-classic
|
||||||
|
# exec startkde
|
||||||
|
# exec startxfce4
|
||||||
|
# exec startfluxbox
|
||||||
|
# exec openbox-session
|
||||||
|
# exec cinnamon-session
|
||||||
|
# exec pekwm
|
||||||
|
# exec catwm
|
||||||
|
# exec dwm
|
||||||
|
# exec startede
|
||||||
|
# exec icewm-session
|
||||||
|
# exec jwm
|
||||||
|
# exec monsterwm
|
||||||
|
# exec notion
|
||||||
|
# exec startdde #deepin-session
|
||||||
|
|
||||||
|
Then from a tty, you can run `startx` and your desktop will start.
|
||||||
|
|
||||||
|
- Install login manager (option 2)
|
||||||
|
|
||||||
|
Example: `lightdm`
|
||||||
|
|
||||||
|
# pacman -S lightdm lightdm-gtk-greeter
|
||||||
|
|
||||||
|
Add to service by default
|
||||||
|
|
||||||
|
# rc-update add lightdm default
|
||||||
|
|
||||||
|
- Reboot
|
||||||
|
|
||||||
|
# reboot
|
||||||
|
|
||||||
|
### Tools
|
||||||
|
|
||||||
|
#### Disks
|
||||||
|
|
||||||
|
- gvfs to mount disks
|
||||||
|
|
||||||
|
# pacman -S gamin gvfs
|
||||||
|
|
||||||
|
#### Net
|
||||||
|
|
||||||
|
- dhcpcd-ui for IP management
|
||||||
|
|
||||||
|
# pacman -S dhcpcd-ui
|
||||||
|
|
||||||
|
#### Key manager
|
||||||
|
|
||||||
|
- gnome-kering
|
||||||
|
|
||||||
|
# pacman -S gnome-keyring
|
||||||
|
|
||||||
|
#### Volume applet
|
||||||
|
|
||||||
|
- Volume icon
|
||||||
|
|
||||||
|
# pacman -S volumeicon
|
||||||
|
|
||||||
|
#### Synchronize Local Time
|
||||||
|
|
||||||
|
Install NTP
|
||||||
|
|
||||||
|
# pacman -S ntp
|
||||||
|
|
||||||
|
Synchronize Time
|
||||||
|
|
||||||
|
# ntpdate -u hora.roa.es
|
||||||
|
|
||||||
|
#### File compressors
|
||||||
|
|
||||||
|
Normally we come across files compressed in ZIP, RAR and/or another
|
||||||
|
format that are usually exchanged on the Internet. In many desktop
|
||||||
|
environments, usually include theirs (File Roller in GNOME, Engrampa
|
||||||
|
in MATE, Ark in KDE, and XArchiver in XFCE/LXDE). To improve functionality
|
||||||
|
of these file compressors, we will add support for 7Z, RAR, ZIP and others.
|
||||||
|
|
||||||
|
- GZip (known with extension ".tar.gz"):
|
||||||
|
|
||||||
|
# pacman -S zlib haskell-zlib
|
||||||
|
|
||||||
|
- BZip2:
|
||||||
|
|
||||||
|
# pacman -S bzip2
|
||||||
|
|
||||||
|
- RAR:
|
||||||
|
|
||||||
|
# pacman -S unar
|
||||||
|
|
||||||
|
- 7Zip:
|
||||||
|
|
||||||
|
# pacman -S p7zip lrzip
|
||||||
|
|
||||||
|
- ZIP:
|
||||||
|
|
||||||
|
# pacman -S zip libzip unzip
|
||||||
|
|
||||||
|
#### Partition detector
|
||||||
|
|
||||||
|
- Udisk utility:
|
||||||
|
|
||||||
|
# pacman -S udevil autofs
|
||||||
|
|
||||||
|
- Reading and writing NTFS file systems:
|
||||||
|
|
||||||
|
# pacman -S ntfs-3g
|
||||||
|
|
||||||
|
- FAT32 file system read and write:
|
||||||
|
|
||||||
|
# pacman -S fatsort exfat-utils dosfstools
|
||||||
|
|
||||||
|
- Reading and writing XFS file systems:
|
||||||
|
|
||||||
|
# pacman -S xfsprogs
|
||||||
|
|
||||||
|
#### Multimedia support
|
||||||
|
To play multimedia files, you need to be able to have the codecs and player.
|
||||||
|
To do this, we will proceed to install ffmpeg and gstreamer codecs, in addition
|
||||||
|
to players.
|
||||||
|
Here I suggest some players that you may find useful.
|
||||||
|
|
||||||
|
- Codecs:
|
||||||
|
|
||||||
|
# pacman -S ffmpeg gstreamer gst-libav gst-plugins-bad gst-plugins-good gst-plugins-ugly gst-plugins-base gstreamer-vaapi gst-transcoder ffms2 x264 libvorbis libvpx libtheora opus vorbis-tools
|
||||||
|
|
||||||
|
- Audacious player:
|
||||||
|
|
||||||
|
# pacman -S audacious
|
||||||
|
|
||||||
|
- SMPlayer:
|
||||||
|
|
||||||
|
# pacman -S smplayer smplayer-themes smplayer-skins
|
||||||
|
|
||||||
|
- VLC player:
|
||||||
|
|
||||||
|
# pacman -S vlc
|
||||||
|
|
||||||
|
- MPV player:
|
||||||
|
|
||||||
|
# pacman -S mpv
|
||||||
|
|
||||||
|
- Lightweight image viewer
|
||||||
|
|
||||||
|
# pacman -S viewnior
|
||||||
|
|
||||||
|
- PDF viewer
|
||||||
|
|
||||||
|
# pacman -S epdfview
|
||||||
|
|
||||||
|
#### Aplicaciones UXP
|
||||||
|
There are browsers included by desktop environments like GNOME with Epiphany
|
||||||
|
or KDE with Konqueror. However, thanks to the developers, in Hyperbola
|
||||||
|
we have **[Iceweasel-UXP][iceweasel-uxp]{:target='_blank' rel='noopener noreferrer'}**
|
||||||
|
a web browser, **[Iceape-UXP][iceape-uxp]{:target='_blank' rel='noopener noreferrer'}**
|
||||||
|
internet suite and a email-manager called
|
||||||
|
**[Icedove-UXP][icedove-uxp]{:target='_blank' rel='noopener noreferrer'}**.
|
||||||
|
|
||||||
|
- Iceweasel-UXP:
|
||||||
|
|
||||||
|
# pacman -S iceweasel-uxp
|
||||||
|
|
||||||
|
- Iceape-UXP:
|
||||||
|
|
||||||
|
# pacman -S iceape-uxp
|
||||||
|
|
||||||
|
- Icedove-UXP:
|
||||||
|
|
||||||
|
# pacman -S icedove-uxp
|
||||||
|
|
||||||
|
#### LibreOffice
|
||||||
|
In general, when using an Operating System, at least you have an office suite.
|
||||||
|
In GNU/Linux, it's customary to have one. Fortunately in Hyperbola, Libreoffice
|
||||||
|
is presented in its stable version. For install, run:
|
||||||
|
|
||||||
|
# pacman -S libreoffice-still
|
||||||
|
|
||||||
|
##### Spell check
|
||||||
|
To check spelling you will need hunspell and a hunspell dictionary (such as hunspell-en_US, hunspell-es, etc)
|
||||||
|
|
||||||
|
# pacman -S hunspell hunspell-en_US
|
||||||
|
|
||||||
|
##### Hyphenation and justification
|
||||||
|
To have provide rules you also need `hyphen` + a set of rules (hyphen-en, hyphen-de, etc)
|
||||||
|
|
||||||
|
# pacman -S hyphen hyphen-en
|
||||||
|
|
||||||
|
##### Synonyms
|
||||||
|
For Synonyms option you will need `mythes` + a mythes synonym library (`mythes-en` `mythes-es`)
|
||||||
|
|
||||||
|
# pacman -S mythes mythes-en
|
||||||
|
|
||||||
|
#### Security
|
||||||
|
Security is important when browsing the Internet, that's why Hyperbola provides
|
||||||
|
a tool called **[firejail][firejail]{:target='_blank' rel='noopener noreferrer'}**
|
||||||
|
in combination with a graphical interface
|
||||||
|
**[firetools][firetools]{:target='_blank' rel='noopener noreferrer'}**.
|
||||||
|
|
||||||
|
# pacman -S firejail firetools
|
||||||
|
|
||||||
|
#### Social
|
||||||
|
Hyperbola have programs for communication:
|
||||||
|
|
||||||
|
- Gajim
|
||||||
|
|
||||||
|
# pacman -S gajim python2-axolotl
|
||||||
|
|
||||||
|
- Tox
|
||||||
|
- qtox:
|
||||||
|
|
||||||
|
# pacman -S qtox
|
||||||
|
|
||||||
|
- toxic:
|
||||||
|
|
||||||
|
# pacman -S toxic
|
||||||
|
|
||||||
|
#### Identifying keycodes
|
||||||
|
|
||||||
|
Showkey utility reports key codes for the virtual console. showkey waits
|
||||||
|
for a key to be pressed and, if there is none for 10 seconds, closes.
|
||||||
|
To run showkey you need to be in a virtual console, not in a graphical
|
||||||
|
environment:
|
||||||
|
|
||||||
|
# showkey --keycodes
|
||||||
|
|
||||||
|
[video-guide]: https://lablibre.tuxfamily.org/hyperbola-gnu-linux-libre-base/
|
||||||
|
[firejail]: https://github.com/netblue30/firejail
|
||||||
|
[firetools]: https://l3net.wordpress.com/projects/firejail/#firetools
|
||||||
|
[usb-boot]: https://wiki.hyperbola.info/doku.php?id=en:guide:beginners#write_the_image_to_your_usb
|
||||||
|
[cd-boot]: https://wiki.hyperbola.info/doku.php?id=en:guide:beginners#burn_the_image_to_your_optical_disk
|
||||||
|
[wpa_link]: https://wiki.archlinux.org/index.php/WPA_supplicant
|
||||||
|
[dhcpcd_link]: https://wiki.archlinux.org/index.php/Dhcpcd
|
||||||
|
[iceweasel-uxp]: https://wiki.hyperbola.info/iceweasel-uxp
|
||||||
|
[iceape-uxp]: https://wiki.hyperbola.info/iceape-uxp
|
||||||
|
[icedove-uxp]: https://wiki.hyperbola.info/icedove-uxp
|
||||||
|
[xe-conf]: https://fedoraproject.org/wiki/Input_device_configuration#xorg.conf.d
|
@ -141,7 +141,7 @@ Instalamos los paquetes base:
|
|||||||
|
|
||||||
# echo hyperpc > /etc/hostname
|
# echo hyperpc > /etc/hostname
|
||||||
|
|
||||||
- Configurar idioma
|
- Configurar lugar
|
||||||
|
|
||||||
# ln -s /usr/share/zoneinfo/America/Lima /etc/localtime
|
# ln -s /usr/share/zoneinfo/America/Lima /etc/localtime
|
||||||
|
|
||||||
@ -370,7 +370,7 @@ Donde:
|
|||||||
|
|
||||||
+ mate: Contiene el entorno de escritorio básico y aplicaciones necesarias para la experiencia estándar de MATE.
|
+ mate: Contiene el entorno de escritorio básico y aplicaciones necesarias para la experiencia estándar de MATE.
|
||||||
+ mate-extra: Contiene un conjunto de paquetes y herramientas opcionales, como un salvapantallas, una calculadora,
|
+ mate-extra: Contiene un conjunto de paquetes y herramientas opcionales, como un salvapantallas, una calculadora,
|
||||||
un editores y otras aplicaciones no problemáticas que van bien con el escritorio MATE.
|
un editor y otras aplicaciones no problemáticas que van bien con el escritorio MATE.
|
||||||
|
|
||||||
#### Instalar XFCE
|
#### Instalar XFCE
|
||||||
|
|
||||||
@ -384,7 +384,7 @@ sin dejar de ser visualmente atractivo y fácil de usar.
|
|||||||
|
|
||||||
Donde:
|
Donde:
|
||||||
|
|
||||||
+ xfce4: es el entorno de escritorio basico Grupo de paquetes que contiene.
|
+ xfce4: es el grupo básico de paquetes de xfce4.
|
||||||
+ xfce4-goodies: es un grupo de paquetes adicionales, como plugins para el panel,
|
+ xfce4-goodies: es un grupo de paquetes adicionales, como plugins para el panel,
|
||||||
notificaciones y otras herramientas del sistema.
|
notificaciones y otras herramientas del sistema.
|
||||||
|
|
||||||
@ -510,13 +510,13 @@ Sincronizar Hora
|
|||||||
|
|
||||||
#### Compresores de archivos
|
#### Compresores de archivos
|
||||||
|
|
||||||
Normalmente nos topamos con carpetas comprimidas en ZIP, RAR y/u otro formato que
|
Normalmente nos topamos con archivos comprimidos en ZIP, RAR y/u otro formato que
|
||||||
se suelen intercambiar en Internet. En muchos entornos de escritorio, suelen
|
se suelen intercambiar en Internet. En muchos entornos de escritorio, suelen
|
||||||
incluir el suyo (File Roller en GNOME, Engrampa en MATE, Ark en KDE y XArchiver
|
incluir el suyo (File Roller en GNOME, Engrampa en MATE, Ark en KDE y XArchiver
|
||||||
en XFCE/LXDE). Para mejorar la funcionalidad de estos compresores de archivos,
|
en XFCE/LXDE). Para mejorar la funcionalidad de estos compresores de archivos,
|
||||||
le añadiremos el soporte para 7Z, RAR, ZIP y otros.
|
le añadiremos el soporte para 7Z, RAR, ZIP y otros.
|
||||||
|
|
||||||
- GZip (conocidos por la extensión “.tar.gz”):
|
- GZip (conocidos por la extensión ".tar.gz"):
|
||||||
|
|
||||||
# pacman -S zlib haskell-zlib
|
# pacman -S zlib haskell-zlib
|
||||||
|
|
||||||
@ -590,7 +590,7 @@ Aquí les sugiero algunos reproductores que les puede resultar útiles.
|
|||||||
|
|
||||||
#### Aplicaciones UXP
|
#### Aplicaciones UXP
|
||||||
Existen navegadores incluidos por los entornos de escritorio como GNOME con Epiphany
|
Existen navegadores incluidos por los entornos de escritorio como GNOME con Epiphany
|
||||||
o KDE con Konqueror. No obstante, gracias a los desarrolladores Hyperbola tenemos
|
o KDE con Konqueror. No obstante, gracias a los desarrolladores en Hyperbola tenemos
|
||||||
**[Iceweasel-UXP][iceweasel-uxp]{:target='_blank' rel='noopener noreferrer'}** un
|
**[Iceweasel-UXP][iceweasel-uxp]{:target='_blank' rel='noopener noreferrer'}** un
|
||||||
navegador web,
|
navegador web,
|
||||||
**[Iceape-UXP][iceape-uxp]{:target='_blank' rel='noopener noreferrer'}** suite de internet
|
**[Iceape-UXP][iceape-uxp]{:target='_blank' rel='noopener noreferrer'}** suite de internet
|
||||||
@ -666,11 +666,11 @@ no en un entorno gráfico. Ejecute el siguiente comando:
|
|||||||
[video-guide]: https://lablibre.tuxfamily.org/hyperbola-gnu-linux-libre-base/
|
[video-guide]: https://lablibre.tuxfamily.org/hyperbola-gnu-linux-libre-base/
|
||||||
[firejail]: https://github.com/netblue30/firejail
|
[firejail]: https://github.com/netblue30/firejail
|
||||||
[firetools]: https://l3net.wordpress.com/projects/firejail/#firetools
|
[firetools]: https://l3net.wordpress.com/projects/firejail/#firetools
|
||||||
[usb-boot]: https://wiki.hyperbola.info/doku.php?id=en:guide:beginners#write_the_image_to_your_usb
|
[usb-boot]: https://wiki.hyperbola.info/doku.php?id=es:guide:beginners#write_the_image_to_your_usb
|
||||||
[cd-boot]: https://wiki.hyperbola.info/doku.php?id=en:guide:beginners#burn_the_image_to_your_optical_disk
|
[cd-boot]: https://wiki.hyperbola.info/doku.php?id=es:guide:beginners#burn_the_image_to_your_optical_disk
|
||||||
[wpa_link]: https://wiki.archlinux.org/index.php/WPA_supplicant
|
[wpa_link]: https://wiki.archlinux.org/index.php/WPA_supplicant
|
||||||
[dhcpcd_link]: https://wiki.archlinux.org/index.php/Dhcpcd
|
[dhcpcd_link]: https://wiki.archlinux.org/index.php/Dhcpcd
|
||||||
[iceweasel-uxp]: https://wiki.hyperbola.info/iceweasel-uxp
|
[iceweasel-uxp]: https://wiki.hyperbola.info/doku.php?id=es:project:iceweasel-uxp
|
||||||
[iceape-uxp]: https://wiki.hyperbola.info/iceape-uxp
|
[iceape-uxp]: https://wiki.hyperbola.info/doku.php?id=es:project:iceape-uxp
|
||||||
[icedove-uxp]: https://wiki.hyperbola.info/icedove-uxp
|
[icedove-uxp]: https://wiki.hyperbola.info/doku.php?id=es:project:icedove-uxp
|
||||||
[xe-conf]: https://fedoraproject.org/wiki/Input_device_configuration#xorg.conf.d
|
[xe-conf]: https://fedoraproject.org/wiki/Input_device_configuration#xorg.conf.d
|
||||||
|
@ -0,0 +1,63 @@
|
|||||||
|
Author: Jesús E.
|
||||||
|
Category: Noticias
|
||||||
|
Date: 2018-12-08 11:25
|
||||||
|
Image: 2018/12/hyperbola-gnu-freedom.png
|
||||||
|
Lang: en
|
||||||
|
Save_as: fsf-approved-hyperbola/index.html
|
||||||
|
URL: fsf-approved-hyperbola/
|
||||||
|
Slug: hyperbola-gnu-linux-libre-es-aprobada-por-la-fsf
|
||||||
|
Tags: fsf, hyperbola, gnu
|
||||||
|
Title: FSF-Approved Hyperbola
|
||||||
|
|
||||||
|
**Hyperbola GNU/Linux-libre** distribution has been accepted
|
||||||
|
by the **Free Software Foundation** (FSF) to its list of 100%
|
||||||
|
free software distributions.
|
||||||
|
|
||||||
|
<figure class="has-text-center is-table">
|
||||||
|
<img src="https://static.fsf.org/nosvn/images/hyperbola_logo.png" alt="Hyperbola logo" height="50" width="276">
|
||||||
|
<figcaption>Hyperbola GNU plus Linux-libre</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
After several months, **Hyperbola GNU/Linux-libre**, a distribution
|
||||||
|
based on **Arch GNU/Linux** and with the stability of **Debian**,
|
||||||
|
is now part of the [list of free distributions][free-distros]
|
||||||
|
being endorsed by FSF.
|
||||||
|
|
||||||
|
<figure class="has-text-center is-table">
|
||||||
|
<img src="https://static.fsf.org/common/img/logo-new.png" alt="FSF logo">
|
||||||
|
<figcaption>Free Software Foundation</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
**John Sullivan** FSF's executive director, said about it:
|
||||||
|
|
||||||
|
>In a world where proprietary operating systems continually
|
||||||
|
>up the ante in terms of the abuse they heap on their users,
|
||||||
|
>adding another distribution to the list of fully free systems
|
||||||
|
>is a welcome development. Hyperbola represents another safe
|
||||||
|
>home for users looking for complete control over their own
|
||||||
|
>computing.
|
||||||
|
|
||||||
|
**André Silva**, Hyperbola co-founder and developer, said about it:
|
||||||
|
|
||||||
|
>Hyperbola is a fully free distribution based on Arch snapshots
|
||||||
|
>and Debian development without nonfree software, documentation,
|
||||||
|
>or any type of support for the installation or execution of
|
||||||
|
>nonfree software. Unlike Arch, which is a rolling release
|
||||||
|
>distribution, Hyperbola is a long-term one focused on stability
|
||||||
|
>and security inspired from Debian and Devuan.
|
||||||
|
|
||||||
|
**Donald Robertson**, FSF's licensing and compliance manager, added:
|
||||||
|
|
||||||
|
>It was a pleasure working with the team behind Hyperbola
|
||||||
|
>throughout this process. They really go above and beyond
|
||||||
|
>in terms of looking out for the rights of their users.
|
||||||
|
|
||||||
|
**Hyperbola** is the first completely free distribution born in
|
||||||
|
**FISL17** (Porto Alegre, Brazil). You have more information on
|
||||||
|
Hyperbola website, from where you can [download][download]
|
||||||
|
the images to [install]({filename}/guia-de-instalacion-de-hyperbola.en.md)
|
||||||
|
or test the distro in "live" mode.
|
||||||
|
|
||||||
|
[free-distros]: https://www.gnu.org/distros/free-distros.html
|
||||||
|
[download]: https://www.hyperbola.info/download/
|
||||||
|
[hypersite]: https://www.hyperbola.info
|
@ -2,6 +2,7 @@ Author: Jesús E.
|
|||||||
Category: Noticias
|
Category: Noticias
|
||||||
Date: 2018-12-08 11:25
|
Date: 2018-12-08 11:25
|
||||||
Image: 2018/12/hyperbola-gnu-freedom.png
|
Image: 2018/12/hyperbola-gnu-freedom.png
|
||||||
|
Lang: es
|
||||||
Slug: hyperbola-gnu-linux-libre-es-aprobada-por-la-fsf
|
Slug: hyperbola-gnu-linux-libre-es-aprobada-por-la-fsf
|
||||||
Tags: fsf, hyperbola, gnu
|
Tags: fsf, hyperbola, gnu
|
||||||
Title: Hyperbola GNU/Linux-libre es aprobada por la FSF
|
Title: Hyperbola GNU/Linux-libre es aprobada por la FSF
|
||||||
|
@ -2,6 +2,7 @@ Author: Jesús E.
|
|||||||
Category: Tutorial
|
Category: Tutorial
|
||||||
Date: 2018-08-22 10:52
|
Date: 2018-08-22 10:52
|
||||||
Image: 2018/08/montar-android-en-hyperbola.png
|
Image: 2018/08/montar-android-en-hyperbola.png
|
||||||
|
Lang: es
|
||||||
Slug: montar-android-en-hyperbola
|
Slug: montar-android-en-hyperbola
|
||||||
Tags: android, mtp, hyperbola, usb
|
Tags: android, mtp, hyperbola, usb
|
||||||
Title: Montar Android en Hyperbola
|
Title: Montar Android en Hyperbola
|
||||||
|
77
content/articles/por-que-no-windows.en.md
Normal file
77
content/articles/por-que-no-windows.en.md
Normal file
@ -0,0 +1,77 @@
|
|||||||
|
Author: Jesús E.
|
||||||
|
Category: Opinión
|
||||||
|
Date: 2018-02-17 08:14
|
||||||
|
Image: 2018/02/question.png
|
||||||
|
Lang: en
|
||||||
|
Save_as: why-not-windows/index.html
|
||||||
|
URL: why-not-windows/
|
||||||
|
Slug: por-que-no-windows
|
||||||
|
Tags: libre, libertad, gnu, linux-libre
|
||||||
|
Title: Why not Windows?
|
||||||
|
|
||||||
|
Windows and Office work well, then: **how can this be so bad?**
|
||||||
|
|
||||||
|
## Restrictions
|
||||||
|
|
||||||
|
A legal copy of Windows is expensive, but what do you get?
|
||||||
|
Windows and Office are licensed, not sold.
|
||||||
|
|
||||||
|
By using these products, we have to agree **to a number of
|
||||||
|
harsh restrictions**. For most Windows licenses, you can't
|
||||||
|
keep the software when you change the hardware. You
|
||||||
|
sometimes can't even give your software away. Who can run
|
||||||
|
the software? On which computer? What can you do with it?
|
||||||
|
The list of restrictions is long and some items are
|
||||||
|
outrageous.
|
||||||
|
|
||||||
|
## Can't we choose?
|
||||||
|
|
||||||
|
Software should come without mechanisms to tie users
|
||||||
|
to a company's products.
|
||||||
|
|
||||||
|
Why are Office documents difficult to export?
|
||||||
|
Why are the formats continually changing? Why can
|
||||||
|
you not even uninstall some programs? It might be
|
||||||
|
that if you look for choice, Microsoft products
|
||||||
|
aren't for you.
|
||||||
|
|
||||||
|
## Without source code
|
||||||
|
|
||||||
|
The source code (the details of how a program works) of Windows
|
||||||
|
and Office are hidden, and also **nobody has legal permission
|
||||||
|
to find out how this work**.
|
||||||
|
|
||||||
|
If you don't have the right to inspect the source code
|
||||||
|
(the description of how a program works), you can't ask a
|
||||||
|
developer to modify the software or evaluate how
|
||||||
|
the software protects your privacy.
|
||||||
|
|
||||||
|
And guess what? On software that comes with source code,
|
||||||
|
viruses and spyware aren't effective, and security isn't
|
||||||
|
bought on extra. The antivirus software industry, in which
|
||||||
|
Microsoft is now a significant player, prefers you
|
||||||
|
to use Windows.
|
||||||
|
|
||||||
|
## For a Free Society
|
||||||
|
|
||||||
|
A free society requires Free Software. Think of "Free" as freedom,
|
||||||
|
not price: the freedom to inspect, learn, and modify the
|
||||||
|
software you use.
|
||||||
|
|
||||||
|
Computers are used to share ideas, culture, and information.
|
||||||
|
Without these liberties over software, we are at risk of
|
||||||
|
losing control over what we share.
|
||||||
|
|
||||||
|
This is happening today. From plain annoying technologies
|
||||||
|
such as [Digital Restrictions Management][drm] (DRM) to
|
||||||
|
downright frightening ones like [Trusted Computing][tc],
|
||||||
|
everyone's ability to participate in culture is threatened.
|
||||||
|
|
||||||
|
If you have to give up your freedoms to use software,
|
||||||
|
maybe you should not be happy with it.
|
||||||
|
|
||||||
|
Original publish: [https://www.getgnulinux.org/windows/](https://www.getgnulinux.org/windows/)
|
||||||
|
|
||||||
|
[drm]: https://www.gnu.org/proprietary/proprietary-drm.html
|
||||||
|
[tc]: https://www.gnu.org/philosophy/can-you-trust.html
|
||||||
|
[locutorio]: https://www.20minutos.es/noticia/3332612/0/prision-duena-locutorio-tenia-copias-ilicitas-windows-instaladas/
|
@ -2,6 +2,7 @@ Author: Jesús E.
|
|||||||
Category: Opinión
|
Category: Opinión
|
||||||
Date: 2018-02-17 08:14
|
Date: 2018-02-17 08:14
|
||||||
Image: 2018/02/question.png
|
Image: 2018/02/question.png
|
||||||
|
Lang: es
|
||||||
Slug: por-que-no-windows
|
Slug: por-que-no-windows
|
||||||
Tags: libre, libertad, gnu, linux-libre
|
Tags: libre, libertad, gnu, linux-libre
|
||||||
Title: ¿Por qué no Windows?
|
Title: ¿Por qué no Windows?
|
||||||
|
43
content/articles/prompt-avanzado.en.md
Normal file
43
content/articles/prompt-avanzado.en.md
Normal file
@ -0,0 +1,43 @@
|
|||||||
|
Author: Jesús E.
|
||||||
|
Category: GNU/Linux
|
||||||
|
Date: 2017-12-05 11:34
|
||||||
|
Modified: 2019-02-06 11:34
|
||||||
|
Image: 2017/12/bash.png
|
||||||
|
Lang: en
|
||||||
|
Save_as: advanced-prompt/index.html
|
||||||
|
URL: advanced-prompt/
|
||||||
|
Slug: prompt-avanzado
|
||||||
|
Tags: bash, hyperbash, shell
|
||||||
|
Title: Advanced prompt
|
||||||
|
|
||||||
|
Many times we need the [command interpreter][bash] to perform
|
||||||
|
the odd task, perhaps it is tedious to put together our
|
||||||
|
own `.bashrc` configuration. But since there is a lot of
|
||||||
|
useful information on the [World Wide Web][www], it has been
|
||||||
|
possible to write a prudent configuration of the
|
||||||
|
aforementioned `.bashrc` for Arch-based distros such as
|
||||||
|
[Hyperbola][hypersite] or [Parabola][parasite], in fact
|
||||||
|
these last 2 are 100% Free distros.
|
||||||
|
|
||||||
|
And where do I get a copy? You can easily download it from
|
||||||
|
[notabug][notabug] under the [GPLv3][license] License.
|
||||||
|
|
||||||
|
Is there a video, showing its use? yes, although the video
|
||||||
|
is in spanish language:
|
||||||
|
|
||||||
|
<video playsinline controls>
|
||||||
|
<source src="https://archive.org/download/libreweb/0001-15599.webm" type="video/webm">
|
||||||
|
<p><em>Your browser does not support the video tag, please download the video instead.</em></p>
|
||||||
|
</video>
|
||||||
|
|
||||||
|
###### Downloads
|
||||||
|
|
||||||
|
- [Vídeo][v0] (1080p)
|
||||||
|
|
||||||
|
[bash]: https://en.wikipedia.org/wiki/Bash
|
||||||
|
[www]: https://en.wikipedia.org/wiki/World_Wide_Web
|
||||||
|
[hypersite]: https://hyperbola.info/
|
||||||
|
[parasite]: https://parabola.nu/
|
||||||
|
[notabug]: https://notabug.org/heckyel/hyperbash
|
||||||
|
[license]: https://www.gnu.org/licenses/gpl-3.0.html
|
||||||
|
[v0]: https://archive.org/download/libreweb/0001-15599.webm
|
@ -3,6 +3,7 @@ Category: GNU/Linux
|
|||||||
Date: 2017-12-05 11:34
|
Date: 2017-12-05 11:34
|
||||||
Modified: 2019-02-06 11:34
|
Modified: 2019-02-06 11:34
|
||||||
Image: 2017/12/bash.png
|
Image: 2017/12/bash.png
|
||||||
|
Lang: es
|
||||||
Slug: prompt-avanzado
|
Slug: prompt-avanzado
|
||||||
Tags: bash, hyperbash, shell
|
Tags: bash, hyperbash, shell
|
||||||
Title: Prompt avanzado
|
Title: Prompt avanzado
|
||||||
|
@ -2,6 +2,7 @@ Author: Jesús E.
|
|||||||
Category: Opinión
|
Category: Opinión
|
||||||
Date: 2018-06-09 10:07
|
Date: 2018-06-09 10:07
|
||||||
Image: 2018/06/RMS-Dominio-Digital.png
|
Image: 2018/06/RMS-Dominio-Digital.png
|
||||||
|
Lang: es
|
||||||
Slug: rms-en-dominio-digital
|
Slug: rms-en-dominio-digital
|
||||||
Tags: GNU/Linux
|
Tags: GNU/Linux
|
||||||
Title: RMS en Dominio digital
|
Title: RMS en Dominio digital
|
||||||
|
49
content/articles/sayonara-openmailbox.en.md
Normal file
49
content/articles/sayonara-openmailbox.en.md
Normal file
@ -0,0 +1,49 @@
|
|||||||
|
Author: Jesús E.
|
||||||
|
Category: Opinión
|
||||||
|
Date: 2017-08-14 11:09
|
||||||
|
Image: 2017/08/openmailbox.png
|
||||||
|
Lang: en
|
||||||
|
Save_as: goodbye-openmailbox/index.html
|
||||||
|
URL: goodbye-openmailbox/
|
||||||
|
Slug: sayonara-openmailbox
|
||||||
|
Tags: openmailbox, mail
|
||||||
|
Title: GoodBye OpenMailBox
|
||||||
|
|
||||||
|
OpenMailBox, has been operating since 2012, but as of the date of
|
||||||
|
this article in 2017, it has changed the policies of its services,
|
||||||
|
which has caused discontent in the majority of its users, and the
|
||||||
|
notorious migration to other services.
|
||||||
|
|
||||||
|
Communication with its users has not been the strong point of
|
||||||
|
this service. At beginning there was an official forum that
|
||||||
|
eventually disappeared without further explanation.
|
||||||
|
|
||||||
|
The only official way to communicate with OpenMailBox was through
|
||||||
|
its Twitter account (a non-free and centralized social network),
|
||||||
|
and they don't seem to lavish too much on explanations either.
|
||||||
|
|
||||||
|
The most notable changes consist of, those who were already users,
|
||||||
|
would have access only to mail through their client web. On the
|
||||||
|
contrary, paying or not for a service is not the problem, the
|
||||||
|
issue comes in the following lines…
|
||||||
|
|
||||||
|
Your login page unfortunately runs **ECMAScript** (JavaScript)
|
||||||
|
Not free from Google (the recaptcha API, [freakspot][fsite] tells
|
||||||
|
in detail about this API), that is the real problem since users
|
||||||
|
would undoubtedly be at the mercy of possible cyber espionage
|
||||||
|
and it goes against the [philosophy of Free Software][gnu-philosophy].
|
||||||
|
|
||||||
|
## Service replacements with Free Software
|
||||||
|
|
||||||
|
+ [Posteo][posteo], payment 1 EUR per month,
|
||||||
|
+ [Riseup][riseup], requires an invitation, and donations for its operation, and
|
||||||
|
+ [Other services][other] that respect freedom.
|
||||||
|
|
||||||
|
For the bad treatment received and the little professionalism of OpenMailBox,
|
||||||
|
I can only say: it has been a pleasure, but goodbye!
|
||||||
|
|
||||||
|
[fsite]: https://www.freakspot.net/como-explota-Google-con-CAPTCHAs
|
||||||
|
[gnu-philosophy]: https://www.gnu.org/philosophy/who-does-that-server-really-serve.html
|
||||||
|
[posteo]: https://posteo.de/
|
||||||
|
[riseup]: https://riseup.net/
|
||||||
|
[other]: https://www.fsf.org/resources/webmail-systems
|
@ -2,6 +2,7 @@ Author: Jesús E.
|
|||||||
Category: Opinión
|
Category: Opinión
|
||||||
Date: 2017-08-14 11:09
|
Date: 2017-08-14 11:09
|
||||||
Image: 2017/08/openmailbox.png
|
Image: 2017/08/openmailbox.png
|
||||||
|
Lang: es
|
||||||
Slug: sayonara-openmailbox
|
Slug: sayonara-openmailbox
|
||||||
Tags: openmailbox, mail
|
Tags: openmailbox, mail
|
||||||
Title: Sayonara OpenMailBox
|
Title: Sayonara OpenMailBox
|
||||||
|
Loading…
x
Reference in New Issue
Block a user