Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

drobbins

Funtoo Linux BDFL
  • Posts

    513
  • Joined

  • Last visited

  • Days Won

    282

Posts posted by drobbins

  1. All good things must come to an end. I've decided to end the Funtoo Linux project. Funtoo started as a philosophy to create a fun community of contributors building something great together. For me, it's no longer that so I need to move on to other things. There is not a successor BDFL for Funtoo nor am I interested in trying to find one, or hand the project off to someone else. You can expect the project to wind down through August. If you have a Funtoo container, it will continue to be online through the end of August so you have time to find another hosting solution if you need one.

  2. 3 hours ago, dutch-master said:

    Can someone PLEASE remove the banner on each forum page for the SUMMER 2023 newsletter!?

    It's unfortunately indicative how this forum is apparently regarded by Funtoo's Admin staff. Not everyone wants Discord. I strongly despise "social" media for profit mass personal data harvesting platforms. If you don't pay, YOU are the currency  🙄

    TIA!

    I think *I* am Funtoo's Admin staff. You seem to be under the impression that there is a large team of dedicated people who exist solely to maintain these free services for you and cater to your preferences. That is not the case. This is a volunteer project and everyone including myself has very limited time. I would like to challenge your apparent perceptions that there is an actual group of people whose job it is to make sure you are happy and satisfied with our infrastructure. It's not true and that is not the way a volunteer project works, unfortunately. (I wish this was how it was)

    Maybe you can try to take things a little less personally and appreciate what we do have, and engage constructively to help improve our services rather than complain about them and cast negative judgement against, in this case, me.

    There are plenty of other Linux distributions that don't use Discord, so if it's a deal-breaker for you, I encourage you to find another Linux distro that reflects your personal values. Discord can be run in-browser and it has full functionality, and is sandboxed by Chrome or whatever browser you use when run in this way. If Funtoo is important enough for you, maybe you will engage with our community to help us maintain our infrastructure and improve what we have to offer. The technologies like Discord are often chosen in large part because they offer a lot of features we need but do not require a lot of our time to use and maintain. If you are in a position to invest your time to offer a superior solution, then you are in a rare position indeed and we would be happy if you  would use this time to help the Funtoo community.

    Consider the perspective change.

  3. This doesn't help your immediate problem but the next release of ramdisk should print a useful "lsblk -f" command when it opens the rescue shell to give you the information on visible block devices automatically.

    I think we need to figure out what modules you need and then I need to make sure I am auto-loading these. Can you give me a bit of detail on your PC/system so I have more context on what we're trying to get booting?

  4. Everyone,

    We are officially retiring 1.4-release in 2024, which means that if you have not yet done so, now is the time to upgrade to next-release. The official way to do this is to do a REINSTALL of Funtoo. You may be able to in-place upgrade from 1.4-release to next-release but THIS IS NOT OFFICIALLY SUPPORTED so if you can't get it to work, you can ask on Discord for help unofficially but if you can't work through the various quirks you WILL need to reinstall.

    Really, a reinstall should be done unless you have a very specific reason why you can't.

    The Funtoo community is around to help with issues you may have with an upgrade, but just be aware of the possibility of hitting something that may warrant reinstall.

    For new installs of next-release, the Funtoo community as well as myself are available to assist you with issues you may encounter. Reach out on Discord in the #install-help channel.

  5. Hi All,

    I've decided to move the Funtoo Telegram channel to non-official status, as we have Discord and it doesn't make sense to have two official discussion channels.

    If you're on Telegram, you're encouraged to come over to Discord.

    I've marked the Telegram channel as "Unofficial" and updated the wiki to make this clearer.

  6. UPDATE: containers are back online -- see below for details on what happened.

    Everyone,

    Our datacenter in Taos, New Mexico experienced a very severe "fiber cut" in close proximity to the datacenter which severed its fiber links. This major fiber cut also has disrupted multiple ISPs and mobile carriers such as Verizon in Taos, NM.

    This has resulted in a number of community containers going offline. This has not impacted Funtoo core infrastructure. The fiber cut is very severe and we expect at least 24 hours of downtime.

    More info here: https://www.taosnews.com/news/severed-fiber-optic-line-causes-cell-phone-internet-outages-in-taos/article_cc7f41e6-03f7-11ee-9df2-fb4957e977a7.html

    UPDATE from our datacenter:

    What happened? At approximately 3:25 pm MT (GMT-6) yesterday a road construction crew caused a large fiber cut which knocked much of Taos, New Mexico's telecommunication infrastructure offline. This outage impacted both of our upstream networks in addition to local cell phone and phone service, as well as many local ISPs, including our sister company, TaosNet.  Lumen fiber technicians worked through the night to repair the broken fiber and are still at work on it.

    Why did this happen?  Know that we're as shocked and devastated as you are by this extended outage and again, apologize profusely.  We were led to believe - by our upstream network providers - that our upstream network redundancy was complete, when in fact it was clearly not.  We have had fiber cuts to one of these fiber connections or the other over the last few years, and each time our traffic failed-over perfectly.  However, what this fiber cut revealed is that there is approximately a one mile stretch - of many hundreds of miles of fiber that our networks traverse - where both networks are in the same conduit. This is where the cut was.

    The good news is that after detailed analysis we believe a network routing change can get us back to fully geographically redundant fiber paths.  We'll be working on implementing this in the coming weeks.

    How did Brownrice get back online? Since the fiber outage was still not fixed, early this morning the CEO of a local ISP, Kit Carson Internet, reached out to us offering network connectivity.  Our network engineers, our TaosNet wireless team, and the team at Kit Carson Internet then formulated and executed a plan to build a high-speed wireless link between our two facilities and route traffic through Kit Carson Internet to our data center.  This brought all of our networking services back online. The amount of skill and know-how to pull this together within a single day was truly staggering.  And we can't thank Kit Carson Internet enough.

    What are you doing to ensure this never happens again?  Now we have an active and tested, fiber-cut-proof backup connection in place and working.  It's not yet as fast as we'd like, and is currently experiencing some packet loss, but our higher speed fiber connections should come back online later tonight.  And once we are back to full strength we'll get the backup connection speed and packet loss sorted out.  And know that we will leave this backup connection in place forever, so this never happens again.

     

  7. @cardinal I don't think your original bug report for this issue was optimal (https://bugs.funtoo.org/browse/FL-11069)

    I think it identifies the wrong problem.

    The real problem here is not that there was a blacklist installed -- the real problem is that by default, the nvidia-drivers are not supporting a legacy card. This is not optimal and if the nouveau drivers are more compatible with all generations of NVIDIA cards, it makes a more reasonable default for our DE stage3's.

    Therefore, I am thinking the bug should be "default nvidia-drivers on stage3 lacks support for legacy NVIDIA cards". And we would explore nouveau by default as a solution. Then we would incorporate the nouveau blacklist into nvidia-drivers so it installs only if you opt-in to the official NVIDIA drivers.

×
×
  • Create New...