Re: Standard way to disable services
On Wed, Aug 06, 2008 at 10:32:14AM +0200, Harald Braumann wrote: > On Thu, 31 Jul 2008 10:56:07 -0400 > Guido Günther <[EMAIL PROTECTED]> wrote: > > > We might not want to use policy-rc.d as is in sysvinit of filerc > > during startup but we might consider moving these policy decisions > > "no I don't want this daemon at startup, yes I want that daemon > > reloaded after resume" into a policy layer that is independent of the > > underlying init mechanism and which can be queried by the different > > tools be it during system startup/shutdown or after/before suspend > > to/from ram/disk. Cheers, > > Is it really necessary? I'm not a big fan of abstraction layers. They > usually complicate things instead of making them easier. So far for me > the sysv init process with its start and kill links is sufficient for > all purposes. It's a simple and stable system. Don't add complicated > cruft on top of it. The obvious advantage is that it's extensible to other init systems like filerc or upstart. -- Guido > I never had the need to restart daemons on suspend/resume. But if this > should be supported, then I'd prefer, if extra runlevels were defined > for going into suspend (similar to rc0.d) and for resuming (similar to > rcS.d) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhclient-script, hooks, and changing the environment
Peter Samuelson wrote: [Brian May] How many dhclient scripts actually make use of this "feature" of being able to change environment variables? If it is little used maybe it isn't worth the effort in supporting. That is exactly the question Martin asked as he opened the thread. While I can't solve the halting problem, I can say that for mailing lists, threads almost always either halt or loop within a short time. I originally misunderstood what Martin was trying to do. Sorry about the detour. Brian May -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packages getting marked not-for-us
On Thu, Aug 07, 2008 at 04:06:50PM -0400, Roberto C. S?nchez wrote: > On Thu, Aug 07, 2008 at 09:57:49PM +0200, Petter Reinholdtsen wrote: > > I would rather have maintainers spend time improving their packages > > instead of wasting it trying to figure out why some architecture > > fail/refuses to build their package. > In some (many?) cases that leads to direct improvement of the package. > I have had a package quit building on a particular architecture and it > ended revealing itself as a problem with something in the build system All of which would go a lot better if the maintainer were told about whatever issue caused the buildd to be configured not to build the package rather than having to discover that this has happened and infer the reasoning for the decision. Also note that this discussion is about the buildds being configured to not even try compiling a package, not about build failures encountered on the buildds. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494269: marked as done (general: TEST, SORRY, Do not take care)
Your message dated Fri, 08 Aug 2008 14:48:21 + with message-id <[EMAIL PROTECTED]> and subject line has caused the Debian Bug report #494269, regarding general: TEST, SORRY, Do not take care to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 494269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494269 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: general Severity: wishlist TEST, excuses me -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- --- End Message ---
Re: Bug#493697: ITP: mobile-manager -- mobile manager GPRS/3G daemon
Am 2008-08-04 17:53:05, schrieb Hendrik Sattler: > Am Montag, 4. August 2008 13:49:09 schrieb Guus Sliepen: > > What is missing here is whether or not mobile-manager comes with a GUI > > component to interact with the daemon. > > ...and how it can maybe interact with network-manager. There is not so much > special about a GPRS/whatever device apart from the few AT chatting that > handles PIN/PUK and the dial commands. The world was using pppd for that. > I vote for all three working together... Does "network-manager" and "mobile-manager" allow SMS or Voice-Connect? It seems, in the next time there will be a third tool. Thanks, Greetings and nice Day/Evening Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: dhclient-script, hooks, and changing the environment
On Wed, Aug 06, 2008 at 09:10:56PM -0300, martin f krafft wrote: > Anything else? Do you know of packages that rely on this > functionality? Do you have scripts of your own which modify the > environment? Would you please be so kind as to explain to me what > they do, and help me figure out whether there isn't a better way for > them? In the past I've used dhclient-enter-hooks.d to work around buggy hotel networks which advertise a gateway for the default route which is outside the local network. So I used a dhclient-enter-hooks.d script to hack the netmask returned by the DHCP server so that the default route would be accepted. (Unfortunately, Windows allows the default route to be outside the local network arrange of the ethernet interface, and apparently if there is only one ethernet interface, Windows will assume that instead of rejecting the route, or dropping packets on the floor, to do the convenient-but-wrong thing of assuming the packets should go out via the default route to the ethernet interface, even though the default route is an invalid non-local address for that interface. As a result, trashy hotel networks have no incentive to fix their DHCP servers, since they work just fine on Windows laptops - Ted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhclient-script, hooks, and changing the environment
also sprach Theodore Tso <[EMAIL PROTECTED]> [2008.08.08.1453 -0300]: > In the past I've used dhclient-enter-hooks.d to work around buggy > hotel networks which advertise a gateway for the default route > which is outside the local network. netconf could handle this internally, and it would be fair to include this. So assuming yo get a 192.168.0.0/24 address and the default gateway is 10.0.0.1, what is the best approach? Hacking the netmask seems awful. Adding a route that makes 10.0.0.1 link-local seems better, no? so assuming a CIDR $ip_addr object, a $router object, and the $iface string parsed from dhclient, you'd do: if not ip_addr.get_network().includes(router): add_linklocal_route(router, iface) ? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems you can't assign IP address 127.0.0.1 to the loopback adapter, because it is a reserved address for loopback devices. -- micro$oft windoze xp professional digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Bug#493697: ITP: mobile-manager -- mobile manager GPRS/3G daemon
Am Freitag, 8. August 2008 19:09:14 schrieb Michelle Konzack: > Am 2008-08-04 17:53:05, schrieb Hendrik Sattler: > > Am Montag, 4. August 2008 13:49:09 schrieb Guus Sliepen: > > > What is missing here is whether or not mobile-manager comes with a GUI > > > component to interact with the daemon. > > > > ...and how it can maybe interact with network-manager. There is not so > > much special about a GPRS/whatever device apart from the few AT chatting > > that handles PIN/PUK and the dial commands. The world was using pppd for > > that. I vote for all three working together... > > Does "network-manager" and "mobile-manager" allow SMS or Voice-Connect? > > It seems, in the next time there will be a third tool. These are kind of mutually exclusive. Some mobile GSM phones can do GSM multiplex (so SMS and data connections can work at the same time) but I don't know about a good working implementation. Voice-connection via bluetooth can be done using alsa, AFAIK, depends on the phone if this can be done in parallel. Anyway, in the best case (means capable hardware), there is no need to do this in one software. BTW: SMS functionality is better integrated in PIM software. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
What is the target used by buildd?
Hi, I believed buildd.debian.org was meant to build only binary-arch packages. But in recent build logs of the zeroc-ice package: http://buildd.debian.org/build.cgi?pkg=zeroc-ice;ver=3.3.0-4 I found buildd tried to build a binary-indep package (libzeroc-ice-3.3-cil). Using ./debian/rules binary-arch in a chrooted environment in an x86 box works as expected. I made my x86 build log for binary-arch target available at http://arco.esi.uclm.es/~francisco.moya/debian/zeroc-ice_3.3.0-4_i386.build Is this a buildd/sbuild/wanna-peruse bug? Thanks Francisco Moya <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What is the target used by buildd?
sbuild calls dpkg-buildpackage to build the package. It doesn't touch the rules file directly. On 8/8/08, Francisco Moya <[EMAIL PROTECTED]> wrote: > Hi, > > I believed buildd.debian.org was meant to build only binary-arch packages. > > But in recent build logs of the zeroc-ice package: > http://buildd.debian.org/build.cgi?pkg=zeroc-ice;ver=3.3.0-4 > I found buildd tried to build a binary-indep package (libzeroc-ice-3.3-cil). > > Using ./debian/rules binary-arch in a chrooted environment in an x86 box > works as expected. I made my x86 build log for binary-arch target available > at > http://arco.esi.uclm.es/~francisco.moya/debian/zeroc-ice_3.3.0-4_i386.build > > Is this a buildd/sbuild/wanna-peruse bug? > > Thanks > > Francisco Moya <[EMAIL PROTECTED]> > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What is the target used by buildd?
Francisco Moya wrote: > Hi, > > I believed buildd.debian.org was meant to build only binary-arch packages. > > But in recent build logs of the zeroc-ice package: > http://buildd.debian.org/build.cgi?pkg=zeroc-ice;ver=3.3.0-4 > I found buildd tried to build a binary-indep package (libzeroc-ice-3.3-cil). > > Using ./debian/rules binary-arch in a chrooted environment in an x86 box > works as expected. I made my x86 build log for binary-arch target available at > http://arco.esi.uclm.es/~francisco.moya/debian/zeroc-ice_3.3.0-4_i386.build > > Is this a buildd/sbuild/wanna-peruse bug? See bug 229357. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhclient-script, hooks, and changing the environment
On Fri, Aug 08, 2008 at 03:29:43PM -0300, martin f krafft wrote: > also sprach Theodore Tso <[EMAIL PROTECTED]> [2008.08.08.1453 -0300]: > > In the past I've used dhclient-enter-hooks.d to work around buggy > > hotel networks which advertise a gateway for the default route > > which is outside the local network. > > netconf could handle this internally, and it would be fair to > include this. > > So assuming yo get a 192.168.0.0/24 address and the default gateway > is 10.0.0.1, what is the best approach? Hacking the netmask seems > awful. Adding a route that makes 10.0.0.1 link-local seems better, > no? Yes, adding a specific link-local route is probably better. In practice, the various Awful Hotel Network implementations would give you an IP configuration that was something like this IP Addr: 10.0.2.67 Netmask: 255.255.255.0 Gateway: 10.0.8.1 So the simpler thing for me to do was to hack the netmask to be 255.255.0.0. But I agree, adding IP-specific route for the gateway out to the interface is the best thing to do. - Ted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#494043: ITP: ozymandns -- An experimental DNS server and miscellaneous DNS tools
I've found that while ozymandns is useful for tunneling some things in a pinch, I've had a lot more luck with running iodine as a daemon and might suggest checking it out. I tend to favor it for experimentation as it's packaged in sid already, is actively maintained, and has support for using the NULL RR type allowing much more data to fit in a "downstream" response. Cheers, jonathan On Wed, Aug 06, 2008 at 11:17:56PM +0100, Steve McIntyre wrote: > Jacob wrote: > >Package: wnpp > >Severity: wishlist > >Owner: Jacob Appelbaum <[EMAIL PROTECTED]> > > > > > >* Package name: ozymandns > > Version : 0.0.1 > > Upstream Author : Dan Kaminsky <[EMAIL PROTECTED]> > >* URL : http://www.doxpara.com/ozymandns_src_0.1.tgz > >* License : (Currently consulting with upstream for explicit > >* license) > > Programming Lang: (C, Perl) > > Description : An experimental DNS server and miscellaneous DNS tools > > > >OzymanDNS is a suite of tools for experimenting with DNS. It includes a > >number of tools: > > > >aska.pl - DNS File/Stream Sender > >geta.pl - DNS File/Stream Receiver > >nomde.pl - Experimental DNS Server > >droute.pl - Reliable DNS Transport for standard input/output > >glance.c - Represents IP addresses as dates > > > >More information about all of these tools can be found in Dan's Black > >Ops DNS 2004 CCC Congress slides: > >http://www.ccc.de/congress/2004/fahrplan/files/297-black-ops-of-dns-slides.pdf > > Hmmm. I used to run this version of ozymandns to provide IP-over-DNS > style services, and it was far from stable. It would often crash, drop > connections or chew lots of CPU for no apparent reason. Unless things > have improved substantially since, I would recommend strongly against > adding these to the archive. > > -- > Steve McIntyre, Cambridge, UK.[EMAIL > PROTECTED] > "We're the technical experts. We were hired so that management could > ignore our recommendations and tell us how to do our jobs." -- Mike Andrews > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
