Search Results for 'ppa'

[Member marcelocripe]

Skiddo,

As a monoglot, I will defer to your expertise. I have redacted that apparent bit of misinformation.

You know that I am also a monoglot and that we are still overcoming the difficulties of communication between two monoglots.

You and Robin have technical knowledge about antiX that I don’t have. You also know that I am learning from everyone here on the forum … I thank you for your teachings and for all your patience in communicating with me.

I endeavor to write in as much detail as possible, even when the information appears to be redundant or may be implied. Internet translators are unable to do all the work, I need to understand the translation of the words and then build the meaning of the sentence in my language, sometimes I can understand the texts and other times I cannot. Therefore, I ask you to write your language in the most cultured way possible, without abbreviations so that I can try to understand you better. I hope that you will be able to understand my words translated by the translator well and that you will also understand that my intention is that we can communicate better each day.

I downloaded the package “packageinstaller_21.3.03 ~ ski_amd64.deb”
https://gitlab.com/skidoo/packageinstaller/-/blob/master/packageinstaller_21.3.03~ski_amd64.deb

antix1 @ antix1: ~ / Downloads
$ sudo dpkg -i packageinstaller_21.3.03_ski_amd64.deb
(Reading database ... 186443 files and directories currently installed.)
Preparing to unpack packageinstaller_21.3.03_ski_amd64.deb ...
Unzipping packageinstaller (21.3.03 ~ ski) on (0.2.6) ...
dpkg: dependency problems prevent packageinstaller configuration:
 packageinstaller depends on aptitude; although:
  Aptitude package is not installed.

dpkg: error while processing the packageinstaller package (--install):
 dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
 packageinstaller
antix1 @ antix1: ~ / Downloads

As the information is displayed almost all in “pt” or “pt-BR”, I was able to understand the need for “aptitude”. Using Synapitc, I installed the “aptitude” package with its dependencies. It was possible to install the package “packageinstaller_21.3.03_ski_amd64.deb”.

antix1 @ antix1: ~ / Downloads
$ sudo dpkg -i packageinstaller_21.3.03_ski_amd64.deb
(Reading database ... 186678 files and directories currently installed.)
Preparing to unpack packageinstaller_21.3.03_ski_amd64.deb ...
Unzipping packageinstaller (21.3.03 ~ ski) on (21.3.03 ~ ski) ...
Configuring packageinstaller (21.3.03 ~ ski) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
antix1 @ antix1: ~ / Downloads

I was able to capture the screens of the new version of the “Package Installer”, unfortunately it crashed during the installation process of the Firefox localization package and so I was unable to capture the completion screen of the installation process. Almost all phrases and words are translated, the text displayed is in the language “pt” and mixed in the language “pt-BR”. I believe that it will be necessary to search for updated texts on the transifex website to correct this.

https://ibb.co/NrB9z1x
https://ibb.co/4KsX5qd
https://ibb.co/7xDbJHr
https://ibb.co/9gvq2f5
https://ibb.co/rZgcDSG
https://ibb.co/tm57mJ8
https://ibb.co/SJNty6N

marcelocripe
(Original text in Brazilian Portuguese)

———-

Skiddo,

As a monoglot, I will defer to your expertise. I have redacted that apparent bit of misinformation.

Você sabe que eu também sou um monoglota e que mesmo assim estamos superando as dificuldades de comunicação entre dois monoglotas.

Você e o Robin possuem conhecimentos técnicos sobre o antiX que eu não possuo. Você sabe também que estou aprendendo com todas as pessoas daqui do fórum … Eu agradeço a você por seus ensinamentos e por toda a sua paciência em se comunicar comigo.

Eu me esforço para escrever com máximo de detalhes possíveis, mesmo quando a informação parece ser redundante ou que possa ser subentendida. Os tradutores da internet não conseguem fazer todo o trabalho, eu preciso compreender a tradução das palavras para depois construir o sentido da frase em meu idioma, às vezes eu consigo compreender os textos e outras vezes não. Diante disso, eu peço a você que escreva o seu idioma da forma mais culta possível, sem abreviações para que eu possa tentar compreender melhor você. Eu espero que você consiga compreender bem as minhas palavras traduzidas pelo tradutor e que compreenda ainda que a minha intenção é que possamos nos comunicar cada dia melhor.

