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. It can be really hard to figure out what is going wrong with a kernel. I am going through my own issues with a server motherboard I have. With 3.17.0, my PCI firewire card stops working. It's not related to the firewire driver exactly -- it can't allocate an IRQ!

     

    What I did, per the suggestion of the firewire devs, is to "bisect" my kernel. That means I used the "git bisect" feature to narrow down the *exact* commit that caused the kernel to start failing on my hardware. I was then able to contact the Intel developer who made the commit, who is being very helpful and considers it a regression (bug), and is trying to fix it.

     

    The basic process for bisecting a kernel is to git clone the kernel sources, and then you use the git bisect command to tag "good" and "bad" versions. git bisect will find the middle commit between good and bad, which you then compile and see if it works or not. If yes, it gets tagged as good, if not, it is tagged as bad. Eventually (took me 13 tries), I found the *exact* commit that caused my issue.

     

    Then I could contact someone who could help.

  2. I think maybe the best approach is to create an /etc/init.d/ModemManager and add a "depend" entry to NetworkManager that says "use ModemManager". Then if you want ModemManager to be started prior to NetworkManager, you would add your ModemManager script to the default runlevel.

     

    depend{ use foo; } in an OpenRC script means "start foo first if it is already enabled for this runlevel."

     

    depend{ need foo; } means "start foo first, even if it hasn't been added to this runlevel."

  3. If you build it in a 32-bit chroot then it will build a 32-bit verson for you. If you want, you can modify the config_extract call in src_prepare (in the ebuild) to do something a little bit different. But for right now, there is no way to control this using USE variables or the like.

  4. Hi All,

     

    Here are some updates on Funtoo Hosting.

     

    I've added a second server, configured identically as the first, to the mix. Right now, it's in "beta" mode as it is having some cooling issues, likely due to thermal grease that needs replacement. It is stable, just hits the CPU throttle temp and performance is affected somewhat. Expect to have this resolved shortly.

     

    OpenVZ kernels have been upgraded to the latest versions on both servers. Live migration between servers is now functioning, which means i can move your container between servers without you even knowing it happened :)

     

    I can even reboot the server when I need to do a kernel update, and your system will freeze for 30 seconds and then come back online in the exact state it was in prior to reboot. Cool stuff.

     

    I have also enabled QoS on both servers which should result in much better network responsiveness, and dedicated bandwidth for UDP packets which are typically used for game hosting as well as mosh sessions. ssh interactive packets are also being prioritized to improve interactive ssh responsiveness.

     

    As part of these changes, I've also gotten HP's Health Management software working under Funtoo! I've documented how to do this here:

     

    http://www.funtoo.org/HP_Health_Management

  5. Nothing from Lennart is unusual for a young male geek, but that doesn't mean that his approach is not harmful to the Linux community.

     

    A lot of distributions were strong-armed into using systemd to maintain compatibility with GNOME, and this hasn't bothered Lennart one bit, and it should have. 

     

    I agree with several comments in earlier threads. Funtoo will remain a non-systemd system and will eventually be upgrading OpenRC to be competitive with systemd.

     

    Frankly, GNOME 3.6 worked quite a bit better than GNOME 3.12. I had tabbed terminal windows and a few other things were cleaner. So it's not always extremely useful to follow GNOME's latest release. I do like the general design of GNOME 3 but in some ways they seem to be continually regressing.

  6. The new layout is great. I wish the layout to be as much consistent with wiki and forums as possible.

     

    We are using IP.Board which has its own CSS framework, so it doesn't use bootstrap. There are supposed to be big improvements in IP.Board 4, which will be available soon, and we will switch to it a little bit after it is released. But no IP.Board uses bootstrap which is what our wiki uses.

     

    I will be looking into a just-as-sexy-but-more-traditional default theme for the forums, though.

     

    -Daniel

  7. Hi All,

     

    Many of you have probably seen our new responsive Web site skin for the wiki at www.funtoo.org.

     

    I switched to a new bootstrap-based skin which is in turn based on an in-development set of MediaWiki extensions that I'm helping out with.

     

    Here are advantages of the new skin:

     

    • Properly renders on mobile devices
    • Much easier to customize and improve over time
    • Much "cleaner" look
    • Makes it possible to integrate the look of auth.funtoo.org with the wiki.

    Here are some negatives:

    • For a while, a few things will not render 100% correctly until tweaked
    • Doesn't look like a "regular" wiki

    Overall, it is a big positive change as the new bootstrap framework with the extensions is much easier to customize and improve than the "old" MediaWiki skin system. And this effort is also being actively developed so by having funtoo.org use this system, I am better able to test it out, find issues, and contribute to its development.

     

    Hope you like it!

     

    -Daniel

     

     

×
×
  • Create New...