Funtoo,плюсы и минусы.

Funtoo,плюсы и минусы.

Сообщение tupoll » 01 июн 2015, 08:58

Переход на четвертое ядро Gentoo привёл к многочисленным проблемам:
1Отказался собираться драйвер nvidia (карточка старая -версия драйвера 340.76) указывая на то что нет соответствующего модуля в ядре.
2Пропал звук oss жалуясь примерно на тоже
3Модуль zfs установленный с репозитория gentoo тож ругнулся и умер,отказавшись собираться.
Пытаюсь выкрутиться:
1Устанавливаю nouveau-свободный драйвер nvidia
2Подключаю очередной оверлей устанавливаю последнию версию модуля zfs-0.6.4
3Звук с оверлея bar-никак ,хотя патч на ядро давно наложен.
В итоге что получилось-работающая худо-бедно система без звука и с кучей подключенных
оверлеев занимающих своими программами место в системе(имеется ввиду что пакеты которые мне никак не нужны храятся у меня в разделе).
Единственно,что порадовало-свободный видеодрайвер,а то я все грешил на то что моя видео карта уже умирает,при просмотре HD периодически сыпал снег через HDMI на телевизоре.И мелкий шрифт на мониторе стал вполне читаем без пакета infinality.Подключенный фреймбуфер(не знаю зачем )в консоли показывает кино без каких-либо настроек на ура.
Ждать когда все это хозяйство багов пропатчат или ковыряться самому на мой взгляд просто глупо.
Ну что ж перебираемся на смешную версию gentoo вслед за её основателем,т.е funtoo linux.
Gentoo естественно сносить при этом вовсе не обязательно-zfs достаточно просто отмонтировать файловые системы с ней и оставить их в режиме монтирования legacy или none,почистить успеется всегда,а в случае неудачи обратно примонтировать.
Идем на сайт funtoo-установка мало чем отличается,зачем-то добавлен boot-update в нее-работает почему-то только с dos,выбрасываем нафиг.
Через два часа вся база чрутом собрана,ещё полдня-собранно всё с одного места ни одного стороннего оверлея и всё работает.Ключевой файл всей системы естественно make.conf
/etc/portage/make.conf
Код: выделить все
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# Contains local system settings for Portage system

# Please review 'man make.conf' for more information.

# Build-time functionality
# ========================
#
# The USE variable is used to enable optional build-time functionality. For
# example, quite a few packages have optional X, gtk or GNOME functionality
# that can only be enabled or disabled at compile-time. Gentoo Linux has a
# very extensive set of USE variables described in our USE variable HOWTO at
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
#
# The available list of use flags with descriptions is in your portage tree.
# Use 'less' to view them:  --> less /usr/portage/profiles/use.desc <--
#
# 'ufed' is an ncurses/dialog interface available in portage to make handling
# useflags for you. 'emerge app-portage/ufed'
#
# Example:
USE=" 3dnow 3dnowext
     -alsa -alsa-lib
   aac amr a52 apng awesome
   -aqua aqualung app-foo/bar app-bar/baz
   binary bindist
   -bluetooth
    cleartype cmake c++0x cairo
   -cups consolekit crypt
   dbus -dolphin development
   -dso -doc -default-term
   -development -dhclient
   dhcpcd deluge dropbox
   -emacs egl
   firmware flac ffmpeg
   -fbcondecor flaggie
   git g3dvl gstreamer -gnome-keyring
   gtk gtk3 -gnome -gnome-online-accounts gtkstyle
   grilo geany -graphite gudev
   -ghcbootstrap -gcrypt -geoloc
   highlight hscolour heather
   -handbook -hoogle -hpn
   icu icq irc
   i18n -introspection
   jpeg jpeg2k
   kmod
   -kerberos -kde
   lodgeit-default llvm ladspa -libav
   -ldap lua libsamplerate librsync-bundled
   minizip mmx mp3 mpeg mms -modemmanager
     mhash minimal nls 
   -networkmanager -nautilus
   
   openssl openvg oss opengl
   osmesa openrc optimization ogg
        plugins
   perl -pulseaudio pypy2_0 png playlist pcre16
   -plasma pcre pango python policykit
    ristretto
   -qt5 -qemu
    -qt3 -qt4
   strong-optimization spell scrobbler
   symlink sse sse2 sse3 ssse3 sse4_1
   steamruntime spamassassin sdl ssl
   -spice -systemd sync
   -subversion -startup-notification
          threads
   truetype traker thunar
   udev udisks unicode
   -virt-network
    video-thumbnails -vala vorbis
        usb
   wavpack wallpapers
   -webkit
   xft xvmc xa xorg  xvid x264 xkb
   xinerama X
   -yahoo
     zfs zlib
   zsh-completion"

