Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Desktop Environments
  • Search

Window manager support for Big Desktop/TwinView [SOLVED]

Problems with GUI applications? Questions about X, KDE, Gnome, Fluxbox, etc.? Come on in. NOTE: For multimedia, go up one forum
Post Reply
Advanced search
8 posts • Page 1 of 1
Author
Message
SDraconis
n00b
n00b
Posts: 53
Joined: Wed Apr 20, 2005 1:33 am

Window manager support for Big Desktop/TwinView [SOLVED]

  • Quote

Post by SDraconis » Mon Mar 05, 2007 5:01 am

Okay, so I've figured out the dual display options with Linux now. We've got Dual Head, which does dual screens but doesn't allow dragging between them. To solve that, there's Xinerama to combine the screens together, but without hardware acceleration. Finally, ATI and nVidia have released Big Desktop w/PairMode and TwinView, respectively, solving the acceleration problem. However, it seems that this last solution is problematic because window managers can't detect where one screen begins and another ends. In this case, I'm guessing the only way to handle it is to manually indicate to the WM the dimensions of each screen and their orientation. I can't seem to figure this out in IceWM so far. Is there any similar lightweight WM that has support for this? What about the big two (KDE & Gnome)?
Last edited by SDraconis on Tue Mar 06, 2007 12:23 am, edited 1 time in total.
Top
fangorn
Veteran
Veteran
User avatar
Posts: 1886
Joined: Sat Jul 31, 2004 1:31 pm
Contact:
Contact fangorn
Website

  • Quote

Post by fangorn » Mon Mar 05, 2007 1:57 pm

what problem do you have with window managers?

Do you want to maximize only on one monitor? works with fvwm, fluxbox, kde, gnome, ... if you enable xinerama support in X (and probably use flag)

I dont know of an option to make the border between the two monitors snappable, but I think this would be doable in fvwm :wink:
Video Encoding scripts collection | Project page
Top
sonicbhoc
Veteran
Veteran
User avatar
Posts: 1805
Joined: Mon Oct 24, 2005 7:52 pm
Location: In front of the computer screen
Contact:
Contact sonicbhoc
Website

  • Quote

Post by sonicbhoc » Mon Mar 05, 2007 2:27 pm

iirc Beryl has support for this.
I'm too lazy to keep this stupid signature up to date, so here's something more interesting:
My friend Hetdegon can draw if you ask me.
Now using PClinuxOS on my laptop and Gentoo on my desktop and new laptop.
Top
SDraconis
n00b
n00b
Posts: 53
Joined: Wed Apr 20, 2005 1:33 am

  • Quote

Post by SDraconis » Mon Mar 05, 2007 4:30 pm

fangorn wrote:Do you want to maximize only on one monitor? works with fvwm, fluxbox, kde, gnome, ... if you enable xinerama support in X (and probably use flag)
That's exactly what I want, but I am using ATI's Big Desktop mode (so I can get 3d acceleration on both displays) and not Xinerama.
sonicbhoc wrote:iirc Beryl has support for this.
Thanks, I'll look into Beryl.
Last edited by SDraconis on Mon Mar 05, 2007 11:28 pm, edited 2 times in total.
Top
SDraconis
n00b
n00b
Posts: 53
Joined: Wed Apr 20, 2005 1:33 am

  • Quote

Post by SDraconis » Mon Mar 05, 2007 11:20 pm

Turns out Beryl is known not to work with ATI's Big Desktop mode, as it doesn't handle combined resolutions as high as mine (1680x1050 + 1280x1024). Any other ideas?
Top
SDraconis
n00b
n00b
Posts: 53
Joined: Wed Apr 20, 2005 1:33 am

  • Quote

Post by SDraconis » Tue Mar 06, 2007 12:23 am

Wow, turns out turning on Xinerama support in my WM does work. I thought that Big Desktop mode didn't support Xinerama extensions for detecting displays. I guess I was wrong.
Top
tronica
n00b
n00b
Posts: 37
Joined: Thu Nov 09, 2006 2:24 pm

  • Quote

Post by tronica » Tue Mar 06, 2007 3:00 am

