User talk:Lahwaacz

From ArchWiki
Jump to: navigation, search

PodCastXDL

About [1] (and [2]) User:Levi0x0x, who should have indeed provided an edit summary, appears to be the developer of the application and the maintainer of the PKGBUILD. I would keep his edit. -- Kynikos (talk) 00:45, 5 July 2014 (UTC)

I know - I've seen also bash-player removed, both from wiki and Github (it seems the repo has been recreated from scratch). PodCastXDL has always been available upstream. -- Lahwaacz (talk) 08:20, 5 July 2014 (UTC)
Didn't he add it to the list one week ago? [3] Maybe he's found some bug and doesn't want people to use it until he fixes it? Anyway I'm not that interested, we can as well see if/how Levi0x0x reacts. -- Kynikos (talk) 04:32, 6 July 2014 (UTC)

bot AUR to Official Repository edit

A recent bot edit (update Pkg/AUR templates) by User:Lahwaacz.bot on the Gitolite page correctly changed the AUR template to Pkg but left the Arch User Repository link

I fixed this, but would it be possible to modify the bot to take this into consideration?

I can imagine that blanket changing AUR links to Official Repository links in any given page could be dangerous - but for common phrasing or possibly word distance it would seem to be relatively safe

Or is there some sort of post-run manual inspection that I am unaware of that handles this situation?

Specifically this edit

From:

{{AUR|gitolite}} is available in the [[Arch User Repository]]

To:

{{Pkg|gitolite}} is available in the [[Arch User Repository]]


Tido.com (talk) 01:50, 1 April 2015 (UTC)

By "word distance" above what I _meant_ was Edit Distance ;)

I was initially thinking of Hamming distance - but apparently that is for strings of equal length.

What looks more promising is the Levenshtein distance - specifically "Comparing a list of strings" from the Python Distance package.

Example shamelessly ripped from that page:

(mainly because I couldn't link directly to the relevant section)

>>> sent1 = ['the', 'quick', 'brown', 'fox', 'jumps', 'over', 'the', 'lazy', 'dog']
>>> sent2 = ['the', 'lazy', 'fox', 'jumps', 'over', 'the', 'crazy', 'dog']
>>> distance.levenshtein(sent1, sent2)
3

Tido.com (talk) 04:07, 1 April 2015 (UTC)

Hi,
the bot currently does not touch the surrounding text at all, it only modifies the package templates or appends Template:Broken package link when the package is not found. This is obviously not perfect, this behaviour may lead to some incorrect combinations as you noticed, but blindly fixing the package links and not the surrounding text is still considered to be an improvement. Checking the surrounding text manually would require a lot of manpower, which we don't have, so it is currently not done systematically. Feel free to ask for further details or see the most recent discussion: ArchWiki:Requests#Strategy_for_updating_package_templates.
Regarding automatic updates of the surrounding text, the edit distance gives a clue about whether given edit should be performed or not, but it does not define how an edit should be performed. It can be useful in cases where there are multiple feasible substitutions in text and the strategy to select the optimal substitution is e.g. to minimize the Levenshtein distance. But we don't have any algorithm to generate feasible substitutions yet, so this technique fails. The surrounding text substitution is also very context sensitive and wiki bots must be designed in a way to minimize (ideally avoid completely) the error of the first kind, which in this case is modifying correct text to be incorrect. This makes defining general rules for the text substitution really hard, on the other hand many rules would be necessary to cover even the basic form of standard wording, so in the end both ways may be comparably hard. Anyway, if you have some ideas, I'm all ears :)
-- Lahwaacz (talk) 17:51, 1 April 2015 (UTC)

bot checking links after move

Hi, re Talk:Touchpad Synaptics#adding libinput alternative. Touchpad Synaptics has 100+ backlinks and the more important ones - a bit tedious task. I was just glancing over your clever github bot scripts. It would be handy to have a script after such moves: walk over the backlinks of Touchpad Synaptics and just replace "[[Touchpad Synaptics" with "[[Synaptics" from the links. That would leave all links to subsections intact. Leaving out the translations to handle manually, there would not be much to go wrong, or? --Indigo (talk) 07:36, 26 September 2015 (UTC)

