January 2010 - Arch-general - lists.archlinux.org

[arch-general] KMS and external monitor resolution
by André Ramaciotti da Silva 13 Jan '10

13 Jan '10

Hi all, I'm sorry if it has already been discussed here, but I couldn't find anything with the keywords I was using. I even had a bad time choosing this message subject. I bought a new, bigger monitor to use with my notebook. I've already configured X, but sometimes I like to write on the tty (there are less distractions there) and I'm having a little problem with it. The native resolution of the notebook screen is 1280x800 and the native resolution of the external monitor is 1920x1080, so when I'm on the tty, the external monitor uses only a box on the top left side with a size of 1280x800. What I would like to do is turn off the notebook monitor and use only the external monitor with its native resolution, without, of course, messing with my X setup, as it's already set. I'm using a Intel GMA965 with KMS. TIA Bye, Andre

2 2

[arch-general] arch-dev-public on dcron 4.3 and logrotate
by Jim Pryor 12 Jan '10

12 Jan '10

On Tue, Jan 12, 2010 at 04:28:40PM -0500, Paul Mattal wrote: > On 01/12/2010 04:16 PM, Eric Bélanger wrote: > >>>As the dcron logging is now managed by syslog-ng, it shouldn't provide > >>>a /etc/logrotate.d/crond. Instead, we should release a new syslog-ng > >>>package with /var/log/crond.log added to the list of logfiles being > >>>taken care of in its /etc/logrotate.d/syslog-ng. We could add, at the > >>>same time, the other logfiles created by syslog-ng but currently > >>>ignored in the log rotation: > >>> > >>>/var/log/lpr.log > >>>/var/log/uucp.log > >>>/var/log/news.log > >>>/var/log/ppp.log > >>>/var/log/debug.log > >>>/var/log/acpid.log > >>> > >>>Am I missing something? Any objections, comments? > >> > >>Actually, that sounds backwards to me. If cron isn't installed, we > >>have no log file. It makes sense to me - if pkgA adds more log files > >>that get big, it should also provide its own logrotate file. > > > >I guess it depends how you see it. The way I see it is that it's > >syslog-ng who creates the file and appends to it so it should be > >responsible for the rotation as well. Plus, we use the missingok > >option so if the file is missing, it just skips it whithout even > >issuing an error message. So no harm is done. > > I can see both sides of this, but in essence, it seems like it's > syslog-ng which ultimately decides the filename-- if syslog-ng.conf > is changed to log cron output to another file, it's syslog-ng that > decides where they go. So I think I agree with Eric that syslog-ng > should be responsible for the rotating the files it determines > should exist in its default configuration. > > I'll wait a while to hear from others before doing anything directly > to address this. Yes, the logrotate script was needed when dcron didn't use syslog. And I'll leave it in the release tarballs "extra" folder as an example for users who continue to use dcron that way. But on my own system I have syslog logging the cron output to "cron.log" not "crond.log": from /etc/syslog-ng.conf: destination d_cron { file("/var/log/cron.log"); }; filter f_cron { facility(cron) or program("rsnapshot"); }; log { source(src); filter(f_cron); destination(d_cron); }; And I have /var/log/cron.log handled by my /etc/logrotate.d/syslog-ng script: /var/log/[..lots of logs, including cron.log..] { missingok sharedscripts postrotate /bin/kill -HUP `cat /var/run/syslog-ng.pid 2>/dev/null` 2> /dev/null || true endscript } I can appreciate arguments both ways myself, but for my own use found it easiest to just ignore the dcron-supplied logrotate script and edit it into my syslog-ng logrotate script. -- profjim(a)jimpryor.net dcron developer

1 0

Re: [arch-general] [arch-dev-public] [signoff] mkinitcpio 0.5.28-1
by Evangelos Foutras 12 Jan '10

12 Jan '10

