Re: [arch-general] how to add autowifi to rc.conf
At the end of your rc.conf, juste like that: DAEMONS=(daemon autowifi daemon) archlinux know where are initscript, and that she have to just start them. She just need to know which you want to start.
Re: [arch-general] When will Arch switch to Systemd
"When will Arch switch to s_d"... yes? ALSA != alsa-lib... yes? terminology is important. PA was created to provide business solutions. it does this; refer to widespread acceptance as a good approach. automation and intelligent decisions by computers are a Good Thing when coupled with transparency; refer to the history of computation and technology at large. as a new contact wisely quoted me recently: "I despise the idea of a human doing a computer's job" break away from this thread if you guys want to discuss sound politics :-) C Anthony btw, since i'm technically the "OP"... systemd w3rks. awesome. looking forward to doing what i can to make it a great solution for Arch.
Re: [arch-general] how to add autowifi to rc.conf
i means write what in rc.conf i think it write like wlan0="dhcp" or other things but not the “/etc/rc.d/autowifi start" 2011/1/27 Ben Tartsa > Perhaps I'm off misunderstanding this but are you asking how to actually > edit the file? If so you will need a text editor and root privileges...and > get friendly with google . > > On Wed, Jan 26, 2011 at 10:27 AM, doherty pete >wrote: > > > To start *autowifi*, run > > > > /etc/rc.d/autowifi start > > > > If you want to start it at boot, add it to rc.conf. > > > > > > but how to write in rc.conf > > > > and any other to write > > > > my wpa_supplicant works well > > > > -- > > pete_doherty > > > -- pete_doherty
Re: [arch-general] Anyone getting 'Forbidden' on oxygen-icons-4.6.0-1-any from mirros.kernel.org?
On 01/27/2011 02:46 AM, Ng Oon-Ee wrote: I can't download it from the website either. Probably the mirror didn't completely sync? indeed. wait a bit more to sync -- Ionuț
[arch-general] Anyone getting 'Forbidden' on oxygen-icons-4.6.0-1-any from mirros.kernel.org?
I can't download it from the website either. Probably the mirror didn't completely sync?
Re: [arch-general] When will Arch switch to Systemd
Am Thu, 27 Jan 2011 00:40:05 +0100 schrieb f...@kokkinizita.net: > So this could probably be solved if PA would accept some manual > configuration in such cases. Maybe it does, but so far apparently > no-one knows how to do it. I guess it's just not possible as manual > configuration sort of goes against the grain of Lennart's work. There shouldn't be some manual configuration at least not for the user or the admin. There needs to be such a PA mixer like envy24control. > One practical solution could be to run PA as a Jack client. Most > people using this type of card would be running Jack anyway. A lot better: Not using PA at all, because ALSA can manage this perfectly. And I guess Jack can do it with ALSA, too, without PA. Heiko
Re: [arch-general] When will Arch switch to Systemd
On Wed, Jan 26, 2011 at 07:31:37PM +0100, Heiko Baums wrote: > They are not comparable to usual sound cards like SoundBlaster, because > they don't have Stereo or Surround sound. They just have several single > input and output channels which can be mixed however you want. And this > is just not supported by PA. But it is fully supported by ALSA and > envy24control. Yes. PA doesn't know what to do with the 8 or more identical channels because ALSA doesn't provide any info on how they are supposed to be used, and ALSA is right in doing this as there simply is no such information. The user decides how to wire up the channels. If he wants to use channels 7 and 3 for stereo, and 8,1,6,2,4,5 for 5.1 surround that's entirely possible, as it should be for any pro or semi-pro card. So this could probably be solved if PA would accept some manual configuration in such cases. Maybe it does, but so far apparently no-one knows how to do it. I guess it's just not possible as manual configuration sort of goes against the grain of Lennart's work. One practical solution could be to run PA as a Jack client. Most people using this type of card would be running Jack anyway. Ciao, -- FA There are three of them, and Alleline.
Re: [arch-general] [AUR] Please, orphan the xdg-user-dirs-gtk
On Wed, Jan 26, 2011 at 6:16 PM, Thomas Dziedzic wrote: > On Wed, Jan 26, 2011 at 2:28 PM, Robson Roberto Souza Peixoto > wrote: >> Please, orphan the package - xdg-user-dirs-gtk >> >> http://aur.archlinux.org/packages.php?ID=14273 >> > > done & thanks > > fyi, next time post a reason. Just say the guy is inactive, as I have > seen by your comments on that package. > OK :D Thanks -- Robson Roberto Souza Peixoto Robinho Computer Science Master's degree student, University of Campinas Linux Counter #395633 IRC: robsonpeixoto Twitter: http://twitter.com/rrspba github: https://github.com/robsonpeixoto Dropbox: http://db.tt/5wEY1DZ
Re: [arch-general] [AUR] Please, orphan the xdg-user-dirs-gtk
On Wed, Jan 26, 2011 at 2:28 PM, Robson Roberto Souza Peixoto wrote: > Please, orphan the package - xdg-user-dirs-gtk > > http://aur.archlinux.org/packages.php?ID=14273 > done & thanks fyi, next time post a reason. Just say the guy is inactive, as I have seen by your comments on that package.
[arch-general] [AUR] Please, orphan the xdg-user-dirs-gtk
Please, orphan the package - xdg-user-dirs-gtk http://aur.archlinux.org/packages.php?ID=14273
Re: [arch-general] xarchiver patch
2011/1/26 Ivan Puntiy > Hello, > > I have patched extra/xarchiver to support xz compression using Slackware's > patch. > It is working on my system, and I uploaded it to AUR: > http://aur.archlinux.org/packages.php?ID=45726 > > What is the procedure of requesting it to be applied to original package? > > Ivan > > I take my words back, just found a bug with the patch: looks like it only allows to see the contents of xz archive.
Re: [arch-general] [signoff] lvm2/device-mapper 2.02.82-1
On 01/26/2011 04:29 PM, Thomas Bächler wrote: Am 26.01.2011 11:38, schrieb Eric Bélanger: On Wed, Jan 26, 2011 at 3:33 AM, Jan Spakula wrote: Excerpts from Eric Bélanger's message of Mi Jan 26 05:16:44 +0100 2011: lvm2/device-mapper 2.02.82-1 are in testing for minor upstream update. Please test and signoff. Users signoffs are welcome. Hi, I have problems with both 2.02.81 and 2.02.82: I have encrypted root (normal partition) + some extra encrypted partitions on lvm via crypttab. The ones in crypttab don't unlock, the error message is something along the lines of "... /dev/vg/swap doesn't exist or access denied" (it gets overwritten immediately, so I don't see the beginning of the message). This is right after lvm2 hook is run. Then a bit later in the emergency shell, the /dev/vg/* links are already there; so perhaps there's some extra delay until the symlinks are created in /dev/ with the newer lvm2? This is weird. I think lvm2 is supposed to wait for udev to finish creating all links before returning. Inserting a 'sleep 1' or '/sbin/udevadm settle' in rc.sysinit after the vgchange call should fix this, but it shouldn't be necessary. I'm getting exactly the same behavior, it started ~ a week ago. Sorry I haven't followed up, been busy with university.
Re: [arch-general] xarchiver patch
On Wed, 2011-01-26 at 21:04 +0100, Andreas Radke wrote: > Am Wed, 26 Jan 2011 20:35:51 +0100 > schrieb Sven-Hendrik Haase : > > > You should bug upstream against, perhaps using direct mail to > > maintainer. > > > > In general, you can post up feature requests but they might be closed > > with "upstream" as a reason as we can't do much about it. We will not > > have feature patches in 99% of the cases if it can be helped. > > > > You seem to be able to read my mind? Yes, I'd close it as won't > implement. Though it would be really useful it's simply against Arch > philosophy as it would add unneeded code to the upstream release. Depends on what you call unneeded. If I would add support for additional compression formats, I would just rewrite a big piece of the code to use either bsdtar instead of parsing output from tar and unzip. File-roller is very famous for its error messages about .tar.gz files that have been un-gzipped by your browser, but which are stored with the same extension. As tar will complain that it's not a gzip archive, file-roller can't open it... The same will be true for xarchiver.
Re: [arch-general] xarchiver patch
Am Wed, 26 Jan 2011 20:35:51 +0100 schrieb Sven-Hendrik Haase : > You should bug upstream against, perhaps using direct mail to > maintainer. > > In general, you can post up feature requests but they might be closed > with "upstream" as a reason as we can't do much about it. We will not > have feature patches in 99% of the cases if it can be helped. > You seem to be able to read my mind? Yes, I'd close it as won't implement. Though it would be really useful it's simply against Arch philosophy as it would add unneeded code to the upstream release. -Andy
Re: [arch-general] xarchiver patch
2011/1/26 Sven-Hendrik Haase > On 26.01.2011 20:29, Ivan Puntiy wrote: > > 2011/1/26 Jelle van der Waa > > > >> On Wed, 2011-01-26 at 21:11 +0200, Ivan Puntiy wrote: > >>> Hello, > >>> > >>> I have patched extra/xarchiver to support xz compression using > >> Slackware's > >>> patch. > >>> It is working on my system, and I uploaded it to AUR: > >>> http://aur.archlinux.org/packages.php?ID=45726 > >>> > >>> What is the procedure of requesting it to be applied to original > package? > >>> > >>> Ivan > >> Feature request, but first bug upstream > >> -- > >> Jelle van der Waa > >> > > Ok, I actually found the patch at upstream's bug about the issue (opened > > since 2009). > > But rechecked now: the patch was added 2 months ago in a comment, I guess > I > > can wait. > > > > And for the future: > > Are feature request are submitted at the bug tracker? > You should bug upstream against, perhaps using direct mail to maintainer. > > In general, you can post up feature requests but they might be closed > with "upstream" as a reason as we can't do much about it. We will not > have feature patches in 99% of the cases if it can be helped. > Ok, thanks.
Re: [arch-general] xarchiver patch
On 26.01.2011 20:29, Ivan Puntiy wrote: > 2011/1/26 Jelle van der Waa > >> On Wed, 2011-01-26 at 21:11 +0200, Ivan Puntiy wrote: >>> Hello, >>> >>> I have patched extra/xarchiver to support xz compression using >> Slackware's >>> patch. >>> It is working on my system, and I uploaded it to AUR: >>> http://aur.archlinux.org/packages.php?ID=45726 >>> >>> What is the procedure of requesting it to be applied to original package? >>> >>> Ivan >> Feature request, but first bug upstream >> -- >> Jelle van der Waa >> > Ok, I actually found the patch at upstream's bug about the issue (opened > since 2009). > But rechecked now: the patch was added 2 months ago in a comment, I guess I > can wait. > > And for the future: > Are feature request are submitted at the bug tracker? You should bug upstream against, perhaps using direct mail to maintainer. In general, you can post up feature requests but they might be closed with "upstream" as a reason as we can't do much about it. We will not have feature patches in 99% of the cases if it can be helped.
Re: [arch-general] xarchiver patch
2011/1/26 Jelle van der Waa > On Wed, 2011-01-26 at 21:11 +0200, Ivan Puntiy wrote: > > Hello, > > > > I have patched extra/xarchiver to support xz compression using > Slackware's > > patch. > > It is working on my system, and I uploaded it to AUR: > > http://aur.archlinux.org/packages.php?ID=45726 > > > > What is the procedure of requesting it to be applied to original package? > > > > Ivan > > Feature request, but first bug upstream > -- > Jelle van der Waa > Ok, I actually found the patch at upstream's bug about the issue (opened since 2009). But rechecked now: the patch was added 2 months ago in a comment, I guess I can wait. And for the future: Are feature request are submitted at the bug tracker?
Re: [arch-general] xarchiver patch
On Wed, 2011-01-26 at 21:11 +0200, Ivan Puntiy wrote: > Hello, > > I have patched extra/xarchiver to support xz compression using Slackware's > patch. > It is working on my system, and I uploaded it to AUR: > http://aur.archlinux.org/packages.php?ID=45726 > > What is the procedure of requesting it to be applied to original package? > > Ivan Feature request, but first bug upstream -- Jelle van der Waa signature.asc Description: This is a digitally signed message part
Re: [arch-general] xarchiver patch
On 26.01.2011 20:11, Ivan Puntiy wrote: > Hello, > > I have patched extra/xarchiver to support xz compression using Slackware's > patch. > It is working on my system, and I uploaded it to AUR: > http://aur.archlinux.org/packages.php?ID=45726 > > What is the procedure of requesting it to be applied to original package? > > Ivan You should always try to get patches upstream.
[arch-general] xarchiver patch
Hello, I have patched extra/xarchiver to support xz compression using Slackware's patch. It is working on my system, and I uploaded it to AUR: http://aur.archlinux.org/packages.php?ID=45726 What is the procedure of requesting it to be applied to original package? Ivan
Re: [arch-general] how to add autowifi to rc.conf
Perhaps I'm off misunderstanding this but are you asking how to actually edit the file? If so you will need a text editor and root privileges...and get friendly with google . On Wed, Jan 26, 2011 at 10:27 AM, doherty pete wrote: > To start *autowifi*, run > > /etc/rc.d/autowifi start > > If you want to start it at boot, add it to rc.conf. > > > but how to write in rc.conf > > and any other to write > > my wpa_supplicant works well > > -- > pete_doherty >
Re: [arch-general] how to add autowifi to rc.conf
On Jan 26, 2011 6:48 PM, "Neil Perry" wrote: > Add it to the daemon array at the bottom. > > Thanks > Neil > On Jan 26, 2011 6:27 PM, "doherty pete" wrote: >> To start *autowifi*, run >> >> /etc/rc.d/autowifi start >> >> If you want to start it at boot, add it to rc.conf. >> >> >> but how to write in rc.conf >> >> and any other to write >> >> my wpa_supplicant works well >> >> -- >> pete_doherty
Re: [arch-general] how to add autowifi to rc.conf
Add it to the daemon array at the bottom. Thanks Neil On Jan 26, 2011 6:27 PM, "doherty pete" wrote: > To start *autowifi*, run > > /etc/rc.d/autowifi start > > If you want to start it at boot, add it to rc.conf. > > > but how to write in rc.conf > > and any other to write > > my wpa_supplicant works well > > -- > pete_doherty
Re: [arch-general] When will Arch switch to Systemd
Am Wed, 26 Jan 2011 00:13:56 -0700 schrieb Brendan Long : > So the ALSA drivers don't do what they're supposed to and that PA's > problem? If it doesn't work on your card, don't use it. It's why I > don't use OSS on my laptop. And remember, what I was replying to was: This is not ALSA's problem. This is a known PA issue. See the PA bugtracker. And I'd suggest informing yourself about those ice1712 based audio cards, how they are designed, how they work and how PA works. And install envy24control and PA's mixer and see the differences and see why PA can't be used for ice1712 cards. They are not comparable to usual sound cards like SoundBlaster, because they don't have Stereo or Surround sound. They just have several single input and output channels which can be mixed however you want. And this is just not supported by PA. But it is fully supported by ALSA and envy24control. > If your ALSA drivers are broken and don't support the feature PA uses, > then don't use it. It doesn't make it bad software. Don't put the blame on other people. PA may work with usual sound cards. It does not work with professional and semi-professional sound cards. And if ALSA would be indeed the reason why some PA functions are not working, why doesn't PA's upstream file appropriate bug reports to ALSA's upstream or why doesn't PA's upstream doesn't implement those features in a way that they work with ALSA as it is? And ALSA is the much older package. PA the newer which sets itself on top of ALSA. So why do PA's upstream or PA enthusiasts blame the older software? Some question too much. Btw., I, of course, don't use PA, because it doesn't work while ALSA is working. Heiko
[arch-general] how to add autowifi to rc.conf
To start *autowifi*, run /etc/rc.d/autowifi start If you want to start it at boot, add it to rc.conf. but how to write in rc.conf and any other to write my wpa_supplicant works well -- pete_doherty
Re: [arch-general] [signoff] kernel-2.6.36.3-2
On 01/24/2011 12:38 PM, Tobias Powalowski wrote: > Upstream update. This package is NOT in testing (2.6.37 currently > resides there), but at: > http://dev.archlinux.org/~tpowa/kernel26/ > > fixed udev crash #22343 > fixed ext3 default mount option #22544 > > please signoff for both arches. > > greetings > tpowa tpowa, 5 out of 6 (4 i686 + 1 x86_64) OK. The whacky MSI box failed to boot "Corrupt partitions table" grub error. This time it took out both 2.6.36.3-2 and LTS. Booting from the net install, assembling the arrays, chrooting and downgrading to 2.6.36.3-1 and the last LTS fixed it. I think we'll just shoot this mobo/chipset in the head. Let me know if you want any logs to look at. Otherwise, same old problem with the one MSI box, all others are perfect :) Great job! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
[arch-general] [RFT] initscripts 2011.01-1
Okay, this has been sitting in git for a lng time, and I am throwing it out there. This should receive lots of testing, as there has been major rewriting done. We need to make sure there are no regressions. It should also fix a small number of bugs. New known bugs: When netcfg's init scripts are called, these lines are printed: /etc/rc.d/functions: line 320: declare: add_hook: readonly variable /etc/rc.d/functions: line 320: declare: run_hook: readonly variable This happens when rc.functions is loaded twice, I'll look into fixing that. This is the shortlog: Dan McGee (1): Unify capitalization of 'Udev' Dave Reisner (2): rc.sysinit: condense calls to mkdir and chmod Use modprobe's --all flag instead of looping. Florian Pritz (1): restrict NETWORK_PERSIST to runlevel 0 and 6 Gerardo Exequiel Pozzi (1): Add support for serial console Heiko Baums (3): cryptsetup: read keys for non-root LUKS partitions as raw data from block device cryptsetup: abort if LUKS is found on swap partition cryptsetup: print name of device being opened Thomas Bächler (5): Remove a redundant subshell, see FS#20016 Fix two typos introduced by the latest patch series Change SWAP sanity check to use blkid in favor of cryptsetup Fix isLuks check Change copyright and license information Tom Gundersen (9): udevadm: trigger events of type subsystems as well as devices udevadm: retry failed udev events after filesystems have been mounted udev: do not copy /lib/udev/devices/* to /dev locale: set the sysfs value default_utf8 rather than enabling/disabling utf8 in locale.sh mount: forbid suid,exec,dev from /proc and /sys lvm: run vgchange in sysinit mode lvm: enable/disable monitoring of lvm2 groups cryptsetup: fix indentation PATH: export a standard path in rc.sysinit Victor Lowther (15): Bashify initscripts. A little creative parameter expansion simplifies stat_die(). Clean up status() function. Simplify in_array. Finish bashifying functions. Bashify rc.multi Bashify rc.single. Both rc.single and rc.shutdown use the same code to kill everything. Bashify rc.shutdown Bashify rc.sysinit, part 1 Rewrite /etc/crypttab processing. Bashify netfs Bashify adjtime.cron Trivial bashification of network script. Add a PKGBUILD for building initscripts-git for testing. signature.asc Description: OpenPGP digital signature
Re: [arch-general] [signoff] kernel-2.6.36.3-2
El 24/01/11 07:38, Tobias Powalowski dijo: > Upstream update. This package is NOT in testing (2.6.37 currently > resides there), but at: > http://dev.archlinux.org/~tpowa/kernel26/ > > fixed udev crash #22343 > fixed ext3 default mount option #22544 > > please signoff for both arches. > > greetings > tpowa hi, where i can find the original patches for this release? they aren't here: http://projects.archlinux.org/linux-2.6-ARCH.git -- Salud! Nicolás Reynolds, xmpp:fa...@kiwwwi.com.ar omb:http://identi.ca/fauno blog:http://selfdandi.com.ar/ gnu/linux user #455044 http://parabolagnulinux.org http://endefensadelsl.org pgpo0nryIDGbf.pgp Description: PGP signature
Re: [arch-general] [signoff] lvm2/device-mapper 2.02.82-1
Am 26.01.2011 11:38, schrieb Eric Bélanger: > On Wed, Jan 26, 2011 at 3:33 AM, Jan Spakula wrote: >> Excerpts from Eric Bélanger's message of Mi Jan 26 05:16:44 +0100 2011: >>> lvm2/device-mapper 2.02.82-1 are in testing for minor upstream update. >>> Please test and signoff. Users signoffs are welcome. >> >> Hi, I have problems with both 2.02.81 and 2.02.82: >> I have encrypted root (normal partition) + some extra encrypted partitions on >> lvm via crypttab. The ones in crypttab don't unlock, the error message is >> something along the lines of "... /dev/vg/swap doesn't exist or access >> denied" (it gets overwritten immediately, so I don't see the beginning of the >> message). This is right after lvm2 hook is run. >> Then a bit later in the emergency shell, the /dev/vg/* links are already >> there; so perhaps there's some extra delay until the symlinks are created in >> /dev/ with the newer lvm2? This is weird. I think lvm2 is supposed to wait for udev to finish creating all links before returning. Inserting a 'sleep 1' or '/sbin/udevadm settle' in rc.sysinit after the vgchange call should fix this, but it shouldn't be necessary. >> Downgrading to lvm2-2.02.79-1 "fixes" the problem. I took a quick look at >> the lvm2 changelog, but I didn't notice anything unusual... but admittedly I >> don't understand things too well. >> > > Is it related to https://bugs.archlinux.org/task/22351 ? > I don't know much about encryption. Better add your experience in the > links above if related or open a new bug report. I don't think there is a relation. signature.asc Description: OpenPGP digital signature
Re: [arch-general] [signoff] kernel-2.6.36.3-2
On 25/01/2011 5:38 AM, Tobias Powalowski wrote: Upstream update. This package is NOT in testing (2.6.37 currently resides there), but at: http://dev.archlinux.org/~tpowa/kernel26/ fixed udev crash #22343 fixed ext3 default mount option #22544 please signoff for both arches. greetings tpowa Works fine for me. Fixes kernel panic I was having on boot that was triggered by udev 165. Signoff i686