Hi, thanks for the suggestion. It would be indeed handy in this case, but most likely not generally. Imagine that there was a UUID page, which was later generalized and renamed to Persistent block device naming and content about UUID is now only a section on the page. In this case using the naive replacement would likely change the meaning of many sentences, and using shorter redirects for convenience is actually encouraged. There would have to be a list of whitelisted "harmless" replacements, which could even help to replace [[pacman|Install]] with [[Install]] etc. -- Lahwaacz (talk) 08:01, 26 September 2015 (UTC)
Yes, good examples, but you are thinking universal already :) I did not mean it could be that. For example, if you take the time when the bulk of the title case moves were done. With such a script one could avoid a lot of internal redirects as well. E.g. [4]. But it's ok, just an idea. Please close this, if you think it's too singular cases with a simple enough replacement where it could be applied. --Indigo (talk) 10:02, 26 September 2015 (UTC)

aur-mirror

Hi Lahwaacz,

It seems that aur-mirror has been down for a while. I'm not sure if this is intentional or not, but if it is, could you have Lahwaacz.bot remove Template:Aur-mirror from pages? At least where they are in a Template:Broken package link like {{Broken package link|{{aur-mirror|foobar}}}}.

If there is anything I can do to help, let me know.

Thanks! Lonaowna (talk) 14:56, 19 October 2016 (UTC)

