Linux

Have you noticed there are some shameless thefts, basically clones, in the world of terminal emulators? At least the ones for GNOME?

For example, Kitty, Tilix, and Terminator have at least one clone, nothing changed, just repackaged, repackaged on the repository even. I won't name them, but those guilty should feel the burn of shame at their hearts!

And now that we got that out of the way, these are the temus I use actively, like each for a certain task:

• Tilix
• Kitty
• Alacritty

Alacritty is fast, but it's not customizable. Kitty is best. Tilix is good, especially since it's a WM of its own. But it's not as 'crisp' as Kitty is.

I don't like Terminator and its clones, because they have this fruity red bar on top, very distracting. Plus Tilix does what these inbred family do a thousand times better.

Now I wanna know if there are temus I am missing, like obscure ones. Should be able to run on Gnome.

I especially want something like the new Micropeni$ Windows terminal. Also terminal emulators that are based on more modern systems languages, e.g. Rust, Zig, Go. Ones that don't 'necessarily' stick to TermInfo.

So; Not some Xterm clone crap. There must be a million Xterm clones out there. I did not name Xterm because every terminal emulator for X is virtually a clone of Xterm lol.

Thanks!

I'm using an old program that doesn't automatically forward ports. I've experimented with using the same ports as another program, but it didn't yield the desired results. Manually opening the ports directly in the router did not resolve the issue. I also tried a port forwarder, and it works but only intermittently.

If you have any recommendations for programs or tools that can reliably forward TCP and UDP ports via UPnP, please share them with me. I'm looking for a solution that is user-friendly, and works consistently.

I think ---DOCKER--- is doing this. I installed based, and userspace(7)-pilled liblxc and libvirt and then this asshole inserted a dependency when I tried to install from their Debian package with sudo dpkg -i. One of them was qemu-system, the other was docker-cli because they were forcing me to use Docker-Desktop, which I would not be caught dead using.

So is this accidental, or another predatory move by one of these 'ooh I wish I did not open source' companies (e.g. HashiCorp)? Why don't we all use LXC and ditch this piece of shit?

I could be misunderstanding how Debian-based packaging works. But this is too '''accidental'''. Correct me if I am wrong.

uname -a for context:

Linux pop-os 6.8.0-76060800daily20240311-generic #202403110203~1714077665~22.04~4c8e9a0 SMP PREEMPT_DYNAMIC Thu A x86_64 x86_64 x86_64 GNU/Linux

So I want to implement my own ROFF. I collected this to have a database for me, and everyone else, about ROFF, especially GROFF.

No-lifes at BSD are trying to push away ROFF in favor of Mandoc. I say booya to that. I will implement a 'new new roff'!

Anyways I hope you enjoy this series of documents and datasets. ROFF is really, really sweet. It's the reason we have UNIX.

RIP Lorinda Cherry, she's the author of eqn and passed away not long ago. When I saw her on the UNIX internal documentary I thought she's a secretary --- and I hope you forgive me since 1980s CS was not exactly a knitting circle.

Ossanna was also a key developer of ROFF. He died not shortly after it was developed.

You can find some blog posts of people reminiscing about using GROFF 'mom' package to format their essays and dissertations even! Kinda jelly. I guess when your first PC you are given at 12 has MS Word 2003 installed on it, you don't think much about DSLs for typesetting. I wish I had something to typeset :D

Thanks.

Linux is super fragmented (and generally has been historically).

If more people in Linux agreed to develop, use, and support the same distro--similarly to how most of us use the same kernel--then that distro would probably be better than Windows and more people would move to Linux.

cross-posted from: https://discuss.tchncs.de/post/15147078

> This release adds the following features: > > * Drop heap as part of a housekeeping action > * Retry downloads to workaround flaky network connections > > This release fixes the following bugs: > > * Assume new ME versions are called CSME > * Fix a buffer-overread when parsing invalid CoSWID entity data > * Fix a logic thinko when parsing GUID strings > * Fix downloading files on Windows with libcurl >= 7.77.0 > * Revert back to a simpler syscall blocklist-based filter > > This release adds support for the following hardware: > > * Acer U32 dock > * Luxshare 7-in-1 dock > * Pixart models 2404, 4206, 2440, 2418, 2752, 2840 and 2818 >

Why the second identical disk is more expensive is beyond me (tried with 1TB Samsung 970 EVO Plus NVMe PCIs).