On 12/01/2010 11:03 πμ, Thomas Bächler wrote: > I think what we have now in the kill-klibc branch might actually boot in > a standard setup (no raid, nfs, lvm, encryption), but I didn't try. I'll > keep you posted. I gave it a try in a VM but it still fails with "Failed to execute /init" like last time (http://i.imgur.com/h6xDu.png). The mkinicpio revision I tried was 54fd032, along with latest mkinitcpio-busybox/trunk. The command used to generate the initramfs image was `./mkinitcpio -g /boot/kernel26.img' from within the cloned Git repository (switched to the kill-klibc branch). Let me know if I can help with further testing.

2 4

Re: [arch-general] [arch-dev-public] [announcement] qemu/qemu-kvm announcement draft
by Simon Boulay 12 Jan '10

12 Jan '10

On 01/09/2010 09:09 PM, Tobias Powalowski wrote: > Am Samstag 09 Januar 2010 schrieb Dan McGee: >> On Sat, Jan 9, 2010 at 11:52 AM, Tobias Powalowski<t.powa(a)gmx.de> wrote: >>> > Yes will change the install message. >>> >>>> Yes there is no mention in the changelogs, really strange. >>>> greetings >>>> tpowa >>> >>> Ok like this? >>> echo ">>> Since kernel 2.6.29:" >>> echo ">>> Qemu package now provides standard qemu with kvm enabled." >>> echo "" >>> echo ">>> PLEASE READ FOR KVM USAGE!" >>> echo ">>> Load the correct KVM module, you will need a KVM capable >>> CPU!" echo ">>> Add yourself to the group 'kvm'." >>> echo ">>> Use 'qemu --enable-kvm' to use KVM." >>> echo "" >>> echo "With the release of qemu and qemu-kvm 0.12.X, the kqemu kernel >>> module" echo "is no longer supported and will be removed from the >>> repositories. You" echo "can safely uninstall it from your system." >> >> Can we put some vercmp checks around messages like this? That way >> people only have to see them once (when they upgrade the first time to >> a 0.12.x version for the second message). The first message should >> really be a post_install message. >> >> And with all that said, why are there two packages in extra if "qemu >> package now provides standard qemu with kvm enabled"? >> >> -Dan >> > Yes sure i can add those vercmp stuff. > qemu and qemu-kvm is different. > qemu-kvm is only for kvm while qemu provides much more machines to emulate. I'm not sure about that. Both seems to share the same code for machine emulation; only the kvm stuff is different. In fedora 12, they build kvm and qemu-system-xxx from qemu-kvm 0.11. But I don't know how this will evolve in the future. If qemu and qemu-kvm are used for different purposes, one may need to install both apps side by side but that's not possible in archlinux. I see two ways to handle that: 1. Permit the installation of both applications at the same time (qemu for system emulation, qemu-kvm for visualization). qemu-kvm executables can be renamed to kvm-xyz. That's what Debian do. 2. Build qemu-kvm with --target="" and all came in the same package. With 0.11, only qemu provided kqemu but as the kqemu support is gone, the second proposition seems to be the way to go. I use this on archlinux for kvm (winXP) and sh or arm emulation without problems since 0.11. Simon. > greetings > tpowa

5 11

[arch-general] Deluge 1.2.0
by Damien Churchill 12 Jan '10

12 Jan '10

I was wondering if it would be possible to add a message, saying the preferred way of running the different user interfaces now is via a deluge-* script, so deluge-gtk, deluge-web and deluge-console, to the post_install() of the package? Damien

2 4

Re: [arch-general] [arch-dev-public] OS News interview
by Xavier 12 Jan '10

12 Jan '10

The common way is to reply on arch-general, so I will include that list in CC now. Thanks for the clarification. So your concern was not about using external binaries, it was about keeping to use outdated Arch programs. That's also a very good point when talking about disadvantages of the rolling release model. It seems most developers answered purely from a developer point of view more than a user one. But I read the answers again and noticed the overlord did mention both sides :) "Aaron Griffin: The biggest problem with the rolling release model is laziness - from upstream developers and Arch users. We try to stay up to date wherever possible, but some upstream developers are slow at adopting new changes. This means we need to do extra work to make their software compatible with new library versions and things of that nature. On the user end, you get people who don't regularly update their system (something we indicate as very important), and you end up with newer software and older libraries on the same system, causing breakages." So I just want to highlight that it's indeed very important to regularly update a Arch system, and it's something that should be made clear when advertising Arch, because it definitely does not fit to everyone. On Tue, Jan 12, 2010 at 5:22 AM, Gregory Eric Sanderson <gzou2000(a)gmail.com> wrote: > Hi Xavier, > > I tried to post an answer to your last message, but since i'm only an > "observer" on the dev list I can't. So I'm transfering directly to you my > answer if ever it might interest you > > ---------- Forwarded message ---------- > From: Gregory Eric Sanderson <gzou2000(a)gmail.com> > Date: Mon, Jan 11, 2010 at 11:20 PM > Subject: Re: [arch-dev-public] OS News interview > To: Public mailing list for Arch Linux development > <arch-dev-public(a)archlinux.org> > > > Actually, that question came from me :-) > > Sorry if the question wasn't clear, I should have phrased it in a different > way. Although my country officiaily has 2 languages, I live in the province > that speaks almost only french, so I don't get much chances practicing my > english. > > The "programs that depend on older libraries who aren't on the system > anymore because of an update" is actually an example that I was trying to > give of a disadvantage that could occur because of the rolling release > model. when I switched full-time to Arch, I din't do system upgrades very > often and It happend regularly that programs would stop to work because they > were linked to libraries who were updated as part of the installation of a > new program. (I hardly get this problem anymore since I upgrade more > regularly now) > > Don't get me wrong, I love the rolling release model. But I was curious to > know what the developers thought of this and if they saw any other > disadvantages or "quirks" that the rolling release model brought > > On Mon, Jan 11, 2010 at 6:59 PM, Xavier <shiningxc(a)gmail.com> wrote: >> >> On Mon, Jan 11, 2010 at 11:22 PM, Allan McRae <allan(a)archlinux.org> wrote: >> > The OS News interview is up: >> > http://www.osnews.com/story/22692/Arch_Linux_Team >> > >> >> Fun interview. Allan's answers are the best, I have to say :) >> >> Some comments : >> - a few formatting issues. like the first reply from Thomas often >> misses a newline. Allan lost his A and became llan and one page. >> >> - whats the difference between these two questions on page 5 : >> What part of the Arch Linux development is the most active? >> Where is development primarily focused for the Arch Linux team (the >> installation, pacman, etc)? >> >> - about this question >> One of the most notable characteristics of Arch is its rolling release >> model, which assures users that they will always have the latest and >> newest version of a program available. Has this model brought any >> noticeable disadvantages (for example: programs that depend on older >> libraries who aren't on the system anymore because of an update)? >> >> I am not sure what the question meant to hint with "programs that >> depend on older libraries who aren't on the system anymore because of >> an update" but that reminded me of several times I tried to run some >> binaries on Arch, and it failed because all libraries were too new. :) > >

1 0

[arch-general] PKGBUILD for extra/cegui
by Rodrigo Amorim Bahiense 11 Jan '10

11 Jan '10

Hi all! I've posted on forum (http://bbs.archlinux.org/viewtopic.php?id=88509) that the package extra/cegui was out of date and then was instructed by Allan to post the modified PKGBUILD on the mailing list. Basically, I just modified the version, the license file location and md5sums. Also, a static reference to old version 0.6.2 to variable $pkgver. ------- pkgname=cegui pkgver=0.7.1 pkgrel=4 pkgdesc="A free library providing windowing and widgets for graphics APIs/engines" arch=(i686 x86_64) url="http://crayzedsgui.sourceforge.net" options=('!libtool') license=("MIT") depends=('pcre' 'expat' 'freetype2' 'libxml2' 'devil' 'freeglut' 'lua' 'silly') [ "$CARCH" = "x86_64" ] && depends=(${depends[@]} 'silly') source=(http://downloads.sourceforge.net/crayzedsgui/CEGUI-$pkgver.tar.gz) build() { cd $startdir/src/CEGUI-$pkgver ./configure --prefix=/usr --sysconfdir=/etc --enable-devil --enable-silly \ --disable-xerces-c --with-default-image-codec=SILLYImageCodec \ --enable-lua make || return 1 make DESTDIR=$startdir/pkg install install -D -m644 doc/COPYING $startdir/pkg/usr/share/licenses/$pkgname/COPYING } md5sums=('0a2815d5204e3c5510884ab62285da97') ------- I didn't check if the old dependencies are still needed, but anyway, that was actually my first pkgbuild. -- Rodrigo

2 3

[arch-general] wchan info in ps
by Dimitrios Apostolou 10 Jan '10

10 Jan '10

Hello list, is anyone actually getting WCHAN information from either ps or top? To try it just use "ps opid,wchan,cmd". I only get dashes, any idea why? Thanks, Dimitris

2 6

[arch-general] Efficiency of devs/TUs
by Ng Oon-Ee 10 Jan '10

10 Jan '10

I just did my -Syu and saw pidgin had been version-bumped to 2.6.5. Since my connection is dog-slow, I browsed to pidgin.im while waiting for the download to finish (I like to check change-logs). Lo and behold, the version advertised on Pidgin's official website was 2.6.4! Of course, the sourceforge was at 2.6.5. Which has just been uploaded today, 10th January. Now THAT'S what I call efficiency. Thanks guys. The PKGBUILD indicates Biru Ionut as the specific maintainer, but thanks to all the rest as well =).

3 2

[arch-general] CUPS
by Weiwei Wang 10 Jan '10

10 Jan '10

Hello, everyone, I'm a freshman in ArchLinux. As my lab owns a printer connected to a windows system, I need to connect it using cups. I read the wiki guide and do as what is told. However, I always receive this messge: Connection failed: NT_STATUS_BAD_NETWORK_NAME My /etc/cups/printers.conf is shown below: # Printer configuration file for CUPS v1.4.2 # Written by cupsd on 2010-01-09 15:32 # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING <Printer HpLaserJ> Info RL Printer Location RL Lab Students Printer MakeModel HP LaserJet 1010, hpcups 3.9.12 DeviceURI smb://elegate:jessica@172.16.65.79/print$/ State Stopped StateMessage Processing page 2... StateTime 1263022347 Reason paused Type 36876 Filter application/vnd.cups-raw 0 - Filter application/vnd.cups-raster 0 hpcups Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer </Printer> <Printer Virtual_PDF_Printer> Info Virtual PDF Printer Location Weiwei's Laptop MakeModel Apple 12/640ps Foomatic/Postscript (recommended) DeviceURI cups-pdf:/ State Idle StateTime 1263021073 Type 8400916 Filter application/vnd.cups-raw 0 - Filter application/vnd.cups-postscript 100 foomatic-rip Filter application/vnd.cups-pdf 0 foomatic-rip Filter application/vnd.apple-pdf 25 foomatic-rip Filter application/vnd.cups-command 0 commandtops Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer </Printer> And I checked that the printer in the windows system is share with the name hpLaserJ, however when I connect it with smbclient //172.16.65.79/hpLaserJ, i receive NT_STATUS_ACCESS_DENIED so i tried with smbclient //172.16.65.79/print$ and it works fine when i try to list the contents using ls command. That's why I use the name print$ in the printers.conf cups and samba are both definitely running. Samba configuration is shown below: # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # For a step to step guide on installing, configuring and using samba, # read the Samba-HOWTO-Collection. This may be obtained from: # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf # # Many working examples of smb.conf files can be found in the # Samba-Guide which is generated daily and can be downloaded from: # http://www.samba.org/samba/docs/Samba-Guide.pdf # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command "testparm" # to check that you have not made any basic syntactic errors. # #======================= Global Settings ===================================== [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = Samba Server # Security mode. Defines in which mode Samba will operate. Possible # values are share, user, server, domain and ads. Most people will want # user level security. See the Samba-HOWTO-Collection for details. security = user # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks and # the "loopback" interface. For more examples of the syntax see # the smb.conf man page ; hosts allow = 192.168.1. 192.168.2. 127. # If you want to automatically load your printer list rather # than setting them up individually then you'll need this load printers = yes # you may wish to override the location of the printcap file ; printcap name = /etc/printcap # on SystemV system setting printcap name to lpstat should allow # you to automatically obtain a printer list from the SystemV spool # system ; printcap name = lpstat # It should not be necessary to specify the print system type unless # it is non-standard. Currently supported print systems include: # bsd, cups, sysv, plp, lprng, aix, hpux, qnx ; printing = cups # Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user "nobody" is used ; guest account = pcguest # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/%m.log # Put a capping on the size of the log files (in Kb). max log size = 50 # Use password server option only with security = server # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ; password server = <NT-Server-Name> # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of ; realm = MY_REALM # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. ; passdb backend = tdbsam # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting. # Note: Consider carefully the location in the configuration file of # this line. The included file is read at that point. ; include = /usr/local/samba/lib/smb.conf.%m # Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. ; interfaces = 192.168.12.2/24 192.168.13.2/24 # Browser Control Options: # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply ; local master = no # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable ; os level = 33 # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job ; domain master = yes # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; preferred master = yes # Enable this if you want Samba to be a domain logon server for # Windows95 workstations. ; domain logons = yes # if you enable domain logons then you may want a per-machine or # per user logon script # run a specific logon batch file per workstation (machine) ; logon script = %m.bat # run a specific logon batch file per username ; logon script = %U.bat # Where to store roving profiles (only for Win95 and WinNT) # %L substitutes for this servers netbios name, %U is username # You must uncomment the [Profiles] share below ; logon path = \\%L\Profiles\%U # Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server ; wins support = yes # WINS Server - Tells the NMBD components of Samba to be a WINS Client # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both ; wins server = w.x.y.z # WINS Proxy - Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be # at least one WINS Server on the network. The default is NO. ; wins proxy = yes # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. The default is NO. dns proxy = no # These scripts are used on a domain controller or stand-alone # machine to add or delete corresponding unix accounts ; add user script = /usr/sbin/useradd %u ; add group script = /usr/sbin/groupadd %g ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u ; delete user script = /usr/sbin/userdel %u ; delete user from group script = /usr/sbin/deluser %u %g ; delete group script = /usr/sbin/groupdel %g #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writable = yes # Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /usr/local/samba/lib/netlogon ; guest ok = yes ; writable = no ; share modes = no # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ;[Profiles] ; path = /usr/local/samba/profiles ; browseable = no ; guest ok = yes # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print guest ok = no writable = no printable = yes # This one is useful for people to share files ;[tmp] ; comment = Temporary file space ; path = /tmp ; read only = no ; public = yes # A publicly accessible directory, but read only, except for people in # the "staff" group ;[public] ; comment = Public Stuff ; path = /home/samba ; public = yes ; writable = no ; printable = no ; write list = @staff # Other examples. # # A private printer, usable only by fred. Spool data will be placed in fred's # home directory. Note that fred must have write access to the spool directory, # wherever it is. ;[fredsprn] ; comment = Fred's Printer ; valid users = fred ; path = /homes/fred ; printer = freds_printer ; public = no ; writable = no ; printable = yes # A private directory, usable only by fred. Note that fred requires write # access to the directory. ;[fredsdir] ; comment = Fred's Service ; path = /usr/somewhere/private ; valid users = fred ; public = no ; writable = yes ; printable = no # a service which has a different directory for each machine that connects # this allows you to tailor configurations to incoming machines. You could # also use the %U option to tailor it by user name. # The %m gets replaced with the machine name that is connecting. ;[pchome] ; comment = PC Directories ; path = /usr/pc/%m ; public = no ; writable = yes # A publicly accessible directory, read/write to all users. Note that all files # created in the directory by users will be owned by the default user, so # any user with access can delete any other user's files. Obviously this # directory must be writable by the default user. Another user could of course # be specified, in which case all files would be owned by that user instead. ;[public] ; path = /usr/somewhere/else/public ; public = yes ; only guest = yes ; writable = yes ; printable = no # The following two entries demonstrate how to share a directory so that two # users can place files there that will be owned by the specific users. In this # setup, the directory should be writable by both users and should have the # sticky bit set on it to prevent abuse. Obviously this could be extended to # as many users as required. ;[myshare] ; comment = Mary's and Fred's stuff ; path = /usr/somewhere/shared ; valid users = mary fred ; public = no ; writable = yes ; printable = no ; create mask = 0765 I feel really frustrated by this job. Help me~~~~~~~~~~~~~~ -- Weiwei Wang Alex Wang 王巍巍 Room 403, Mengmin Wei Building Computer Science Department Gulou Campus of Nanjing University Nanjing, P.R.China, 210093 Homepage: http://cs.nju.edu.cn/rl/weiweiwang

3 8