[Discuss] On rebooting, Linux, Emacs, etc.
> It's not a bad practice to reboot whenever you change a system, whether > this is configuration changes or OS updates, in order to test those > changes. More subtly, until you reboot, kernels and non-terminating processes will still be the old code, so you haven't fully updated your operating environment. That's especially significant for security fixes. > I don't like to reboot because I have stuff in progress. Such as an > emacs session with lots of buffers open. There are Emacs add-ons that keep track of what files are in buffers, etc. Really, you shouldn't have anything "live" on your computer that you can't reconstruct quickly because your system could crash at any moment. People are less aware of this now (having Linux run for 100 days continuously is common, as opposed to early Windows, which would crash every day), but it's still a risk. > That said, I kill my web browser frequently, which reverts it to the > same starting state each time, removing all history and cookies and > storred who-knows-what. I suspect most people would find their browser > tabs the hardest part about doing a reboot. I use Firefox. Killing it does *not* remove history, cookies, or cache, you have to do that explicitly. OTOH, if you have it configured correctly, it doesn't loose the tab/window configuration either. Conveniently, I can clear the cookies without losing the tabs/windows. > When I was an undergrad, Emacs was considered huge, a burden to the > multi-user Sun workstations in the computer lab. Today, compared to a > web browser, Emacs is tight and efficient! I know a guy who back in the Sun workstation days disdained Emacs (he used Micro-Emacs) because it sucked up 5 *megs* on the disk! And that was a reasonable complaint in those days. Dale ___ Discuss mailing list Discuss@driftwood.blu.org https://driftwood.blu.org/mailman/listinfo/discuss
Re: [Discuss] ssh issue
> ssh moylan@cmp1 > > asked if i really wanted to connect, i said yes, and then > was asked for moylan's password. an incorrect password > prompted a second request followed by a correct password. > the window then locked up. This probably isn't your problem, but: I see that the failure shows up immediately when you should have successfully logged into the account. So one failure mode is that the .bash_login or some other part of user-session-startup is hanging. So check whether the same failure pattern is seen when logging in to a different account on the same host. Dale ___ Discuss mailing list Discuss@driftwood.blu.org https://driftwood.blu.org/mailman/listinfo/discuss
Re: [Discuss] On rebooting, Linux, Emacs, etc.
On 6/23/24 07:48, Dale R. Worley wrote: There are Emacs add-ons that keep track of […] Emacs itself already does this reasonably well. If I have a crash I already lose essentially no "work", but I do lose context. I run shell sessions in emacs buffers, and I really like being able to search back through what I have done. I like not just the files I was editing to be opened again, but the state of my editing of them, where is the cursor?, what is the selection?, and is it actually selected? Do I have a keyboard macro defined? What man pages are open? How are things physically laid out? Etc. There are clean-desk bosses who poo-poo such concerns and I am sure there are elaborate emacs add-ons that try to reproduce much of that. I prefer to decide when I quit my emacs sessions. That said, I kill my web browser frequently, which reverts it to the same starting state each time, removing all history and cookies and storred who-knows-what. I suspect most people would find their browser tabs the hardest part about doing a reboot. I use Firefox. Killing it does *not* remove history, cookies, or cache, you have to do that explicitly. *Mine* does. I set up Firefox the way I want it, and when I run my Firefox script (usually from a menu item, regular Firefox menu item is hidden) it first blows away Firefox's settings files, it copies in my pre-done versions, then starts Firefox. And when Firefox exits, it does all of that again. (That way just in case Firefox gets occasionally run without my script, the result is similar.) It is possible Firefox is saving away things in places I don't know about, but I suspect not. -kb ___ Discuss mailing list Discuss@driftwood.blu.org https://driftwood.blu.org/mailman/listinfo/discuss