Maybe drifting a bit offtopic... but I'm in favor to finally remove any and all packages that are not on AUR4 from the wiki. Users have had over a year time to migrate, which is a century in Arch standards. -- Alad (talk) 16:21, 19 October 2016 (UTC)
I agree, especially on pages like List of games (already took care of that), and List of Applications (see Talk:List of applications#AUR3 packages). On other pages, where the non-existing packages are mentioned inline, it requires some more knowledge and effort to remove them. -- Lonaowna (talk) 16:34, 19 October 2016 (UTC)
Hmm... For the moment I just updated the template to point to Github instead. What would be the alternative "hint" without the link? It should still be different from just "package not found". -- Lahwaacz (talk) 18:08, 19 October 2016 (UTC)
The GitHub repository is fine as well. I think we can keep that one while we (carefully) remove/update all broken links. Thanks! Lonaowna (talk) 06:52, 20 October 2016 (UTC)

OpenVPN

Hi, the topic about setting the key password was a tip, and the only way that work to have the openvpn "ask" for the key password. The systemd-ask-pass is not working. So when the openvpn service is started it does not ask for the key password. I know it is not the best sollution, far away from that, but it was the only way that i can put it to work. I think it is a valuable tipo, although it have to came with a security note. Can be this way?

—This unsigned comment is by Mawcomw (talk) 10:52, 31 October 2016‎. Please sign your posts with ~~~~!

Is there a reason why you have a password-protected key or was it set up implicitly by following some guide? Note that you can remove the passphrase without generating a new key. If you have a good reason for using the passphrase, using plain --askpass without a file would allow openvpn to ask for the passphrase on its standard input, but that probably does not work well with systemd units starting at boot. -- Lahwaacz (talk) 13:41, 31 October 2016 (UTC)

GPIO / I2C

Hi, I notice you have un-done my edit on the raspberry pi page. [5]

My intention was that to access the I2C bus, you need to use the GPIO connector - hence in this context I believe that I2C should be a sub-heading in the same way as the SPI bus is currently a sub-heading. (The Wikipedia articles on GPIO you referred to, also suggests that I2C and GPIO are related)

Hence, I believe my edit should stand.

I was planning to add further buses to the GPIO section as / when I use them (including references to the pinouts, ie: [6])

Let me know what you think.

Thanks RuneArch (talk) 09:16, 23 November 2016 (UTC)

Well I guess it depends on how you look at it. Maybe this will do? -- Lahwaacz (talk) 09:35, 23 November 2016 (UTC)
Ah, I think I see your point of view about GPIO and the python package... yep, I think that's much better :) RuneArch (talk) 09:47, 23 November 2016 (UTC)

CPU frequency scaling

Done a few tests with i5-6400 CPU @ 2.70GHz (TB up to 3.30GHz):

$ cpupower frequency-info
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 800 MHz - 3.30 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 800 MHz and 3.30 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency: 800 MHz (asserted by call to hardware)
  boost state support:
    Supported: yes
    Active: yes
# cpupower frequency-set -g performance

Using watch:

current CPU frequency: 3.25 GHz (asserted by call to hardware)
current CPU frequency: 3.29 GHz (asserted by call to hardware)
current CPU frequency: 3.26 GHz (asserted by call to hardware)
current CPU frequency: 3.28 GHz (asserted by call to hardware)
current CPU frequency: 3.30 GHz (asserted by call to hardware)

As you can see the CPU keeps trying to run at the max. frequency (including TB).

If not running any commands, moving the cursor, or any other activity, the CPU starts throttling back, but will immediately boost again to full freq. when doing a simple task.

The same behaviour happen with a Intel i5-2400 (including TB).

I don't recommend the use of the performance governor at all, even on good cooling.

What are your thoughts on this? Thanks.

Francoism (talk) 21:39, 11 December 2016 (UTC)

You're already observing that it does not "run at the maximum frequency". It's simply (much) more aggressive at rising the frequency, nothing more. Also, you should use i7z to monitor the per-core frequency. -- Lahwaacz (talk) 22:15, 11 December 2016 (UTC)
That's the thing I want to show, it doesn't aggressive rising the frequency, but simple tries to run the CPU at max. speed all the time, even when doing nothing at all:
# i7z

Cpu speed from cpuinfo 2712.00Mhz
True Frequency (without accounting Turbo) 2712 MHz
  CPU Multiplier 27x || Bus clock frequency (BCLK) 100.44 MHz

Socket [0] - [physical cores=4, logical cores=4, max online cores ever=4]
  TURBO ENABLED on 4 Cores, Hyper Threading OFF
  Max Frequency without considering Turbo 2812.44 MHz (100.44 x [28])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  33x/33x/32x/31x
  Real Current Frequency 3241.60 MHz [100.44 x 32.27] (Max of below)
  Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
        Core 1 [0]:       3155.71 (31.42x)      1.25    93.9       1    3.65    21      1.1155
        Core 2 [1]:       3241.60 (32.27x)      1.49    95.3       1    1.88    20      1.1091
        Core 3 [2]:       2844.39 (28.32x)         1    95.4       1    2.59    20      1.1090
        Core 4 [3]:       3226.32 (32.12x)      1.45    95.7       1    1.56    20      1.1090

One. sec. later, keep in mind this is including turbo-boost and nothing happens in the background and I'm not touching anything. Command electron is running, but keeps hitting <10% CPU usage, could try to disable, but 5% usage isn't really needed to boost the CPU to it's max. clockspeed:

# i7z

Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
Core 1 [0]:       2917.95 (29.06x)         1    97.9       0    1.78    21      1.1044
Core 2 [1]:       3276.91 (32.64x)         1    98.2       0    1.12    21      1.1072
Core 3 [2]:       3266.05 (32.53x)      1.36    98.4       0       0    20      1.1138
Core 4 [3]:       3278.00 (32.65x)         1    97.6       0    1.19    21      1.1138

Switching back to powersave, also notice the decrease of the VCore:

# i7z

Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
Core 1 [0]:       800.14 (7.97x)        18.1    75.9       1    17.8    21      0.7522
Core 2 [1]:       801.91 (7.98x)        13.1    77.3       1    17.8    21      0.7512
Core 3 [2]:       825.59 (8.22x)        18.5    72.4       1      21    20      0.7511
Core 4 [3]:       800.47 (7.97x)        16.2    77.5       1    16.7    21      0.7512

That's why I've added the warning message, the voltage and temperatures will increase, and it doesn't have any positive effect, maybe if running games, but it seems like a waste of energy atm.
Francoism (talk) 12:59, 12 December 2016 (UTC)
Then I'd say that your system is not really idle - what if you run it from the Linux console, with Xorg shut down? On i5-2430M (base freq 2394 MHz, boost to 2993 MHz), I'm getting the following with powersave:
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
        Core 1 [0]:       857.47 (8.60x)         2.1    99.2       0       0    47      0.8206
        Core 2 [2]:       997.56 (10.00x)       3.95    97.4       1       0    47      0.8156
And with performance:
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
        Core 1 [0]:       1162.35 (11.65x)      1.09    99.5       0       0    47      1.2109
        Core 2 [2]:       1553.64 (15.58x)         1    98.5       1       0    45      1.2109
-- Lahwaacz (talk) 13:24, 12 December 2016 (UTC)
Without X or any apps, using performance:
Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
Core 1 [0]:       3292.33 (32.78x)      63.5    22.9       0       0    24      1.1078
Core 2 [1]:       3237.91 (32.24x)         0     100       0       0    22      1.1031
Core 3 [2]:       3286.59 (32.72x)         1      64       1    34.9    22      1.1028
Core 4 [3]:       3165.25 (31.51x)         1     100       0       0    21      1.0978
# htop

  PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
    1 root       20   0  132M  6804  5184 S  0.0  0.0  0:00.86 /sbin/init
    2 root       20   0     0     0     0 S  0.0  0.0  0:00.01 kthreadd
    3 root       20   0     0     0     0 S  0.0  0.0  0:00.08 ksoftirqd/0
    7 root       20   0     0     0     0 S  0.0  0.0  0:01.95 rcu_preempt
    8 root       20   0     0     0     0 S  0.0  0.0  0:00.01 rcu_sched
    9 root       20   0     0     0     0 S  0.0  0.0  0:00.00 rcu_bh
   10 root       RT   0     0     0     0 S  0.0  0.0  0:00.02 migration/0
   11 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 lru-add-drain
   12 root       RT   0     0     0     0 S  0.0  0.0  0:00.00 watchdog/0
   13 root       20   0     0     0     0 S  0.0  0.0  0:00.00 cpuhp/0
   14 root       20   0     0     0     0 S  0.0  0.0  0:00.00 cpuhp/1
   15 root       RT   0     0     0     0 S  0.0  0.0  0:00.00 watchdog/1
   16 root       RT   0     0     0     0 S  0.0  0.0  0:00.02 migration/1
   17 root       20   0     0     0     0 S  0.0  0.0  0:00.09 ksoftirqd/1
   20 root       20   0     0     0     0 S  0.0  0.0  0:00.00 cpuhp/2
   21 root       RT   0     0     0     0 S  0.0  0.0  0:00.00 watchdog/2
   22 root       RT   0     0     0     0 S  0.0  0.0  0:00.02 migration/2
   23 root       20   0     0     0     0 S  0.0  0.0  0:00.10 ksoftirqd/2
   26 root       20   0     0     0     0 S  0.0  0.0  0:00.00 cpuhp/3
   27 root       RT   0     0     0     0 S  0.0  0.0  0:00.00 watchdog/3
   28 root       RT   0     0     0     0 S  0.0  0.0  0:00.02 migration/3
   29 root       20   0     0     0     0 S  0.0  0.0  0:00.08 ksoftirqd/3
   31 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 kworker/3:0H
   32 root       20   0     0     0     0 S  0.0  0.0  0:00.00 kdevtmpfs
   33 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 netns
   34 root       20   0     0     0     0 S  0.0  0.0  0:00.00 khungtaskd
   35 root       20   0     0     0     0 S  0.0  0.0  0:00.00 oom_reaper
   36 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 writeback
   37 root       20   0     0     0     0 S  0.0  0.0  0:00.00 kcompactd0
   38 root       25   5     0     0     0 S  0.0  0.0  0:00.00 ksmd
   39 root       39  19     0     0     0 S  0.0  0.0  0:00.44 khugepaged
   40 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 crypto
   41 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 kintegrityd
   42 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 bioset
   43 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 kblockd
   44 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 devfreq_wq
   45 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 watchdogd
   47 root       20   0     0     0     0 S  0.0  0.0  0:00.00 kswapd0
   48 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 vmstat
   57 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 kthrotld
   58 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 ipv6_addrconf
   60 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 deferwq
   61 root       20   0     0     0     0 S  0.0  0.0  0:00.32 kworker/u8:1
   83 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 ttm_swap
  129 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 nvme
  155 root       20   0     0     0     0 S  0.0  0.0  0:00.00 scsi_eh_0
  156 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 scsi_tmf_0
  157 root       20   0     0     0     0 S  0.0  0.0  0:00.00 scsi_eh_1
  158 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 scsi_tmf_1
  159 root       20   0     0     0     0 S  0.0  0.0  0:00.00 scsi_eh_2
  160 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 scsi_tmf_2
  161 root       20   0     0     0     0 S  0.0  0.0  0:00.00 scsi_eh_3
  162 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 scsi_tmf_3
  163 root       20   0     0     0     0 S  0.0  0.0  0:00.00 scsi_eh_4
  164 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 scsi_tmf_4
  165 root       20   0     0     0     0 S  0.0  0.0  0:00.00 scsi_eh_5
  166 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 scsi_tmf_5
  172 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 bioset
  173 root        0 -20     0     0     0 S  0.0  0.0  0:00.00 bioset

PS. Sorry for all the spam, if you want I can moved to pastebin or something else. :)
Francoism (talk) 13:48, 12 December 2016 (UTC)
Well, on i7-5820K (base freq 3.3 GHz, boost to 3.6 GHz) that we have at school, I get the following result with performance:
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
        Core 1 [0]:       1725.61 (17.25x)      1.27    5.46       0    93.9    27      0.7705
        Core 2 [1]:       2322.11 (23.21x)         1    0.123      0    99.9    29      0.9701
        Core 3 [2]:       2532.10 (25.31x)         1    0.204      0    99.7    29      0.9801
        Core 4 [3]:       2128.67 (21.27x)         1    0.177      0    99.8    30      0.9724
        Core 5 [4]:       2267.82 (22.66x)         1    0.311      0    99.6    29      0.9703
        Core 6 [5]:       1792.93 (17.92x)         1    0.495      0    99.4    29      0.9974
