#Debian Android
Explore tagged Tumblr posts
conatic · 6 months ago
Text
~ $ cat prootdebian.sh
#proot-distro login debian
proot-distro login debian --user masterli --shared-tmp
2 notes · View notes
despertarsabiendo · 4 months ago
Text
Linux: un sistema operativo potente y gratuito
Linux: El sistema operativo que usas sin saberlo Desde la llegada de los sistemas operativos, las computadoras se volvieron más accesibles para el público general. Con Windows y sus interfaces gráficas, su uso se masificó hasta el punto en que hoy casi todo el mundo tiene un ordenador en casa. Pero hay un sistema operativo que probablemente usas todos los días sin siquiera notarlo: Linux. A…
Tumblr media
View On WordPress
1 note · View note
virtualgirladvance · 10 months ago
Text
Anyone know how to reimage a laptop with an iPad or Android phone being your only working device(plus the necessary adapters and flash drives)? I'll accept any os at this point. Or even how to go from a base void install with nothing but kernel and terminal access to something useable for someone who went from all in Linux user to tired windows copef
Kinda in a desperate gtfo out of current living space and getting my laptop to work would be an amazing step to getting help, work and keeping myself together rn
Please share and tag your computer savvy blogs
Sorry for another os tag spam but
@foone @ubuntu-official @debian-official @arch-official @puppylinux-unofficial @puppylinux-official @lilithtransrights @xenasaur @catboybiologist @transhuman-priestess @predatory-lesbians-too @demilypyro @estrogenesis-evangelion @nataliaflintlock @coelii @k1nky-r0b0t-g1rl
55 notes · View notes
q4os-tde-official · 2 months ago
Text
Android 16 has some cool features
like a Debian environment :3
Tumblr media
add in the ability to connect to an external display, and a bluetooth keyboard (dunno if the display thing is a stock android thing or just oneui), and that basically means you can use any android device as a PC
9 notes · View notes
autolenaphilia · 10 months ago
Text
Currently using Debian 12, with KDE Plasma, which i previously used. But i had problems running plasma last year, with repeated random plasmashell crashes. I could even repeatedly cause plasmashell to crash by removing a second panel/taskbar.
But i returned to plasma to check out running wayland, i've previously used x11-based desktops and even ran plasma on x11. And it turns out plasma is actually more stable on wayland, at least the 5.27 version debian 12 ships with. Which is not something i expected, because all the talk of wayland not being fully there yet, which iirc is why i defaulted to using x11 earlier despite plasma's wayland session. I can still cause plasmashell to crash on x11 by removing a panel, but not on wayland, and the random crashes don't happen either on wayland either. It's a smooth reasonably bugfree experience that lives up to debian's reputation for stability.
I'm running older versions of KDE Plasma and of most things on this OS, because that's the Debian way, but who cares. if the software works I don't care if it's old, and with Debian I don't have to worry about an update breaking my system, and don't have to worry about frequent updates in general, which is a plus in my book (don't judge me, I have Windows update trauma /j).
Tumblr media
my current desktop, the theme is Sweet KDE and the wallpaper is from this post by greekie-via-linux
So now finally KDE Plasma works good for me, without all the crashing. And I'm slowly becoming a fan. It's very customizable, KDE provides a traditional desktop layout by default (which i prefer) but so customizable that you can turn it into almost anything you like. It's defaults might borrow from the windows 95 to 7 desktop paradigm, but Windows never gave users this much control.
It's pretty looking, it has all the eye candy effects and animations you want, but not too heavy on the ram useage (the performance is actually comparable to xfce) , and you can turn the effects off thanks to the aforementioned customizability. And it provides all the programs you need for a fully featured desktop environment, everything from basic stuff like a terminal emulator and file browser to a GUI package manager that supports basically all packaging formats. Neither mate or xfce has the latter, for example, when I ran debian with xfce i had to manage my flatpaks through the terminal.
Maybe even too many programs. KDE makes a lot of programs, and i'll probably never switch from mozilla firefox and thunderbird to kmail, falkon or konqueror. Though to be fair, KDE does develop a lot of programs that are first-rate in the linux world, practically without competition. And i personally find KDE connect to be extremely useful. It syncs your android phone with your desktop or laptop computer and it's awesome. Once I learned how to allow it through my firewall, I can see my SMS messages on my computer and type them with an actual keyboard on my computer, it's great. And It works on other desktop environments and even on windows.
18 notes · View notes
utopicwork · 10 months ago
Text
After the prototype drops we're going to set up a proper gofundme/kickstarter/what have you to get us funding for the beta and 1.0.0 so I'll work on what the goals are for that but I think primarily its going to be: getting a native app on Android, iOS, Windows, Mac and various Linux platforms other then Ubuntu (since it will be developed Ubuntu/Debian first), getting nodes out to people to expand the network and fleshing out the application layer/dev experience
12 notes · View notes
good-fwiend-in-wome · 8 months ago
Note
Plain arch or a distro based on it? :3c (No judgement, I think that's silly. We use NixOS, Garuda, Debian (via proxmox), and working on Qubes. Oh, and Android, plus Alpine via iSH.)
well okay technically i use EndeavourOS btw, but really it's just arch for people with better shit to do than learning to install arch lol. I'm honestly really surprised how much easier to use arch is than people make it out to be
8 notes · View notes
digitaldetoxworld · 4 months ago
Text
Building Your Own Operating System: A Beginner’s Guide
An operating system (OS) is an essential component of computer systems, serving as an interface between hardware and software. It manages system resources, provides services to users and applications, and ensures efficient execution of processes. Without an OS, users would have to manually manage hardware resources, making computing impractical for everyday use.
Tumblr media
Lightweight operating system for old laptops
Functions of an Operating System
Operating systems perform several crucial functions to maintain system stability and usability. These functions include:
1. Process Management
 The OS allocates resources to processes and ensures fair execution while preventing conflicts. It employs algorithms like First-Come-First-Serve (FCFS), Round Robin, and Shortest Job Next (SJN) to optimize CPU utilization and maintain system responsiveness.
2. Memory Management
The OS tracks memory usage and prevents memory leaks by implementing techniques such as paging, segmentation, and virtual memory. These mechanisms enable multitasking and improve overall system performance.
3. File System Management
It provides mechanisms for reading, writing, and deleting files while maintaining security through permissions and access control. File systems such as NTFS, FAT32, and ext4 are widely used across different operating systems.
4. Device Management
 The OS provides device drivers to facilitate interaction with hardware components like printers, keyboards, and network adapters. It ensures smooth data exchange and resource allocation for input/output (I/O) operations.
5. Security and Access Control
 It enforces authentication, authorization, and encryption mechanisms to protect user data and system integrity. Modern OSs incorporate features like firewalls, anti-malware tools, and secure boot processes to prevent unauthorized access and cyber threats.
6. User Interface
 CLI-based systems, such as Linux terminals, provide direct access to system commands, while GUI-based systems, such as Windows and macOS, offer intuitive navigation through icons and menus.
Types of Operating Systems
Operating systems come in various forms, each designed to cater to specific computing needs. Some common types include:
1. Batch Operating System
These systems were widely used in early computing environments for tasks like payroll processing and scientific computations.
2. Multi-User Operating System
 It ensures fair resource allocation and prevents conflicts between users. Examples include UNIX and Windows Server.
3. Real-Time Operating System (RTOS)
RTOS is designed for time-sensitive applications, where processing must occur within strict deadlines. It is used in embedded systems, medical devices, and industrial automation. Examples include VxWorks and FreeRTOS.
4  Mobile Operating System
Mobile OSs are tailored for smartphones and tablets, offering touchscreen interfaces and app ecosystems. 
5  Distributed Operating System
Distributed OS manages multiple computers as a single system, enabling resource sharing and parallel processing. It is used in cloud computing and supercomputing environments. Examples include Google’s Fuchsia and Amoeba.
Popular Operating Systems
Several operating systems dominate the computing landscape, each catering to specific user needs and hardware platforms.
1. Microsoft Windows
 It is popular among home users, businesses, and gamers. Windows 10 and 11 are the latest versions, offering improved performance, security, and compatibility.
2. macOS
macOS is Apple’s proprietary OS designed for Mac computers. It provides a seamless experience with Apple hardware and software, featuring robust security and high-end multimedia capabilities.
3. Linux
Linux is an open-source OS favored by developers, system administrators, and security professionals. It offers various distributions, including Ubuntu, Fedora, and Debian, each catering to different user preferences.
4. Android
It is based on the Linux kernel and supports a vast ecosystem of applications.
5. iOS
iOS is Apple’s mobile OS, known for its smooth performance, security, and exclusive app ecosystem. It powers iPhones and iPads, offering seamless integration with other Apple devices.
Future of Operating Systems
The future of operating systems is shaped by emerging technologies such as artificial intelligence (AI), cloud computing, and edge computing. Some key trends include:
1. AI-Driven OS Enhancements
AI-powered features, such as voice assistants and predictive automation, are becoming integral to modern OSs. AI helps optimize performance, enhance security, and personalize user experiences.
2. Cloud-Based Operating Systems
Cloud OSs enable users to access applications and data remotely. Chrome OS is an example of a cloud-centric OS that relies on internet connectivity for most functions.
3. Edge Computing Integration
With the rise of IoT devices, edge computing is gaining importance. Future OSs will focus on decentralized computing, reducing latency and improving real-time processing.
4. Increased Focus on Security
Cyber threats continue to evolve, prompting OS developers to implement advanced security measures such as zero-trust architectures, multi-factor authentication, and blockchain-based security.
3 notes · View notes
abbiistabbii · 11 months ago
Note
Hey sorry I saw your post about Linux being better/just as good as Windows for gaming PCs, and I was wondering which type you’d recommend downloading for a mid-tier PC? (I’m not super tech savvy tbh but I’m a fast learner and would rather download Linux at this point than Windows after all the shit it’s done lately). Also, did not know Android uses Linux that is cool!
If you're a beginner, either one of the Linux Mint flavours or one of the Ubuntu flavours, depending on how mid-tier we're talking about. Mint is based on Ubuntu but they're both ultimately based on Debian, which is the most stable and easy to use (in my experience) Distro. You'll find this a lot that a lot of distros are based on other distros, but if I were to talk about distros, the best ones tend to be debian based.
So Linux Mint is made to be as user friendly as possible and have most, if not everything, working out the box, and it's great, but it does use an older version of the Kernel so you need to bare that in mind (but as a beginner you don't need to worry too much, everything will still work). It comes in three versions: Cinnamon (using the Cinnamon desktop), MATE (using the Mate Desktop) and XFCE (using the xfce desktop). On a mid-tier PC any of these will work, even the heaviest of them has a recommended ram of 4GB but if you know your PC you might wanna try MATE (about 1GB ram recommended) or XFCE (512 MB).
However I would recommend Ubuntu (it's what I'm using rn). It's what Linux Mint is based on and is just as user friendly as Mint but with the big difference being it uses a newer Kernel version and has more flavors using different Desktop Environments and for different uses. The flavors however are on different websites but more or less work closely with Ubuntu itself.
Vanilla Ubuntu used Gnome as it's default which is okay, some people like it, but I don't and nor does a lot of my friends. Different flavors have different requirements and levels of usability but again, 4GB is enough to run any flavor. Other Flavors include:
Kubuntu: this is the one I use, and in my option it's better than Vanilla. It used KDE and it's suite of apps which are both user friendly, wide ranging and really nice looking. KDE is quite resource intensive (again that's not saying much compared to windows) but if you have a mid tier PC with more than 4GB ram, it should run fine and I recommend it. I'm a big KDE fangirl.
Xubuntu: This is one I used in the past. Xubuntu used XFCE which is designed to be lightweight without sacrificing functionality. It's not as flashy, but it's easy to use, functional, and great for lower-powered computers or just people who wanna save on computing power.
Ubuntu Cinnamon: This flavor uses Cinnamon (which the "main" version of Mint uses) but with Ubuntu as the distro. I used Cinnamon as my desktop when I used Mint and I loved it. It has all the functionality of Gnome with all the ease of use and flashiness of KDE, so if you try out Cinnamon on Mint but like Ubuntu, try it out.
Lubuntu: This is the lightest of Ubuntu flavors. It's light enough that it's ARM version can run on a Raspberry pi. This was designed for computers with not much power like those old netbooks (remember those?) and it's not as flashy or functional, but it's a good option if your computer is a potato.
Ubuntu Budgie: This is the one I know least about because I have never used budgie. I checked it out on distrosea but other than that all I know is from people who have tried it. Some like Budgie (which uses the Budgie desktop) some don't, but I think I might need to check it out before I pass judgement.
Each of these versions are distributed from their own websites so be sure to google.
As for gaming I would recommend that after installing it, if you have a separate graphics card, install the drivers either from the driver manager or from the website itself. Steam runs on Linux and follow the instructions from steam on how to activate Proton.
Happy nerding.
7 notes · View notes
conatic · 6 months ago
Text
curl -sL https://raw.githubusercontent.com/01101010110/proot-distro-scripts/main/debian-x11-app.sh -o debian-x11-app.sh && chmod +x debian-x11-app.sh && ./debian-x11-app.sh
0 notes
firstinspires · 4 months ago
Text
PSA for FTC/FRC software folks
in previous seasons, the game manual had explicit writing about using the FIRST-provided SDK (the "FtcRobotController" app), but those rules have since been removed from the manual entirely???
I'm not a rules lawyer, but given that the Android NDK exists, it's possible to write your bots in Rust (cough cough please) or other native languages without the world's largest headache!!! I myself am planning on tinkering with this idea in my free time :)
This won't last forever- if you didn't already know, FIRST is unifying the control systems of FTC and FRC under a new system in 2027. They explicitly state the requirement of running on the Linux kernel (specifically they note using the Debian or Ubuntu kernel versions), which would be awesome. You can read their spec here but the actual system has yet to be introduced. But, just judging by their specifications, they intend on exposing a far more flexible system for control methods (via a C/C++ API, as well as official layers for Python and Java aka Kotlin But Worse) which I'm all on board for.
I might consider actually mentoring a season if it means getting to see a Rust-powered bot in FTC
Or maybe I'll just make jokes about bombs, drones, and genocides that FIRST and its sponsors remain complicit to. 🇵🇸
6 notes · View notes
clatterbane · 1 year ago
Text
Oh my. Another thing that I probably don't really need to start messing around with, but couldn't resist. Largely thanks to this person.
I had considered trying to get a couple of less demanding games running on my phone through Termux already. But, for whatever reason it hadn't occurred to me to try Windows emulation. (Possibly because I just rarely use Windows.) But of course you could run good old Wine through Android too. I am interested to see how usable this implementation really is on a touchscreen.
Yes, I do have access to a perfectly good Debian system with uncomfortable chair right there in his office lair. I could just fire up my Pokewilds, etc. there. But, fucking around with this sort of thing is more fun.
11 notes · View notes
daveknowstech · 6 months ago
Text
Where the Android Tablet is today, and what it might become in a post chromebook world..
Tumblr media
There has been a lot of discussion about Google, chromeOS, and the future on this Discord, and this post isn't about that. this post looks at the current state of Android Tablets where they can learn from chromeOS and also where Google might go with this..
To do this I've recently purchased the very large Samsung Galaxy Tab10 Ultra. this is a very big, premium tablet device from arguably one of the biggest Android device manufacturers on the planet. A company whom while the rest of the world forgot about android tablets, carried on and paved a solid lineup of Galaxy Tab products.
The purpose of purchasing this behemoth as two fold. firstly I like big tablets, big real-estate. I take a lot of photos, and having the bigger screen helps a lot editing and working with both photos and videos. The second reason was. Its about the sweet spot for a laptop screen as well. So with the Samsung Folio keyboard, there is a familiarity as a Chromebook user to all of this..
So lets cut to the chase, what has a week using this device to do work been like?
At times it felt just like being on a Chromebook, others its as frustrating as anything.. However its frustrating for the same reasons a Windows User would be frustrated going to a Mac (or Vice Versa). things are not available..
Lets start with the good…
Putting the Samsung Folio keyboard on this tablet, and sitting down at a desk, turning on Dex and working was, because i've been using chromeOS, a seamless experience in the most part. I'm used to the Android experience or the web app experience. The tablet is quick. I'm able to edit Insta360 Videos, or in Lightroom or VCSO.. I get Slack messages and apparently look good in Meet calls because the webcam is where it should be (top middle in landscape mode). the battery has lasted all day and I've been able to do what I need to do (DevOps, Ansible, Terraform, sysadmin stuff)
The processor is more than capable of having 15+ apps running, multiple tabs.. the screen is crystal clear, the speakers are good. However i'd expect all of this, its a premium product (RRP: £800ish) just as I would from a similar priced chromeOS tablet.
However I do think this is the case because of the tablets screen real-estate. personally i think if i had got the Galaxy tab10 plus with a smaller screen, I'd have felt much more constricted in what I was doing..
Compared to the Ipad Pro experience, this is no matter what any tech bro influencer will tell you a huge leap over said device. Being able to actually multi task and run apps (in dex) not full screen alone takes this to a level above the Apple product.
However then there is whats missing.. These as i inferred above are things i've noticed having used a Chromebook as my daily driver for the last 5+ years.
As a huge Linux user on Native platforms and chromeOS, i really missed the Chromebooks Linux shell. this is something I've seen Google are working on with android. Both the full debian runing on the OS with Icons aoppearing when you install Linux apps with GUI's (OnlyOffice for example) which launch independetly of the shell is not a feature to be sniffed at and IMO make the Chromebook one of the best entry level Linux devices available today. Whatever Google have done here, they need to replicate.
I'd also like to see the desktop version of the Chrome browser especially on the bigger scren, the android version of chrome is ok for most things, having the desktop version however should not be a huge leap of development to get this working.. with a huge highlight on PWAs which i use a lot on ChromeOS
Finally there is Dex, I have a love hate relationship over the years with Dex, and the classic version has been my workhorse for the last week. with a keyboard, mouse and external monitor this is more than a workable solution for checking email, slack, meet meetings and even some coding. All the time however i am thinking why not chromeOS?
Dex for its time was a great and groundbreaking idea, and interestingly is the last of many convergence tools over the years, and its always made we wonder why when i plug in a Pixel Phone/Tablet into a USB Hub with a monitor I don't get a ChromeOS like experience.
So what are my thoughts on chromeOS becoming Android based on using arguably the top tier Android experience as my sole PC for a week?
It boils for me into these areas
While ChromeOS will run fine on a 4Gb Arm chip for browsing the web and a few tasks. 8Gb is the minimum you need to start using it properly.. The same will be the same with any new android tablet, for this to work, the 8Gb equivalent needs to be the base hardware, same with processors and storage. Google will need as they did with chromebook Plus to set a minimum spec for these new devices day 1. Or they will cause a lot of market confusion and again get that chromeOS low power second screen device label that they have never shifted from the tech press narrative. This i think has only worked for me because of the premium experience, i think had i gone mid tier i'd have been writing something very different.
The interface and app experience is somewhat comparable, however if Google do put the desktop browser on android as has been suggested they may do, this will make a big difference. OneUI for all its haters, does do a good job of presenting a nice desktop above the Pixel equivalent. Its, dare i say it, more "windows like" and having that as an option interface wise would be a good thing.
Expanding on Interface, the experience presnted to the user of Dex when plugging into an external monitor and adding a keyboard/mouse is important, I would like to see Google work here on something which looks like chromeOS appear when i plug an (lets call it Android Plus) Android Plus device into a hub. a step above dex and a more Usable desktop. this provides huge value ad, and really starts to differentiate Android from Ipad Pro and (i think its called) stage manager. This starts to become an easy drop in replacement for schools, businesses etc while staying familiar and enterprise admins can still do thier thing.
And finally there are things which google should 100% be pulling over from ChromeOS, i think the whole material you type experience is better on chromeOS (although this might just be Samsungs OneUI), the Linux shell experience is another huge thing. Better PWA support and the inbuilt VPN support would be nice too.
All in all a space I'll be hugely interested in over the next few years, if google is serious about making a dent in that lucrative iPad/Pro market it needs to make changes and the convergence of the two OS might actually be the thing which takes the Android OS everyone gave up on on Tablets and the chromeOS only good as a second screen device and makes them the thing you guy to get stuff done..
2 notes · View notes
bored-bi · 9 months ago
Text
so i got Immich [^] working on the homelab as a google photos alternative. super simple to set up, i just made a VM with 4 cpu cores and 6gb ram running debian and installed docker on it. it has a really cool android app that i used to back up all of my photos. the server is saving them to a 2tb hdd and then backing them up to another one every week. im happy to have my photos backed up cuz i didnt have any functional backups before :3 next ill probably come back to the networking course i was doing and then to setting up a vpn
3 notes · View notes
mentalisttraceur-software · 2 years ago
Text
I think it's a really good sign of growth and healing that I'm finding myself increasingly repulsed by the kind of portability extremism that once compelled me.
One of the biggest and worst examples was shell scripts. /bin/sh was the Bourne shell in UNIXv7 (prior to that, there was the Thompson shell, and thankfully I managed to keep my mind cancer from metastasizing further backwards in time to try to achieve compatibility with that shell too). After the Bourne shell, every /bin/sh on every system was a Bourne-like shell, and if you thought that meant you could just write something that worked, take a glance at:
GNU Autoconf's Portable Shell documentation.
Sven Mascheck's various pages.
Paul Jarc's "lintsh" notes.
Ubuntu's "dash"-as-/bin/sh guide.
and others which you can find from there.
Now, a healthy person simply rejects this problem space. But for years, I was obsessed with writing shell scripts which would work on all /bin/sh still in production. It started as a growing annoyance with so many programs depending on bash - I was otherwise happily using a system with a more minimal shell at the time, and the limitations of my beloved Nokia N900 as a pocket Linux device gave me some real reason to prefer "reducing bloat" back then. Of course if it mattered to me, my compassion generalized it to everyone else in the same boat (everyone real or imagined... and in this case, mostly imagined). Then one day in the first year of my career as a software developer I got into a small argument with a coworker about them mandating #!/bin/bash instead of #!/bin/sh in our shell scripts - after he asserted that it was unreasonable to expect developers to remember what is or isn't a bashism, my maladaptive narcissistic cope reflexively kicked into full gear and now I had something to prove.
I still remember bits of that evening after work. It's... kinda horrifying looking back on it, because I was aware of what was happening in my mind. I was aware that I was basically starting to involuntarily, compulsively terraform my own preferences and values about shell scripts, from the modest and real and practical "I just want scripts to run on my N900s (BusyBox ash implementation for /bin/sh), and maybe also my Debian boxes (dash for /bin/sh)" to some perverse "principled" stance with poorly-defined scope which was divorced from any specific concrete goals. I had seen this runaway snowballing of artificial nitpicky values happen in my mind before, and I recognized that what I was doing in my head was feeding it, that it was happening again or that I was making it happen again, and I felt some conflict with that, I could see how it was bad... but back then I didn't know how to do anything about it. I didn't know how to diffuse those wants back then. I could in some technical sense, have chosen to not do it, but I couldn't stop wanting to, and I couldn't stop rationalizing it.
So I became the kind of guy that basically had every caveat mentioned on the above pages memorized. I even went as far as having a Solaris 10 VM, some old Android phones, and a PDP emulator running UNIXv7, so that I could test things not mentioned or not elaborated on those pages. But since it's really costly to remember so much trivia, I only remembered the caveats themselves, not necessarily which shells/systems they applied to. I could tell you off the top of my head "well you see, on some shells, 'set -e' will not affect the code inside functions", but I couldn't tell you which shells - I just had the caveats grouped by
"only matters on systems that no one runs anymore",
"only matters in situations you/we will never need to be compatible with (like Solaris 10's /bin/sh)",
"only matters if you want portability on Windows ports of UNIX-y shell stuff",
"only matters if you want portability beyond just Linux", and
"only matters if you want portability beyond just 'bash'".
I also used to have a little template for shell portability disclaimers that I would add to my shell scripts, deleting/re-adding lines as-needed:
# This script is compatible with Bourne and POSIX shells. # EXCEPT for the following exceptions (last verified on YYYY-MM-DD): # Comments (Appeared in 1981, still not universal around 1987) # Functions (First appeared in SVR2 Bourne shells in 1984) # `mkfifo` (First appeared sometime circa 1984, possibly earlier; unsure) # `test -p` (First appeared in SVR1 Bourne shell in 1983). # `wait` exit status (Missing in Almquist shell until 4.4BSD in 1993) # `hash` builtin (First appeared in SVR2 Bourne shells in 1984) # `type` builtin (First appeared in SVR2 Bourne shells in 1984) # $() is used instead of `` (not supported by some ancient Bourne shells) # `shift` when no positional parameters (broke some old MIPS RISC/os shells) # ${VAR%glob} substitution (Solaris (<= 10) /bin/sh does not support it) ...
That version of me looked at my old esceval.sh with pride, as if it was important or worthwhile. It tries to use modern-ish POSIX shell features but falls back to portable shell if it must. Basically every single line has at least one detail that is a deliberate portability choice. Almost every degree of freedom has been optimized for portability (and then some performance optimization within that) - change almost anything and it's probably less portable.
I revisited "esceval" for the first time in years this past week, and I noticed something really nice. I no longer have enough appetite for this portabiliy stuff. I'm too acutely aware, down to my motivating emotions, that it's a waste of my life. I'm once again in touch with actual concrete use-cases and benefits that have high odds of coming up in my life. I've re-learned to value myself and my goals more than this portability shit.
So I'm going to delete the portability fallback from "esceval.sh". I'm done trying to figure out what the portability fallback looks like for the other esceval pieces that I still want to finish. Unless I'm being compensated better than I can get elsewhere, I'm never again going to lift a finger to support Solaris 10 /bin/sh, or Android phones lobotomized to the point of not having a "printf" command in their shell, or anything else that isn't at least POSIX-compatible shell. And even then I'd suggest implementing that by writing a backpiler from modern shell to older. Maybe I'll answer portability questions if I still remember the answer and can say it off the top of my head - I enjoy helping people after all.
And it goes deeper than that. I'm very done giving Bourne-style shells nearly as much time and effort as I've given them so far. They're good DSLs for redirecting file descriptors and sorta okay DSLs for invoking and managing processes, and that's about it. As an unfortunate practical matter, Bourne-style shell is one of the most widely deployed programming language families, so if the goal is "I want to be able to give this tiny CLI to a coworker so they can run it on their machine with minimal human hassle", it can be nice to have a #!/bin/sh implementation (but so is having a couple statically compiled executables for the common platforms and a cross-compiler ready for the rest, or a Python script, or [...]).
It'll take me some time to figure out exactly where that balance is, and to fully unlearn the various hangups and compulsions that I've built up which motivate writing a /bin/sh script instead of something else, but what I've been doing so far definitely ain't that balance, ain't even close, and now I finally have a strong-enough hunger for breaking free and moving in the direction of that healthier balance.
13 notes · View notes
riczkypratama · 1 year ago
Text
Linux: Mengungkap 5 Fakta Menarik tentang Sistem Operasi Open Source yang Kuat
Linux, sebuah sistem operasi open source yang menjadi salah satu pilihan utama di dunia komputasi modern, telah memberikan kontribusi besar terhadap perkembangan teknologi informasi. Berikut adalah lima fakta menarik tentang Linux:
Tumblr media
1. Open Source dan Gratis
Salah satu ciri khas Linux adalah sifatnya yang open source. Artinya, kode sumbernya dapat diakses, diedit, dan didistribusikan oleh siapa pun. Kebebasan ini memberikan peluang bagi pengembang untuk berkolaborasi dan menciptakan solusi-solusi inovatif tanpa batasan biaya lisensi. Meskipun ada distribusi Linux yang disertakan dengan dukungan dan layanan berbayar, banyak distribusi Linux populer seperti Ubuntu, Fedora, dan Debian dapat diunduh dan digunakan tanpa biaya.
2. Diversitas Distribusi
Linux bukan sekadar satu sistem operasi tunggal, melainkan sebuah keluarga besar distribusi. Distribusi-distribusi Linux, atau disebut "distro," memiliki ciri khas masing-masing. Misalnya, Ubuntu dikenal karena kemudahan penggunaannya, sementara Arch Linux lebih terkenal di kalangan pengguna yang lebih berpengalaman dan ingin mengonfigurasi sistem secara mendalam. Diversitas ini memberikan fleksibilitas kepada pengguna untuk memilih distribusi yang paling sesuai dengan kebutuhan dan preferensi mereka.
3. Dominasi di Server
Linux mendominasi pasar server. Banyak server di seluruh dunia menggunakan sistem operasi Linux karena keandalannya, keamanannya, dan kemampuannya untuk menangani beban kerja yang besar. Apache, salah satu server web terkemuka, umumnya dijalankan di atas sistem operasi Linux. Keberhasilan Linux di ranah server juga menciptakan banyak peluang karir bagi administrator sistem Linux yang terampil.
4. Kernel Sebagai Inti
Kernel Linux, yang dikembangkan oleh Linus Torvalds pada tahun 1991, adalah inti dari sistem operasi Linux. Kernel inilah yang bertanggung jawab atas manajemen sumber daya perangkat keras, penjadwalan tugas, dan kontrol terhadap akses memori. Sifatnya yang modular memungkinkan pengguna untuk menyesuaikan kernel sesuai kebutuhan mereka. Kernel Linux juga menjadi fondasi bagi banyak sistem operasi lainnya, seperti Android.
5. Performa dan Keamanan
Linux terkenal karena performanya yang stabil dan keamanannya yang tinggi. Kebanyakan serangan malware dan virus yang umumnya ditargetkan pada sistem operasi Windows memiliki dampak yang lebih terbatas pada Linux. Selain itu, siklus pembaruan yang cepat dan komunitas pengembang yang aktif membuat kerentanan keamanan dapat segera diatasi. Kinerja yang efisien juga membuat Linux menjadi pilihan populer untuk perangkat dengan sumber daya terbatas, seperti server, router, dan perangkat Internet of Things (IoT).
Linux terus berkembang dan berinovasi, menjadi kekuatan dominan di berbagai bidang teknologi. Dengan basis pengguna yang besar dan komunitas pengembang yang aktif, Linux akan terus memberikan kontribusi signifikan terhadap dunia komputasi dan teknologi informasi.
2 notes · View notes