Linux

48224 readers

1094 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]

Idea for a new project: reblued (self.linux)

submitted 9 months ago* (last edited 9 months ago) by djtech to c/[email protected]

11 comments fedilink hide all child comments

Hi everybody,

i'm a long time Debian user and, while i've always loved the Linux experience, the bluetooth side of things was always a little bit... painful.

Lately, i've been digging on how bluetooth on Linux works (i knew about BlueZ, but i didn't know about HCI sockets, standard protocols for bluetooth controllers, ...). Seeing how Android manages to work fine with bluetooth (yes, i know, money and company support, blah blah blah), i was thinking about re-writing the bluetooth daemon, in order to be modern, modular, safe (written in Rust), stable and retro-compatible (exposes the same D-Bus APIs as BlueZ) I already found some documents about HCI socket in Linux, HCI communication with bluetooth controllers, HID standards for Bluetooth, etc...

My questions are:

is this a good idea?
does somebody want to collaborate?

Thanks for reading.

EDIT: The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project's skeleton, license, README and disussions for collaborators.

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

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

i was thinking about re-writing the bluetooth daemon, in order to...

The NIH is strong with this one.

IMO you'd be better off putting that enthusiasm into fixing BlueZ - you might actually be able to fix some real issues and improve things for a great number of users relatively quickly.

Writing a new, competing, piece of software is going to take a while to achieve both feature parity and see any adoption by major distros.

retro-compatible (exposes the same D-Bus APIs as BlueZ)

Is there any reason for this? I can't think of anything off the top of my head that would require it. It's an admirable goal but make sure it's worthwhile doing this and that there aren't actual benefits that could be achieved by breaking compatibility.