Linux

48648 readers

1152 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Do you have a more complicated shell history scheme than the distro default? (lemmy.world)

submitted 6 months ago by [email protected] to c/[email protected]

19 comments fedilink hide all child comments

I've used distrobox more and more and am at the point where I need to start saving and integrating history differently. Or like, when I'm installing and building something complicated, I need to start saving that specific session's history. I am curious what others might be doing and looking for simple advice and ideas.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 6 months ago (1 children)

For me, it is not about "lost history." It is about contextual history and knowing if some tool I built in a distrobox uses only dandified, pacman, aptitude, portage; or if it also uses venv, conda; or if there was some install script.

It would be nice if I was on a stable kernel to avoid such a dependency salad, but that is not within the scope of playing with the latest AI toys where new tools and exploring new spaces is constantly creating opportunities to explore.

It would be nice if I was some genius full stack dev that could easily normalized all the tools under a single dependency containerization scheme, but that is not within my mental scope or interests at the present. For most AI tools, I follow the example given and only add a distrobox container as an extra layer of dependency buffering from the host. The ability to lazily see the terminal history for each of those containers is a handy way to see exactly what I did months ago.

[–] [email protected] 2 points 6 months ago

Thanks for your insight ! Even though I didn't really get everything, but It seems there is a specific use case !

Maybe overtime with more experience I will get there and have a better understanding of what you meant with contextual history.