I'm a big fan of the terminology terminal.
Having just switched from Arch to Ubuntu, I installed it again and when I turned on transparency it closed down and restarted with nothing but the title bar and a completely transparent window. No input was accepted - nothing.
Just a completely transparent window.
The only solution to get it back to opaque and working is to delete it's config file and restart it.submitted by /u/kalolparty
Hey everyone, you may remember I made a post not too long ago. I'm taking an online class for the Linux command line, and I have another question that I'm having issues with. I'm giving question 2 for context, but number 3 is the real problem for me. Here it is:
This is directly copy/pasted, and I've had issues understanding this teacher in the past. I do understand creating aliases, and pipelines. I believe I understand redirecting the output to the end of a new file with heads and tails. However, he does not elaborate on what he means by the middle of the day. Also, the part about executing the command three times I don't understand at all. I apologize for my lack of understanding, but I've had issues basically trying to learn the fundamentals myself. I guess, my issues are more so about what exactly he means, and if I figure that out I can figure out the necessary commands. Any help what-so-ever is appreciated.submitted by /u/tonelocMD
We are all aware of the serious issues that these supposedly security enhancing technologies bring. So serious, in fact, that multiple parties have sought to disable or neutralize these technologies with varying levels of success (which is excellent work).
But here's an idea: instead of disabling or neutralizing these hardware components, why not attempt to FREE them so we could actually USE them as intended?
This is where the seL4 microkernel would come in handy. It is a formally verified microkernel - there is a formal and robust mathematical proof that shows that the semantics of its C code are implemented correctly against its abstract specification. That means no buffer overflows, dangling pointers, stack smashing, etc.
What makes seL4 actually USEFUL in this context is that it is designed to be real time operating system kernel (yes! no joke!), as well as being the world's fastest microkernel (drools). And, its licensed under the GPLv2.
I want to know what other people think about this.submitted by /u/DESTRUCTOCORN