antiX-23-beta1-runit-full (64bit) for testing

[Member marcelocripe]

Helpful

Up

0

::

No space available on device

I used all the default settings offered in the frugal installation process. The 80GB IDE hard disk being used for full frugal persistence is no longer able to be used for installing an operating system because the MBR of this hard disk is damaged.

Could it be that the default values offered in the frugal installation process are no longer appropriate for the latest antiX?

I booted with LiveUSB and can look at the folders “antiX-Frugal-6.1.18-antiX.1-amd64-smp” which is 19.6 GB and 1025 files, “Live-usb-storage” which is 60 KB and 5 files, “lost+found” which is 16 KB and 1 file and “swap-file” which is 4 GB.

I’m going to redo the frugal installation and set a size of 60GB to help with testing this ISO.

Dear Marcelo (and all): one of the reasons antiX-Updater always shows the terminal, even in the “Automatic Mode” is so users have an easy way to see what the system is doing and also reading the reason for any error.

It’s always great to be able to see what’s going on, even with the “Auto Update” option.

Now I was curious, how did you find out that it could be a lack of space?

I’m please to see that your revised localization works perfectly 🙂

I think you misunderstood, I revised the line breaks after seeing the initial translation work which will not display correctly on small screens due to the lack of line breaks. That is, I needed to see the initial translation work to be able to adjust the texts in Transifex. I hope that today’s revised text can be re-downloaded and used in a new “yad-updater” program package.

Sir Brian, I thank you for these commands. I’ll save them in my notes for future use.

– – – – –

No space available on device

Eu utilizei todas as configurações padrões oferecidas no processo de instalação frugal. O disco rígido IDE de 80 GB que está sendo utilizado para a persistência frugal total não é mais capaz de ser utilizado para a instalação de um sistema operacional, porque a MBR deste disco rígido está danificada.

Será que os valores padrões oferecidos no processo de instalação frugal não são mais apropriados para o antiX mais recente?

Eu iniciei com o LiveUSB e posso olhar as pastas “antiX-Frugal-6.1.18-antiX.1-amd64-smp” que possui 19,6 GB e 1025 arquivos, “Live-usb-storage” que possui 60 KB e 5 arquivos, “lost+found” que possui 16 KB e 1 arquivo e o “swap-file” que possui 4 GB.

Eu vou refazer a instalação frugal e definir um tamanho de 60 GB para ajudar com os testes desta ISO.

Dear Marcelo (and all): one of the reasons antiX-Updater always shows the terminal, even in the “Automatic Mode” is so users have an easy way to see what the system is doing and also reading the reason for any error.

É sempre muito bom podermos ver o que está acontecendo, mesmo com a opção “Atualização Automática”.

Agora eu fiquei curioso, como vocês descobriram que poderia ser falta de espaço?

I’m please to see that your revised localization works perfectly 🙂

Eu acho que você não entendeu, eu revisei as quebras de linhas após ver funcionado a tradução inicial que não será exibida corretamente em telas pequenas, devido a falta das quebras de linhas. Ou seja, eu precisei ver a tradução inicial funcionado para conseguir ajustar os textos no Transifex. Eu espero que o texto revisado no dia de hoje possa ser baixado novamente e ser utilizado em um novo pacote do programa “yad-updater”.

Senhor Brian, eu agradeço por estes comandos. Eu vou guardá-los em minhas anotações para uso futuro.

[Moderator Brian Masinick]

Helpful

Up

0

::

After some “early questions”, I’ve been using antiX 22 and antiX 23 Beta 1 at least for a couple hours each day.
Regarding antiX-23-beta1-runit-full (64bit) I’ve not found any entries in the package installer the past two days
that failed to respond. I’ll try some more.

Does anyone have a list they are compiling?
I have invoked the runit service manager; no issues. I will try adding a few services at some
point, though I’ve not done that YET.

I’ve installed and removed a couple of Web browsers; no problems.
I’ve also been using my own private browser builds and they
continued to work when I copied them here. That may be unimportant
to others, but it matters a lot to me, and antiX 23 passes that
check with excellence.

I’ve been using antiX Updater and antiX autoremove every day
and they have been working great, zero issues that I’ve spotted.

I use Backlight Brightness every time I use the system and I’m
happy that is has been working properly on both antiX 22 and 23
each day.