Eu baixei o pacote “packageinstaller_21.3.03~ski_amd64.deb”
https://gitlab.com/skidoo/packageinstaller/-/blob/master/packageinstaller_21.3.03~ski_amd64.deb

antix1@antix1:~/Downloads
$ sudo dpkg -i packageinstaller_21.3.03_ski_amd64.deb
(Lendo banco de dados ... 186443 ficheiros e directórios actualmente instalados.)
A preparar para desempacotar packageinstaller_21.3.03_ski_amd64.deb ...
A descompactar packageinstaller (21.3.03~ski) sobre (0.2.6) ...
dpkg: problemas com dependências impedem a configuração de packageinstaller:
 packageinstaller depende de aptitude; porém:
  Pacote aptitude não está instalado.

dpkg: erro ao processar o pacote packageinstaller (--install):
 problemas de dependência - deixando desconfigurado
A processar 'triggers' para desktop-file-utils (0.23-4) ...
A processar 'triggers' para mime-support (3.62) ...
A processar 'triggers' para hicolor-icon-theme (0.17-2) ...
Erros foram encontrados durante o processamento de:
 packageinstaller
antix1@antix1:~/Downloads

Como as informações são exibidas quase todas em “pt” ou “pt-BR”, eu consegui entender a necessidade do “aptitude”. Utilizando o Synapitc, instalei o pacote “aptitude” com as suas dependências. Foi possível instalar o pacote “packageinstaller_21.3.03_ski_amd64.deb”.

antix1@antix1:~/Downloads
$ sudo dpkg -i packageinstaller_21.3.03_ski_amd64.deb
(Lendo banco de dados ... 186678 ficheiros e directórios actualmente instalados.)
A preparar para desempacotar packageinstaller_21.3.03_ski_amd64.deb ...
A descompactar packageinstaller (21.3.03~ski) sobre (21.3.03~ski) ...
Configurando packageinstaller (21.3.03~ski) ...
A processar 'triggers' para desktop-file-utils (0.23-4) ...
A processar 'triggers' para mime-support (3.62) ...
A processar 'triggers' para hicolor-icon-theme (0.17-2) ...
antix1@antix1:~/Downloads

Eu consegui capturar as telas da nova versão do “Package Installer”, infelizmente ele travou durante o processo de instalação do pacote de localização do Firefox e por isso eu não consegui capturar a tela de conclusão do processo de instalação. Quase todas as frases e palavras estão traduzidas, os texto exibidos estão em idioma “pt” e misturados em idioma “pt-BR”. Eu acredito que será preciso buscar os textos atualizados no site transifex para corrigir isso.

https://ibb.co/NrB9z1x
https://ibb.co/4KsX5qd
https://ibb.co/7xDbJHr
https://ibb.co/9gvq2f5
https://ibb.co/rZgcDSG
https://ibb.co/tm57mJ8
https://ibb.co/SJNty6N 

marcelocripe
(Texto original em idioma Português do Brasil)

[Anonymous]

Verify and test this yourself, please.

As a monoglot, I will defer to your expertise. I have redacted that apparent bit of misinformation.

Somebody else will have to step in.

Aye.

I’ve had this issue with both antiX-19 64-bit and antiX-17 64-bit. I can’t see the login entry fields when I have two monitors.

I managed to setup my two monitors to work with antiX and my IceWM windows manager config files. I used arandr and saved the settings and added it to the IceWM startup config file. But I can’t figure out how to get Slim to show the login entry box in a place where I can see it.

At one point I could see the sign in box all the way to the right of one of the screens but I could only see a sliver of the entry box. In my current setup I can not see the sign in entry box at all. I can type my username and password blindly and hit enter and I am logged in.

I figured out that I could set auto login and bypass the sign in entry box on the Slim display manager screen. But I would prefer to see my login/sign in entry fields and type in my username and password.

I have another antiX box that I am using to test the latest “testing” version of antiX-19 32-bit. On that box the sign in fields are in the upper left of the screen. How do I make that happen? The standard antiX setup has Slim showing the entry fields in the center of the screen. This is apparently what is causing the trouble when I have two monitors.