INPUT_DEVICES="keyboard mouse evdev"
VIDEO_CARDS="nouveau"
#VIDEO_CARDS="nvidia"
#VIDEO_CARDS="radeon radeonsi"

OSS_CARDS="cmi878x  hdaudio ich imux midiloop midimix userdev"

# Please don't ruin my language settings
CONFIG_PROTECT="${CONFIG_PROTECT} /usr/share/i18n/locales /usr/lib/oss/soundon.user"




# Host Setting
# ============
#
CHOST="x86_64-pc-linux-gnu"

LINGUAS="en ru"

# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# If your gcc supports it, you can add -frecord-gcc-switches to all of the
# following *FLAGS in order to enable *FLAGS ignorance checking for ebuilds:
# CFLAGS, CXXFLAGS, FFLAGS, and FCFLAGS.
# Note that this check is only enabled if every one of these variables contains
# -frecord-gcc-switches, since otherwise the check could result in false
# positive results.
#
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without
# breaking compatibility with other CPUs. GCC 3.4 has deprecated support for
# -mcpu, so use -mtune instead if using this compiler.
#
# -march=<cpu-type> means to take full advantage of the ABI and instructions
# for the particular CPU; this will break compatibility with older CPUs (for
# example, -march=athlon-xp code will not run on a regular Athlon, and
# -march=i686 code will not run on a Pentium Classic.)
#
# CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron),
# pentium3, and pentium4.
#
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
#
# amd64 CPU types supported in gcc-3.4: athlon64, opteron, k8
#
# CRITICAL WARNINGS: ****************************************************** #
# K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
# Pentium-M CPUs should not enable sse2 until at least gcc-3.4. Bug 50616. #
# GCC 3.3 doesnt support an amd64 specific -march setting, use 3.4.         #
# ************************************************************************* #
#
# Decent examples:
#
CFLAGS="-mtune=k8 -O2 -pipe"
#CFLAGS="-march=athlon64 -O2 -pipe"

# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
CXXFLAGS="${CFLAGS}"
#
# If you set a CFLAGS above, then this line will set your default FORTRAN 77
# flags to the same settings.
FFLAGS="${CFLAGS}"
#
# If you set a FFLAGS above, then this line will set your default FORTRAN
# flags to the same settings for modern build systems
FCFLAGS="${FFLAGS}"


# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
#
# Please note that this is not for development, alpha, beta, nor cvs release
# packages. "Broken" packages will not be added to testing and should not be
# requested to be added. Alternative routes are available to developers
# for experimental packages, and it is at their discretion to use them.
#
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
ACCEPT_KEYWORDS="~amd64"

# ACCEPT_LICENSE is used to mask packages based on licensing restrictions.
# It may contain both license and group names, where group names are
# prefixed with the '@' symbol. License groups are defined in the
# license_groups file (see portage(5) man page). In addition to license
# and group names, the * and -* wildcard tokens are also supported.
#
# Accept any license except those in the EULA license group (default).
#ACCEPT_LICENSE="* -@EULA"
#
# Only accept licenses in the FREE license group (i.e. Free Software).
ACCEPT_LICENSE="-* @FREE"