More to come. For me, the bottom line has been that I can use
our Beta test or our every day system and there are no
appreciable changes in the behavior of all regular tools that I use.

--
Brian Masinick

[Member Robin]

Helpful

Up

0

::

PPC wrote:

Simply not randomly replacing a single quote with a double quote, inside a variable would do. I only know a little of bash and yad – I will not learn a programming language just to please a translator that thinks it’s a good idea to replace the special characters used on the text.

That’s all not a problem when using the UTF8 typographical equivalents of the ASCII code characters which refuse to work. You have to accept that translators usually won’t understand the complexity of different quotings in script code (which drive me nuts sometimes myself). So it is a good idea not to use the ASCII representations in the original strings already, even when possible by some masking, but the typographical UTF-8 equivalents there also. Then the translator can easily see, whether a special character is part of a code fragment left in the translatable string for sake of not breaking a sentence into untranslatable chunks, or whether (then you are not to change it under any circumstances), or whether it is part of translatable text and can be replaced by country specific quoting style (use of brackets, dashes etc.).

PPC wrote:

I had scripts localized to other alphabets, like Russian Cyrillic, and no one every complained those scripts were broken by the localization- this was the very first time. Why? Once again, thanks to the fr localization, it now has double quotes inside a yad text. Yad seems not to like that.

So this doesn’t mean not to avoid the creative replacement of special characters at all, you only need to know what is allowed and what is not. I have not looked into the resource, I do hope there have been some developers notes present making translators aware of the pitfalls. We have seen exactly the very issue with the ASCII style single and double quotes and the Backtick that many times now, I believe the pieces of information about how to resolve it properly in translation should get pinned somewhere in the translators section of the board.

PPC wrote:

Nothing I can do about that, except suggesting, once again: stick as much as possible to the original text, when localizing.

Exactly this wording made your original intention misunderstood, even by me, who knows very well the pitfalls with ASCII quoting and its masquing. Now after you having explained it detailed, I understand you don’t mean to stick to the original text as your wording suggests (which is generally a very bad idea in translation), but it’s all about these ASCII characters…

PPC wrote:

Use special characters (and I do not meant accented characters or non latin alphabet, or pictugrams, hell, even cunniform writing!!!), like quotes or double quotes, etc, only when they are on the original text!

As said above, it would be better to replace them from the beginning in the original strings already by the respective typographical UTF-8 equivalents to avoid all the trouble. Then you can tell the translators simply: keep all ASCII quotings etc., while you can freely replace all UTF8 typographic quoting characters.

So long
Robin

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

[Moderator Brian Masinick]

Helpful

Up

0

::

Some of the resource management tools DO show different values. It’s something that has been observed before and discussed before.
It’s pretty clear that they’re not measuring exactly the same thing. For instance, I just asked free -h and it reported 1.8Gi used.
Seconds later I ran sudo ps_mem.py, a Python program that lists processes, their Private Memory used, Shared Memory used and RAM
used, which the program describes as the sum of the two values. It lists them for major programs and adds them up.

This does NOT represent ALL processes, but it does concisely list most major programs. It came up with 1.2 GiB, of which
1.0 GiB –> firefox-esr, (930.2 MiB + 140.9 MiB = 1.0 GiB).

If that’s not enough, I turned on Conky to “get it’s ‘opinion’ on resources used.
It states that I’m somehow using 66.9 GiB/78.2 GiB HD, 1.39 GiB/7.67GiB RAM, and 2% CPU.
Those might be the correct values of something, but I suspect if I run top or htop I’ll find yet a different set of numbers.
It all depends on exactly what each tool is measuring, and it’s usually something different!

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

Sure enough, top “thinks” that between 1800-1900 MB of memory is used; htop says 1.18G – notice different measurements too – GB, G, MB, GiB!

--
Brian Masinick

[Member Robin]

Helpful

Up

0

::

Dear Wallon,

Wallon wrote:

If we could have a list of allowed or forbidden characters, it would be easier for all translators. We could avoid some bugs.

Yes, this is a good idea, but a demanding task to create such a list. If will not be identical for all resources, since it depends on the programming or scripting language as well as on the position of a translatable string in the source code. So what will be fine for one resource, will horribly fail on another. This will get a pretty long list with many ifs, ands and buts.

