HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MrMEEE
bumblebee-Old-and-abbandoned
Shell2012–2026
MrMEEE / bumblebee-Old-and-abbandoned

bumblebee-Old-and-abbandoned

OUTDATED!!!!! - Replaced by "The Bumblebee Project" and "Ironhide"

48Distinct people
48Mentions
1Explicit recommenders
469GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

OUTDATED!!!!! - Replaced by "The Bumblebee Project" and "Ironhide"

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

My favorite all time bug was the infamous "Bumblebee" commit of 2011[1]. IIRC this was the first github commit to go viral. Make sure you have 30 minutes to read the thread. It…

freedomben used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 2:19:09 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year48 dated mentions

Observed mentions: 2012-02-21 18:27:50 UTC to 2026-10-06 01:31:42 UTC.

02462012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC615
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC514
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC606
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC413
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC321
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC312
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC422
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC211

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
OBSOLETE PROJECT: Please READ: http://www.martin-juhl.dk/2011/08/reassemble-of-the-bee/ and http://www.martin-juhl.dk/2011/08/ironhide-reporting-for-duty/ IMPORTANT: Ubuntu Users: Bumblebee has now been packaged into a PPA @ Launchpad: https://launchpad.net/~mj-casalogic/+archive/bumblebee/ This will probably be the most up-to-date version for Ubuntu from now on... For people currently running the script/git version please do : sudo bumblebee-uninstall sudo apt-get install ppa-purge sudo ppa-purge ppa:ubuntu-x-swat/x-updates sudo ppa-purge ppa:xorg-edgers/ppa sudo apt-add-repository ppa:mj-casalogic/bumblebee sudo apt-get update sudo apt-get install bumblebee openSuSE Users: Bumblebee has been ported to the openSuSE Build Service repository : http://download.opensuse.org/repositories/home:/Ximi1970:/bumblebee/openSUSE_11.4/ For people currently running the script/git version please do : sudo bumblebee-uninstall If you have used the nVidia package option: sudo bash NVIDIA-Linux-xxxxx-xxxx.run --uninstall If you have used the nVidia repository (mirror) option: rpm -e x11-video-nvidiaG02 rpm -e nvidia-computeG02 rpm -e nvidia-gfxG02-kmp zypper rr "nVidia Graphics Drivers (local mirror)" Install the nVidia repository and packages if you do not want to use the nouveau driver: zypper ar -f ftp://download.nvidia.com/opensuse/11.4 "nVidia Graphics Drivers" zypper install nvidia-gfxG02-kmp-`uname -r | cut -f3 -d"-"` zypper install x11-video-nvidiaG02 Installing bumblebee: zypper ar -f http://download.opensuse.org/repositories/home:/Ximi1970:/bumblebee/openSUSE_11.4 "Bumblebee" zypper install bumblebee or just use Yast to add the repositories and packages. # ---------------------------------------------------------------------------- # "Red Bull License" # <mj@casalogic.dk> wrote this file and is providing free support # in any spare time. If you need extended support, you can fuel him up by # donating a Red Bull here to get him through the nights..: # # http://tinyurl.com/bumblebee-project # # ---------------------------------------------------------------------------- # # ---------------------------------------------------------------------------- # "THE BEER-WARE LICENSE" (Revision 42): # <mj@casalogic.dk> wrote this file. As long as you retain this notice you # can do whatever you want with this stuff. If we meet some day, and you # think this stuff is worth it, you can buy me a beer in return Martin Juhl # ---------------------------------------------------------------------------- # # This file is part of bumblebee. # # bumblebee is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # bumblebee is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with bumblebee. If not, see <http://www.gnu.org/licenses/>. # This project is containing bumblebee (formerly known as prime-ng).. bumblebee is Optimus support for Linux, with real offloading, and not switchable graphics.. More important.. it works on Optimus Laptops without a graphical multiplexer.. Bumblebee Supports: Ubuntu, Linux Mint, OpenSuSE and Fedora. More are coming. Arch Linux Support: http://aur.archlinux.org/packages.php?ID=49469 Debian Linux Support: https://github.com/z0rc/debumblebee Gentoo Linux Support: https://github.com/iegor/rainyday/tree/master/x11-misc/bumblebee openSuSE Linux Support: Github: https://github.com/Ximi1970/bumblebee Repositories: http://download.opensuse.org/repositories/home:/Ximi1970:/bumblebee/openSUSE_11.3 http://download.opensuse.org/repositories/home:/Ximi1970:/bumblebee/openSUSE_11.4 Unstable repositories ( build with the latest cvs, svn and git packages ): http://download.opensuse.org/repositories/home:/Ximi1970:/bumblebee-unstable/openSUSE_11.3 http://download.opensuse.org/repositories/home:/Ximi1970:/bumblebee-unstable/openSUSE_11.4 The Installation should now be completely automatic... First of all: If you have any problem... please create a bug report package with the bumblebee-bugreport tool.. Then create an issue on github... This project have had great succes and I need to have a way to easily manage support problems.. Now 3D is enabled on both the Intel and the nVidia at the same time.. The Intel card is running the Desktop and the nVidia card can be used for the thougher applications with the command "optirun32 <application>" or "optirun64 <application>"... Support for automatically shutting down and starting up the nVidia card is in developpement. There are several ways to start using bumblebee : Download the .zip or .tar.gz by clicking the 'Downloads' button on the 'Source' page to a directory of your liking. Unzip or untar and run the install script with 'sudo ./install.sh' (or 'sudo -E ./install.sh' on Fedora) Go to the directory of your liking and: 1. git clone http://github.com/MrMEEE/bumblebee.git 2. cd bumblebee/ 3. sudo ./install.sh (or 'sudo -E ./install.sh' on Fedora) (The second method makes it easier to regularly update bumblebee if you're willing to invest a little bit of time in working with git.) Status updates can be found here: http://www.martin-juhl.dk or on twitter: http://twitter.com/martinjuhl Or join the facebook group: http://tinyurl.com/bumblebeefacebook
Read the full README on GitHub