and with powersave:
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
        Core 1 [0]:       1280.11 (12.79x)         1    5.29       0    94.3    26      0.7755
        Core 2 [1]:       1267.35 (12.67x)         1      46       0      54    28      0.7617
        Core 3 [2]:       1211.02 (12.10x)         1    0.442      0    99.5    28      0.7468
        Core 4 [3]:       1213.45 (12.13x)         1     100       0       0    30      0.7474
        Core 5 [4]:       1268.28 (12.68x)         1     100       0       0    28      0.7678
        Core 6 [5]:       1392.95 (13.92x)         1    22.2       0    77.7    27      0.7374
While the frequency stays considerably higher with performance, it's nowhere near the peak frequency. So the behaviour must be model-specific. -- Lahwaacz (talk) 19:28, 16 December 2016 (UTC)
Thanks for the test. Tested on a few Intel i3/i5 procs and they all seem to show this behaviour, however I didn't test any i7 CPU, but indeed your results differ a lot. What should we do about the warning? :) -- Francoism (talk) 18:48, 22 December 2016 (UTC)
Currently it only says to watch out for temperature and voltage, which is fine in my view... -- Lahwaacz (talk) 19:43, 22 December 2016 (UTC)

Linux-ck

> linux-ck is not that much useful

agree, i already removed most details about Linux-ck and replaced it by a single link, then dumped them into the Linux-ck wikipage.