Rook is a lightweight, stand-alone, headless secret service tool backed by a Keepass v2 database. It provides client and server modes in a single executable, built from a reasonably small (auditable) code base with a small and shallow dependency tree - it should not be challenging to verify that it is not doing anything sketchy with your secrets.

Reasonable auditability, the desire to use KeePass files, and to do so through a headless tool that doesn't spawn off the better part of a DE through otherwise unused services, were the main motivations for Rook.

You might be interested in Rook if one or more of these are true:

• you use KeePass v2-compatible tools to store secrets already
• you are not running a DE like KDE or Gnome (although Rook may still be interesting because of secret consolidation)
• you prefer to minimize background GUI applications (KeePassXC is excellent and provides a secret service, but doesn't run headless)
• you run background applications such as vdirsyncer, mbsync (isync), offlineimap, or restic, or applications such as aerc that can be configured to fetch credentials from a secret service rather than hard-coded in a config file.

Pre-built binaries for limited OS/archs are built by the CI, and Rook if available in AUR. There's an nfpm config in the repos that will build RPMs and Debs, among others. I consider Rook to be essentially free of any major bugs and fit-for-purpose, although I welcome hearing otherwise.

Utility scripts in zsh and bash are available for providing autotyping and entry/attribute selection using xdotool, rofi, xprop, and so on; these are YMMV-quality.

Changes from v0.1.1 are:

Added

• one-time pin soft locking
• installation instructions for distributions that have rook in a repository
• more of the special autotype {} commands are supported (backspace, space, esc)

Changed

• getAttr adds a little delay before typing, allowing initiator tools (like rofi) to close windows before text is output
• cleans up code per golint/gochk

Fixed

• an autotype bug in outputting literals

Something tells me Fish is not a capable login shell? It was in /etc/shells, but that does not mean it's a login shell right? Would any shell with job control be a login shell? I'm really scared to logout! Any help is appreciated.

PS: What happens if I choose a shell with no job control whatsover, like Marsh, the shell I've been making lately (it has JC, but let's say it doesn't!) a my login shell after force-adding it to '/etc/shells'? What a design flaw! Or is it?

> We test the Linux-first, all-AMD Sirius 16 laptop, discuss the new Hyprland release, and share a few stories from our recent trip.

About 50% of the time, if I choose sleep, it turns back on as soon as it shuts down. This can happen a couple times in a row. Other times, it sleeps normally and only comes back on with keyboard input. I’ve looked at running processes and there doesn’t seem to be anything I dual happening at the times it starts back up. Any ideas?

Hi all,

I'm visiting a relative that has a Google WiFi system with multiple access points. There's an access point literally right next to me that I can see in the KDE BSSID list with 100% connection strength.

For some reason, it's instead picking a BSSID with only 60% strength. Does anyone have any thoughts on why it's choosing this access point instead of one of the others? Is this something the Google WiFi controls/suggests to the laptop, is something bugged, or is there a good reason Linux might be choosing this particular access point?

EDIT: It turns out the access point placement was actually just really bad, and the access point in question was not even making it to the rest of the LAN... The speed difference between my phone and laptop seems to be just that, something to do with a difference between the framework and the Pixel's wireless cards (or drivers). Even with everything corrected, the Pixel is significantly out performing the framework.

Does anybody know how that's going? It's been 2 years.

Hey. Just for fun, I wanna make a Tumblr blog where I introduce every POSIX utility listed in IEEE 1003.1 XCU. I know about the reputation of Tumblr and I think it is a neat thing to do, some kid may stumble upon the blog and know what POSIX is.

So I want every utility to have a Moe mascot, but I am

1- Not an artist; 2- Lack the funds to hire an artist;

so I was wondering, is there a way I can generate random moe girls? It's just for 'lark' it does not need to be super detailed.

(Keep in mind that I don't have any money or the access to international banking necessary to register on DALL-E or any paid service).

Thanks.

cross-posted from: https://programming.dev/post/9907720 >The SSH port is 22. This is the story of how it got that port number. And practical configuration instructions.

I just noticed, that my SSD is almost full and I think it is because of all the zypper packages I got installed. I've got another ~100gb SSD thats just for stuff (mounted unter "Misc" says it all) and would like to move some (or all?) of the packages like vscode, podman or other stuff on that second SSD. Is there a way to do that with zypper without removing and installing them again under the new path?

😱

v0.1 was released recently