I looked around in the configuration files but I cannot figure out where this setting may be to place the sign in fields in the upper left corner, or in the center, or wherever I want. Can someone point me in the right direction for this setting? Is it in the slim.conf file and I am missing it?

Thanks for any tips you can share. My inxi -Fxz follows.
Seaken64

inxi -Fxzr
System:
  Host: antix17464 Kernel: 4.9.160-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
  v: 6.3.0 Desktop: IceWM 1.4.2 
  Distro: antiX-17.4.1_x64-full Helen Keller 28 March 2019 
  base: Debian GNU/Linux 9 (stretch) 
Machine:
  Type: Desktop System: Dell product: Dimension E521 v: N/A serial: <filter> 
  Mobo: Dell model: N/A serial: <filter> BIOS: Dell v: 1.1.6 date: 04/07/2007 
CPU:
  Topology: Dual Core model: AMD Athlon 64 X2 3600+ bits: 64 type: MCP arch: K8 rev.F+ 
  rev: 1 L2 cache: 1024 KiB 
  flags: lm nx pae sse sse2 sse3 svm bogomips: 7215 
  Speed: 1800 MHz min/max: 1000/1900 MHz Core speeds (MHz): 1: 1800 2: 1800 
Graphics:
  Device-1: NVIDIA NV43 [GeForce 6600] driver: nouveau v: kernel bus ID: 03:00.0 
  Display: server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa 
  resolution: 1360x768~60Hz, 1280x1024~60Hz 
  OpenGL: renderer: Gallium 0.4 on NV43 v: 2.1 Mesa 13.0.6 direct render: Yes 
Audio:
  Device-1: NVIDIA MCP51 High Definition Audio vendor: Dell driver: snd_hda_intel 
  v: kernel bus ID: 00:10.1 
  Sound Server: ALSA v: k4.9.160-antix.1-amd64-smp 
Network:
  Device-1: Broadcom Limited BCM4401-B0 100Base-TX vendor: Dell driver: b44 v: 2.0 
  port: cc00 bus ID: 04:07.0 
  IF-ID-1: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 232.83 GiB used: 4.52 GiB (1.9%) 
  ID-1: /dev/sda vendor: Samsung model: HE253GJ size: 232.83 GiB 
