Re: More advanced home directory creation in Debian?
On Sun, 2010-08-22 at 19:00 -0300, Fernando Lemos wrote: On Sun, Aug 22, 2010 at 6:40 PM, Christoph Anton Mitterer cales...@scientia.net wrote: You're aware that not only .bash_* and .profile can be distributed by /etc/skel,... but any other config file (e.g. .vimrc) a specific site or organisation may found useful for their users? Or a predefined directory structure,... ssh config perhaps specific for each user? /etc/skel is used to populate user home directories on user creation, nothing more. For system-wide settings , use /etc (e.g. /etc/vim/vimrc.local). Use site-specific scripts for any more convoluted needs you might have. There's nothing to be discussed about this, really. Think about places where the home is on a server, while /etc is on local workstations. You need to extend your vision. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284146874.1939.1.ca...@fbrt233-laptop
Re: More advanced home directory creation in Debian?
On Sun, 2010-08-15 at 15:42 +0200, Christoph Anton Mitterer wrote: Hi. I'd like the idea... it would make home-dir creation here at the faculty a lot more easier. On Tue, 2010-08-03 at 11:08 +0200, Petter Reinholdtsen wrote: The location could for example be /etc/skel.d/ I'd however suggest e.g. /etc/adduser.d or so... or at least not skel.d Conceptually the skel contents are copied to the homedir, which the skel.d contents are not but that's just cosmetics. I second this, as I feel the need to have some hook to create the home directory. Recently, with ZFS or Btrfs (I imagine for this one, did not check myself) or remotely-stored (ex.: NFS) homes, it makes sense to have some local script to create them, not only something to fill them up with stuff. I was thinking into uglily patching my own adduser, but it's definitely worst something more generic, as many people might benefit from it. Cheers, Chris. PS: sorry for the cross-posting, but I feel the debian-...@d.o should be aware of this topic. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282477072.1998.108.ca...@fbrt233-laptop
dpkg and hardlinks
Hi guys, I'm currently thinking about deduplication[1] on my Debian systems. As you probably know, the whole thing about deduplication is that replacing files with content with hardlink to other file(s) with the exact same content is sometimes a good idea, at least to regain (uselessly used) disk space. The problem is that sometimes, files are identical at a given time, but are meant to evolve separately. So using deduplication for data basically depends upon how your data is actually used (don't try this at home without knowing what you are doing!). For files from packages, though, deduplication might be a good idea, as dpkg is supposedly the only one to ever modify the files (under /usr for example). I don't know however how dpkg treats hardlinks. Does it break the hardlink before replacing a file or does it replace the file whatever its real nature is? Some packages are particularly affected by duplication of data (example: packages with .ppd files). [1] http://en.wikipedia.org/wiki/Data_deduplication -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: dpkg and hardlinks
Raphael Hertzog wrote: On Tue, 24 Mar 2009, Jerome Warnier wrote: For files from packages, though, deduplication might be a good idea, as dpkg is supposedly the only one to ever modify the files (under /usr for example). I don't know however how dpkg treats hardlinks. Does it break the hardlink before replacing a file or does it replace the file whatever its real nature is? IIRC dpkg preserves hardlinks inside a binary package but I don't see how it could do the same across multiple binary packages. Oh, I didn't expect it to. I just wanted to know its behaviour when it upgrades a package. Before the upgrade, the file is a hardlink (because I hardlinked it manually), then it tries to upgrade the file/hardlink. Does it break the hardlink* before upgrading the file or does it overwrite the file/hardlink and all of its siblings? Cheers, * because it knows it is supposed to be a plain file, and it no longer is. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: dpkg and hardlinks
Peter Samuelson wrote: [Jerome Warnier] I don't know however how dpkg treats hardlinks. Does it break the hardlink before replacing a file or does it replace the file whatever its real nature is? You know, given the time it takes to type a 20-line email, including finding the appropriate Wikipedia article to link to, it would have been a lot faster to just try it. # ln /bin/ls /bin/ls2 # aptitude reinstall coreutils # ls -l /bin/ls /bin/ls2 Maybe, but I also wanted to bring attention to it. ;-) Interesting subject, isn't it? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: dpkg and hardlinks
Giacomo A. Catenazzi wrote: Jerome Warnier wrote: Raphael Hertzog wrote: On Tue, 24 Mar 2009, Jerome Warnier wrote: For files from packages, though, deduplication might be a good idea, as dpkg is supposedly the only one to ever modify the files (under /usr for example). I don't know however how dpkg treats hardlinks. Does it break the hardlink before replacing a file or does it replace the file whatever its real nature is? IIRC dpkg preserves hardlinks inside a binary package but I don't see how it could do the same across multiple binary packages. Oh, I didn't expect it to. I just wanted to know its behaviour when it upgrades a package. Before the upgrade, the file is a hardlink (because I hardlinked it manually), then it tries to upgrade the file/hardlink. Does it break the hardlink* before upgrading the file or does it overwrite the file/hardlink and all of its siblings? Do you really care? (not theoretically, but in normal use). I would expect that same content will be delivered: - by brother packages (same source), thus usually updated at the same time. - in documentation (so maybe not so important for your use). I think the most problem are in files outside dpkg control, i.e. /var and /etc. I'm just curious: do you have a list of same content files? maybe I'm completely wrong. Here you are, for /usr on a typical Lenny AMD64 server (generated with finddup -n from package perforate): http://glouglou.beeznest.org/~jwarnier/usr-duplicates.list.gz ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: dpkg and hardlinks
Steve McIntyre wrote: In article 49c8dcdb.90...@beeznest.net you write: Before the upgrade, the file is a hardlink (because I hardlinked it manually), then it tries to upgrade the file/hardlink. Does it break the hardlink* before upgrading the file or does it overwrite the file/hardlink and all of its siblings? * because it knows it is supposed to be a plain file, and it no longer is. Your language suggests that you don't understand how hard links work. A hard link to a file *is* a plain file. See http://en.wikipedia.org/wiki/Hard_link for some explanation. Of course I know what a hardlink is. I'm not native in English, and even tried to find the right words on the Net before writing, but I couldn't find better ones. The question here is: which one is the hardlink to the other? :-P -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: dpkg and hardlinks
Mike Hommey wrote:
On Tue, Mar 24, 2009 at 02:34:09PM +0100, Jerome Warnier
jwarn...@beeznest.net wrote:
Giacomo A. Catenazzi wrote:
Jerome Warnier wrote:
Raphael Hertzog wrote:
On Tue, 24 Mar 2009, Jerome Warnier wrote:
For files from packages, though, deduplication might be a good
idea, as
dpkg is supposedly the only one to ever modify the files (under
/usr for
example).
I don't know however how dpkg treats hardlinks. Does it break the
hardlink before replacing a file or does it replace the file whatever
its real nature is?
IIRC dpkg preserves hardlinks inside a binary package but I don't
see how
it could do the same across multiple binary packages.
Oh, I didn't expect it to. I just wanted to know its behaviour when it
upgrades a package.
Before the upgrade, the file is a hardlink (because I hardlinked it
manually), then it tries to upgrade the file/hardlink. Does it break
the hardlink* before upgrading the file or does it overwrite the
file/hardlink and all of its siblings?
Do you really care? (not theoretically, but in normal use).
I would expect that same content will be delivered:
- by brother packages (same source), thus usually updated
at the same time.
- in documentation (so maybe not so important for your use).
I think the most problem are in files outside dpkg control,
i.e. /var and /etc.
I'm just curious: do you have a list of same content files?
maybe I'm completely wrong.
Here you are, for /usr on a typical Lenny AMD64 server (generated with
finddup -n from package perforate):
http://glouglou.beeznest.org/~jwarnier/usr-duplicates.list.gz
$ zcat usr-duplicates.list.gz | awk '{t+=$1*(NF-2)}END{print t}'
33142129
You would free 33MB. How big is your disk ? Is it worth bothering ?
I'm not an awk god, but isn't that supposed to just be the total size of
the files it could take if deduplicated?
In this case, it is not the size I would reclaim, as there are sometimes
up to 4 copies of the same content.
You can get much more free space than that by reducing the number of inodes
supported by your filesystem:
For instance, on my / fs, that contains /usr, and is only 3GB:
Inode count: 384000
Free inodes: 314133
I will obviously never use that many inodes... Now, consider an inode
is 128 bytes (or even 256 in some cases), and do some maths...
Mike
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted and 1.2.2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 13 Aug 2007 20:45:27 +0200 Source: and Binary: and Architecture: source i386 Version: 1.2.2-2 Distribution: unstable Urgency: high Maintainer: Jerome Warnier [EMAIL PROTECTED] Changed-By: Jerome Warnier [EMAIL PROTECTED] Description: and- Auto Nice Daemon Closes: 436457 Changes: and (1.2.2-2) unstable; urgency=high . * Acknowledge NMU (thanks to Steinar H. Gunderson) * Disable unconditional stripping of binaries to allow use of DEB_BUILD_OPTIONS=nostrip (Closes: #436457) * Some cleanup to make lintian happier Files: 4396c96d84fe3878c7274a64f88c5951 549 misc extra and_1.2.2-2.dsc 3041a01d1e4f48070825fc27762c8193 5626 misc extra and_1.2.2-2.diff.gz 806b2c09d1ccd518cbc7b02fe0cf1226 25882 misc extra and_1.2.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGwMAppGK1HsL+5c0RAjImAKCPz9cDgsTF/aut292f42uj6u/I9gCfXJkl 0h4uSUlRkTQYolJ8vNwVLbw= =N7X8 -END PGP SIGNATURE- Accepted: and_1.2.2-2.diff.gz to pool/main/a/and/and_1.2.2-2.diff.gz and_1.2.2-2.dsc to pool/main/a/and/and_1.2.2-2.dsc and_1.2.2-2_i386.deb to pool/main/a/and/and_1.2.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted and 1.2.2-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 13 Oct 2005 19:11:27 +0200 Source: and Binary: and Architecture: source i386 Version: 1.2.2-1 Distribution: unstable Urgency: low Maintainer: Jerome Warnier [EMAIL PROTECTED] Changed-By: Jerome Warnier [EMAIL PROTECTED] Description: and- Auto Nice Daemon Closes: 310360 360713 363065 Changes: and (1.2.2-1) unstable; urgency=low . * New upstream release * Fix watch file (I hate how SourceForge does it!) * Fix typo in manpages (Closes: #310360) * Add highpriostart.c as example (Closes: #363065) * Fix initscript to stop it using erroneous pid file (Closes: #360713) * Fix manpages minus (-) not escaped. * Fixed the debian/copyright file. Many thanks to Guilherme de S. Pastore [EMAIL PROTECTED] for this and more. Files: ab346c2dce5ffebc28017fe5c98da3f3 549 misc extra and_1.2.2-1.dsc b939909039a8487eec93ff7eb56a4779 29989 misc extra and_1.2.2.orig.tar.gz 97d0833bb78d227e3fa3ada32c58fb26 5226 misc extra and_1.2.2-1.diff.gz 4d1edc8d9eea8922ff5602edec438b28 25564 misc extra and_1.2.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEZyfqGJU/LHOwJZIRAk6KAJsFRX0xvy7h/V48cg+JRBFPzevgtgCePDtZ 4bCzugWt/yGNV/ZtdHajUh4= =Y857 -END PGP SIGNATURE- Accepted: and_1.2.2-1.diff.gz to pool/main/a/and/and_1.2.2-1.diff.gz and_1.2.2-1.dsc to pool/main/a/and/and_1.2.2-1.dsc and_1.2.2-1_i386.deb to pool/main/a/and/and_1.2.2-1_i386.deb and_1.2.2.orig.tar.gz to pool/main/a/and/and_1.2.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#366900: ITP: asterisk-prompt-es-co -- Colombian Spanish voice prompts for the Asterisk PBX
Le jeudi 11 mai 2006 à 18:33 -0500, Santiago Ruano Rincón a écrit : Package: wnpp Severity: wishlist Owner: Santiago Ruano Rincón [EMAIL PROTECTED] * Package name: asterisk-prompt-es-co Version : 0.0.20060503 Upstream Author : Avatar Ltda. [EMAIL PROTECTED] * URL : http://www.avatar.com.co/ * License : GPL Description : Colombian Spanish voice prompts for the Asterisk PBX These are Colombian Spanish voice prompts for the Asterisk PBX, courtesy of Avatar Ltda., Colombia. . You need this package if you intend to run Asterisk and wish to support Spanish-speaking callers. You should probably join the pkg-voip-maintainers team instead of packaging it on your own. I put their mailing-list in copy of this mail. Hope it helps -- Jérôme Warnier FLOSS Consultant http://beeznest.net
Re: Emphasize teams, not packages
Le samedi 21 janvier 2006 à 10:17 +0100, Petter Reinholdtsen a écrit : [Jérôme Warnier] But why would you want to become a DD if you are not willing to maintain a package. Debian is just about maintaining packages. Debian needs more than just people maintaining packages. We need people working on translations, documentation, testing, web pages, system administration, press relations and probably some tasks I forgot. And we should accept people interested in working on these tasks as full members of the project. BTW, how could I apply for becoming DD with only doing sysadmin tasks? I'd do it immediately. That's my job, I'm pretty good at it, and I prefer that to packaging, while I'm able to package too (I already have a package of mine in Debian). I've found that in real life, packaging is the only way to *become* DD. I've already contributed a lot to Debian, for years now (back around 2000), and would like to become a DD, but the work needed just to reach the Holy Grail is simply too much when you are already working a lot (especially on Debian bugreporting and patching). So, how can I apply for DDship while doing the things I'm best at? -- Jérôme Warnier FLOSS Consultant http://beeznest.net
Bug#356670: ITP: goupil -- Association membership management tool for GNOME
Package: wnpp Severity: wishlist Owner: Jerome Warnier [EMAIL PROTECTED] * Package name: goupil Version : 0.0.2 Upstream Author : Dodji Seketeli [EMAIL PROTECTED] * URL : http://goupil.tuxfamily.org * License : GPL Description : Association membership management tool for GNOME Goupil is an association membership management tool for the GNOME environment. . It is a fully desktop-based application. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341894: ITP: pessulus -- lockdown editor for GNOME
Package: wnpp Severity: wishlist Owner: Jerome Warnier [EMAIL PROTECTED] * Package name: pessulus Version : 0.2 Upstream Author : Vincent Untz [EMAIL PROTECTED] * URL : http://www.gnome.org/~vuntz/pessulus/ * License : GPL Description : lockdown editor for GNOME pessulus is a lockdown editor for GNOME. . pessulus enables administrators to set mandatory settings in GConf. The users cannot change these settings. . Use of pessulus can be useful on computers that are open to use by everyone, e.g. in an Internet cafe. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: device nodes with udev?
Le lundi 07 novembre 2005 à 14:06 +0100, Marco d'Itri a écrit : On Nov 07, Gabor Gombas [EMAIL PROTECTED] wrote: Wrong. Nothing needs BSD ptys but some *very* old applications (I would not even know where to find one). At least /sbin/bootlogd does not work without BSD ptys and this is not Actually it does. documented anywhere. I needed some time to figure out why it complains about some completely bogus tty name not being available even if I specify the correct console at the kernel's command line. Because it's half broken. Maybe you could tell us how to do it, then, hmmm? :-) -- Jérôme Warnier FLOSS Consultant http://beeznest.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Work-needing packages report for Oct 14, 2005
Le vendredi 14 octobre 2005 à 00:26 -0600, [EMAIL PROTECTED] a écrit : [..] The following packages have been orphaned: and (#333683), orphaned today [..] I'm maintainer (but still not DD) of this package and, and the bugreport does not apply to it, still I do not want to orphan it at all. Do I need to do something or contact someone to confirm this? Regards -- Jérôme Warnier FLOSS Consultant http://beeznest.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Which CD is a package on?
I wonder if it is possible to find out on which CD of a stable release the package I look for is? I guess it is possible, as apt can do it. But is it available somewhere online? Thanks -- Jerome Warnier [EMAIL PROTECTED] BeezNest -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NFSv4 support absent from mount
Le vendredi 13 mai 2005 à 13:00 +0200, Steinar H. Gunderson a écrit : On Fri, May 13, 2005 at 12:52:14PM +0200, Jerome Warnier wrote: As #302420 says, NFSv4 is not supported by current mount (part of util-linux) in Sarge/Sid while support is present for the server part. It would be great to have it in Sarge, if still possible, or at least in Sid soon. Please see the bugreport (still unanswered now) for the patch. Note that as soon mount gets NFSv4 support, #294959 becomes RC. You should also perhaps merge the bug with #236435/#254775. Bugs #290873 and #239611 are also related directly. /* Steinar */ -- Jerome Warnier [EMAIL PROTECTED] BeezNest
NFSv4 support absent from mount
As #302420 says, NFSv4 is not supported by current mount (part of util-linux) in Sarge/Sid while support is present for the server part. It would be great to have it in Sarge, if still possible, or at least in Sid soon. Please see the bugreport (still unanswered now) for the patch. Thanks -- Jerome Warnier [EMAIL PROTECTED] BeezNest -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted and 1.2.1-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 25 Oct 2004 11:40:27 +0200 Source: and Binary: and Architecture: source i386 Version: 1.2.1-2 Distribution: unstable Urgency: low Maintainer: Jerome Warnier [EMAIL PROTECTED] Changed-By: Jerome Warnier [EMAIL PROTECTED] Description: and- Auto Nice Daemon Closes: 197010 272782 Changes: and (1.2.1-2) unstable; urgency=low . * Fix defaultnice in manpage (Closes: #272782). . and (1.2.1-1) unstable; urgency=low . * New upstream version (Closes: #197010). Files: 06c45b61c16b649c6832ed2e168bbd33 549 misc extra and_1.2.1-2.dsc 22c813aef3a6b2ab531906e0abc67c36 29284 misc extra and_1.2.1.orig.tar.gz d8ffe1cbe39da59114e06648facbbcc0 2669 misc extra and_1.2.1-2.diff.gz 6f99f562ed700551df6f23477385591a 23498 misc extra and_1.2.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCQKxXexmdExmX588RAmAEAJwIX2ODHpQZr7lYysHkpvv/kMmTigCgl6sX qCEyoHCfRaNmo3TNk5DPRGA= =tHK3 -END PGP SIGNATURE- Accepted: and_1.2.1-2.diff.gz to pool/main/a/and/and_1.2.1-2.diff.gz and_1.2.1-2.dsc to pool/main/a/and/and_1.2.1-2.dsc and_1.2.1-2_i386.deb to pool/main/a/and/and_1.2.1-2_i386.deb and_1.2.1.orig.tar.gz to pool/main/a/and/and_1.2.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Simultaneous loading of e100 and eepro100 by hotplug
On Wed, 2004-12-01 at 16:25 +0100, Christoph Hellwig wrote: On Wed, Dec 01, 2004 at 07:55:59PM +0900, Mike Hommey wrote: The problem is the following: is the e100 driver available in all kernel flavours/versions ? If yes, then it is safe to blacklist it in hotplug directly. If not, then it is not safe to do it in hotplug because it would blacklist eepro100 which would be the only working module on some flavours/versions. eepro100 is the older driver, but e100 has been available since early 2.4, so it's there in all debian kernels. e100 supports much more hardware than eepro100 (like the one on the mainboard of one of my boxens) and is actively maintained by Intel while eepro100 only gets odd fixes. Unfortunately there's some older hardware where eepro100 works and e100 doesn't, and debugging this is really hard because the hardware has gazillions of slightly incompatible variants. Worse: debian kernels 2.4.18 didn't have it yet, and a lot of Woody system probably still have this version. -- Jerome Warnier [EMAIL PROTECTED] BeezNest
Which 2.6 kernel for Sarge on a Via C3?
I'm wondering why I can't see many different 2.6 kernels on my Sarge systems any longer. I own a Via C3-based computer (an x86 for those who didn't know) and can find only -386 and -686 kernels which could possibly match. Somebody knows? Thanks -- Jerome Warnier [EMAIL PROTECTED] BeezNest
Re: Which 2.6 kernel for Sarge on a Via C3?
On Wed, 2004-11-10 at 23:49 +0100, Finn-Arne Johansen wrote: On Wed, Nov 10, 2004 at 07:33:43PM +0100, Jerome Warnier wrote: I'm wondering why I can't see many different 2.6 kernels on my Sarge systems any longer. I own a Via C3-based computer (an x86 for those who didn't know) and can find only -386 and -686 kernels which could possibly match. Somebody knows? I would go for a 386 kernel, If I remember correctly my via paniced when I tried the 686 kernel. Thanks, but honestly, I expected someone to say: hey, where are all those kernels gone? like me ;-) I'm already using -386, but Via C3 has MMX and other stuff like that which could probably be useful for maximum performance. -- Jerome Warnier [EMAIL PROTECTED] BeezNest
Re: NMU on sysklogd
On Fri, 2004-10-29 at 09:02 +0200, Petter Reinholdtsen wrote: [Jerome Warnier] So what? Am I stuck with my problem like so many people are already? And a friendly takeover of the package? I suspect you will discover and get stuck in the power games in Debian. I always found that funny, but I know the game. ;-) I already have to problem on at least 4 machines, with things as POP-before-SMTP and log analysers, packaged in Debian. I would recommend changing to another syslogd. There are several, and you could switch to one with a closer match to your needs. Well, I already tried others, but they have more dependencies or are more difficult to configure to do what I want. And sysklogd is in section base, so in my point of view, it should just _work_ out of the box. Moreover it is the default syslogd installed for now. In fact, I dug into the problem, and found that the initscript (/etc/cron.daily/sysklogd) had a 'reload-or-restart' argument, which is used by the cronjob and does not always work (in my case, on several machines, never) nor do the restart one (I'm not sure anymore I tried it, though). So, I replaced the last line: /etc/init.d/sysklogd reload-or-restart /dev/null with: kill -HUP `cat /var/run/syslogd.pid` /dev/null One more thing to say: because of this bug (#275111), the logs do not get rotated right, which can cause big trouble on heavily-loaded servers (or using Quagga, which generates a lot of messages because of failed communication with SNMP, but that's another story). -- Jerome Warnier [EMAIL PROTECTED] BeezNest s.a r.l.
Re: NMU on sysklogd
On Fri, 2004-10-29 at 13:28 +0200, Javier Fernández-Sanguino Peña wrote: On Fri, Oct 29, 2004 at 11:56:46AM +0200, Jerome Warnier wrote: In fact, I dug into the problem, and found that the initscript (/etc/cron.daily/sysklogd) had a 'reload-or-restart' argument, which is used by the cronjob and does not always work (in my case, on several machines, never) nor do the restart one (I'm not sure anymore I tried it, though). So, I replaced the last line: (...) I think it would be best if you sent this information to the BTS, as a patch for the current package. That way others (including the maintainer, which needs not be following this thread) can test it too. Well, the problem is that I'm not happy with that solution. In fact, the initscript should be fixed, which maybe involves bug #211858 (relates to --pidfile), which has already a non-applied patch. The fact is that both 'reload-or-restart' and 'restart' do not work as expected. Please provide as much information in order to reproduce this issue as possible too. It is very simple: install a Sarge, let it run and you'll see at some point that /var/log/syslog (this is not the only file affected of course) is empty and keeps empty and syslog.0 continues to be filled by the new messages. All my Sarge systems show the same behaviour. Those are the very first steps you should take before even considering a NMU. Also, in this particulary case, read the README.NMU file in the sources. I cannot do a NMU myself, so don't worry, I won't ;-) I've been reviewing these packages' bugs. Even if some patches could be introduced to fix some of the issues I'm not sure all of them are appropiate. Even so, this package is of base priority, so it's frozen in sarge, only RC bugs should be fixed there. Maybe a cleanup of the package I'm aware of that too. could be considered (following the NMU procedures above) and I'm open to doing it myself (as I've been doing it for other base packages). Well, thanks but it is not quite ready for that. I haven't yet contacted Joey, however, since I'm still considering this option and how to do it best. One option, for example, is to do a NMU to experimental so other people can test the package (and verify that the bugs are actuall fixed) before uploading to sid. I have done this for other base packages (like ifupdown). I suggest you think about it (and the consequences of a broken^Wuntested upload at this point) before talking with him. We'll see that in due time. I have lots of other things to do. Regards Javier -- Jerome Warnier [EMAIL PROTECTED] BeezNest s.a r.l.
Re: Bug#278027: RFP: ibm-acpi -- Driver for IBM laptops to extend ACPI support
On Tue, 2004-10-26 at 09:22 +0200, David Schweikert wrote: On Sun, Oct 24, 2004 at 13:07:34 +0100, Matthew Garrett wrote: * Package name: ibm-acpi This has been integrated into the acpi.sf.net patch, so is fairly likely to end up in the mainstream kernel before too long. Even if it gets integrated in the kernel (which I am not 100% sure about), having a package would make it work on older kernels. Also, an init script is needed to configure what events you are interested in and the package can provide example configuration files in /etc/acpi. Shouldn't it be integrated to package acpid then? Cheers David -- Jerome Warnier [EMAIL PROTECTED] BeezNest s.a r.l.
NMU on sysklogd
Hello guys, I'm having a problem with sysklogd on Sarge: everytime it rotates logs, it fails to log in the new file, it continues in the previous, renamed one. I introduced bug #275111 about that. It is really annoying since every log analysis tool is failing on this every week at least? By log analysis tool I mean anything relying on files in /var/log to do something. I notice that that package has a huge number of bugs, with many having a patch attached, but many bugs are really old. Could someone go through the list and NMU this? I'm willing to help, if necessary. Thanks -- Jerome Warnier [EMAIL PROTECTED] BeezNest s.a r.l.
Re: NMU on sysklogd
On Fri, 2004-10-29 at 00:46 +0200, Petter Reinholdtsen wrote: [Jerome Warnier] Could someone go through the list and NMU this? I'm willing to help, if necessary. The maintainer of sysklogd have a problematic relationship with NMUs. Have a look at bug #225895 for an ironic view on this. :) So what? Am I stuck with my problem like so many people are already? And a friendly takeover of the package? I already have to problem on at least 4 machines, with things as POP-before-SMTP and log analysers, packaged in Debian. -- Jerome Warnier [EMAIL PROTECTED] BeezNest s.a r.l.
Accepted and 1.2.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 19 Jul 2004 14:51:37 +0200 Source: and Binary: and Architecture: source i386 Version: 1.2.0-1 Distribution: unstable Urgency: low Maintainer: Jerome Warnier [EMAIL PROTECTED] Changed-By: Jerome Warnier [EMAIL PROTECTED] Description: and- Auto Nice Daemon Closes: 154147 230777 Changes: and (1.2.0-1) unstable; urgency=low . * New upstream version. * Added watch file. * New maintainer with permission from Andras . and (1.0.9-1) unstable; urgency=low . * New upstream version (Closes: #154147, #230777). Files: 255255897647e7f76b1c737c7573d970 549 misc extra and_1.2.0-1.dsc 6467a5d1301ad2bbcdd45db944789a67 29102 misc extra and_1.2.0.orig.tar.gz 3f39a9109516a019faaa7bdfc9035e05 2480 misc extra and_1.2.0-1.diff.gz 192b98901af73302d8cbc80521b58896 23272 misc extra and_1.2.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBGzw9exmdExmX588RAgGkAJ0ZXR8OG56bSl0B7sxmFgxH0qO1nACfWHNJ 6KYmlx4EFvz3wW45GMW4klE= =u4Bh -END PGP SIGNATURE- Accepted: and_1.2.0-1.diff.gz to pool/main/a/and/and_1.2.0-1.diff.gz and_1.2.0-1.dsc to pool/main/a/and/and_1.2.0-1.dsc and_1.2.0-1_i386.deb to pool/main/a/and/and_1.2.0-1_i386.deb and_1.2.0.orig.tar.gz to pool/main/a/and/and_1.2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
