From: firstname.lastname@example.org To: 9fans <email@example.com> Subject: [9fans] Despite being called a fork, is 9front similar to how Linux distros work? Date: Mon, 17 Jan 2022 17:04:44 -0500 [thread overview] Message-ID: <16424570840.4902C04.firstname.lastname@example.org> (raw) [-- Attachment #1: Type: text/plain, Size: 1303 bytes --] Hello. I just found out about Plan 9 and I'm trying to understand more. I see that 9front is often called a fork of Plan 9. However, reading the FAQ and the 9front wiki, the authors seem to often "conflate" both. I mean, I don't really understand what's written, but it's like the instructions for some stuff isn't really meant specifically for 9front, but rather Plan 9. Besides that, reading what's different in 9front from Plan 9, it mentions drivers and programs. That makes me think that while 9front is called a fork, it doesn't really differ from Plan 9 in how it works and is structured, much like a Linux distro may change some things about the Linux kernel, but in essence they're the same and easily interoperable. Is that right? I know it's subjective, but a fork implies to me that the goals and methods of the forking developers are different from the original software, maybe eventually leading to a completely contrasted software, with different environment, tools and inner workings, like Android is to Linux. That's why I wanted to clarify this question. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T395156d4f2b00cde-Ma8a28f35f9d907ccf2f413ff Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 1877 bytes --]
next reply other threads:[~2022-01-17 22:04 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 22:04 matthpmoreira [this message] 2022-01-17 22:41 ` Humm 2022-01-17 23:04 ` ori 2022-01-17 23:18 ` Matt 2022-01-17 23:22 ` ori 2022-01-17 23:31 ` Matt 2022-01-17 23:36 ` Sigrid Solveig Haflínudóttir 2022-01-18 0:29 ` Matt 2022-01-18 0:33 ` hiro 2022-01-18 16:22 ` Humm 2022-01-18 18:54 ` Antonio Barrones 2022-01-18 19:55 ` Humm 2022-01-18 20:48 ` Kurt H Maier via 9fans 2022-01-18 22:16 ` vic.thacker 2022-01-18 22:59 ` Duke Normandin 2022-01-18 0:47 ` Kurt H Maier via 9fans 2022-01-18 4:38 ` Andrew Back 2022-01-18 0:20 ` Thaddeus Woskowiak
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=16424570840.4902C04.email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [9fans] Despite being called a fork, is 9front similar to how Linux distros work?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).