1·
3 months agoInstall and run “btop”.
You could scroll down to the screenshots on the GitHub page, but I had a friend recommend btop to me and seeing it for the first time running on my own machine was an experience. Highly recommend.
- 0 Posts
- 29 Comments
Joined 1 year ago
Cake day: August 4th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
10 year old bug?
What are they talking about, that bug report is from 2014‽
… Fuck
“I was referring to open book reader…”
The lack of capitalization, and the project name that could just as easily be a descriptor, made me miss it at first too.
"The Open Book is my long-standing attempt to design a comprehensible and accessible e-book reader that you can build yourself (or at least have manufactured affordably). The current edition is something I’m calling the “Abridged” or “Developer Preview” edition. It’s designed to be incredibly simple: there are 7 through-hole and 14 surface mount components, nearly all in a chunky 1206 package that’s easy to hand solder. The tradeoff is that it has no LiPo charging circuit; instead it uses AAA batteries, making it a bit more chunky than previous versions of the book.
The goal with this version is to get hardware in hands so we can start hacking on firmware."
https://www.oddlyspecificobjects.com/projects/openbook/
So:
- This is a hobby / project of love
- The current focus is on hardware
I’m sure that the eventual plan is to support ePub.
I’m not sure it will ever get there, because it’s not a well resourced project, but I personally don’t like criticizing one person’s efforts, which they are making freely available.
It’s at least gotten a bit better.
There was a time when Photoshop and other programs used a copy-protection scheme that overwrote parts of grub, causing the user not to be able to boot Linux or Windows.
They knew about it, and just DGAF. I don’t remember their exact FAQ response, but it was something along the lines of “Photoshop is incompatible with GRUB. Don’t dual boot if you use Photoshop.”
Grub still has code for BIOS based installs that uses reed-solomon error correction at boot time to allow grub to continue to function even if parts of its core.img were clobbered by shitty copy protection schemes for Windows software.
I was helping you there and asked you to back up configs and post some information.
Once you’ve done that I think actually getting things back the way they should be will go fine.
I didn’t know TWAIN, so I looked it up and am glad I did:
TWAIN: Technology Without An Interesting Name
I tried to solve these cross-distro compatibility problems in a generic way with this “standard”, more years ago than I’d like to think about:
https://www.supergrubdisk.org/wiki/Loopback.cfg
If someone wants to come up with a bootloader agnostic solution rather than one tied to grub, like an extension to Bootloader spec , https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ , I’d be happy to evangelize it and add support to grub for using it.
I’m not aware of any other bootloader that supports reading a config file that exists within an iso though, and secure boot support may add additional complications.
Bottom line:
I feel like we could relatively easily get to a point where every Live iso that actually supports loop booting can just be added, as a file, to your USB drive (from Windows, or your android phone even) and be detected at boot in a nice little menu, no editing of config files needed.
I don’t have the time or spoons to get the Linux community there alone, but if people are interested in helping I’m more than happy to pick this up again.
(Note: Please don’t blindly suggest “Just chain load the iso!” Things aren’t that easy, unfortunately).
Like me, that user wants to use ISO-8601 format for dates.
I didn’t see that option in the screenshot. Anyone know if that’s possible in this Beta?
What version of Ubuntu are you using?
What is the output of the following command?:
dpkg -l | grep grubIf you urgently want your grub menu to default to the first entry that can be done first, but unless that’s needed I’d prefer to get to the root of the problem(s) and get a proper fix.
This should get you back to defaults:
sudo cp /usr/share/grub/default/grub /etc/default/grub && sudo update-grubAt some point you definitely did accidentally write to /etc/default/grub when you meant to write to /boot/grub/grub.cfg.
There’s no shame in that; Grub’s configuration process is very confusing and counter-intuitive.
Everybody who has used Linux long enough has stories of breaking their systems in sillier ways, and this didn’t even really break your system 🙂.
Pulseaudio used features of sound cards (most prominently the hardware read pointer) that ALSA/dmix alone never used.
ALSA/dmix could allow you to get the same power savings as pulseaudio if you set the hardware ring buffer size to, say, 2 seconds.
And that would be fine of you were just playing some music, but if you were also chatting and wanting to get prompt notification sounds they would always be delayed between 0 and 2 seconds depending on where the hardware read pointer happened to be when the system tried to play a notification sound.
ALSA/dmix could also allow you to set a tiny buffer size. Then your music would play, and your notification sounds would play promptly too. But if you were just playing music your CPU would never be able to go into the lower power sleep states because it would need to wake up every centisecond to service the tiny ring buffer.
That would kill your battery life.
Pulseaudio’s (terribly named) “glitch free” audio feature was the first solution for Linux that allowed you to get power savings and low-ish latency. Your mp3 player filled up the ring buffer once every two seconds, and if a notification came in pulseaudio would look at where the hardware read pointer was, take the contents of the buffer that was just about to be read, and mix the notification sound into it, writing the newly mixed sound data to the buffer just before the sound card read it.
So, from the user’s perspective nothing interesting seemed to happen, but they get better battery life and things like notifications or game sounds work like they expect them to.
ALSA drivers would commonly advertise support for accurately and precisely reporting the position of the hardware pointer, but since nothing actually used that info before, many drivers gave incorrect results, which would only cause problems when using pulseaudio.
No.
This is a vulnerability which allows bypassing secure boot protections. You have already manually bypassed those protections by disabling secure boot.
Please be sure to check that the smart switches you have space heaters plugged into are rated for that many amps.
…unless the videos have captions, in which case you absolutely can.
View the transcript, search for something, click what you found and boom: You’re at that precise moment in the video.
For literal grep, use something like NewPipe to download the subtitle file.
USB block devices containing mountable filesystems (on Desktop systems) can generally have those filesystems mounted and files written to them by regular users; But the block device itself stays only root writeable.
So, you need root privileges either way.
(Going from memory, but also decently confident)
Until you use a system that doesn’t have a ~/.bashrc , and now your tab completion helpfully expands “~/.ba[TAB]” to “~/.bash_history” .
Every “terminal app” is a terminal emulator, because non-emulated terminals are physical pieces of hardware.
So you are already using a terminal emulator, I’d guess Gnome Terminal, and it’s a fairly full featured modern terminal emulator (in my opinion at least).
Fun fact!
Teletypes predate “computers” and were used for efficiently transmitting and recording text.
Here is a purely mechanical teletype from the 1930s being used to interface with a modern Linux machine:
Just keep “hollywood” running in another terminal at all times.