Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
[SOLVED] - it turns out that the driver I thought I needed to use, it8718, was only one of the drivers detected by sensors-detect (or detect-sensors, whatever), other one I've missed was actually called just "coretemp". I thought it was a label, not an actual driver. My sensors.conf hadn't a section for such driver though. I've googled a
Not to be confused with ROFL.
Fbrun is quite nice, does what is supposed to, but the history corruption is quite disappointing.
Gmrun looks nice, but is terribly limited, you can't launch a command with any parameter, "foobarizer /path/to/file --foo --bar" becomes just "foobarizer." Yet it seems somewhat noticeably slower than FBrun.
I thought I could have an improvised replacement with something like bash -c "$(zenity --entry)", but it's...
Posted 07-10-2019 at 01:18 PM bythe dsc (linux-related notes)
Updated 07-10-2019 at 01:20 PM bythe dsc
At least that's what apparently happened to me.
On Unix' stack exchange I've found this handy way of recovering it, partly at least, if you happen to have another terminal open, from before the wipe-out:
Code:
history | cut -c 8- > histback_user1.txt
The person who gave this tip suggested doing it in "every terminal", but I believe it would just overwrite it completely for whatever number of times one did it, with the simple ">." In order...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
