FC18 kernel command lines
by Bill Davidsen
Two simple suggestions for install, upgrade, etc.
1 - fix the kernel command line options, I think one was console font, replace
the ones which the kernel labels as "obsolete" and/or "archaic" with something
which works silently with the kernels installed.
2 - for reasons religious, political, or egotistical, Fedora doesn't use working
vendor video drivers for chips sets identified as nVidia, ATI, Radeon, etc.
Would it be too much to ask to always without fail provide a boot line using
VESA driver for display, and rather than do whatever is current, use a screen
size large enough to hold some minimum number of characters? The install on one
netbook picked 320x200 for screen resolution, and it seems the vga= option is no
longer supported (maybe just vga=ask). In any case, the default kernel drivers
for these video cards only work right on a subset of chips, and a lot of users
don't know, and don't want to know, how to edit the kernel command line in the
middle of the boot sequence to overcome the issue.
3 - I know of no way to tell if "nomodeset" will make things better or worse, so
I make no suggestion other than users who know how to edit the kernel command
line can try inverting that option (remove if present, add if not) if all else
fails to initialize the video at boot.
I'm sure these suggestions for improvement will be flamed as criticism, followed
by the users of the subset of working chips claiming that the drivers are fixed
because it works on their hardware.
--
Bill Davidsen <davidsen(a)tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
11 years
RE: Avoiding LVM -
by J.Witvliet＠mindef.nl
-----Original Message-----
From: users-bounces(a)lists.fedoraproject.org [mailto:users-bounces@lists.fedoraproject.org] On Behalf Of Craig White
Sent: zaterdag 6 april 2013 3:45
To: users(a)lists.fedoraproject.org
Subject: Re: Avoiding LVM -
On Thu, 2013-04-04 at 12:41 -0500, Matthew J. Roth wrote:
> Joe Zeff wrote:
> >
> > On 04/04/2013 08:45 AM, Bill Oliver wrote:
> > >
> > > I take my laptop on the road a lot, and I have work stuff on it I
> > > don't want the world to see. I don't encrypt the whole disk, but
> > > I have an encrypted partitiion, and keep sensitive data on it.
> >
> > You might also consider keeping it on a flash drive with an ext4
> > file system, as most people who'd find it wouldn't know how to read it.
>
>
> As a warning to future readers, this is just bad advice because then
> the files would be unencrypted on a device that is much easier to lose.
----
and one that has a substantially higher likelihood of failure than a hard drive. It was a bad recommendation on so many levels. Anyone who entrusts their only copy of a valued file to a USB flash drive is certain to learn a lesson the hard way.
Craig
-----Original Message-----
So, a better advise is to simply encrypt the entire disk,
And to keep sensitive info on an _also_ encrypted mem-stick.
If you worry about failures (loosing) the mem stick, perhaps you can put the encrypted image on your own web-site...
Or keep an "dd"-copy of the stick in "/tmp/random.tmp"
Security has its price, the more secure you want to feel, the higher the costs, or efforts.
Hw
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
11 years
Gnome dies just before login screen F18
by Kevin
I been having Gnome fail at the login screen intermittently since I
reinstalled a few weeks ago. I read that `setenforce 0` should fix
the problem and it did for about a week, but this time I'm really
stuck. `getenforce` returns Permissive and the problem persists. In
the attached paste from /var/log/messages I tried google for
"gnome-shell.desktop respawning too quickly" and most of the solutions
involve graphics cards I don't have.
Also, the error I see on the screen is the gnome sad face.
thanks in advance for any ideas
3.8.5-201.fc18.x86_64
http://pastebin.com/hUsewVjz
Kevin
DON'T PANIC
11 years
mailto links from Chrome w/Thunderbird
by SternData
If I click on a mailto link in Firefox, Thunderbird opens up a new email
with "user(a)domain.com" in the address field. If I click on the same link
in Chrome, Thunderbird displays "mailto:user@domain.com" in the address
field.
Anyone have an idea where in Chrome I might fix this?
--
-- Steve
11 years
RE: Avoiding LVM -
by J.Witvliet＠mindef.nl
-----Original Message-----
I think I can handle the next install without LVM.
-----Original Message-----
Afaicr LVM is the only option if you want to encrypt your entire disk.
Hw
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
11 years
esint10.pfb
by Patrick Dupre
Hello,
I got an error when I compile an old latex file:
!pdfTeX error: pdflatex (file esint10.pfb): cannot open Type 1 font
file for re
I have texlive-esint.noarch installed.
which install the mf file:
/usr/share/texlive/texmf-dist/fonts/source/public/esint/esint10.mf
but not esint10.pfb.
How can I get this font?
Thank
--
======================================================================
Patrick DUPRÉ || email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale ||
Tel. (33)-(0)3 28 23 76 12 || Fax: 03 28 65 82 44
189A, avenue Maurice Schumann || 59140 Dunkerque, France
======================================================================
11 years
fedora18 stopped suspending on lid closed
by Aleksandar Kostadinov
From some time my fedora stopped suspending when lid is closed. I see
in system log that lid event is detected. So I'm wondering what can be
the cause.
Suspend works when I choose to suspend clicking on the XFCE power applet.
Pls keep me in cc in replies.
Thanks!
11 years
wifi issue on F17, eeepc 901
by Fred Smith
Hi all!
This has been going on for a few months now, but I haven't gotten around
to asking about it yet, so here goes:
I've got F17 on my eeepc 901, where it works quite well. But after it had
been on that machine for a while (a month? two? I can't say) it started
exhibiting a problem:
using the FN keys, turn off wireless networking, then turn it back on.
the blue idiot light shows it's on, but Fedora never re-connects the
wlan. in fact, it still thinks the wireless hardware is turned off,
as it would appear, since clicking the NM icon does not even show any
wlans at all.
a quick reboot/power cycle fixes it.
it's mostly not an issue, but sometimes becomes a nuisance, since turning
off wireless networking can be a big battery-life-enhancer.
Anyone got clues?
here's some entries from /var/log/messages thath I think correspond
to turning it off then attempting to turn it back on. Some of the entries
around 20:46:01 say something aboujt the PCI device being absent, so
that probably tells us something useful...:
Apr 4 20:18:59 eeepcbox kernel: [ 2697.351491] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3
-2/3-2:1.0/input/input10
Apr 4 20:18:59 eeepcbox kernel: [ 2697.354256] hid-generic 0003:046D:C51B.0001: input,hidraw0: USB HID v1.11 Mouse [Lo
gitech USB Receiver] on usb-0000:00:1d.1-2/input0
Apr 4 20:18:59 eeepcbox kernel: [ 2697.371261] hid-generic 0003:046D:C51B.0002: hiddev0,hidraw1: USB HID v1.11 Device
[Logitech USB Receiver] on usb-0000:00:1d.1-2/input1
Apr 4 20:18:59 eeepcbox mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2"
Apr 4 20:18:59 eeepcbox mtp-probe: bus: 3, device: 2 was not an MTP device
Apr 4 20:45:00 eeepcbox kernel: [ 4258.590137] wlan0: deauthenticating from bc:ae:c5:c3:60:04 by local choice (reason=
3)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.598188] cfg80211: Calling CRDA to update world regulatory domain
Apr 4 20:45:00 eeepcbox NetworkManager[716]: <info> WiFi now disabled by radio killswitch
Apr 4 20:45:00 eeepcbox NetworkManager[716]: <info> (wlan0): device state change: activated -> unavailable (reason 'no
ne') [100 20 0]
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Interface wlan0.IPv4 no longer relevant for mDNS.
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2
.117.
Apr 4 20:45:00 eeepcbox dhclient[1905]: receive_packet failed on wlan0: Network is down
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Withdrawing address record for fe80::215:afff:febc:ba13 on wlan0.
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637132] cfg80211: World regulatory domain updated:
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637144] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max
_eirp)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637153] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637162] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637169] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637177] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637185] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637240] cfg80211: Calling CRDA for country: US
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Withdrawing address record for 192.168.2.117 on wlan0.
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Withdrawing workstation service for wlan0.
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655253] cfg80211: Regulatory domain changed to country: US
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655264] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max
_eirp)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655273] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655280] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655288] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655296] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655304] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655312] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655318] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm
)
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> (wlan0): deactivating device (reason 'none') [0]
Apr 4 20:18:59 eeepcbox kernel: [ 2697.351491] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3
-2/3-2:1.0/input/input10
Apr 4 20:18:59 eeepcbox kernel: [ 2697.354256] hid-generic 0003:046D:C51B.0001: input,hidraw0: USB HID v1.11 Mouse [Lo
gitech USB Receiver] on usb-0000:00:1d.1-2/input0
Apr 4 20:18:59 eeepcbox kernel: [ 2697.371261] hid-generic 0003:046D:C51B.0002: hiddev0,hidraw1: USB HID v1.11 Device
[Logitech USB Receiver] on usb-0000:00:1d.1-2/input1
Apr 4 20:18:59 eeepcbox mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2"
Apr 4 20:18:59 eeepcbox mtp-probe: bus: 3, device: 2 was not an MTP device
Apr 4 20:45:00 eeepcbox kernel: [ 4258.590137] wlan0: deauthenticating from bc:ae:c5:c3:60:04 by local choice (reason=
3)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.598188] cfg80211: Calling CRDA to update world regulatory domain
Apr 4 20:45:00 eeepcbox NetworkManager[716]: <info> WiFi now disabled by radio killswitch
Apr 4 20:45:00 eeepcbox NetworkManager[716]: <info> (wlan0): device state change: activated -> unavailable (reason 'no
ne') [100 20 0]
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Interface wlan0.IPv4 no longer relevant for mDNS.
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2
.117.
Apr 4 20:45:00 eeepcbox dhclient[1905]: receive_packet failed on wlan0: Network is down
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Withdrawing address record for fe80::215:afff:febc:ba13 on wlan0.
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637132] cfg80211: World regulatory domain updated:
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637144] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max
_eirp)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637153] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637162] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637169] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637177] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637185] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.637240] cfg80211: Calling CRDA for country: US
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Withdrawing address record for 192.168.2.117 on wlan0.
Apr 4 20:45:00 eeepcbox avahi-daemon[760]: Withdrawing workstation service for wlan0.
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655253] cfg80211: Regulatory domain changed to country: US
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655264] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max
_eirp)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655273] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655280] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655288] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655296] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655304] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655312] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm
)
Apr 4 20:45:00 eeepcbox kernel: [ 4258.655318] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm
)
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> (wlan0): deactivating device (reason 'none') [0]
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> (wlan0): deactivating device (reason 'none') [0]
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1905
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <warn> (3) failed to find interface name for index
Apr 4 20:45:01 eeepcbox NetworkManager[716]: nm_system_iface_flush_routes: assertion `iface != NULL' failed
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <warn> (3) failed to find interface name for index
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <warn> (3) failed to find interface name for index
Apr 4 20:45:01 eeepcbox NetworkManager[716]: (nm-system.c:769):nm_system_iface_get_flags: runtime check failed: (iface != NULL)
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <error> [1365122701.342927] [nm-system.c:771] nm_system_iface_get_flags(): (unknown): failed to get interface link object
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> radio killswitch /sys/devices/pci0000:00/0000:00:1c.3/0000:01:00.0/ieee80211/phy0/rfkill2 disappeared
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> (wlan0): now unmanaged
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> (wlan0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <info> (wlan0): cleaning up...
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <warn> (3) failed to find interface name for index
Apr 4 20:45:01 eeepcbox NetworkManager[716]: (nm-system.c:769):nm_system_iface_get_flags: runtime check failed: (iface != NULL)
Apr 4 20:45:01 eeepcbox NetworkManager[716]: <error> [1365122701.345881] [nm-system.c:771] nm_system_iface_get_flags(): (unknown): failed to get interface link object
Apr 4 20:45:01 eeepcbox dbus-daemon[804]: dbus[804]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 4 20:45:01 eeepcbox dbus[804]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 4 20:45:01 eeepcbox dbus-daemon[804]: dbus[804]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 4 20:45:01 eeepcbox dbus[804]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 4 20:45:01 eeepcbox systemd[1]: Cannot add dependency job for unit mdmonitor-takeover.service, ignoring: Unit mdmonitor-takeover.service failed to load: No such file or directory. See system logs and 'systemctl status mdmonitor-takeover.service' for details.
Apr 4 20:45:01 eeepcbox systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Apr 4 20:45:01 eeepcbox chronyd[813]: Source 208.69.120.201 offline
Apr 4 20:45:01 eeepcbox chronyd[813]: Source 96.44.142.5 offline
Apr 4 20:45:01 eeepcbox chronyd[813]: Source 216.45.57.38 offline
Apr 4 20:45:01 eeepcbox chronyd[813]: Source 199.102.46.72 offline
Apr 4 20:45:01 eeepcbox systemd[1]: PID 1964 read from file /run/sm-client.pid does not exist.
Apr 4 20:46:41 eeepcbox kernel: [ 4359.079852] eeepc_laptop: BIOS says wireless lan is unblocked, but the pci device is absent
Apr 4 20:46:41 eeepcbox kernel: [ 4359.079868] eeepc_laptop: skipped wireless hotplug as probably inappropriate for this model
Apr 4 20:46:41 eeepcbox NetworkManager[716]: <info> WiFi now enabled by radio killswitch
Apr 4 20:46:41 eeepcbox kernel: [ 4359.179813] eeepc_laptop: BIOS says wireless lan is unblocked, but the pci device is absent
Apr 4 20:46:41 eeepcbox kernel: [ 4359.179822] eeepc_laptop: skipped wireless hotplug as probably inappropriate for this model
Apr 4 20:46:42 eeepcbox kernel: [ 4360.286865] eeepc_laptop: BIOS says wireless lan is unblocked, but the pci device is absent
Apr 4 20:46:42 eeepcbox kernel: [ 4360.286880] eeepc_laptop: skipped wireless hotplug as probably inappropriate for this model
Apr 4 20:46:42 eeepcbox kernel: [ 4360.386869] eeepc_laptop: BIOS says wireless lan is unblocked, but the pci device is absent
Apr 4 20:46:42 eeepcbox kernel: [ 4360.386883] eeepc_laptop: skipped wireless hotplug as probably inappropriate for this model
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
"And he will be called Wonderful Counselor, Mighty God, Everlasting Father,
Prince of Peace. Of the increase of his government there will be no end. He
will reign on David's throne and over his kingdom, establishing and upholding
it with justice and righteousness from that time on and forever."
------------------------------- Isaiah 9:7 (niv) ------------------------------
11 years
auditd is afiled how to enable
by Prashanth Kasula
Hi all,
For sshd service there is a problem in enabling auditd service.if any one
knows the process please let us know.
Thanks
Prashanth
11 years
Avoiding LVM -
by Bob Goodwin
On 02/04/13 14:13, Joe Zeff wrote:
As a home user, I don't need to resize things dynamically, and LVM is
the solution to a problem I don't have.
Over the last couple of years I've managed to install Fedora a few times
minus LVM but I never seem to get the directory structure optimized, in
fact far from it.
What I need is an example of a simple directory tree with the proper
sizes. I may not get to try it until F-19 is released but would like to
have an example on hand, might be inspired to try redoing an F-18 LVM
installation.
Bob
--
http://www.qrz.com/db/W2BOD
box10 Fedora-18 XFCE Linux
11 years
