Re: Dates? Re: Printing woes...
No its not. Here are two lines from your headers: Received: from paradise.net.nz (210-246-27-184.paradise.net.nz [210.246.27.184]) by smtp4.clear.net.nz (CLEAR Net Mail) with ESMTP id [EMAIL PROTECTED] for linux-users@it.canterbury.ac.nz; Tue, 13 May 2008 17:28:53 +1200 (NZST) Date: Wed, 14 May 2008 09:29:48 +1200 This shows your message dated tomorrow at 9;29 am but received by paradise today at 5:28 pm Your timezone is set right, now as root run: ntpdate nz.pool.ntp.org That will set your date right and it should be fine from there on in. On Wed, May 14, 2008 at 9:29 AM, Barry [EMAIL PROTECTED] wrote: Thanks, Please check that its ok now. Its the result of a new install which caused me a lot of grief Barry Craig Falconer wrote: On Tue, 2008-05-14 at 05:18 -0400, Barry wrote: ^ Your clock is one day fast, and you're in the wrong timezone. So your emails are dated 10 hours in the future. Just thought you'd like to know...
Re: Dates? Re: Printing woes...
On Tue, 13 May 2008 18:56:11 +1200 Nick Rout [EMAIL PROTECTED] wrote: ntpdate nz.pool.ntp.org If is whinges that the port is already in use, then sudo /etc/init.d/ntp stop ( that might be ntpd or ntp-server on Mandriva - not sure ) Then sudo ntpdate nz.pool.ntp.org then sudo /etc/init.d/ntp start They ( ntp and ntpdate ) sort of do the same thing, but the ntpdate program is designed to be a large mallet, run once to correct the time no matter how wrong it is, then the ntp daemon attempts to keep it there, but it can only make small changes. I usually update the /etc/init.d/ntp script so that it calls ntpdate before starting the daemon, so the clock's put right when the machine's switched on. This used to be standard practice on DEC and HP Unixes ( where are they now! ). Steve -- Steve Holdoway [EMAIL PROTECTED]
Re: A quick quiz for fun
On Monday 12 May 2008 21:16, Christopher Sawtell wrote: Your score: 100 out of 100. I only scored 100/100. Guessed the month Linux was released, as well. The question of Wang VS versus S/390 amused me - those Wangs are museum pieces by now, surely! ;) Wesley Parish Not too terribly difficult imho I too guessed the the month Linux was released. I just tied it in to the Northern academic timetable, surprise surprise. On Mon, May 12, 2008 at 8:17 PM, Ross Drummond [EMAIL PROTECTED] wrote: On Mon, 12 May 2008, Nick Rout wrote: http://www.pcworld.idg.com.au/survey/9 Post back your results, I got 90/100. I got 90/100 which surprised me as some of my answers were no more than wild guesses. Cheers Ross Drummond -- Clinersterton beademung, with all of love - RIP James Blish - Gaul is quartered into three halves. Things which are impossible are equal to each other. Guerrilla warfare means up to their monkey tricks. Extracts from Schoolboy Howlers - the collective wisdom of the foolish. - Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.
USB drive needs nudge to automount (Ubuntu 7.10)
At some point, Ubuntu stopped automounting my USB drives. It hasn't been a major inconvenience, but I thought I'd probe the collective wisdom and see if I can't come up with a solution. If I plug in a memory stick, nothing happens. Then I open the Removable drives and media control panel. *Sometimes* that's enough to get the system to recognize them, but usually I need to toggle the automatically mount option off then back on to get the drive to show up. Any ideas on why the system needs a little nudge to get it to notice the drive? --Mike ** This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails. Views expressed in this email may not be those of the Airways Corporation of New Zealand Limited **
Updating ubuntu for openssl/openssh vulnerabilities
There is a huge debian/ubuntu (and distros based on them) security issue through a screw up by debian in removing random number generation from the generation of keys in libssl (part of openssl) a couple of years ago. The reports for ubuntu are here: https://lists.ubuntu.com/archives/ubuntu-security-announce/2008-May/000705.html https://lists.ubuntu.com/archives/ubuntu-security-announce/2008-May/000706.html Oh and openvpn is affected too, although that isn't used by me https://lists.ubuntu.com/archives/ubuntu-security-announce/2008-May/000707.html Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list.
Re: Tuesday night meeting...
I'd just like to thank last nights' speaker (was it Chris?) for his rather impromptu talk on networking last night - it was quite informative when things works (and sometimes when they weren't). It's making me seriously consider taking another look at KDE. Regards, Kerry
Re: Updating ubuntu for openssl/openssh vulnerabilities
On Wed, 14 May 2008 09:16:28 +1200 Nick Rout [EMAIL PROTECTED] wrote: There is a huge debian/ubuntu (and distros based on them) security issue through a screw up by debian in removing random number generation from the generation of keys in libssl (part of openssl) a couple of years ago. The reports for ubuntu are here: https://lists.ubuntu.com/archives/ubuntu-security-announce/2008-May/000705.html https://lists.ubuntu.com/archives/ubuntu-security-announce/2008-May/000706.html Oh and openvpn is affected too, although that isn't used by me https://lists.ubuntu.com/archives/ubuntu-security-announce/2008-May/000707.html Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list. Well, the irony is at the core of this. It is possible that you'll lose connectivity - permanently - if you upgrade over ssh. There are also some key upgrade issues that may affect your connectivity. I have no idea how they do it, but they do normally manage to keep the connections up. sudo apt-get install openssh-client openssh-server works fine over ssh though. Steve -- Steve Holdoway [EMAIL PROTECTED]
Re: Updating ubuntu for openssl/openssh vulnerabilities
Answering the question, Any idea why not? I believe that this can be due to broken or new dependencies.
Re: Updating ubuntu for openssl/openssh vulnerabilities
2008/5/14 Nick Rout [EMAIL PROTECTED]: Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list. do you need sudo apt-get dist-upgrade
Re: Tuesday night meeting...
2008/5/14 Kerry [EMAIL PROTECTED]: I'd just like to thank last nights' speaker (was it Chris?) for his Indeed -- thanks Chris! It's making me seriously consider taking another look at KDE. I'm just really impressed by the capabilities of fish. Is there any way of getting that on a gnome desktop without installing konqueror, or is one part-and-parcel of the other?
Re: Updating ubuntu for openssl/openssh vulnerabilities
On Wed, 14 May 2008 10:12:19 +1200 Roy Britten [EMAIL PROTECTED] wrote: 2008/5/14 Nick Rout [EMAIL PROTECTED]: Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list. do you need sudo apt-get dist-upgrade No, that is intended upgrade to a new distro - gutsy to hardy for example. Steve -- Steve Holdoway [EMAIL PROTECTED]
Re: Updating ubuntu for openssl/openssh vulnerabilities
On Wed, May 14, 2008 at 10:57 AM, Steve Holdoway [EMAIL PROTECTED] wrote: On Wed, 14 May 2008 10:12:19 +1200 Roy Britten [EMAIL PROTECTED] wrote: 2008/5/14 Nick Rout [EMAIL PROTECTED]: Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list. do you need sudo apt-get dist-upgrade No, that is intended upgrade to a new distro - gutsy to hardy for example. Steve -- Steve Holdoway [EMAIL PROTECTED] No its also useful where a new dependency is introduced (as in here where there is a new dependency on openssh-blacklist). see also here http://www.debian-administration.org/articles/69 And indeed I have lost connectivity and will fix it tonight. Never mind if I cannot log in I suppose no-one else can either :-) so in short the way to update openssh-* is to use dist-upgrade which will install the new dependency. This fubar seems to have rocked confidence in debian, but perhaps thats another discussion.
Re: Tuesday night meeting...
I think you can connect via sftp in a nautilus window. Which should have the same effect. On Wed, May 14, 2008 at 10:37 AM, Roy Britten [EMAIL PROTECTED] wrote: 2008/5/14 Kerry [EMAIL PROTECTED]: I'd just like to thank last nights' speaker (was it Chris?) for his Indeed -- thanks Chris! It's making me seriously consider taking another look at KDE. I'm just really impressed by the capabilities of fish. Is there any way of getting that on a gnome desktop without installing konqueror, or is one part-and-parcel of the other?
Re: Updating ubuntu for openssl/openssh vulnerabilities
On Wed, 14 May 2008 11:08:48 +1200 Nick Rout [EMAIL PROTECTED] wrote: On Wed, May 14, 2008 at 10:57 AM, Steve Holdoway [EMAIL PROTECTED] wrote: On Wed, 14 May 2008 10:12:19 +1200 Roy Britten [EMAIL PROTECTED] wrote: 2008/5/14 Nick Rout [EMAIL PROTECTED]: Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list. do you need sudo apt-get dist-upgrade No, that is intended upgrade to a new distro - gutsy to hardy for example. Steve -- Steve Holdoway [EMAIL PROTECTED] No its also useful where a new dependency is introduced (as in here where there is a new dependency on openssh-blacklist). see also here http://www.debian-administration.org/articles/69 And indeed I have lost connectivity and will fix it tonight. Never mind if I cannot log in I suppose no-one else can either :-) so in short the way to update openssh-* is to use dist-upgrade which will install the new dependency. Interesting. I just did exactly as I suggested, whilst ssh'd back in to my pc from my server - so ssh out then back in - and had no connectivity problems at all. I do just use password authentication here though. This fubar seems to have rocked confidence in debian, but perhaps thats another discussion. Also explains why I'm getting so many brute force breakin attempts on my servers... picked a good time to be out of the office again! Steve -- Steve Holdoway [EMAIL PROTECTED]
Re: Updating ubuntu for openssl/openssh vulnerabilities
On Wed, May 14, 2008 at 11:57 AM, Steve Holdoway [EMAIL PROTECTED] wrote: so in short the way to update openssh-* is to use dist-upgrade which will install the new dependency. Interesting. I just did exactly as I suggested, whilst ssh'd back in to my pc from my server - so ssh out then back in - and had no connectivity problems at all. I do just use password authentication here though. I think mine might have been a problem with a loss of network connectivity, our internet at the office has been diabolical today.
Re: Updating ubuntu for openssl/openssh vulnerabilities
On Wed, 14 May 2008 12:10:40 +1200 Nick Rout [EMAIL PROTECTED] wrote: On Wed, May 14, 2008 at 11:57 AM, Steve Holdoway [EMAIL PROTECTED] wrote: so in short the way to update openssh-* is to use dist-upgrade which will install the new dependency. Interesting. I just did exactly as I suggested, whilst ssh'd back in to my pc from my server - so ssh out then back in - and had no connectivity problems at all. I do just use password authentication here though. I think mine might have been a problem with a loss of network connectivity, our internet at the office has been diabolical today. There've been a lot of complaints about packet loss in Orcons routers as well as the stuff I mentioned over the weekend. -- Steve Holdoway [EMAIL PROTECTED]
Re: Updating ubuntu for openssl/openssh vulnerabilities
Steve Holdoway wrote: On Wed, 14 May 2008 11:08:48 +1200 Nick Rout [EMAIL PROTECTED] wrote: On Wed, May 14, 2008 at 10:57 AM, Steve Holdoway [EMAIL PROTECTED] wrote: On Wed, 14 May 2008 10:12:19 +1200 Roy Britten [EMAIL PROTECTED] wrote: 2008/5/14 Nick Rout [EMAIL PROTECTED]: Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list. do you need sudo apt-get dist-upgrade No, that is intended upgrade to a new distro - gutsy to hardy for example. Steve -- Steve Holdoway [EMAIL PROTECTED] No its also useful where a new dependency is introduced (as in here where there is a new dependency on openssh-blacklist). see also here http://www.debian-administration.org/articles/69 And indeed I have lost connectivity and will fix it tonight. Never mind if I cannot log in I suppose no-one else can either :-) so in short the way to update openssh-* is to use dist-upgrade which will install the new dependency. Interesting. I just did exactly as I suggested, whilst ssh'd back in to my pc from my server - so ssh out then back in - and had no connectivity problems at all. I do just use password authentication here though. This fubar seems to have rocked confidence in debian, but perhaps thats another discussion. Also explains why I'm getting so many brute force breakin attempts on my servers... picked a good time to be out of the office again! Steve Note doing an apt-get upgrade alone won't fix this - you need to regenerate all your SSH keys (user host) SSL certificates that have been created using this library as well. Be a little careful of just hitting apt-get dist-upgrade or you may be locked out of your boxes (openssh-blacklist gets installed and will block insecure keys). begin:vcard fn:Brett Davidson n:Davidson;Brett org:Net24 Limited;Network Operations adr:;;404 Barbadoes Street;Christchurch;;8041;New Zealand email;internet:[EMAIL PROTECTED] title:Systems Engineer tel;work:+64 3 962 9518 tel;cell:+64 21 868 137 note:CCNA, RHCE, MCSE, SCSA x-mozilla-html:TRUE url:www.net24.co.nz version:2.1 end:vcard
Re: Updating ubuntu for openssl/openssh vulnerabilities
On Wed, May 14, 2008 at 2:56 PM, Brett Davidson [EMAIL PROTECTED] wrote: Steve Holdoway wrote: On Wed, 14 May 2008 11:08:48 +1200 Nick Rout [EMAIL PROTECTED] wrote: On Wed, May 14, 2008 at 10:57 AM, Steve Holdoway [EMAIL PROTECTED] wrote: On Wed, 14 May 2008 10:12:19 +1200 Roy Britten [EMAIL PROTECTED] wrote: 2008/5/14 Nick Rout [EMAIL PROTECTED]: Anyway I am trying to update a system remotely (over ssh of course, how ironic). The openssh-client and -server updates don't seem to get applied: [EMAIL PROTECTED]:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: openssh-client openssh-server 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea why not? aptitude does much the same. This is on hardy, with no changes to the default sources.list. do you need sudo apt-get dist-upgrade No, that is intended upgrade to a new distro - gutsy to hardy for example. Steve -- Steve Holdoway [EMAIL PROTECTED] No its also useful where a new dependency is introduced (as in here where there is a new dependency on openssh-blacklist). see also here http://www.debian-administration.org/articles/69 And indeed I have lost connectivity and will fix it tonight. Never mind if I cannot log in I suppose no-one else can either :-) so in short the way to update openssh-* is to use dist-upgrade which will install the new dependency. Interesting. I just did exactly as I suggested, whilst ssh'd back in to my pc from my server - so ssh out then back in - and had no connectivity problems at all. I do just use password authentication here though. This fubar seems to have rocked confidence in debian, but perhaps thats another discussion. Also explains why I'm getting so many brute force breakin attempts on my servers... picked a good time to be out of the office again! Steve Note doing an apt-get upgrade alone won't fix this - you need to regenerate all your SSH keys (user host) SSL certificates that have been created using this library as well. Be a little careful of just hitting apt-get dist-upgrade or you may be locked out of your boxes (openssh-blacklist gets installed and will block insecure keys). True, but I did point to the security advisory which goes through the steps. host ssh keys *will* be updated but user keys will not. Not all user keys need re-generating, use ssh-vulnkey to check your keys. Its all in the advisory.
Totem, Mplayer crash on X error insufficient resources
Totem-xine and Mplayer both play videos fine up to 640x480, but won't play DVD or DV, being higher resolution: Totem: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 159 error_code 11 request_code 142 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Segmentation fault Mplayer: [snip] Starting playback... VDec: vo config request - 720 x 576 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1.36:1 - prescaling to correct movie aspect. VO: [xv] 720x576 = 786x576 Planar YV12 X11 error: BadAlloc (insufficient resources for operation)?,?% 0 0 X11 error: BadAlloc (insufficient resources for operation) X11 error: BadAlloc (insufficient resources for operation)?,?% 1 0 X11 error: BadAlloc (insufficient resources for operation)?,?% 2 0 X11 error: BadAlloc (insufficient resources for operation)?,?% 4 0 X11 error: BadAlloc (insufficient resources for operation)?,?% 6 0 X11 error: BadAlloc (insufficient resources for operation) X11 error: BadAlloc (insufficient resources for operation) There have been a number of bugs reported on launchpad: * https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/183969 o The version of xserver-xorg-core that they recommend was the one in Gutsy - which didn't work for me * https://bugs.launchpad.net/ubuntu/+source/totem/+bug/35229 o Fixed in Dapper * https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/124610 o SiS graphics chip, not Intel It worked fine in Dapper and Feisty, but broke when I upgraded to Gutsy. Hardy hasn't fixed it. Some people have recommended the following: http://ubuntuforums.org/archive/index.php/t-194746.html I added these lines to Section Device in xorg.conf: Option VideoRam 65536 Option CacheLines 1980 I've tried this to no avail, but I have little confidence that I got the lines in the right place. They are commented out in the attached xorg.conf. Suggestions? Thanks, Douglas. === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === # xorg.conf (xorg X Window System server configuration file) # # This file was generated by failsafeDexconf, using # values from the debconf database and some overrides to use vesa mode. # # You should use dexconf or another such tool for creating a real xorg.conf # For example: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files EndSection Section Module Loadglx LoadGLcore Loaddri Loadv4l EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 Option Emulate3Buttons true EndSection Section Device Identifier Failsafe Device Boardname Matrox Millennium G550 DualHead Busid PCI:1:0:0 Driver mga Screen 0 Vendorname Matrox EndSection Section Monitor Identifier Failsafe Monitor Vendorname ViewSonic Modelname ViewSonic PT795 Horizsync 30-110 Vertrefresh 50-180 modeline [EMAIL PROTECTED] 25.2 640 656 752 800 480 490 492 525 -vsync -hsync modeline [EMAIL PROTECTED] 31.5 640 664 704 832 480 489 491 520 -vsync -hsync modeline [EMAIL PROTECTED] 31.5 640 656 720 840 480 481 484 500 -vsync -hsync modeline [EMAIL PROTECTED] 36.0 640 696 752 832 480 481 484 509
Re: Totem, Mplayer crash on X error insufficient resources
Sent the wrong xorg.conf. === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf(5) manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/share/fonts/X11/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 Option Emulate3Buttons true EndSection Section InputDevice Driver wacom Identifier stylus Option Device/dev/input/wacom Option Type stylus Option ForceDevice ISDV4 # Tablet PC ONLY EndSection Section InputDevice Driver wacom Identifier eraser Option Device/dev/input/wacom Option Type eraser Option ForceDevice ISDV4 # Tablet PC ONLY EndSection Section InputDevice Driver wacom Identifier cursor Option Device/dev/input/wacom Option Type cursor Option ForceDevice ISDV4 # Tablet PC ONLY EndSection Section Device Identifier Silicon Integrated Systems [SiS] 630/730 PCI/AGP VGA Display Adapter Driver sis BusID PCI:1:0:0 # Option VideoRam 65536 # Option CacheLines 1980 EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-51 VertRefresh 43-60 EndSection Section Screen Identifier Default Screen Device Silicon Integrated Systems [SiS] 630/730 PCI/AGP VGA Display Adapter Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 EndSubSection SubSection Display Depth 4 Modes 1024x768 EndSubSection SubSection Display Depth 8 Modes 1024x768 EndSubSection SubSection Display Depth 15 Modes 1024x768 EndSubSection SubSection Display Depth 16 Modes 1024x768 EndSubSection SubSection Display Depth 24 Modes 1024x768 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse InputDevice