Wallon wrote:

I will change the translation in Transifex right away and use the US quotes.

Not the very best idea. Just make sure these are true quotes and not part of coding, then you can use the typographic replacement characters in many cases:

The default keyboard double quoting ASCII 34 (or 22 hex) = U+0022 Unicode

Instead of  "  U+0022  use  «  U+00AB (in French guillemotleft, in German this is guillemotright)
Instead of  "  U+0022  use  »  U+00BB (in French guillemotright, in German this is guillemotleft)
Instead of  "  U+0022  use  “  U+201C (left double quotation mark)
Instead of  "  U+0022  use  “  U+201D (right double quotation mark)
Instead of  "  U+0022  use  „  U+201E (low double quotation mark)

The default keyboard single quoting ASCII 39 (or 27 hex) = U+0027 Unicode

Instead of  '  U+0027  use  ’  U+2019  (right single quotation mark)

The default keyboard less than ASCII 60 (or 3C hex) = U+002C Unicode

Instead of  <  U+002C  use  ‹  U+2039 single left-pointing angle quotation mark

The default keyboard greater than ASCII 62 (or 3E hex) = U+002 Unicode

Instead of  >  U+002E  use  ›  U+203A single right-pointing angle quotation mark

The default keyboard backtick/grave ASCII 96 (or 60 hex) = U+0060 Unicode

Instead of  ˋ  U+0060 use  ˋ  U+02CB

But always only if the character is NOT part of code fragments within translatable strings like <i>…</i> etc. In these cases you must keep the original characters by all means, otherwise it most likely will break code and stop the program or code working in translation the same way as the functional special characters do when used within translated strings without masking them (which can be quite tricky if you really want to do it that way instead of using the typographical replacement technique).

Please look other possible replacements up from one of the tables listed here: https://fr.wikipedia.org/wiki/Table_des_caract%C3%A8res_Unicode

All Unicode characters can be entered in antiX (like in most Linux) by pressing the Ctrl+Shift+u keys the same time, then let them go. You’ll see an underlined small letter u. Then key in the key value, e.g. 201e and press Ctrl+Shift (without u) again (simply pressing enter might also work) to close the unicode input mode. Then you’ll have the proper character.

Many greetings
Robin

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

[Moderator caprea]

Helpful

Up

1

::

app-select has a new feature to add an icon to the desktop,which does not work for me here, or do I miss something?

Attachments:

1. 

   screenshot-9.jpg
   

[Member vance]

Helpful

Up

0

::

I installed AntiX 23 beta1 on a Lenovo Thinkcentre 6234A1U. The install goes fine. I select custom for the partition so I can add a swap partition but other than that everything is standard with a username & password needed to login. When I boot up on the hard drive it freezes on the login screen. This was using the modern kernel but I try booting up again just to make sure it wasn’t a fluke problem to no avail. I can boot up on the legacy kernel though!! When I boot off the jump drive the modern kernel works fine. What should my troubleshooting steps be?
Thanks!
Vance

[Member vance]

Helpful

Up

0

::

It turned out the problem was the USB port. I have to unplug the keyboard & mouse & then plug them back in to get them to work. Is this a bug?
Thanks!
Vance

[Member Wallon]

Helpful

Up

0

::

Hello to all,

On my 2 computers (installation in English and installation in French), I have this message “dbind-Warning…” when I do the [sudo upgrade] command.

Best regards,
Wallon

Updating Slimski /etc/slimski.local.conf
desktop-session-update-wm-menus: Writing file: /usr/share/desktop-session/wm-menus/fluxbox-wm-menu
desktop-session-update-wm-menus: Writing file: /usr/share/desktop-session/wm-menus/icewm-wm-menu
desktop-session-update-wm-menus: Writing file: /usr/share/desktop-session/wm-menus/jwm-wm-menu
desktop-session-update-wm-menus: Writing file: /usr/share/desktop-session/wm-menus/RAW-wm-menu

(desktop-menu:9143): dbind-WARNING **: 11:27:01.497: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Writing Menu: fluxbox
Writing Menu: icewm
Writing Menu: jwm

[Member PPC]

Helpful

Up

0

::

I get the same warning as Wallon. Above that, there’s:

cryptsetup: Error: Could not resolve device overlay
cryptsetup: Warning: Could not determine root device.

Is that serious?

P.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Both messages are harmless.

AT-SPI: Error can be fixed by installing at-spi2-core but that brings in libelogind0
cryptsetup: Error: can be fixed by purging cryptsetup-initramfs

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator Brian Masinick]

Helpful

Up

0

::

Now I’m here with my HP 5000 series s5747c desktop computer, an old 2010 relic that my brother in law used long ago.
I’m actually trying the legacy kernel and it works fine here; I will have to try the V6.1.18 kernel too, since this one works well!

inxi -b
System:
  Host: antix1 Kernel: 5.10.173-antix.1-amd64-smp arch: x86_64 bits: 64
    Desktop: IceWM v: 3.3.2 Distro: antiX-23-beta1-runit_x64-full Grup Yorum 21
    March 2023
Machine:
  Type: Desktop System: Hewlett-Packard product: s5747c v: N/A
    serial: <superuser required>
  Mobo: PEGATRON model: 2A6C v: 5.00 serial: <superuser required>
    BIOS: American Megatrends v: 6.01 date: 09/29/2010
CPU:
  Info: dual core AMD Athlon II X2 255 [MCP] speed (MHz): avg: 3114
Graphics:
  Device-1: NVIDIA C61 [GeForce 6150SE nForce 430] driver: nvidiafb v: kernel
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: fbdev,nouveau
    unloaded: modesetting,vesa dri: swrast gpu: nvidiafb
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.5 Mesa 22.3.3 renderer: llvmpipe (LLVM 15.0.6 128 bits)
Network:
  Device-1: NVIDIA MCP61 Ethernet type: network bridge driver: forcedeth
  Device-2: Ralink RT2790 Wireless 802.11n 1T/2R PCIe driver: rt2800pci
Drives:
  Local Storage: total: 755.94 GiB used: 1.57 GiB (0.2%)
Info:
  Processes: 127 Uptime: 41m Memory: 3.58 GiB used: 1.1 GiB (30.8%)
  Shell: Bash inxi: 3.3.25

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

BACK with the NEWER kernel; happy to see that BOTH work on this 2010 system!

inxi -b
System:
  Host: antix1 Kernel: 6.1.18-antix.1-amd64-smp arch: x86_64 bits: 64
    Desktop: IceWM v: 3.3.2 Distro: antiX-23-beta1-runit_x64-full Grup Yorum 21
    March 2023
Machine:
  Type: Desktop System: Hewlett-Packard product: s5747c v: N/A
    serial: <superuser required>
  Mobo: PEGATRON model: 2A6C v: 5.00 serial: <superuser required>
    BIOS: American Megatrends v: 6.01 date: 09/29/2010
CPU:
  Info: dual core AMD Athlon II X2 255 [MCP] speed (MHz): avg: 3114
Graphics:
  Device-1: NVIDIA C61 [GeForce 6150SE nForce 430] driver: N/A
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: nouveau,vesa
    unloaded: fbdev,modesetting dri: swrast gpu: N/A resolution: 1024x768
  API: OpenGL v: 4.5 Mesa 22.3.3 renderer: llvmpipe (LLVM 15.0.6 128 bits)
Network:
  Device-1: NVIDIA MCP61 Ethernet type: network bridge driver: forcedeth
  Device-2: Ralink RT2790 Wireless 802.11n 1T/2R PCIe driver: rt2800pci
Drives:
  Local Storage: total: 755.94 GiB used: 1.57 GiB (0.2%)
Info:
  Processes: 123 Uptime: 4m Memory: 3.58 GiB used: 430.7 MiB (11.7%)
  Shell: Bash inxi: 3.3.25

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

1

::

I finally located my first two issues – both browsers.

I installed two of the three variations of Waterfox, the Waterfox Current and the Waterfox G3. Both installed but neither worked properly; they’d keep rejecting pages with some kind of Gah! failure, offer to repeat, and do the same. I tried two, and also reinstalled; right now they don’t work on the HP 5000 desktop. Now that I’ve found an issue, I’ll try them on other hardware.

I did successfully install Vivaldi and I’m using it on the HP s5747c to write this message.

--
Brian Masinick

[Author]

Posts