| Alverstone | Sometimes, when I try to bash complete a non-existent file (basically make a typo), it blocks for a minute or so, becoming completely unresponsive, then suddenly goes back to normal. This really annoys me but there are so many variables involved I can't even make it into a bug report. Anyone experienced something similar? | 12:37 |
|---|---|---|
| rkta | probably a some network share or unresponsive mount | 12:39 |
| fsmithred | Alverstone, I see the exact same thing sometimes. Also see 'ls' take a long time to respond if there are a lot of files in the directory. (a lot could be 100, nn 10,000)) | 12:43 |
| fsmithred | no/not | 12:43 |
| fsmithred | same if I open thunar. It takes a long time to show me the files in my home dir. | 12:44 |
| Alverstone_ | rkta, nope, it's just a HDD drive. The last few times it happened that I remember were with one of my USB drives. They're were responsive just fine, but still the console would block completely. | 13:03 |
| Alverstone_ | fsmithred, any way in which I can reproduce the bug with lots of files? | 13:03 |
| Alverstone_ | for ; do touch ; done ?? | 13:03 |
| * Alverstone is annoyed with random internet reconnections! | 13:04 | |
| freem | <Alverstone> Sometimes, when I try to bash complete a non-existent file (basically make a typo), it blocks for a minute or so, becoming completely unresponsive, then suddenly goes back to normal. This really annoys me but there are so many variables involved I can't even make it into a bug report. Anyone experienced something similar? | 13:05 |
| freem | I have that as well (except for zsh), especially with my slow HDD or with git. It can be cancelled with ctrl+c though. | 13:05 |
| djph | ^ | 13:06 |
| djph | I've seen it with older/slower computers where it takes forever to try to figure out what it is I meant ... | 13:06 |
| Alverstone | freem, I wish. In my case it ignores all input. At first I thought I pause it accidentally (you know, ^S and ^Q sequences), but nope. Not even ^C works | 13:07 |
| freem | (and that HDD is slow because hardware is aging and didn't enjoyed all the travels. I should just migrate data, but I say that since 2 or 3 years already...) | 13:07 |
| Alverstone | My drive isn't slow though. It's only a few years old | 13:07 |
| Alverstone | It can write its legitimate 100-200 mb/s just fine. | 13:08 |
| Alverstone | 5600 rmp iirc | 13:08 |
| Alverstone | rpm | 13:08 |
| freem | I suspect my drive to have damaged sectors, actually. Which the kernel does not exactly enjoys, so that makes bunches of failed I/Os, which can't help with speed | 13:08 |
| Alverstone | freem, smartctl -A ? | 13:08 |
| Alverstone | touch {1..10000}; ls | 13:09 |
| Alverstone | works fine to me | 13:09 |
| freem | https://p.mort.coffee/g2H | 13:10 |
| freem | yeah, I guess it's on the end life | 13:10 |
| Alverstone | looks fine though? | 13:11 |
| freem | really? The old-age and other stuff are not problems? | 13:11 |
| Alverstone | see smartctl manpage about -A | 13:12 |
| Alverstone | Each Attribute also has a Threshold value (whose range is 0 to 255) which is printed under | 13:12 |
| Alverstone | the heading "THRESH". If the Normalized value is less than or equal to the Threshold | 13:12 |
| Alverstone | value, then the Attribute is said to have failed. If the Attribute is a pre-failure At‐ | 13:12 |
| Alverstone | tribute, then disk failure is imminent. | 13:12 |
| freem | I also have this kind of files which spawn in my /tmp: https://p.mort.coffee/awv | 13:12 |
| Alverstone | freem, run an extended self test | 13:13 |
| freem | how? I have doing that stuff on TODO-list since years, but never actually put enough time to do more than getting smartd running (which is useless since I don't understand it's results... but is a reminder that I need to dig) | 13:14 |
| Alverstone | smartctl -t long /dev/sdX | 13:15 |
| Alverstone | when it completes, `smartctl -a /dev/sdX` | 13:15 |
| Alverstone | Also, see `smartctl -c /dev/sdX`, under offline data collection capabilities, it should say 'Suspend Offline collection upon new command.' | 13:16 |
| freem | that's going to take litterally 8H according to the command... | 13:16 |
| Alverstone | I never measured to be honest, but yes, usually several hours. | 13:16 |
| freem | "Please wait 483 minutes for test to complete." guess I should ensure my tea/beer storage is not empty... | 13:17 |
| Alverstone | This test is the only reliable way to see what's up with your disk though. I don't do it often, but nonetheless do it just to prepare my ass in case of an imminent error. | 13:17 |
| freem | sounds like a good idea | 13:19 |
| Alverstone | I think all modern disks allow suspension of the test when a new command arrives. But if it doesn't, then you must not invoke smartctl until the test completes, and how you know about its completion is... a mystery :) | 13:19 |
| Alverstone | Also to be honest I don't really know why I run smartd either :) I guess just in case or whatever | 13:21 |
| Alverstone | And finally, `smartctl -c /dev/sdX` IS the way to monitor the progress of the test | 13:21 |
| freem | what's certain is that I don't see any disk activity | 13:21 |
| freem | ah | 13:21 |
| Alverstone | ahh | 13:22 |
| Alverstone | '-c' to check if it's still running. If it is, leave it alone. It seems to idle one second and throttles you IO completely the next | 13:22 |
| freem | kind of looks like this stuff have no actual end... : | 13:23 |
| freem | recommended polling time: ( 2) minutes. | 13:23 |
| freem | Extended self-test routine | 13:23 |
| freem | recommended polling time: ( 483) minutes. | 13:23 |
| Alverstone | What do you quote? | 13:23 |
| freem | the "xtended self-test routine" is placed as if in the case you continue the test longer, it improves | 13:23 |
| freem | the output of smartctl -c | 13:24 |
| freem | that's just guessing though | 13:24 |
| freem | in 8H... I'll probably *really* want to sleep so I don't think I'll try :) | 13:24 |
| Alverstone | I don't actually know what it means. I only know that self tests are not infinite and that they can be aborted using '-X' option. | 13:26 |
| Alverstone | Anyway it requires a bit of patience, I usually run these tests before going to sleep :) | 13:27 |
| morenonatural | hey, y'all ... probably a long shot, but... how should I monitor a specific gamepad being connected/disconnected? currently doing `ls /dev/input/js0` on a 1s sleep loop, `inotifywait` didn't work | 13:29 |
| freem | I would probably do something akin to "dmesg -w | grep /dev/input/js0" | 13:30 |
| fsmithred | tail -f /var/log/syslog | 13:30 |
| * Alverstone sighs | 13:33 | |
| Alverstone | grep Xorg log | 13:33 |
| fsmithred | maybe some way with udev rules. | 13:33 |
| Alverstone | or go wild as a true linuxoid and abuse udev. You can even abuse libudev to do it as a regular user, I remember writing something ugly like that a while ago for fun:) | 13:34 |
| morenonatural | that scaled quickly | 13:34 |
| Alverstone | If you find some python/go bindings it isn't even going to be that complex. 50-100 lines at worst | 13:35 |
| morenonatural | in all fairness, I'm probably gonna use such script until this week... the replacement PCB for said gamepad arrives this week | 13:35 |
| Alverstone | If you hardcode gamepad info instead of implementing configs it's basically trivial | 13:35 |
| Alverstone | But honestly, write a udev rule and abuse notify-send | 13:35 |
| morenonatural | 👍🏾 | 13:36 |
| Alverstone | morenonatural, also, `man udevadm`, see monitor section. I bet it's trivial to write a wrapper shell script for that, gonna be by far the easiest way to go | 13:37 |
| Alverstone | MonsoonSecrecy, look, I made a 10-minutes masterpiece for you https://paste.debian.net/plain/1335179 | 14:12 |
| Alverstone | :D | 14:13 |
| Alverstone | morenonatural, | 14:13 |
| Alverstone | MonsoonSecrecy, sorry, accidentally tagged you instead of morenonatural | 14:13 |
| morenonatural | Alverstone, ohmysystemd thank you! sorry to trigger that OCD, too | 14:15 |
| Alverstone | morenonatural, can't help that :P I'd even go as far as to say it's good it got triggered for something simple like this, sometimes it derail my brain for several days | 14:16 |
| Alverstone | can derail* | 14:16 |
| morenonatural | well, that's what's so interesting to me about Emacs: you can always re-charge energies by going into a fine-tuning void for several hours before going back to mundane repetitive work | 14:18 |
| AlexLikeRock | whats alternativo to : gksu , kdesudo , pkexec | 17:07 |
| debdog | su-to-root [-X] | 17:10 |
| debdog | su-to-root - A simple script to give an `interactive' front-end to su. It can be used in menu entry commands to ask for the root password | 17:10 |
| debdog | -X The command is a X11 program that does not require a terminal. This is to be used with menu entries that declare needs="X11". | 17:10 |
| AlexLikeRock | where can find ? | 17:15 |
| AlexLikeRock | its not at synaptic | 17:15 |
| debdog | package "menu" | 17:18 |
| n4dir | it is part of "menu", so you probably have it installed | 17:18 |
| AlexLikeRock | heheh | 17:18 |
| AlexLikeRock | yes, its install it ! | 17:18 |
| AlexLikeRock | where are the path ? | 17:19 |
| n4dir | in case it comforts you: i never heard of su-to-root myself | 17:19 |
| AlexLikeRock | yes | 17:19 |
| AlexLikeRock | inever heard of su-to-root my self | 17:19 |
| AlexLikeRock | XD | 17:19 |
| * debdog created and maintains his own menu so he's required to know | 17:20 | |
| n4dir | i got no display-manager like gdm running, so i think i usually can just type su in a terminal and start gui apps from there. | 17:20 |
| n4dir | seldom have to, so not sure | 17:20 |
| n4dir | well: am pretty sure | 17:21 |
| AlexLikeRock | ¬_¬ | 17:22 |
| AlexLikeRock | usage: /usr/sbin/su-to-root [-X] [-p <user>] -c <command> | 17:31 |
| AlexLikeRock | yes , | 17:31 |
| AlexLikeRock | its working , by terminal | 17:31 |
| AlexLikeRock | thanks debdog | 17:31 |
| debdog | nw | 17:31 |
| Alverstone | >gksu, kdesudo, pkexec | 19:39 |
| * Alverstone is acutely pained | 19:39 | |
| Alverstone | Honestly just use doas or `su -` | 19:40 |
| Alverstone | By the way | 19:40 |
| Alverstone | is making cgroup tasks file world readable a good idea? It's just a CPU cgroup to set lower priority to processes. `nice -n 19` isn't enough for me | 19:41 |
| Alverstone | world writable* | 19:42 |
| AlexLikeRock | hoe to reboot with hardward too ? | 20:56 |
| AlexLikeRock | init 6 : just restart the kernel | 20:57 |
| AlexLikeRock | , i need shutdown and boot again | 20:57 |
| fsmithred | alt-sysrq-R... S... U... B | 20:57 |
| AlexLikeRock | hahahhaha | 20:58 |
| AlexLikeRock | you forget "I" | 20:58 |
| AlexLikeRock | and "E" | 20:58 |
| fsmithred | E and I do nothing | 20:58 |
| fsmithred | and what I typed might not work with the default settings - I'm not sure | 20:59 |
| fsmithred | in /etc/sysctl.conf | 20:59 |
| fsmithred | replace B with O for powerOff | 21:00 |
| FatPhil | shutdown -r will reboot | 21:01 |
| AlexLikeRock | ok | 21:01 |
| rwp | If you are on the hardware vt console with a keyboard then Control-Alt-Delete will trigger a graceful "shutdown -r now" action. | 21:05 |
| Alverstone | sysrq + B works like a breeze | 21:05 |
| rwp | On a hardware X console Control-Alt-F1 will switch to the hardware vt console and then Control-Alt-Delete will trigger the reboot. | 21:06 |
| AlexLikeRock | not work reboot -r | 21:06 |
| rwp | And then if that fails to work then using SysRq is the best way. | 21:06 |
| AlexLikeRock | my laptop not have "SysRq" | 21:06 |
| AlexLikeRock | sorry | 21:06 |
| rwp | What would "-r" do with "reboot" on a GNU/Linux system? That's not a valid option here. | 21:06 |
| Alverstone | alt+print screen | 21:06 |
| Alverstone | is the sysrq combination | 21:06 |
| AlexLikeRock | they have , but take a screen shot | 21:06 |
| Alverstone | alt + print screen + B | 21:07 |
| Alverstone | you'll like it | 21:07 |
| rrq | you might try: echo b > /proc/sysrq-trigger | 21:07 |
| AlexLikeRock | hahahah | 21:07 |
| rwp | I often need to look it up on random keyboards but I think it is Alt+Fn+PrtSc on my current keyboard. | 21:07 |
| AlexLikeRock | thanks i like so much rrq | 21:07 |
| rwp | If the system is running enough to do those commands then it is probably running enough to run "shutdown -r now" then too. | 21:07 |
| Alverstone | I wish I could break my system like that | 21:09 |
| AlexLikeRock | what stop to you? | 21:09 |
| Alverstone | Lately whatever I do it still works somehow and the worst part it works more or less like I intended | 21:09 |
| AlexLikeRock | do it! | 21:09 |
| Alverstone | Kinda takes all the fun from tinkering | 21:10 |
| AlexLikeRock | hhahha | 21:10 |
| Alverstone | I am actually on the verge of encrypting my drive, but somehow I still have enough sanity to resist it | 21:17 |
| Alverstone | On the other hand, if I understand it correctly, with su disabled, when the root is encrypted, I can disable password for some users (I mean the agetty's feature to log you in without requiring password), since it doesn't add any meaningful protection anymore | 21:18 |
| Alverstone | Though if somebody has physical access... | 21:19 |
| Alverstone | I just can't get over having to type one more password at boot | 21:19 |
| rrq | doesn't encryption bring a "single-byte failure" problem for the whole ? | 21:21 |
| Alverstone | :) | 21:22 |
| Alverstone | LUKS header can actually be backed up. But in general encryption is a lot of things too keep in mind and maintain and I do not have any data to protect against theft. Critical passwords are encrypted already. | 21:25 |
| Alverstone | He finally managed to reboot, ehh | 21:25 |
| Alverstone | Which password encryption do you use? Bookworm had sha512 with default amount of rounds (or it is leftovers from buster or bullseye), but now I see it has changed to YESCRYPT. Is YESCRYPT better? | 21:26 |
| djph | Alverstone: 'yes'. it's even in the name :P | 21:27 |
| djph | As with all cryptography options, it's likely better in some respects, parity in others, and worse in others. | 21:28 |
| * rrq keeps protected stuff in a gocryptfs partition that I unshare mount | 21:28 | |
| Alverstone | https://github.com/openwall/yescrypt sounds good to me | 21:31 |
| Alverstone | rrq, I use gocryptfs too, but instead with pam_mount, because I don't want to enable allow_others in fuse.conf | 21:31 |
| Alverstone | gocryptfs is a very handy thing | 21:31 |
| rrq | yeah I do unshare mount to disallow others :) | 21:32 |
| Alverstone | unshare mount ? :) | 21:32 |
| rrq | while accessing through a single session shell | 21:32 |
| Alverstone | you have an entire partition for gocryptfs? | 21:33 |
| rrq | mmm actually I changed it to be a directory ... mounting gocryptfs within "unshare -m" | 21:35 |
| rrq | that makes the gocryptfs mount unavaliable to other sessions | 21:35 |
| rrq | (root obviously may do "nsenter") | 21:37 |
| Alverstone | But what is the point? Uh, can you describe the bigger picture? Mine is simple, I do pam_mount with gocryptfs and then simply stuff whatever I want to encrypt in there as a regular user. Easy, handy, whatever. Another benefit is that it's trivial to make a shell script to notify you if mounting has failed | 21:39 |
| rrq | by unsure I lock out all others from peeping into the decrypted tree, including same user in other sessions. So it's "stronger" lock-out.. not actually needed from a practial perspective, but it ended up like that while I learnt about unsharing. | 21:42 |
| rrq | "unsure" => "unshare" | 21:42 |
| rrq | I stepped away from partition encryption so as to the avoid "single-byte error" problem for my "secret" data. | 21:44 |
| rrq | otoh I need to keep some junk in the files to make them large enough to hide the data with encryption | 21:47 |
| Alverstone | size shouldn't matter? | 21:56 |
| Alverstone | Also, `unshare -m` requires root privileges! | 21:57 |
| rrq | yes unsure requires root. Not knowing the datum size makes it a harder nut to crack. | 21:58 |
| Xenguy_ | I'm unfamiliar with gocryptfs; does it resemble an encryption scheme like 'veracrypt' at all? | 21:58 |
| Xenguy_ | Meanwhile I've been using KeePassXC for encrypting passwords, and 'ccrypt' for one-off file encryption operations | 21:59 |
| Alverstone | IIRC the file size isn't obscured so if the have the plain text file they can with high probability say that you have it too, but even if they know the size of a file with passwords, even if they know the syntax, it would be pretty damn hard to brute force it. | 22:00 |
| Xenguy_ | (I also use LUKS at boot time) | 22:00 |
| rrq | gocryptfs does directory tree encryption by mapping to a decrypted tree, preserving the directory structure whilst scramblilng the names as well as file contents. | 22:01 |
| rrq | the decrypted tree is a fuse filesystemm | 22:02 |
| Alverstone | >KeePassXC | 22:03 |
| Xenguy_ | rrq, Putting it on the todo list to look into further | 22:04 |
| Alverstone | I symlinked my clipboard manager's directory with the history file to the gocryptfs mount point and don't care about anything anymore | 22:04 |
| rrq | right. I only use my vault transiently. | 22:05 |
| Alverstone | rrq, ?? mount, write, unmount? | 22:05 |
| Alverstone | There is just no point in using stuff like KeePassXC when there is such a beautiful thing as gocryptfs :) | 22:06 |
| Xenguy_ | Sounds like a better mousetrap, hrm | 22:07 |
| rrq | yes; mostly mount+read+unmount .. scripted of course | 22:07 |
| rrq | so "read" is basically starting a shell to do whatever (aka run emacs :) | 22:08 |
| rrq | (emacs-nox) | 22:08 |
| Alverstone | emacs :( gimme a break | 22:08 |
| * Xenguy_ solved one religious war by running both Vim and Spacemacs : -) | 22:09 | |
| Xenguy_ | I've come to appreciate emacs fans more since I took up using Spacemacs | 22:09 |
| rrq | if I could learn and remember how to make and run keyboard macros in vi or whatever, I could probably use that/those too | 22:10 |
| Xenguy_ | rrq, I use Vim macros all the time at work. I usually just press 'qq' to record a macro, then '@q' to replay it (assuming that's what you are talking about) | 22:11 |
| rrq | mmm sounds easy enough... now on my reading list; thanks | 22:12 |
| Xenguy_ | my pleasure | 22:12 |
| Alverstone | The problem with vim is that while it seems easy, its documentation is a black hole in which you can effortlessly waste a lifetime | 22:19 |
| Alverstone | emacs is pretty much the same in this regard | 22:19 |
| Xenguy_ | Alverstone, I think of it as the 'beautiful mystery of Vim': the idea that the editor is so vast that one person could never learn it completely in a lifetime is fascinating to me... | 22:21 |
| Alverstone | It's what happens when software is developed for a lifetime of an entire team of developers | 22:21 |
| rrq | I don't really mind the tool; just that I'm most efficient using emacs.. been using it since 1980 | 22:22 |
| Alverstone | >1980 | 22:22 |
| Alverstone | Now isn't you gray beard heavy these days? | 22:22 |
| Alverstone | your* | 22:22 |
| Xenguy_ | Because Vim is so vast, it almost guarantees those 'mystery moments' when you discover a new feature and think 'why did I only learn about this amazing feature now?' : -) | 22:23 |
| rrq | my first terminal editor.. teco emacs on mips-20.. the step after shuffling cards | 22:23 |
| djph | rrq: great OS, all it needs now is a goo editor :P | 22:23 |
| djph | *good | 22:23 |
| Xenguy_ | rhymes with pico | 22:23 |
| djph | ... er, oops, this isn't offtopic :( | 22:24 |
| Xenguy_ | Oh right | 22:25 |
| Xenguy_ | Well, on the topic of text editors, pico was my first in a *nix environment | 22:26 |
| Xenguy_ | Nowadays that's nano I suppose | 22:27 |
| rrq | Alverstone: some leasure time reading .. https://en.wikipedia.org/wiki/TECO_(text_editor) | 22:33 |
| rrq | ah; it was TOPS-20 | 22:34 |
| Alverstone | I can't believe people actually wrote something in TECO | 22:37 |
| Alverstone | I don't have capacity to take recreational computing to this level of magnificence | 22:39 |
| rrq | yeah, today we look for other conveniences than "saying a lot with few characters" | 22:55 |
| FatPhil | APL was pretty whack. | 22:57 |
| rrq | indeed .. and I looking for a way to have my aarch64 h/w boot an aarch32 kernel. | 22:58 |
| onefang | Well off topic, but APL was my first language, and I have programmed in TECO, coz that's what the system I took over was written in. | 23:37 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!