What Hacker News says

6 sources
`curl|bash` is just as secure, as downloading and executing a binary or as downloading and "make"-ing a tarball or downloading an .rpm or .deb file. And all these are absolutely ugly and definitely less secure than your distro's package manager downloading packages from the supported repository. 1. Ugly. Just take a look at this: https://fedoraproject.org/wiki/Packaging:Guidelines. This is Fedora packaging guidelines/policies. Every distribution worth it's salt has one (https://www.debian.org/doc/manuals/maint-guide/, http://packaging.ubuntu.com/html/). There quite strict constraints on what a package should look like, how it should be compiled, in which directories it can place files and so on and so forth. Custom installers (be it `curl|bash` or a .sh file or a .bin file) on the other hand are not policed by anyone except the original a
Read the rest
uthor. The installer can stop and ask you to read/accept a license agreement, it can open a browser, it can start background jobs. It can absolutely do `rm -rf /*` (https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commi...). 2. Less Secure. There are hundreds of software packages which are supposed to be installed with `curl|bash`. Are you sure all of them adhere to infrastructure/server security best practices? I for one trust the SysOps team @RedHat. To be clear - if the source code of the program is infected and the distro package maintainer doesn't notice it, you're in big trouble.
In Is curl|bash insecure?
It doesn't even have to be intentional malice: https://news.ycombinator.com/item?id=8896186 https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/issue... You can limit the damage by keeping backups, and running software you don't really trust under a limited account. The latter is understandably more difficult with certain applications, but it's once again one of those security-usability tradeoffs. I basically avoid installing much in the way of new software as much as I can, as my existing setup does what I need, and anything new gets subjected to careful scrutiny first, but this is not a workable solution for everyone. Nevertheless, I can see how those with an attitude that makes them very eager to install and try new software could also make them more vulnerable to things like this.
In Npm install could be dangerous
> That's part of my issue with systemd: replacing safe (-r) shell scripts with C. Because shell scripts are always safe, right? [1][2][3] We used to get root on Android devices by exploiting poorly-written shell scripts. > Also, it probably doesn't help Lennart that he looks like the Rolfe Gruber in the Sound of Music… Personal attacks won't help your case. [1] https://github.com/ValveSoftware/steam-for-linux/issues/3671 [2] https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commi... [3] http://www.exploit-db.com/papers/13199/
In Interview: Lennart Poettering

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.