Partition:
  ID-1: / size: 38.20 GiB used: 3.67 GiB (9.6%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 76.40 GiB used: 867.0 MiB (1.1%) fs: ext4 dev: /dev/sda2 
  ID-3: swap-1 size: 4.00 GiB used: 456 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 60.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/stretch stretch main nosystemd nonfree
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
  2: deb http://security.debian.org/ stretch/updates main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/onion.list 
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 151 Uptime: 7h 08m Memory: 1.96 GiB used: 766.8 MiB (38.3%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.36 

• This topic was modified 2 years, 2 months ago by seaken64.

[Member DaveW]

In order to maintain one operating system on my 3 computers, I’m running 32 bit AntiX 17 on all of them.
I suppose the only one that needs 32 bit is the Asus eeepc 900. The Dell D620 and a formerly Windows 7 Asus laptop could run the 64 bit. Awhile back, I tried to upgrade the D620 from AntiX 17 to 19, but ran into internet connectivity problems, and, to avoid the headache, went back to what was working well for me (v. 17).

Most of the time, I am using Kernel 4.9.240. It is very stable on all machines.

However, I occasionally use Kernel 5.8.16, in order to access a Wireguard vpn service. I have seen some instability with the 5.x.xx series Kernels on 32 bit OS system. But typically, it is stable for the first two or three restarts with that kernel. After the fourth restart, the session may lock up for no apparent reason. But a restart with 4.9.xxx fixes that (then, the 5.x.xx kernel will go for another 2 or 3 restarts).

In any case, the built-in Wireguard capability is my only reason for using 5.x.xx kernels on 32 bit system.

Thanks for asking for feedback.

[Member marcelocripe]

Hello Robin,

Will the file I added in the folder “/usr/share/locale/pt_BR/LC_MESSAGES” be overwritten in the next antiX update by another file in English?

The answer to my question came in the update that occurred last week, the “unplugdrive” program was shown again in English.

anticapitalista wrote:
About translations and antiX (I’m not interested in the translated MX apps).
transifex is where we want all our native apps to be translated so translators will have to use that platform.Otherwise it would be a nightmare trying to coordinate across git/transifex/personal emails etc.

I asked the MX Linux forum to unblock areas that are blocked from transifex website, the richb administrator’s response was this:

The current system has worked well for us and we see no compelling reason to change it, thanks.

Apparently, what is working well, but with the wrong texts, will continue to be wrong. Even though I asked MX Linux administrators to read this topic, in order to become aware that the actions carried out in the transifex interfere in both distributions. Unfortunately they did not want to discuss the matter and still blocked the topic. Even insisting on a private message, the conversation does not evolve. Who knows if other people request the unblocking of the blocked areas, MX Linux administrators can pay attention to the subjects covered in this topic.

As long as antiX administrators do not talk to MX Linux administrators, I believe that the transifex areas in different languages ​​will remain blocked, preventing others from making the necessary corrections.

I asked the reviewers zeh and hugok to keep the pt-BR area unlocked, me and other colleagues are working on the constant improvement of the translations of antiX and MX Linux for the Brazilian Portuguese language.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Robin,

O arquivo que eu adicionei na pasta “/usr/share/locale/pt_BR/LC_MESSAGES” será sobrescrito na próxima atualização do antiX por outro arquivo em idioma Inglês?

A resposta da minha pergunta veio na atualização que ocorreu na semana passada, o programa “unplugdrive” voltou a ser exibido em idioma inglês.

anticapitalista wrote:
About translations and antiX (I’m not interested in the translated MX apps).
transifex is where we want all our native apps to be translated so translators will have to use that platform.Otherwise it would be a nightmare trying to coordinate across git/transifex/personal emails etc.

Eu pedi no fórum do MX Linux que fosse feito o desbloqueio das áreas que estão bloqueadas do site transifex, a resposta do administrador richb foi esta:

Tradução do tradutor da internet:
O sistema atual tem funcionado bem para nós e não vemos nenhuma razão convincente para alterá-lo, obrigado.

Ao que parece, o que está funcionando bem, mas com os textos errados, irão continuar errados. Mesmo eu pedindo para os administradores do MX Linux lerem este tópico, afim de tomarem ciência de que as ações feitas no transifex interferem em ambas as distribuições. Infelizmente não quiseram discutir sobre o assunto e ainda bloquearam o tópico. Mesmo insistindo com mensagem particular, a conversa não evolui. Quem sabe se outras pessoas solicitarem o desbloqueio das áreas bloqueadas, os administradores do MX Linux possam prestar atenção nos assuntos tratados neste tópico.
 
Enquanto os administradores do antiX não conversarem com os administradores do MX Linux, eu acredito que as áreas do transifex em diversos idiomas permanecerão bloqueadas, impedindo que outras pessoas façam as correções necessárias.

Eu pedi aos revisores zeh e o hugok para manterem a área pt-BR desbloqueada, eu e outros colegas estamos trabalhando na melhoria constante das traduções do antiX e do MX Linux para idioma Português do Brasil.

marcelocripe
(Texto original em idioma Português do Brasil)

[Member LarryDC]

anticapitalista wrote:

Read what I posted.

apt purge ONLY libbsd0:i386 and libsndfile1:i386

Are you deliberately misreading my instructions?

No, not5 at all. That’s all I did but I mistakenly only “remove” not “purge”.

The rest was all with “-s” simulating. Just in case it revealed anything useful… apparently not.

As requested:

# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  getty-run
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  init runit-init
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  init runit-init (due to init)
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 73.7 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'

"ουκ εν τω πολλώ το ευ" Aristotle
i5 8GB RAM, 3 HDs mainly JWM.
Linux User #305687 (Antix runit, Crowz, Michaels-Duvuan, Absolute, Sparky, Endeavouros)
Pawtucket RI EE.UU.

[Member Wallon]

Dear Xecure, Dear Skidoo

Your explanations are highly technical. I find it difficult to follow you. I’m only a simple user. I’m not Linus Torvalds who uses AMD Threadripper 3970x-based processor.

I’ve done something simpler.
I took my live USB key (with the installer). I choose F2 Language (->French BE). If I check “locale” in Terminal, all variables are on fr_BE. On my first screen, I’m going to search for spaceFM in the applications (so, without changing my desktop). SpaceFM is badly translated in French. I use the other file manager (Rox) to delete ~/.config/spacefm directory.
I go back in the applications to launch spaceFM and magic, it is well translated.
So, I didn’t use command lines in a Terminal.
I hope this can help you.

I don’t like to do a lot of tests on my installed version anymore because I have difficulties to restore my Antix with Timeshift. This is new in Antix and MX Linux, I have GTK warnings, rsync syntax of Linux files not compatible … when I make a backup. I can’t find the Linux directory or file that is not compatible with the messages I receive. Apparently it’s not related to Timeshift.
I don’t use snapshot anymore because I can’t retrieve my password, my fstab, AppImage… when I reinstall.

Do I need to do another test to better understand the origin of the problem?

Thank you very much for your support.

Best regards,
Wallon
Antix 19.3 Full

• This reply was modified 2 years, 2 months ago by Wallon.

[Member eric]

Can s6/66 work on 32 bit?

It should work whatever the architecture. Also, it can be build with GCC,clang or musl. It should work on BSD and Solaris but never tested yet.

sulogin(): 84): warning : unable to wait for : 66-scandir

You seem to have a PATH definition problem here. Note: if you get a sulogin that means that the issue occur before launching any services even the main svscan responsible of the PID1. So the issue is on the 66-boot program itself. In your case the PATH of the 66-scandir cannot be found. The path is define at /etc/66/init.conf file but obviously it also depends of how the software was build. See below.

Debian has skalibs, execlines and s6 in their repos.

Apparently you use the skalibs, execline and s6 directly from debian repo which is a very bad idea because debian dev do not compile and install the skarnet softwares correctly in particular for execline. As far as i know, the execline package is completely broken. Laurent Bercot struggled a lot with debian dev about this and they do not install it correctly for obscure reason. At the last new of what i know about this, they say that execline is not a POSIX program(i never see a programs which respect the POSIX standard as many as skarnet programs) whereas systemd is it lol.

So, i advise you to build by your own the skarnet package and to define a correct path at build time. Also, you need to respect a good order to get a correct build.
the order is:
1) skalibs
2) execline
3) s6
4) s6-rc, s6-portable-utils, s6-linux-utils
5) oblibs
6) 66, 66-tools