So? -- Lahwaacz (talk) 18:59, 6 January 2017 (UTC)

Packages development pages

Hi Lahwaacz. I see you reverted my edits. Actually sorting alphabetically was not the main purpose of my changes but include a link to the article VCS package guidelines. Yesterday, as I was updating my AUR packages, I had a hard time recovering the VCS page, just because it was not linked at all from any package development pages, not even from the Arch Linux wiki table of content (if I'm not wrong). Could you please investigate this issue? Also, I wanted to add precisions brought to AllanMcrae blog post in the Arch Linux pages, because without the help of our friends on IRC who linked me back to that post, I would have made false assumptions with my GPG signature check in my PKGBUILD. -- wget (talk) 11:26, 7 January 2017 (UTC)

I must have missed that. In that case, there are many package guidelines pages for different programming languages etc., but the top level page for them is Creating packages (which is already linked from the related articles of PKGBUILD). The other pages are linked from e.g. Creating packages#More detailed guidelines or Arch packaging standards#Additional guidelines (the "Package creation guidelines" at the top of the navigation template leads to Creating packages).
As for Table of contents, it lists only categories and VCS package guidelines is in Category:Package development.
I'm not aware of any inaccuracy on the wiki regarding Allan's blog post, see e.g. the note in makepkg#Signature checking.
-- Lahwaacz (talk) 11:41, 7 January 2017 (UTC)
Thanks for letting me know the VCS page was actually already linked from Creating packages#More detailed guidelines. It was well hidden. If I wasn't able to find it easily, while I'm used to use the Arch Linux wiki, imagine how hard it is for newcomers to find it. :-) This might be a problem.:-/ Additional/excessive cross-linking won't harm especially for SEO. -- wget (talk) 12:43, 7 January 2017 (UTC)
Catching up in my Arch related duties: we can clearly see "signature and .sig" files is a question that is often asked. It needs clarification as, for other packages managers, relying on the package manager to download the public GPG key from a key server is not always the case (e.g. chocolatey on Windows). -- wget (talk) 14:43, 7 January 2017 (UTC)
Fixed. -- wget (talk) 15:16, 7 January 2017 (UTC)

On hold Inter language links bot update for a short time

Hi, I see all recent inter language link auto update is run by your bot. Please notice that zh-cn will change to zh-hans and zh-tw change to zh-hant. Please on hold the bot run in a few days until all changes are landed. See Help_talk:I18n#Chinese_interlanguage_links for detail. If you have some suggestion, we can discuss it there too. Thanks. --Fengchao (talk) 05:39, 10 January 2017 (UTC)

Thank you for the notice, I've made the update in wiki-scripts just now. -- Lahwaacz (talk) 11:11, 11 January 2017 (UTC)