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. Everyone, I hope you are enjoying the new wiki.

    I've added a catalog of all Intel 64-bit processors in existence, along with mapping each of these 1800 CPUs to the appropriate stage3 to download. You can see this database here: https://www.funtoo.org/Funtoo_CPU_Database

    When browsing 64-bit Intel subarch pages, they will now display a subset of this list -- the list of CPUs for which that particular subarch is recommended.

    Enjoy, everyone.

    Oh -- And AMD is coming next ;)

  2. The 1.0 release of Funtoo Linux is not going to be maintained after September 30, 2018. So please be sure to upgrade your systems to Funtoo Linux 1.2 using https://www.funtoo.org/Upgrade_Instructions so that you will continue to get updates!

    We will also be starting development on Funtoo Linux 1.3 in a few days, on August 31. We are moving to a new agile (scrum) process, where we will be doing 1-week sprints (time-constrained sets of work). Our work will include some portion of fixes for 1.2 and some new work on 1.3. When we as a team decide that 1.3 is ready for various milestones (alpha, beta, release candidate) we will mark it as such. Thus, we have no hard deadline for 1.3 as I do not want to try to hit arbitrary dates that are not based on the actual work. But we will get there, sooner rather than later!

  3. Ryzen stages are now available for download at the following links:

    https://build.funtoo.org/funtoo-current/x86-64bit/amd64-zen/

    https://build.funtoo.org/funtoo-current/pure64/amd64-zen-pure64/

    A new pure64 stage is building right now.

    Also, many thanks to CDN77 for sponsoring Funtoo -- our downloads now use a combined funtoo/CDN77 infrastructure for world-wide speed rather than a mirroring infrastructure. This applies to stage3 downloads as well as fastpull downloads.

  4. We need maintainers for non-GNOME desktop environments who will help us test and maintain kits. Please let me know if you are interested in doing this. The primary reason the DE's are out-of-date is because we need some people to volunteer to maintain the DE's and apply funtoo-style testing to them. We don't want to just track Gentoo's changes since we then have no process to ensure things are working as things get updated.

  5. The following ebuilds are available for testing by end users and are currently keyword-masked. Add the following to your package.accept_keywords to test:

    =sys-apps/portage-2.3.47 **
    =sys-devel/gcc-7.3.1-r3 **
    =sys-apps/corenetwork-1.6.4 **
    =x11-drivers/xf86-video-intel-2.99.917_p20180609 **

    Here is a quick review of changes in the above packages. Portage is a new version from Gentoo, which has passed all unit tests. Gcc-7.3.1-r3 is a much-improved ebuild from @Temptorsent which now enables SSP by default for improved security. Corenetwork-1.6.4 has some bug fixes that have accumulated in git, and the new xf86-video-intel is the latest from git and needs testing, particularly on newer intel hardware like Coffee Lake and Kaby Lake refresh -- and it always seems like google chrome has rendering issues, so be sure to test Chrome with this driver.

    Please test these things and report back your experiences.

  6. Hey everyone,

    A large number of home routers are vulnerable to malware and can be used to scrape your passwords and other important data. Please take a look at https://blog.talosintelligence.com/2018/06/vpnfilter-update.html -- specifically the "Known affected devices" part -- and see if your router has an exploitable security hole. Affected devices listed below....

    Given our observations with this threat, we assess that this list may still be incomplete and other devices may be affected.
    
    ASUS DEVICES:
    RT-AC66U (new)
    RT-N10 (new)
    RT-N10E (new)
    RT-N10U (new)
    RT-N56U (new)
    RT-N66U (new)
    
    D-LINK DEVICES:
    DES-1210-08P (new)
    DIR-300 (new)
    DIR-300A (new)
    DSR-250N (new)
    DSR-500N (new)
    DSR-1000 (new)
    DSR-1000N (new)
    
    HUAWEI DEVICES:
    HG8245 (new)
    
    LINKSYS DEVICES:
    E1200
    E2500
    E3000 (new)
    E3200 (new)
    E4200 (new)
    RV082 (new)
    WRVS4400N
    
    MIKROTIK DEVICES:
    CCR1009 (new)
    CCR1016
    CCR1036
    CCR1072
    CRS109 (new)
    CRS112 (new)
    CRS125 (new)
    RB411 (new)
    RB450 (new)
    RB750 (new)
    RB911 (new)
    RB921 (new)
    RB941 (new)
    RB951 (new)
    RB952 (new)
    RB960 (new)
    RB962 (new)
    RB1100 (new)
    RB1200 (new)
    RB2011 (new)
    RB3011 (new)
    RB Groove (new)
    RB Omnitik (new)
    STX5 (new)
    
    
    
    NETGEAR DEVICES:
    DG834 (new)
    DGN1000 (new)
    DGN2200
    DGN3500 (new)
    FVS318N (new)
    MBRN3000 (new)
    R6400
    R7000
    R8000
    WNR1000
    WNR2000
    WNR2200 (new)
    WNR4000 (new)
    WNDR3700 (new)
    WNDR4000 (new)
    WNDR4300 (new)
    WNDR4300-TN (new)
    UTM50 (new)
    
    QNAP DEVICES:
    TS251
    TS439 Pro
    Other QNAP NAS devices running QTS software
    
    TP-LINK DEVICES:
    R600VPN
    TL-WR741ND (new)
    TL-WR841N (new)
    
    UBIQUITI DEVICES:
    NSM2 (new)
    PBE M5 (new)
    
    UPVEL DEVICES:
    Unknown Models* (new)
    
    ZTE DEVICES:
    ZXHN H108N (new)
    
    * Malware targeting Upvel as a vendor has been discovered, but we are unable to determine which specific device it is targeting.

     

  7. Hi All,

    By default, we are now building stage3's using Funtoo Linux 1.2 release as default. This means that new installs will have this in their /etc/ego.conf:

    [global]

    release = 1.2

    If you are still using release 1.0, that's fine -- your system will continue to use 1.0. When you upgrade to ego 2.4.1 or later, you will be able to set the release as above in your ego.conf, re-run "ego sync", and you will be upgraded to the 1.2 release. The release= setting is simply a short-hand for setting the various 1.2-related kits individually in the [kits] section, so many of you are already running 1.2.

    Best,

    Daniel

  8. Today, Gentoo's GitHub account was compromised. From initial observation, this was a pretty blatant attack, akin to vandalism, and not an attempt to stealthfully compromise the integrity of Gentoo systems. However, the Gentoo project is urging caution until GitHub has restored the git repos to proper function and ensured their integrity, and for safety to treat all repositories as "compromised."

    As a precaution, we are now pulling updates directly from Gentoo rather than from Gentoo's GitHub account.

    Reference: https://www.gentoo.org/news/2018/06/28/Github-gentoo-org-hacked.html

×
×
  • Create New...