The s6-portable-utils and s6-linux-utils is not strictly mandatory for 66 and 66-tools but its needed for the boot@-66serv service.

When you build it with the script that i posted all goes well. So yeah, debian bullshit…

• This reply was modified 2 years, 2 months ago by eric.
• This reply was modified 2 years, 2 months ago by eric.

[Anonymous]

I just don’t know if storing in different folders generates some kind of rework for the development team.

Your apparent intent is to produce “zipfiles”. That detail (expecting others to consume zipfiles) and your apparent insistence to adhere to that detail is what would “generate unnecessary rework”. For an single contributed script (or single contributed collection of scripts+resources), the extra chore of dealing with intermediary zipfiles may be, or might not be, feasible.

antiX programs are delivered via, installed via, .deb files
and the content to be delivered via the .deb files is maintained, is “collaborated”, via git project source code repositories. You seem to be asking collaborators and antiX developers to, instead, consume zipfiles which you intend to provide ~~ forcing someone else to extract from zipfile and add it to the appropriate git project source code repository. (just emphasizing/explaining here, not scolding)

Click this link and notice that many of the existing scripts in use which might be described as “community scripts” are (already) provided by the “antix-goodies” .deb package
https://gitlab.com/antiX-Linux/antix-goodies/-/tree/master/bin