could you post your xorg, i need a reference. thanks.
Top
SDraconis
n00b
n00b
Posts: 53
Joined: Wed Apr 20, 2005 1:33 am

  • Quote

Post by SDraconis » Tue Mar 06, 2007 8:48 am

Sure thing. This is my config for a Big Desktop setup with my primary 1680x1050 display on the right and the secondary 1280x1024 display on the left. Note that after loading X I need to use xrandr to switch to the appropriate dimensions.

Code: Select all

# $XdotOrg: xc/programs/Xserver/hw/xfree86/xorgconf.cpp,v 1.2 2004/04/23 19:20:02 eich Exp $
#
# Copyright (c) 1994-1998 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# $XConsortium: XF86Conf.cpp /main/22 1996/10/23 11:43:51 kaleb $
# **********************************************************************
# This is a sample configuration file only, intended to illustrate
# what a config file might look like.  Refer to the XF86Config(4/5)
# man page for details about the format of this file. This man page
# is installed as /usr/share/man/man5/xorg.conf.5x 
# **********************************************************************
# The ordering of sections is not important in version 4.0 and later.
# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Module section -- this is an optional section which is used to specify
# which run-time loadable modules to load when the X server starts up.
# **********************************************************************
# **********************************************************************
# Server flags section.  This contains various server-wide Options.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# Some examples of extended input devices
# Section "InputDevice"
#    Identifier	"spaceball"
#    Driver	"magellan"
#    Option	"Device"	"/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier	"spaceball2"
#    Driver	"spaceorb"
#    Option	"Device"	"/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier	"touchscreen0"
#    Driver	"microtouch"
#    Option	"Device"	"/dev/ttyS0"
#    Option	"MinX"		"1412"
#    Option	"MaxX"		"15184"
#    Option	"MinY"		"15372"
#    Option	"MaxY"		"1230"
#    Option	"ScreenNumber"	"0"
#    Option	"ReportingMode"	"Scaled"
#    Option	"ButtonNumber"	"1"
#    Option	"SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier	"touchscreen1"
#    Driver	"elo2300"
#    Option	"Device"	"/dev/ttyS0"
#    Option	"MinX"		"231"
#    Option	"MaxX"		"3868"
#    Option	"MinY"		"3858"
#    Option	"MaxY"		"272"
#    Option	"ScreenNumber"	"0"
#    Option	"ReportingMode"	"Scaled"
#    Option	"ButtonThreshold"	"17"
#    Option	"ButtonNumber"	"1"
#    Option	"SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# **********************************************************************
# Screen sections.
# **********************************************************************
# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".  In this example, "Mouse1" is the core pointer,
# and "Mouse2" is an extended input device that also generates core
# pointer events (i.e., both mice will move the standard pointer).
	Identifier     "Main Layout"
	Screen      0  "aticonfig Screen 0" 0 0
	InputDevice    "Mouse1" "CorePointer"
	InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "ServerLayout"
	Identifier     "another layout"
	Screen         "Screen 1" 0 0
	Screen         "Screen MGA 1" 0 0
	InputDevice    "Mouse1" "CorePointer"
	InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "ServerLayout"
	Identifier     "simple layout"
	Screen         "Screen 1" 0 0
	InputDevice    "Mouse1" "CorePointer"
	InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
    # For XFS, uncomment this and comment the others
    # FontPath	"unix/:-1"
# The default path is shown here.
	FontPath     "/usr/share/fonts/local/"
	FontPath     "/usr/share/fonts/misc/"
	FontPath     "/usr/share/fonts/75dpi/:unscaled"
	FontPath     "/usr/share/fonts/100dpi/:unscaled"
	FontPath     "/usr/share/fonts/Type1/"
	FontPath     "/usr/share/fonts/TTF/"
	FontPath     "/usr/share/fonts/CID/"
	FontPath     "/usr/share/fonts/Speedo/"
	FontPath     "/usr/share/fonts/75dpi/"
	FontPath     "/usr/share/fonts/100dpi/"
EndSection

Section "Module"

# This loads the DBE extension module.
# initialisation of the XFree86-DGA extension within that module.
# This loads the Type1 and FreeType font modules
	Load  "dbe"