# Portage Directories
# ===================
#
# Each of these settings controls an aspect of portage's storage and file
# system usage. If you change any of these, be sure it is available when
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
#     temporary storage of data. This can get VERY large depending upon
#     the application being installed.
PORTAGE_TMPDIR=/var/tmp
#
# PORTDIR is the location of the portage tree. This is the repository
#     for all profile information as well as all ebuilds.
#     ***Warning***
#     Data stored inside PORTDIR is in peril of being overwritten or deleted by
#     the emerge --sync command. The default value of PORTAGE_RSYNC_OPTS
#     will protect the default locations of DISTDIR and PKGDIR, but users are
#     warned that any other locations inside PORTDIR are not necessarily safe
#     for data storage.
#PORTDIR=/usr/portage
#
# DISTDIR is where all of the source code tarballs will be placed for
#     emerges. After packages are built, it is safe to remove any and
#     all files from this directory since they will be automatically
#     fetched on demand for a given build. If you would like to
#     selectively prune obsolete files from this directory, see
#     eclean from the gentoolkit package. Note that locations under
#     /usr/portage are not necessarily safe for data storage. See the
#     PORTDIR documentation for more information.
#DISTDIR=/usr/portage/distfiles
DISTDIR=/var/db/distfiles

# PKGDIR is the location of binary packages that you can have created
#     with '--buildpkg' or '-b' while emerging a package. This can get
#     up to several hundred megs, or even a few gigs. Note that
#     locations under /usr/portage are not necessarily safe for data
#     storage. See the PORTDIR documentation for more information.
PKGDIR=/var/db/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
#     creates from each individual merge. They are stored as
#     ${CATEGORY}:${PF}:YYYYMMDD-HHMMSS.log in the directory specified.
#     If the directory does not exist, it will be created automatically and
#     group permissions will be applied to it.  If the directory already
#     exists, portage will not modify it's permissions.
PORT_LOGDIR=""
#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
#     concern that they will be deleted by rsync updates. Default is not
#     defined.
#PORTDIR_OVERLAY=/usr/local/portage

# Fetching files
# ==============
#
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
# all users on your system should use them.
#
# Portage uses wget by default. Here are some settings for some alternate
# downloaders -- note that you need to merge these programs first before they
# will be available. The command should be written to place the fetched file
# at \${DISTDIR}/\${FILE}.
#
# Default fetch command (3 tries, passive ftp for firewall compatibility)
FETCHCOMMAND="wget -t 3 -T 60 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
RESUMECOMMAND="wget -c -t 3 -T 60 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
#
# Using wget, ratelimiting downloads
#FETCHCOMMAND="wget -t 3 -T 60 --passive-ftp --limit-rate=200k -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
#RESUMECOMMAND="wget -c -t 3 -T 60 --passive-ftp --limit-rate=200k -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space separated list which is read left to right. If you use
# another mirror we highly recommend leaving the default mirror at the end of
# the list so that portage will fall back to it if the files cannot be found
# on your specified mirror. We _HIGHLY_ recommend that you change this setting
# to a nearby mirror by merging and using the 'mirrorselect' tool.
#GENTOO_MIRRORS="<your_mirror_here> http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
#
# Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
# The list is a single entry specifying the full address of the directory
# serving the tbz2's for your system. Running emerge with either '--getbinpkg'
# or '--getbinpkgonly' will cause portage to retrieve the metadata from all
# packages in the directory specified, and use that data to determine what will
# be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
# consult the man pages and 'emerge --help' for more information. For FTP, the
# default connection is passive -- If you require an active connection, affix
# an asterisk (*) to the end of the host:port string before the path.
#PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
# This ftp connection is passive ftp.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
# This ftp connection is active ftp.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site:21*/pub/grp/i686/athlon-xp/"

# Synchronizing Portage
# =====================
#
# Each of these settings affects how Gentoo synchronizes your Portage tree.
# Synchronization is handled by rsync and these settings allow some control
# over how it is done.
#
# SYNC defines the server used by git to clone a local Portage tree.
#
# PORTAGE_RSYNC_RETRIES sets the number of times portage will attempt to retrieve
#     a current portage tree before it exits with an error. This allows
#     for a more successful retrieval without user intervention most times.
#     If set to a negative number, then retry until all possible addresses are
#     exhausted.
PORTAGE_RSYNC_RETRIES="-1"
#
# PORTAGE_RSYNC_EXTRA_OPTS can be used to feed additional options to the rsync
#     command used by `emerge --sync`. This will not change the default options
#     which are set by PORTAGE_RSYNC_OPTS (don't change those unless you know
#     exactly what you're doing).
PORTAGE_RSYNC_EXTRA_OPTS=""
#
# Advanced Features
# =================
#
# EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are
#     specified on every run. Useful options include --ask, --verbose,
#     --usepkg and many others. Options that are not useful, such as --help,
#     are not filtered.
#EMERGE_DEFAULT_OPTS="--ask --ask-enter-invalid --with-bdeps=y --keep-going=y --quiet-unmerge-warn --quiet-build=y --jobs=3 --ignore-built-slot-operator-deps=y"
#
# INSTALL_MASK allows certain files to not be installed into your file system.
#     This is useful when you wish to filter out a certain set of files from
#     ever being installed, such as INSTALL.gz or TODO.gz
#INSTALL_MASK=""
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
#     program is compiled. Presently the only use is for specifying
#     the number of parallel makes (-j) to perform. The suggested number
#     for parallel makes is CPUs+1.
MAKEOPTS="-j5"
#
# PORTAGE_NICENESS provides a default increment to emerge's niceness level.
#     Note: This is an increment. Running emerge in a niced environment will
#     reduce it further. Default is unset.
PORTAGE_NICENESS=3
#
# PORTAGE_IONICE_COMMAND provides a command for portage to call in order to
#     adjust the io priority of portage and it's subprocesses. Default is
#     unset.
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
#     packages from the system after every successful merge. This is the
#     same as running 'emerge -c' after every merge. Set with: "yes" or "no".
#     This does not affect the unpacked source. See 'noclean' below.
#
#     Warning: AUTOCLEAN="no" can cause serious problems due to overlapping
#              packages.  Do not use it unless absolutely necessary!
#AUTOCLEAN="yes"
#
# FEATURES defines actions portage takes by default. This is an incremental
# variable. See the make.conf(5) man page for a complete list of supported
# values and their respective meanings.
#FEATURES="ccache distcc installsources \
# splitdebug test userpriv usersandbox"

# CCACHE_SIZE and CCACHE_DIR are used to control the behavior of ccache, and
#     and are only used if "ccache" is in FEATURES.
#
# CCACHE_SIZE sets the space limitations for ccache. The default size is
#     "2G", or 2 gigabytes.  Units are specified with 'G', 'M', or 'K'.
#
CCACHE_SIZE="2G"
#
# CCACHE_DIR sets the ccache path.  If not specified, portage will default
#     to "${PORTAGE_TMPDIR}/ccache".
#
#     Note that to display ccache statistics outside of portage, you must
#     remember to give the correct path to the cache.
#
#        # CCACHE_DIR=/var/tmp/ccache ccache -s
#
CCACHE_DIR="${PORTAGE_TMPDIR}/ccache"

# DISTCC_DIR sets the temporary space used by distcc.
#DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"

# logging related variables:
# PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
#                          info, warn, error, log, qa, *
#PORTAGE_ELOG_CLASSES="log warn error"

# PORTAGE_ELOG_SYSTEM: selects the module(s) to process the log messages. Modules
#                      included in portage are (empty means logging is disabled):
#                          echo (display messages again when emerge exits)
#                          save (saves one log per package in $PORT_LOGDIR/elog,
#                                /var/log/portage/elog if $PORT_LOGDIR is unset)
#                          custom (passes all messages to $PORTAGE_ELOG_COMMAND)
#                          syslog (sends all messages to syslog)
#                          mail (send all messages to the mailserver defined
#                                in $PORTAGE_ELOG_MAILURI)
#                          save_summary (like "save" but merges all messages
#                                        in $PORT_LOGDIR/elog/summary.log,
#                                        /var/log/portage/elog/summary.log if
#                                        $PORT_LOGDIR is unset)
#                          mail_summary (like "mail" but sends all messages in
#                                        a single mail when emerge exits)
#                      To use elog you should enable at least one module
#                      The module name may be followed by a colon and a comma
#                      separated list of loglevels to override PORTAGE_ELOG_CLASSES
#                      for this module (e.g.
#                        PORTAGE_ELOG_SYSTEM="mail:warn,error syslog:* save")
#PORTAGE_ELOG_SYSTEM="save_summary:log,warn,error,qa echo"