Click this link and notice that, via the installation manifest, a debfile can install various content to various (multiple) specified directories
https://gitlab.com/antiX-Linux/antix-goodies/-/blob/master/debian/install
When collaborating, and intending to have your content (scripts//icons//.desktop//.mo) installed via debfile, you really do not need to “worry about” the detail of what is the appropriate installed locations ~~ you can relegate that detail, that decision, to the person who is acting as the “package maintainer” for the debfile targeted by your content. Additionally (as an additional consideration), the person maintaining the gui & cli ControlCenter packages can add an entry (button, label) if we intend the new script to be accessible via ControlCenter.

Placement to / opt… installed executables are accessible to all users …
Does the same rule apply to scripts if they are placed in the “/usr/local/bin/” folder?

As sysadmins, as package maintainers… we are responsible for making the rules. If the existing rules do not suit us (users on our systems), we modify them. The remark stating “/opt accessible to all users” just describes the convention(al) case. Any debfile can provide overriding instructions, for instance “install myProgram to /opt/myex AND set its permission so that it is executable only by user accounts which are are members of ‘advancedusers’ group”.

A sysadmin (or a package maintainer) can specify, for each individual executable residing in /usr/local/bin/, a restrictive permission set. You can notice that, on an antiX system, /usr/local/sbin/ exists… but is empty. On another operating system, we might expect this (by convention) to be an installation destination for “executable only by root user, or via elevated permissions” programs. You can also notice (via ‘ls -al /usr/local/bin’ or browsing via file manager) that yes (answering your question “does the same ‘rule’, same as /opt, apply?) all the executables residing here are executable by all usergroups. Perhaps confusingly, many of the executables residing here do refuse to run if they are not launched with elevated permissions, but such restriction is a separate consideration.

[Moderator Brian Masinick]

I did purchase a brand new Chromebook back in November. I had been looking at the Google Pixelbook Go but at $649 for the least expensive model that was too much.
I did put a few hundred into it because I wanted a backlit keyboard and decent performance. I just missed the best deal around Cyber Monday but saved at least $150 over what my model is going for now, so I did shop for a decent deal.

With that exception I have not bought any other new hardware in several years. I have a five year old laptop and three other “cast-off” units I got free.
I’ve been getting my Android phones using Swappa or similar service, looking for good units that are around a year old with at least 1-2 years of software updates available.

Naturally the older the computer hardware happens to be the more likely I have antiX installed; it’s on most of my systems. No commercial software on these computers!

--
Brian Masinick

I’ve been using, for a long time a very nice piece of software that I don’t recall ever mentioning here: cryptomator

What this app does: cryptomator creates a virtual encrypted “volume” that on your local hard drive (for example to protect sensitive data – or your porn stash – in a shared computer) or on a cloud drive.
No one will be able to access your data (not even your file/folder names), unless something like a quantum computer is used to crack your password- if anyone spends those resources on you, you probably are doing some very nasty stuff (or live on a very opressive regime)

This tool is free and opensource, so, go nuts and use their appimage over at https://cryptomator.org/downloads/
(or live dangerously and try to install de .deb file from their PPA: https://launchpad.net/~sebastian-stenzel/+archive/ubuntu/cryptomator/+packages )

The appimage is about 50Mb in size, and even in a a single computer it takes some seconds to load on, but, after that, you do not even notice its running… And your data stays yours alone…
I use this in conjunction with my script to mount cloud drives, but it should work if you use rclone from the cli or rclone-gui to mount your cloud drive.

P.

[Member olsztyn]

marcelocripe wrote:

Does it work? (I have no way to test this process today, I would need to have another pendrive available)

1 Prepare the first bootable USB stick with a program that works on Windows and that works on computer startup.
2 Boot the computer with the first bootable flash drive.
3 After antiX starts, connect the second USB stick to be prepared with Live USB Maker.
4 Open the Live USB Maker program, select the second flash drive, locate the antiX ISO that was downloaded in Windows to prepare the second flash bootable with antiX.
5 Select “Full Mode – Recordable LiveUSB”

This process seems to be very complicated for those who are leaving Windows and are arriving in antiX, especially for those who arrived here due to the possibility of having persistence through the bootable USB stick with antiX.

I am not clear if this Marcello’s question has been answered so please allow me to add my two cents:

1. This process works and I had been using this process in the past.
2. If booting antiX ISO from DVD drive you obviously do not need two USB sticks. After booting from DVD you can create antiX Live USB on the one USB drive you have. As I was using this process some time ago I am not quite sure it is still the case though…

I think this would be the simplest for users not quite versed in Linux tools and crypto speak.

One news to me (apparently I fail to keep current on antiX documentation) is that Live USB Maker is available as appimage, which means you could start it on any Linux instance, even such as typical recovery boot CDs, such as GParted or Parted Magic. In such case either such tools can be booted and Live USB Maker started to create antiX Live on USB stick. The question to resolve however how in practice you address the antiX installation ISO location in such scenario. This in my opinion makes the use of Live USB Maker appimage on another Linux distro more complex than it seems at the first glance…
Just my two cents…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Anonymous]

Hi. I posted a followup here (prior to olsztyn’s post) but it is being held up by the spamfilter. In that post you’ll notice that I’m suggesting how (not via a sticky) the “onboarding” instructions could be improved.

Placed this topic in Kafeino instead of nosing into the ongoing portuguese topic because this is about a broader issue, not a criticism of well-intentioned folks who are attempting to offer help/advice.

The persistence mechanism of other distros that offer liveboot persistence probably is not ill-affected by a read-only boot partition. Mint, Ubuntu, Debian… they employ a separate (writable) partition into which the persisted files are written. People onboarding from those other distros probably cannot fathom why “read-only or not” matters when creating a liveboot antiX pendrive. Apparently even some longtime antiX users ~~ folks who typically do not liveboot, just view the live media as a momentary bridge toward getting an O/S installed-to-disk on a new machine ~~ apparently they fail to consider the significance of this detail.

@rokytnji the wording in the OP intended to acknowkedge that PLoP does indeed have a special place (may be “your friend” in certain circumstances)… but, as you have repeatedly mentioned across the years (here, mx forum, linuxquestions forum) PLoP is sloooooow ~~ “it is like waiting for paint to dry”.

[Member olsztyn]

Xecure wrote:

Yes. It will make a bootable ISO of your current installed system. It will give you the option of including your user information, so the image will be almost identical to the running system (except removing some specific machine configurations, so you can boot the ISO form any/all other computer).
It is even able to snapshot a Live system with any modifications

To add to this excellent overview:
ISO-Snapshot is brilliant in it’s function and unique in Linux world. To my knowledge it is specific to antiX (and to some degree to MX) and not available to any other Linux distro. Nothing else comes close to it in functionality and it is puzzling that other distros can get by without it. Apparently users of other distros are not serious enough about their distros to appreciate such capability of precise backup image of their system.
Their ultimate objective (late in the game as it is) should be a project to retrofit ISO-Snapshot into their distros to add such important function. However nothing like this is being done that I heard of.
This fact alone gives antiX (perhaps to some degree MX too) a significant advantage not yet widely appreciated.
Just my two cents in addition to Xecure’s overview…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Robin]