# This loads the miscellaneous extensions module, and disables
	SubSection "extmod"
		Option	    "omit xfree86-dga"
	EndSubSection
	Load  "type1"
	Load  "freetype"
	Load  "dri"
	Load  "glx"
EndSection

Section "DRI"
	Mode 0666
EndSection

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
#    Option	"NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.
#    Option	"DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
#    Option	"DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.
#    Option	"DontZoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
#    Option	"DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
#    Option	"AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
#    Option	"DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
#    Option	"AllowNonLocalModInDev"
# Set the basic blanking screen saver timeout.
# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.
# Option   "EstimateSizesAggresively" "0"
	Option	    "blank time" "10"	# 10 minutes
	Option	    "standby time" "20"
	Option	    "suspend time" "30"
	Option	    "off time" "60"
# On some platform the server needs to estimate the sizes of PCI
EndSection

Section "InputDevice"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris), comment
# out the above line, and uncomment the following line.
#    Option	"Protocol"	"Xqueue"
# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.
#    Option	"Xleds"	"1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#    Option	"XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option	"XkbModel"	"pc102"
#    Option	"XkbModel"	"pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option	"XkbModel"	"microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option	"XkbModel"	"pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
#    Option	"XkbLayout"	"de"
#
# or:
#
#    Option	"XkbLayout"	"de"
#    Option	"XkbVariant"	"nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
#    Option	"XkbOptions"	"ctrl:swapcaps"
# These are the default XKB settings for xorg
#
#    Option	"XkbModel"	"pc101"
#    Option	"XkbLayout"	"us"
#    Option	"XkbVariant"	""
#    Option	"XkbOptions"	""
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
	Identifier  "Keyboard1"
	Driver      "kbd"
EndSection

Section "InputDevice"

# Identifier and driver
# The mouse protocol and device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.
# protocol setting can be used when using a newer PnP mouse:
#    Option	"Protocol"	"Auto"
# When using mouse connected to a PS/2 port (aka "MousePort"), set the
# the protocol as follows.  On some platforms some other settings may
# be available.
#    Option "Protocol"	"PS/2"
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris), use
# the following instead of any of the lines above.  The Device line
# is not required in this case.
#    Option	"Protocol"	"Xqueue"
# Baudrate and SampleRate are only for some older Logitech mice.  In
# almost every case these lines should be omitted.
#    Option	"BaudRate"	"9600"
#    Option	"SampleRate"	"150"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
#    Option	"Emulate3Buttons"
#    Option	"Emulate3Timeout"	"50"
# ChordMiddle is an option for some 3-button Logitech mice, or any
# 3-button mouse where the middle button generates left+right button
# events.
#    Option	"ChordMiddle"
	Identifier  "Mouse1"
	Driver      "mouse"
	Option	    "Protocol" "ImPS/2"
	Option	    "Device" "/dev/input/mice"
	Option	    "Buttons" "7"
	Option	    "ZAxisMapping" "4 5"
# On platforms where PnP mouse detection is supported the following
EndSection

Section "InputDevice"
	Identifier  "Mouse2"
	Driver      "mouse"
	Option	    "Protocol" "MouseMan"
	Option	    "Device" "/dev/mouse2"
EndSection

Section "Monitor"

# The identifier line must be present.
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    HorizSync	31.5  # typical for a single frequency fixed-sync monitor
#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    VertRefresh	60  # typical for a single frequency fixed-sync monitor
#    VertRefresh	50-100        # multisync
#    VertRefresh	60, 65        # multiple fixed sync frequencies
#    VertRefresh	40-50, 80-100 # multiple ranges of sync frequencies
# Modes can be specified in two formats.  A compact one-line format, or
# a multi-line format.
# A generic VGA 640x480 mode (hsync = 31.5kHz, refresh = 60Hz)
# These two are equivalent
#    ModeLine "640x480" 25.175 640 664 760 800 480 491 493 525
# These two are equivalent
#    ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace
#    Mode "1024x768i"
#        DotClock	45
#        HTimings	1024 1048 1208 1264
#        VTimings	768 776 784 817
#        Flags		"Interlace"
#    EndMode
# If a monitor has DPMS support, that can be indicated here.  This will
# enable DPMS when the monitor is used with drivers that support it.
#    Option	"dpms"
# If a monitor requires that the sync signals be superimposed on the
# green signal, the following option will enable this when used with
# drivers that support it.  Only a relatively small range of hardware
# (and drivers) actually support this.
#    Option	"sync on green"
	Identifier   "Generic Monitor"
	ModeLine     "640x480" 25.2 640 664 760 800 480 491 493 525