# PORTAGE_ELOG_COMMAND: only used with the "custom" logging module. Specifies a command
#                      to process log messages. Two variables are expanded:
#                          ${PACKAGE} - expands to the cpv entry of the processed
#                                       package (see $PVR in ebuild(5))
#                          ${LOGFILE} - absolute path to the logfile
#                  Both variables have to be quoted with single quotes
#PORTAGE_ELOG_COMMAND="/path/to/logprocessor -p '\${PACKAGE}' -f '\${LOGFILE}'"

# PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
#                       module. In most cases listing the recipient address and
#                       the receiving mailserver should be sufficient, but you can
#                       also use advanced settings like authentication or TLS. The
#                       full syntax is:
#                           address [[user:passwd@]mailserver[:port]]
#                       where
#                           address:    recipient address
#                           user:       username for smtp auth (defaults to none)
#                           passwd:     password for smtp auth (defaults to none)
#                           mailserver: smtp server that should be used to deliver the mail (defaults to localhost)
#                                       alternatively this can also be a the path to a sendmail binary if you don't want to use smtp
#                           port:       port to use on the given smtp server (defaults to 25, values > 100000 indicate that starttls should be used on (port-100000))
#                       Examples:
#PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
#PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain)
#PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader exercise ;)

# PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable,
#                        if unset mails are sent by "portage" (this default may fail
#                        in some environments).
#PORTAGE_ELOG_MAILFROM="portage@some.domain"

# PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following
#                           variables are expanded:
#                               ${ACTION} - merged, unmerged, or unknown
#                               ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND
#                               ${HOST} - FQDN of the host portage is running on
#PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for \${PACKAGE} on \${HOST}"

#SYNC="https://github.com/funtoo/ports-2012.git"
PORTDIR="/var/db/repos/funtoo"
PORTDIR_OVERLAY="/var/db/repos"

#SYNC="git://github.com/funtoo/ports-2015.git"
SYNC_USER="oleg"
SYNC_UMASK="022"

#source /var/lib/layman/make.conf

Система отзывчивей реагирует на изменения флагов.Звук отличный ,частота дискретизации
115000Hz,видео работает нормально,пакет webkit-gtk также приказал долго жить как и на gentoo,нагрузка на процессор при работе google-chrome -0%,при работе gcc(версии 4.9) тоже
значительно ниже чем у gentoo,сборка проходит быстрее.Настройка portage отличается немногим.Попытка перебраться на funtoo методом пересбора мира,смены репов тоже прошла успешно,но ковырять руками мусор нет резона-удаляем два корня gentoo и все лишние теперь файловые системы.
Из минусов funtoo пока один-умер eix -консольный поиск пакетов и подключенных оверлеев-это мелочь пожалуй поправима,а все необходимые мне пакеты уже есть.
Загрузка кстати тоже проходит быстрее,не разбирался ещё с двумя подключенными по умолчанию демонами(оба мертвые)-времени и netif -время кажет UTC нормально,а интернет dhcpcd.Остается только выбрать профиль или создать свой.
eselect profile list:
Код: выделить все
Currently available arch profiles:
  [1]   funtoo/1.0/linux-gnu/arch/x86-64bit *
  [2]   funtoo/1.0/linux-gnu/arch/pure64