Hi skidoo,
you are right, I just managed to transfer the merge request. This gitlab page is a nightmare. You can’t find the fundamental functions well-aranged, but have to guess where and what instead. The places seem And the manual presents screenshots which show things in completely different places. Who could guess they differenciate between clone and fork. First I created a clone, simply because there was apparently no other button to create something like a fork, so I presumed it was a slightly divergent translation only. This was the reason I could not chose anticapitalista as target. But now, trying to correct this was even worse. They wouldn’t let me fork, since they told me the path was in use already. No explanation why, I could only guess they meant the other clone. Actually I had to delete all the correction work I had done in git already, and start from scratch with forking. After I had successfully created the first merge request, they wouldn’t let me do the second one. Nowhere was clearly visible, they had put silently the second one into the first already. In my eyes this page is pure chaos, but I’m sure this is only since I’m not a real programmer. I’m obviously trained in a completely different way of structured thinking, so I’ll probably be lost completely on this gitlab page forever. Never seen a confusion like that.

Well, finally I’ve managed it. That’s what counts. I really hope I didn’t produce some unintended flaws into the requests, while struggling with tons of check-boxes and options on the way through, some of which I didn’t even understand the meaning… Please examine carefully whether the script code I intended to upload hasn’t suffered from all this fuss. Really, this page distracts me from the gist of the task.

P.S. Not to forget: Thank you very much for helping me out.

• This reply was modified 2 years, 3 months ago by Robin.

Windows is like a submarine. Open a window and serious problems will start.