I am using this myself in Android app, where you can write files only inside /data/data/your.app.id/
So naturally, if you want to publish a different app, your.app.id will be different, so you need to recompile all your Linux tools that you bundle inside your app.
If you are not running your Linux tools on Android, you’d probably be better off using Docker or a chroot.
--prefix=$(pwd) is resolved at compile time. If you move your compiled .so files to a different directory, they stop working.
Do you know how to build portable executables?
configure --prefix=/proc/self/pwd
It even works in .so files and libtool.
Browse Linux credits for some funky names. My favorite is Jos Vos.
killall kdeconnectd ; kdeconnect-cli -l
Fixes connection problems instantly. Yeah, I’ve put that into my crontab.
Written in hand-optimized assembly with individual implementation for every CPU on the planet, with integer division function in 10000 lines of code impelented with XOR and bit-shifting which is somehow 0.3% faster than CPU built-in division operation.
I’ve recently used Codeberg. It’s online about two hours per day.
TreeView is designed as an afterthought. Some manager at MICROS~1 was like ‘ah yes we need an expanding nested list widget by tomorrow’ and they mutilated text edit box to draw text lines that expand when you click them. It does not have keyboad focus. It can only be operated with a mouse. It does not have shadow or raised widget borders. It has black text on white background, while every other widget has Windows Gray background.
The proper UI would be a separate button for each label, like multiple hierarchical combo boxes.
When you open a serverless website in your browser, it becomes a regular app.
More like garbage dispenser.
Pro C++ coders don’t use delete, they call abort()
Justice for the 5.25" floppy disk! It had an actual hole inside, which would fit your finger! You could see it’s a disk and not a weird shaped square box, and you could hear it’s rotating.
That corner cutout is grossly exagerrated. In the actual floppy disk (which is also not floppy anymore) the cutout is tiny.
https://man7.org/linux/man-pages/man3/mbsrtowcs.3.html
https://man7.org/linux/man-pages/man3/strxfrm.3.html
https://man7.org/linux/man-pages/man3/wcstold.3p.html
https://man7.org/linux/man-pages/man3/wcscoll.3p.html
wcsoll in the picture is an error, unless it’s Welsh.
Plasma, with the taskbar on the side, and 15 virtual desktops.
Nope. The server receives UDP packet from WiFi and sends reply over Ethernet, which simply gets lost in your router. From the Linux side there’s no error, it sent the packet somewhere, and what happens next is your router’s problem.
It’s perfectly possible on Linux to have several network adapters with the same IP address, or several default routes.
Most server applications will listen to 0.0.0.0 address, which means all network interfaces. Any incoming TCP connection will remember it’s network interface, and the server will send responses to the same interface.
This will not work for UDP connections, and for outgoing TCP connections - they will always choose the network interface with the lowest metric, which you can print with ip r command.
This does not include advanced techniques like bridge or bonding or iptables routing - you need to run special commands in the terminal, which you cannot do just by clicking your mouse in system settings app.
Green paint will be extra $2000.
The executable will search for .so files not inside predefined paths like /usr/lib but inside it’s current directory. You may theoretically put
.as an argument toconfigure, but it converts that into an absolute path, snd libtool and linker fail when encountering relative paths inside shared library dependencies.