Currently available subarch profiles:
  [3]   funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-bulldozer
  [4]   funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-jaguar
  [5]   funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k10
  [6]   funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8
  [7]   funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8+sse3
  [8]   funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-piledriver
  [9]   funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-steamroller
  [10]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/atom_64
  [11]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/btver1_64
  [12]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core2_64
  [13]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core-avx-i
  [14]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7
  [15]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/generic_64 *
  [16]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-broadwell
  [17]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-haswell
  [18]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-ivybridge
  [19]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-sandybridge
  [20]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-silvermont
  [21]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/native_64
  [22]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/nocona
  [23]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/opteron_64
  [24]  funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/xen-pentium4+sse3_64
Currently available build profiles:
  [25]  funtoo/1.0/linux-gnu/build/stable
  [26]  funtoo/1.0/linux-gnu/build/current *
  [27]  funtoo/1.0/linux-gnu/build/experimental
Currently available flavor profiles:
  [28]  funtoo/1.0/linux-gnu/flavor/minimal
  [29]  funtoo/1.0/linux-gnu/flavor/core *
  [30]  funtoo/1.0/linux-gnu/flavor/desktop
  [31]  funtoo/1.0/linux-gnu/flavor/workstation
  [32]  funtoo/1.0/linux-gnu/flavor/hardened
Currently available mix-ins profiles:
  [33]  funtoo/1.0/linux-gnu/mix-ins/audio
  [34]  funtoo/1.0/linux-gnu/mix-ins/cinnamon
  [35]  funtoo/1.0/linux-gnu/mix-ins/console-extras
  [36]  funtoo/1.0/linux-gnu/mix-ins/dvd
  [37]  funtoo/1.0/linux-gnu/mix-ins/gnome
  [38]  funtoo/1.0/linux-gnu/mix-ins/kde
  [39]  funtoo/1.0/linux-gnu/mix-ins/mate
  [40]  funtoo/1.0/linux-gnu/mix-ins/media
  [41]  funtoo/1.0/linux-gnu/mix-ins/media-pro
  [42]  funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-consumer
  [43]  funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro
  [44]  funtoo/1.0/linux-gnu/mix-ins/mediadevice-base
  [45]  funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-consumer
  [46]  funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-pro
  [47]  funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-common
  [48]  funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-extra
  [49]  funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-common
  [50]  funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-extra
  [51]  funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-common
  [52]  funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-extra
  [53]  funtoo/1.0/linux-gnu/mix-ins/lxde
  [54]  funtoo/1.0/linux-gnu/mix-ins/lxqt
  [55]  funtoo/1.0/linux-gnu/mix-ins/no-emul-linux-x86
  [56]  funtoo/1.0/linux-gnu/mix-ins/no-systemd
  [57]  funtoo/1.0/linux-gnu/mix-ins/print
  [58]  funtoo/1.0/linux-gnu/mix-ins/python3-only
  [59]  funtoo/1.0/linux-gnu/mix-ins/X
  [60]  funtoo/1.0/linux-gnu/mix-ins/xfce
  [61]  funtoo/1.0/linux-gnu/mix-ins/vmware-guest
  [62]  funtoo/1.0/linux-gnu/mix-ins/hardened

Ядро:
Код: выделить все
tupoll@awesome ~ % uname -a
Linux awesome 4.0.4-gentoo #3 SMP Thu May 28 16:02:31 UTC 2015 x86_64 AMD Phenom(tm) II X4 B55 Processor AuthenticAMD GNU/Linux

Вот так за сутки можно посмеяться над неуловимым неубиваемым линуксом Gentoo.
Правильный линукс-BSD.
Аватар пользователя
tupoll
Уважаемый участник
Уважаемый участник
 
Автор темы
Сообщений: 235
Фото: 3
Стаж: 3 года 7 месяцев
Откуда: Vladivostok
Благодарил (а): 31 раз.
Поблагодарили: 44 раз.

Funtoo,плюсы и минусы.

Спонсор

Спонсор
 

Вернуться в ОСТАЛЬНЫЕ ДИСТРИБУТИВЫ

Кто сейчас на форуме

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 1