EndSection

Section "Monitor"
	Identifier   "aticonfig Monitor 0"
EndSection

Section "Device"

# The Identifier must be present.
# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.
#    Chipset	"generic"
# Various other lines can be specified to override the driver's automatic
# detection code.  In most cases they are not needed.
#    VideoRam	256
#    Clocks	25.2 28.3
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.
#    BusID	"PCI:0:10:0"
# Various option lines can be added here as required.  Some options
# are more appropriate in Screen sections, Display subsections or even
# Monitor sections.
#    Option	"hw cursor" "off"
	Identifier  "Generic VGA"
	Driver      "vga"
EndSection

Section "Device"
	Identifier  "any supported Trident chip"
	Driver      "trident"
EndSection

Section "Device"
	Identifier  "MGA Millennium I"
	Driver      "mga"
	Option	    "hw cursor" "off"
	BusID       "PCI:0:10:0"
EndSection

Section "Device"
	Identifier  "MGA G200 AGP"
	Driver      "mga"
	Option	    "pci retry"
	BusID       "PCI:1:0:0"
EndSection

Section "Device"
	Identifier  "ATI Graphics Adapter 0"
	Driver      "fglrx"
	Option	    "ForceMonitors" "notv"
	Option	    "UseInternalAGPGART" "on"

	# Dual screen ("Big desktop")
	Option	    "DesktopSetup" "horizontal,reverse"
	Option	    "PairModes" "1680x1050+1280x1024"
	Option      "OverlayOnCRTC2" "0"
	Option		"EnablePrivateBackZ"	"yes" #Enable 3d support

	BusID       "PCI:1:0:0"
EndSection

Section "Extensions"
	Option	"Composite"	"0"
EndSection

Section "Screen"

# The Identifier, Device and Monitor lines must be present
# The favoured Depth and/or Bpp may be specified here
	Identifier "Screen 1"
	Device     "Generic VGA"
	Monitor    "Generic Monitor"
	DefaultDepth     24
	SubSection "Display"
		Depth     24
		Modes    "1680x1050" "1280x800"
	EndSubSection
	SubSection "Display"
		Depth     4
		Modes    "640x480"
	EndSubSection
	SubSection "Display"
		Depth     1
		Modes    "640x480"
	EndSubSection
EndSection

Section "Screen"

#    DefaultDepth	24
	Identifier "Screen MGA1"
	Device     "MGA Millennium I"
	Monitor    "Generic Monitor"
	DefaultDepth     16
	Option	    "no accel"
	SubSection "Display"
		Depth     8
		Visual    "StaticColor"
		Modes    "1280x1024"
		Option	    "rgb bits" "8"
	EndSubSection
	SubSection "Display"
		Depth     16
		Modes    "1280x1024"
	EndSubSection
	SubSection "Display"
		Depth     24
		Modes    "1280x1024"
	EndSubSection
EndSection

Section "Screen"
	Identifier "Screen MGA2"
	Device     "MGA G200 AGP"
	Monitor    "Generic Monitor"
	DefaultDepth     8
	SubSection "Display"
		Depth     8
		Visual    "StaticColor"
		Modes    "1280x1024"
		Option	    "rgb bits" "8"
	EndSubSection
EndSection

Section "Screen"
	Identifier "aticonfig Screen 0"
	Device     "ATI Graphics Adapter 0"
	Monitor    "aticonfig Monitor 0"
	DefaultDepth     24
	SubSection "Display"
		Depth     24
		Modes    "1680x1050" "1280x800"
	EndSubSection
EndSection

Top
Post Reply

8 posts • Page 1 of 1

Return to “Desktop Environments”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy