Which group to use for system users (adduser bug #290623)
Hi, I am asking for discussion about bug #290623. The bug basically says that it is a bad idea to generate system accounts with primary group "nogroup", which I feel is a valid report. The bug report continues to suggest generating a dedicated group for each system account that has been generated under USERGROUPS set, which I find a good idea. This leaves to be discussed how adduser should behave with USERGROUPS unset. Which group to choose? The bug report suggests using a dedicated group like "sysusers", which I do not quite like with regard to the pre-defined group "sys" which will be confusing if paired with sysusers. May I ask for comments? Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: Bug#292831: udev: udev prevents X from beeing started
On Sat, Feb 05, 2005 at 04:43:41AM +0100, Jérôme Warnier wrote: > Le lundi 31 janvier 2005 à 08:58 +, David Pashley a écrit : > > On Jan 31, 2005 at 04:46, Hamish Moffatt praised the llamas by saying: > > Surely the solution is for hotplug/discover to load it during bootup. > > Could hotplug use mdetect? > IIRC, mdetect does not support devfs, and devfs is still in use in the > installer, right? This is irrelevant here. Devfs is not in the use after an install (not even in the first bootup into base-config). Mdetect would have to run on every bootup to avoid putting the modules in /etc/modules. Gaudenz signature.asc Description: Digital signature
Re: Bug#292831: udev: udev prevents X from beeing started
* Jérôme Warnier | > Surely the solution is for hotplug/discover to load it during bootup. | > Could hotplug use mdetect? | | IIRC, mdetect does not support devfs, and devfs is still in use in the | installer, right? mdetect won't run during the first phase of the installation, so that's not a problem. The installed system does not use devfs. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
About valid and invalid user names
Hi, adduser has two bug reports open where people are asking for user name rules to be relaxed. One report wants "." to be allowed in user names, another wants usernames to start with numbers. May I ask for your opinion before denying or following the requests? Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: About valid and invalid user names
On Sat, Feb 05, 2005 at 01:38:36PM +0100, Marc Haber wrote: > Hi, > > adduser has two bug reports open where people are asking for user name > rules to be relaxed. One report wants "." to be allowed in user names, > another wants usernames to start with numbers. > > May I ask for your opinion before denying or following the requests? Let's quote SUS a little. Base def (Definitions) Login Name A user name that is associated with a login. User ID A non-negative integer that is used to identify a system user. When the identity of a user is associated with a process, a user ID value is referred to as a real user ID, an effective user ID, or a saved set-user-ID. User Name A string that is used to identify a user; see also User Database . To be portable across systems conforming to IEEE Std 1003.1-2001, the value is composed of characters from the portable filename character set. The hyphen should not be used as the first character of a portable user name. Portable Filename Character Set The set of characters from which portable filenames are constructed. A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 . _ - The last three characters are the period, underscore, and hyphen characters, respectively. >From the chown utility: The following operands shall be supported: owner[:group] A user ID and optional group ID to be assigned to file. The owner portion of this operand shall be a user name from the user database or a numeric user ID. Either specifies a user ID which shall be given to each file named by one of the file operands. If a numeric owner operand exists in the user database as a user name, the user ID number associated with that user name shall be used as the user ID. Similarly, if the group portion of this operand is present, it shall be a group name from the group database or a numeric group ID. Either specifies a group ID which shall be given to each file. If a numeric group operand exists in the group database as a group name, the group ID number associated with that group name shall be used as the group ID. [...] The BSD syntax user[. group] was changed to user[: group] in this volume of IEEE Std 1003.1-2001 because the period is a valid character in login names (as specified by the Base Definitions volume of IEEE Std 1003.1-2001, login names consist of characters in the portable filename character set). The colon character was chosen as the replacement for the period character because it would never be allowed as a character in a user name or group name on historical implementations. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sat, Feb 05, 2005 at 01:38:36PM +0100, Marc Haber wrote: > Hi, > > adduser has two bug reports open where people are asking for user name > rules to be relaxed. One report wants "." to be allowed in user names, > another wants usernames to start with numbers. > > May I ask for your opinion before denying or following the requests? > > Greetings > Marc > I think the discussion came up earlier here. IIRC the conclusion was that it could be relaxed for .'s (don't know about numbers). Although it can cause confusion with chown a.b format. But chown should now be patched to behave correctly on chown a.a:b.b (eg username and group name separated by ':'). At least that's how I remember it. Can somebody verify this? greets, Wim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sath, 2005-02-05 at 13:38 +0100, Marc Haber wrote: > Hi, > > adduser has two bug reports open where people are asking for user name > rules to be relaxed. One report wants "." to be allowed in user names, > another wants usernames to start with numbers. > > May I ask for your opinion before denying or following the requests? > > Greetings > Marc The last time I looked, POSIX allowed '.' in usernames; it certainly works for me where I use it, and allows sensible names that scale. (fitting names like 'alastair.mckinstry' in ls -l is a different matter, but it makes for usable login names; I work for an ISP and our usernames and email names are 'firstname.lastname'; we don't give shell accounts, though. GNU chown has an extension of interpreting 'foo.bar' as username foo, group bar. This is problematic. Fortunately it also supports the Correct (TM) way of doing it, foo:bar . ':' is definitely not allowed in usernames in POSIX. I can dig out the actual spec, if necessary. Regards Alastair McKinstry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: library packaging doc...
Hi Joey > > > > Just request to [EMAIL PROTECTED] while pointing them our message on > > this list. > > Or see and follow the instructions summarised on > http://master.debian.org/~joey/misc/webwml.html#ddp According to the page you pointed to, it seems to tell me that I should send request to you, after approval of debian doc people. Hereby I am sending a request. Is this okay? I consider that with this thread debian-doc people have given approval. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
Am 2005-02-05 14:18:32, schrieb Wim De Smet: > I think the discussion came up earlier here. IIRC the conclusion was > that it could be relaxed for .'s (don't know about numbers). Although > it can cause confusion with chown a.b format. But chown should now be > patched to behave correctly on chown a.a:b.b (eg username and group name > separated by ':'). At least that's how I remember it. Can somebody > verify this? Hello Wim, I am using WOODY and 'chown' already support 'chown a.a:b.b' So I think, it works under SARGE and SID too. __( command 'ls -Al /home' )__ / | drwxr-xr-x 30 athina.r athina.r 1024 1. Jan 21:40 athina.russel | drwxr-xr-x 24 root root 1024 3. Dez 20:46 BAK_debian | drwxr-xr-x 10 root root 1024 16. Jan 20:11 BAK_michelle1 | drwxr-xr-x 28 diana.se diana.se 1024 1. Jan 22:36 diana.seitz | drwxr-xr-x 29 eyup.dog eyup.dog 1024 13. Nov 00:58 eyup.dogu | drwxr-xr-x 25 fathia.r fathia.r 1024 13. Nov 00:58 fathia.rachek | drwxr-xr-x 29 fayah.do fayah.do 1024 13. Nov 00:58 fayah.dogan | drwxr-xr-x 24 root root 1024 13. Nov 00:58 home | drwxr-xr-x 27 karima.k karima.k 1024 19. Jan 18:40 karima.kalaaji | drwxr-xr-x 22 leila.pa leila.pa 1024 28. Dez 18:32 leila.pahlavi | drwxr-xr-x2 root root12288 20. Nov 19:23 lost+found | drwxr-xr-x 28 lydia.ac lydia.ac 1024 13. Nov 00:58 lydia.ackermann | drwxr-xr-x 34 marian.d marian.d 1024 13. Nov 00:58 marian.domeracki | drwxr-xr-x 27 mehdi.se mehdi.se 1024 13. Nov 00:58 mehdi.serhane | drwxr-xr-x 139 michelle privat 4096 5. Feb 12:10 michelle.konzack | drwxr-xr-x 28 michiar developm 1024 9. Jan 13:42 michiar | drwxr-xr-x 22 michitr developm 1024 13. Nov 00:58 michitr | drwxr-xr-x 24 nancynancy1024 13. Nov 00:58 nancy | drwxr-xr-x 30 noor.nur noor.nur 1024 13. Nov 00:58 noor.nurani | drwxr-xr-x 24 onlinest business 1024 12. Nov 21:31 onlinestore | drwxr-xr-x 24 pascale. pascale. 1024 13. Nov 00:58 pascale.domeracki | drwxr-xr-x 24 peer.jan peer.jan 1024 29. Jan 20:02 peer.janssen | drwxr-xr-x 26 sandrine sandrine 1024 19. Jan 18:37 sandrine.dario | drwxr-xr-x 37 tamay.do privat 1024 13. Nov 00:58 tamay.dogan | drwxr-xr-x 28 zelie.do zelie.do 1024 13. Nov 00:58 zelie.domeracki \__ I have already patched "adduser" to allow the "." in Names. So the "." should be allowed. > greets, > Wim Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Plese test new adduser in experimental
Hi, please test the new adduser package in experimental which was uploaded today. It fixes a number of minor functionality bugs and also three issues where deluser --remove-home wasn't foolproof enough. It will now by default refuse to delete /, /bin, /usr, /var and other important directories, and it will stop deleting at a mountpoint. I would appreciate your comments and bug reports before I upload to unstable and start pestering the release team to push adduser to sarge. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: About valid and invalid user names
[Marc Haber] > adduser has two bug reports open where people are asking for user name > rules to be relaxed. One report wants "." to be allowed in user names, > another wants usernames to start with numbers. > > May I ask for your opinion before denying or following the requests? Personally, I prefer to stick to the POSIX minimum requirements (max 8 chars), and limit usernames to [a-z][a-z0-9]. I would prefer the default in adduser to enforce such limit, but see the convinience of others with a different view to be able to configure adduser to allow more relaxed rules. Because of this, I would suggest making it _possible_ to relax the rules by updating the configuration file, but leave the default as they are at the moment. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sat, 05 Feb 2005, Marc Haber wrote: > adduser has two bug reports open where people are asking for user name > rules to be relaxed. One report wants "." to be allowed in user names, > another wants usernames to start with numbers. Allowing the dot is ok. I do think that usernames starting with numbers is asking for total breakage, though. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
* Henrique de Moraes Holschuh ([EMAIL PROTECTED]) [050205 16:35]: > On Sat, 05 Feb 2005, Marc Haber wrote: > > adduser has two bug reports open where people are asking for user name > > rules to be relaxed. One report wants "." to be allowed in user names, > > another wants usernames to start with numbers. > Allowing the dot is ok. I do think that usernames starting with numbers is > asking for total breakage, though. IMHO even the dot is, eh, difficult. Consider a chown user.group file. Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sat, 2005-02-05 at 16:39 +0100, Andreas Barth wrote:
> IMHO even the dot is, eh, difficult. Consider a chown user.group file.
if (no_such_username)
{
chown();
chgrp();
}
else
{
chown();
}
If there is such an username and the user meant to change both user and
group, it's his own fault for not using the user:group notation. chown
could print a warning when the dot notation is used.
--
Petri Latvala
signature.asc
Description: This is a digitally signed message part
Re: About valid and invalid user names
In article <[EMAIL PROTECTED]> you wrote: > On Sat, 05 Feb 2005, Marc Haber wrote: >> adduser has two bug reports open where people are asking for user name >> rules to be relaxed. One report wants "." to be allowed in user names, >> another wants usernames to start with numbers. > > Allowing the dot is ok. I do think that usernames starting with numbers is > asking for total breakage, though. Why not make it an configurable RE? You cant avoid ppl breaking their systems, but you can help them to enforce their policy. For example : may be fine on non-passwd systems (however some tools will have trouble with that). chown was recently fixed to allow . in usernames, no? Gruss Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sat, 05 Feb 2005, Bernd Eckenfels wrote: > In article <[EMAIL PROTECTED]> you wrote: > > On Sat, 05 Feb 2005, Marc Haber wrote: > >> adduser has two bug reports open where people are asking for user name > >> rules to be relaxed. One report wants "." to be allowed in user names, > >> another wants usernames to start with numbers. > > > > Allowing the dot is ok. I do think that usernames starting with numbers is > > asking for total breakage, though. > > Why not make it an configurable RE? You cant avoid ppl breaking their Because people will use it to enable users with start with a digit, since they certainly don't know better or they would never have asked for this. If I name an user "0", what is the expected result of chown 0 somefile ? root or the new user "0"? For all programs out there? Please don't give people this much rope to hang themselves with *so easily*. > systems, but you can help them to enforce their policy. For example : may be > fine on non-passwd systems (however some tools will have trouble with that). : is not fine because it is not POSIX. Other stuff might croak very hard on : it. > chown was recently fixed to allow . in usernames, no? Because '.' is POSIX, thus valid. And not accepting the '.' is a damn bug in any POSIX-compliant utility. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On 05-Feb-05, 10:47 (CST), Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: > > Because '.' is POSIX, thus valid. And not accepting the '.' is a damn > bug in any POSIX-compliant utility. According the SUS section that Kurt quoted, leading digits are equally acceptable. I think it might be reasonable to accept leading digits when there is at least one non-digit in the name. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sat, 05 Feb 2005 17:21:28 +0100, Bernd Eckenfels <[EMAIL PROTECTED]> wrote: >Why not make it an configurable RE? I am quite reluctant with a so big change in a base package, ranking at #1 in popcon, so soon before sarge release. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: About valid and invalid user names
On Sat, 5 Feb 2005 14:47:37 -0200, Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: >Because people will use it to enable users with start with a digit, since >they certainly don't know better or they would never have asked for this. Right now, we have users patching the adduser "binary" to allow their user names. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: About valid and invalid user names
* Marc Haber: > On Sat, 05 Feb 2005 17:21:28 +0100, Bernd Eckenfels > <[EMAIL PROTECTED]> wrote: >>Why not make it an configurable RE? > > I am quite reluctant with a so big change in a base package, ranking > at #1 in popcon, so soon before sarge release. The check is on a very common code path. It will be comparatively well-tested when it's released with sarge. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sat, 05 Feb 2005, Marc Haber wrote: > On Sat, 5 Feb 2005 14:47:37 -0200, Henrique de Moraes Holschuh > <[EMAIL PROTECTED]> wrote: > >Because people will use it to enable users with start with a digit, since > >they certainly don't know better or they would never have asked for this. > > Right now, we have users patching the adduser "binary" to allow their > user names. They are going a long way to be able to shoot themselves in the foot :( Maybe an initial digit is valid as long as there are other no-digit characters in the username? I still am not sure tools will like it. Still, if it is POSIX, we do it and we fix whatever tools that break, like it was done to chown. All-digit usernames are clearly an extremely bad idea, IMHO. Anyone who needs it better make damn sure they *always* map one-to-one to the same numerical userid, or they might be creating a huge security hole. While adduser might enforce the above match for all-numerical usernames, I am not sure it is a good idea on the long run. If the users ever get renumbered, kabloom! It is a very bad practice that IMHO we should not be making any easier. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293772: ITP: gr-audio-alsa -- GNU Radio interface to ALSA audio
Package: wnpp Severity: wishlist * Package name: gr-audio-alsa Version : 0.1 Upstream Author : Eric Blossom <[EMAIL PROTECTED]> * URL or Web page : http://www.gnu.org/software/gnuradio * License : GNU GPL v2 or later Description : GNU Radio interface to ALSA audio The package interfaces the GNU Radio libraries to OSS audio interface. . GNU Radio is a Software Defined Radio package which does the functionality of a traditional Radio Receiver and Transmitter, including normal AM, FM and amateur radio transmissions and also Television transmissions. The ultimate goal is to have the ability to demodulate every form of communication which is happening in the entire spectrum. . The GNU Radio homepage is http://www.gnu.org/software/gnuradio . The unofficial packages are available at http://pkg-gnuradio.alioth.debian.org Thanks Ramakrishnan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293771: ITP: gr-ssrp -- GNU Radio interface to SSRP
Package: wnpp Severity: wishlist * Package name: gr-ssrp Version : 0.2 Upstream Author : David Carr <[EMAIL PROTECTED]> * URL or Web page : http://oscar.dcarr.org/ssrp/ * License : GNU GPL v2 Description : GNU Radio interface to SSRP The package interfaces the GNU Radio libraries to SSRP hardware interface. . GNU Radio is a Software Defined Radio package which does the functionality of a traditional Radio Receiver and Transmitter, including normal AM, FM and amateur radio transmissions and also Television transmissions. The ultimate goal is to have the ability to demodulate every form of communication which is happening in the entire spectrum. . The GNU Radio homepage is http://www.gnu.org/software/gnuradio . The unofficial packages are available at http://pkg-gnuradio.alioth.debian.org Thanks Ramakrishnan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293773: ITP: gr-wxgui -- GUI toolkit for GNURadio
Package: wnpp Severity: wishlist * Package name: gr-wxgui Version : 0.1 Upstream Author : Eric Blossom <[EMAIL PROTECTED]> * URL or Web page : http://www.gnu.org/software/gnuradio * License : GNU GPL v2 or later Description : GUI toolkit for GNURadio This package is a wxWindows based toolkit for use with GNU Radio libraries. The functions provided are oriented towards mostly plotting and displaying the data processed by GNU Radio. . GNU Radio is a Software Defined Radio package which does the functionality of a traditional Radio Receiver and Transmitter, including normal AM, FM and amateur radio transmissions and also Television transmissions. The ultimate goal is to have the ability to demodulate every form of communication which is happening in the entire spectrum. . The GNU Radio homepage is http://www.gnu.org/software/gnuradio . The unofficial packages are available at http://pkg-gnuradio.alioth.debian.org Thanks Ramakrishnan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293774: ITP: gr-audio-oss -- GNU Radio interface to OSS audio
Package: wnpp Severity: wishlist * Package name: gr-audio-oss Version : 0.2 Upstream Author : Eric Blossom <[EMAIL PROTECTED]> * URL or Web page : http://www.gnu.org/software/gnuradio/ * License : GNU GPL v2 or later Description : GNU Radio interface to OSS audio The package interfaces the GNU Radio libraries to OSS audio interface. . GNU Radio is a Software Defined Radio package which does the functionality of a traditional Radio Receiver and Transmitter, including normal AM, FM and amateur radio transmissions and also Television transmissions. The ultimate goal is to have the ability to demodulate every form of communication which is happening in the entire spectrum. . The GNU Radio homepage is http://www.gnu.org/software/gnuradio . The unofficial packages are available at http://pkg-gnuradio.alioth.debian.org Thanks Ramakrishnan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293775: ITP: gnuradio-examples -- Example programs to test and use GNURadio
Package: wnpp Severity: wishlist * Package name: gnuradio-examples Version : 0.2 Upstream Author : Eric Blossom <[EMAIL PROTECTED]> * URL or Web page : http://www.gnu.org/software/gnuradio * License : GNU GPL v2 or later Description : Example programs to test and use GNURadio This package contains Python programs which uses and tests the GNU Radio libraries. The examples include dialtone generation, complete FM receiver and many more exciting applications. . GNU Radio is a Software Defined Radio package which does the functionality of a traditional Radio Receiver and Transmitter, including normal AM, FM and amateur radio transmissions and also Television transmissions. The ultimate goal is to have the ability to demodulate every form of communication which is happening in the entire spectrum. . The GNU Radio homepage is http://www.gnu.org/software/gnuradio . The unofficial packages are available at http://pkg-gnuradio.alioth.debian.org Thanks Ramakrishnan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293776: ITP: ssrp -- Simple Software Radio Peripheral
Package: wnpp Severity: wishlist * Package name: ssrp Version : 0.3.3 Upstream Author : David Carr <[EMAIL PROTECTED]> * URL or Web page : http://oscar.dcarr.org/ssrp/ * License : GNU GPL v2 or later Description : Simple Software Radio Peripheral SSRP is a simplified version of the Universal Software Radio Peripheral, which lets a user to capture analog signals via USB 2.0 port and process it using GNU Radio. . The package contains the firmware for use with the SSRP board which uses the Cypress EZ-USB 2.0 chip and the LTC1746 ADC board. . GNU Radio is a Software Defined Radio package which does the functionality of a traditional Radio Receiver and Transmitter, including normal AM, FM and amateur radio transmissions and also Television transmissions. The ultimate goal is to have the ability to demodulate every form of communication which is happening in the entire spectrum. . The GNU Radio homepage is http://www.gnu.org/software/gnuradio . The unofficial packages are available at http://pkg-gnuradio.alioth.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293785: ITP: gnomebaker -- CD/DVD writer for the GNOME desktop
Package: wnpp Severity: wishlist * Package name: gnomebaker Version : 0.3 Upstream Author : Luke Biddel <[EMAIL PROTECTED]> * URL : http://www.sourceforge.net/projects/gnomebaker/ * License : GPL Description : CD/DVD writer for the GNOME desktop Gnomebaker is an easy to use CD/DVD burner.Its current features include: * Data and audio CD burning * Multisession CDs * CD/DVD formatting * DVD data disk burning Obs.: version 0.3 has not been released, yet. Packages built from current CVS can be found at http://people.debian.org/~goedson/debian/packages/gnomebaker/snapshots/ -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-k7 Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
Am 2005-02-05 17:21:28, schrieb Bernd Eckenfels: > Why not make it an configurable RE? You cant avoid ppl breaking their > systems, but you can help them to enforce their policy. For example : may be > fine on non-passwd systems (however some tools will have trouble with that). > chown was recently fixed to allow . in usernames, no? It works since WOODY... I can not call it "recently". > Gruss > Bernd Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: About valid and invalid user names
Am 2005-02-05 11:13:50, schrieb Steve Greenland: > According the SUS section that Kurt quoted, leading digits are equally > acceptable. I think it might be reasonable to accept leading digits when > there is at least one non-digit in the name. Agreed. > Steve Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
dpkg-preconfigure error messages
Hello,
suddenly I start to get mighty frightening error messages:
plonk:~# apt-get install --reinstall dpkg
Reading Package Lists... Done
Building Dependency Tree... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not
upgraded.
Need to get 0B/1656kB of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue? [Y/n]
String found where operator expected at /usr/sbin/dpkg-preconfigure line
96, near "die sprintf(gettext(""
(Might be a runaway multi-line "" string starting on line 94)
(Missing semicolon on previous line?)
Bareword found where operator expected at /usr/sbin/dpkg-preconfigure line
96, near "die sprintf(gettext("debconf"
(Do you need to predeclare die?)
Unquoted string "debconf" may clash with future reserved word at
/usr/sbin/dpkg-preconfigure line 96.
String found where operator expected at /usr/sbin/dpkg-preconfigure line
103, near "gettext(""
(Might be a runaway multi-line "" string starting on line 96)
(Missing semicolon on previous line?)
Bareword found where operator expected at /usr/sbin/dpkg-preconfigure line
104, near "$package, $confmodule"
(Might be a runaway multi-line ff string starting on line 103)
(Missing operator before dule?)
Unquoted string "dule" may clash with future reserved word at
/usr/sbin/dpkg-preconfigure line 104.
syntax error at /usr/sbin/dpkg-preconfigure line 96, near "die
sprintf(gettext(""
Unmatched right curly bracket at /usr/sbin/dpkg-preconfigure line 108, at
end of line
syntax error at /usr/sbin/dpkg-preconfigure line 108, near "}"
Execution of /usr/sbin/dpkg-preconfigure aborted due to compilation errors.
(Reading database ... 158298 files and directories currently installed.)
Preparing to replace dpkg 1.10.26 (using .../d/dpkg/dpkg_1.10.26_i386.deb)
...
Unpacking replacement dpkg ...
Setting up dpkg (1.10.26) ...
Is this problem known? What is the cause of this? I checked both the
dpkg and the gettext bug report pages but did not recognise anything similar.
All the best,
Jochen
--
http://seehuhn.de/
signature.asc
Description: Digital signature
Re: dpkg-preconfigure error messages
* Jochen Voss <[EMAIL PROTECTED]> [2005-02-05 20:43]: > Is this problem known? What is the cause of this? I checked both > the dpkg and the gettext bug report pages but did not recognise > anything similar. It's fixed in debconf 1.4.44 which just got accepted today. debconf (1.4.44) unstable; urgency=low . * Fix a rogue quotation mark intorduced in the translatable string patch in the previous version. Closes: #293666 (and approximatly 2e5 other bugs that will be filed before dinstall tomorrow). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-preconfigure error messages
Hello Martin, On Sat, Feb 05, 2005 at 08:51:38PM +, Martin Michlmayr wrote: > It's fixed in debconf 1.4.44 which just got accepted today. Thank you for the quick answer. > * Fix a rogue quotation mark intorduced in the translatable string patch > in the previous version. Closes: #293666 (and approximatly 2e5 other bugs > that will be filed before dinstall tomorrow). It is only 2e5-1 since I won't file mine. All the best, Jochen -- http://seehuhn.de/ signature.asc Description: Digital signature
Re: Bug#293771: ITP: gr-ssrp -- GNU Radio interface to SSRP
On Sat, Feb 05, 2005 at 11:16:54PM +0530, Ramakrishnan Muthukrishnan wrote: > The package interfaces the GNU Radio libraries to SSRP > hardware interface. Just so people know; there will be a gr-usrp as well (for the http://comsec.com/wiki?UniversalSoftwareRadioPeripheral), but as I haven't received mine yet, I haven't gotten around to writing a proper ITP yet. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debug packages cluttering the archive
With the increasing numbers of libraries, especially libraries in development, we have an increasing number of -dbg packages in the archive. As they are useful only for debugging, and not for the average user, I think they are mostly cluttering the Packages file and mirror space. Practically speaking, there is a very small chance, when you find a bug in a library, that the -dbg package is available. This is worse if the bug is in a binary and not a library; you often end up rebuilding a debugging version of the package for the submitting user. In fact, the availability of a -dbg version could be useful for every architecture-dependent package. The most obvious solution I can come up for this issue is to build a separate tree with DEB_BUILD_OPTIONS="noopt nostrip", at least for i386. That means having a dedicated machine that would be used to run a buildd for that. Unfortunately, I don't have such a machine, and I don't know of an available i386 project machine. Are there some people here who'd be interested, or who could point me to available resources? If not, do you have other ideas to make debugging packages easily available? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
DD needing a sponsor to upload
Hi, As I moved recently, I currently have no decent Internet connectivity. Hence, I'm quite unable to keep an unstable system up-to-date, si I can't build packages to upload. Several packages of mine are in need of an upload, especially libcdio and vcdimager. I have uploaded the source packages to my debian homepage on http://people.debian.org/~nboullis. Could someone please build the binary packages and upload for me? (As far as I know source-only uploads are not allowed, and anyway, I can't be sure it'll work fine with an up-to-date sid; I only tested with a one month old sarge.) Thanks in advance, Nicolas Boullis PS: please CC your replies to me (MFT set accordingly) as I currently can't track d-d. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#293772: ITP: gr-audio-alsa -- GNU Radio interface to ALSA audio
* Ramakrishnan Muthukrishnan | Package: wnpp | Severity: wishlist | | * Package name: gr-audio-alsa | Version : 0.1 | Upstream Author : Eric Blossom <[EMAIL PROTECTED]> | * URL or Web page : http://www.gnu.org/software/gnuradio | * License : GNU GPL v2 or later | Description : GNU Radio interface to ALSA audio | | The package interfaces the GNU Radio libraries to OSS audio | interface. Could they be called gnuradio-audio-alsa and similar? gr is a bit short and doesn't really tell what the package is about. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About valid and invalid user names
On Sat, Feb 05, 2005 at 02:47:37PM -0200, Henrique de Moraes Holschuh wrote: > Please don't give people this much rope to hang themselves with *so easily*. Why dont u think they dont change the name of the user in the passwd?! I dont think it is needed to play big daddy microsoft here. If somebody can configure a RE, she also can deal with the consequences. Gruss Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Xen-devel] Re: xen 2.0.x and debian
On Sat, 5 Feb 2005, Adam Heath wrote: > On Wed, 2 Feb 2005, Nuutti Kotivuori wrote: > > > Tom Hibbert wrote: > > > I think we are waiting on 2.6.10 to get accepted into testing. If > > > you're tired of waiting you can build the debs yourself (like I did > > > :) > > > > > > http://people.debian.org/~doogie/xen_2.0.3-0.diff.gz > > > > Please add 'dh-kpatches' to build-deps. > > Already done, just not uploaded there. I'll do so when I wake up. > > Here is the list of things left to do, before uploading: > > * Disable 2.4.29 patch generation. This kernel source is not yet in > debian(arg!). > > * Copy package descriptions from 1.2, and extend for 2.0. > > * Verify sanity of xendomains init script, as far as debian policy is > concerned. > > * Generate pristine 2.6.10 source from debian kernel source, instead of > requiring ../linux-2.6.10.tar.bz2 to exist. > > * Allow for installation of xend(and friends) when not running a xen kernel. > The code currently breaks badly if a system dual-boots. Users are also > prone to install a set of tool debs and the kernel in one run, before > rebooting into the new kernel. > > The above are all that is required for an upload to experimental. I need to > do upgrade testing from 1.2 before I can upload to unstable, however. Ok, I've uploaded to debian's experimental tree. This is to make certain it doesn't blow up when people install it(even tho I'm using it locally). The main problem with it is that it doesn't do upgrades from 1.2 at all. All the above TODO items are solved, except that the xendomains init script doesn't implement force-reload. If you want to fetch the packages before they are processed thru debian's NEW archive, then visit http://people.debian.org/~doogie/packages/. The debs, and source archives, are both there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Inconsistent naming of ethernet interfaces...
I have a computer system with 3 ethernet ports, one on the motherboard and two on a dual NIC PCI card. Typically, the onboard port is aliased as eth0 while the ports on the NIC get assigned eth1 and eth2. Lately, eth1 gets assigned to the onboard port, which is very annoying since that messes up my connections to the internet and LAN subnets. I know this is a problem that many people have complained about when upgrading their kernel from 2.4.x to 2.5.x or 2.6.x. For some people this problem happens when they upgrade their hardware (as it did for me). I understand that one way to fix the naming of the interfaces is to use the nameif utility and store the static interface-to-mac mappings for my system in /etc/mactab. I've gotten this to work with trivial effort. So far so good. In the future, if I swap out my dual NIC with a newer one, I'd like a way to be able to produce the new mappings automatically. Perhaps I could do it like this for a port I want to call "eth1": 1- Connect ethernet loopback plug to port 2- Run my script, which does this: a. determine that I am trying to configure eth1 b. probe all ports to see which has loopback activity. c. store the mac addr of that port in mactab (along with eth1 tag) 3- Done. This is a simple self-calibration procedure. But I'm guessing somebody has some thoughts on how to better implement this. This will be especially useful to someone who is trying to ship a large number of computers pre-configured with Debian, and they want to ensure that eth0 is always the onboard port, eth1 is the left port on the dual nic, and eth2 is the right port on the dual nic, and so on. Any thoughts will be appreciated. Thanks, Salman __ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debug packages cluttering the archive
On Sun, Feb 06, 2005 at 12:36:55AM +0100, Josselin Mouette wrote: > With the increasing numbers of libraries, especially libraries in > development, we have an increasing number of -dbg packages in the > archive. As they are useful only for debugging, and not for the average > user, I think they are mostly cluttering the Packages file and mirror > space. > > Practically speaking, there is a very small chance, when you find a bug > in a library, that the -dbg package is available. This is worse if the > bug is in a binary and not a library; you often end up rebuilding a > debugging version of the package for the submitting user. In fact, the > availability of a -dbg version could be useful for every > architecture-dependent package. > > The most obvious solution I can come up for this issue is to build a > separate tree with DEB_BUILD_OPTIONS="noopt nostrip", at least for i386. > That means having a dedicated machine that would be used to run a buildd > for that. Unfortunately, I don't have such a machine, and I don't know > of an available i386 project machine. > > Are there some people here who'd be interested, or who could point me to > available resources? If not, do you have other ideas to make debugging > packages easily available? It was brought up on IRC, a couple of weeks ago (my apologies, but I don't recall who brought it up, nor do I have a log) that it is now possible to strip debugging information from a binary or library, and keep the debugging information in a separate file. When invoking GDB (I don't know about other debuggers, yet, but it seems like an easy thing to add as an extension given the way it's done), it checks first for debugging symbols directly, then for the presence of a pointer to a file to find them in. If it finds the pointer, it checks that (using a short search path to try more than just the flat name, generally), and if found, loads the debugging symbols from there. Switching dh_strip to use this would provide a number of benefits: 1) It would become possible (I'm not sure if it would be *sane*) to include debugging information for all binaries and libraries in a fairly straightforward manner - and one which could target a directory that, like /usr/share/doc or others, can safely be purged by the local admin if they don't want the disk bloat. 2) Even if only applied to -dbg packages, it would make -dbg packages significantly smaller (only needing the debug symbols file, not a complete secondary copy of the library). 3) Allows you to generate a -dbg package without doing a second build-run over the libraries or having to do strange convolutions to package both stripped and unstripped libraries without duplicating the build. 4) Allows you to use debugging on any library without having to restart the application with a suitable LD_LIBRARY_PATH (nor does it run afoul of things that muck with library search paths or don't permit the environment to override it for security reasons). I believe the proper Google search for more details would be "gdb separate debug files". -- Joel Aelwyn <[EMAIL PROTECTED]> ,''`. : :' : `. `' `- signature.asc Description: Digital signature
Re: Debug packages cluttering the archive
On Sat, Feb 05, 2005 at 10:33:53PM -0700, Joel Aelwyn wrote: > It was brought up on IRC, a couple of weeks ago (my apologies, but I don't > recall who brought it up, nor do I have a log) that it is now possible > to strip debugging information from a binary or library, and keep the > debugging information in a separate file. When invoking GDB (I don't know Wow. I've wanted this for a while, and VC has done it for years (at least since 1998)--it's a little disappointing that this has apparently been around for a couple years and still isn't mainline (/usr/bin/strip shows no sign of the -f option mentioned in the info page found from your google search). I had no idea it was even implemented, though. (Aha: the strip tool mentioned is in elfutils, which is non-free. Blah.) -- Glenn Maynard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
