Re: Rebuilding Debian Live gnome image fails
On 12-02-2021 03:12, John Crawley wrote:
On 09/02/2021 21:40, Matthijs wrote:
Following the Debian Live manual on using a predefined
configuration(https://live-team.pages.debian.net/live-manual/html/live-manual/managing-a-configuration.en.html#333):
$ mkdir live-images && cd live-images
$ lb config --config
https://salsa.debian.org/live-team/live-images.git::debian
$ cd images/standard
$ sudo lb build
...this works and I get an ISO image in that directory.
But, instead doing this:
$ mkdir live-images && cd live-images
$ lb config --config
https://salsa.debian.org/live-team/live-images.git::debian
$ cd images/gnome-desktop
$ sudo lb build
(note the change in the 'cd' command)
...this does NOT work. The build command starts doing a lot of work,
fetching & installing stuff, but then simply stops at this point
(copy/paste of ~17 lines of build.log):
It's not mentioned in those docs, but I'm pretty sure you'll need to
run 'lb config' one more time after moving to the config directory
(and possibly editing the files inside), before 'lb build'.
Interesting. I've tried it, but it doesn't make much of a difference -
stops at roughly the same point (well, I get two lines extra, but not
much information from that).
I did manage to trace the root cause back to lines 75/76 in
/usr/lib/live/build/chroot_package-lists:
Expand_packagelist "$(basename ${LIST})" "config/package-lists" \
| grep -v '^#' >> chroot/root/packages.chroot
It seems that at some point, with the config I'm using,
"Expand_packagelist" does not return anything and the script then simply
stops. When I replace it with:
My_list=$(Expand_packagelist "$(basename ${LIST})"
"config/package-lists")
echo ${My_list} | grep -v '^#' >> chroot/root/packages.chroot
...the build continues and delivers a bootable image. So, my issue seems
to be solved with that, or at least I have a workaround. Perhaps I'll
dive a bit further, because right now I don't fully understand why the
build would stop originally: I would expect, if "expand_packagelist"
doesn't return anything, that the following "grep" would hang
indefinitely.
Nevertheless, an additional "lb config" doesn't seem to be necessary, as
the modified chrot_package-list script works correctly with the original
procedure.
--
Matthijs
Rebuilding Debian Live gnome image fails
Hi all, I'm trying to build a custom Debian live USB image. To do so, I start trying to rebuild an original non-modified live image - specifically from "https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid";, the debian-live-10.8.0-amd64-gnome.iso image. Following the Debian Live manual on using a predefined configuration(https://live-team.pages.debian.net/live-manual/html/live-manual/managing-a-configuration.en.html#333): $ mkdir live-images && cd live-images $ lb config --config https://salsa.debian.org/live-team/live-images.git::debian $ cd images/standard $ sudo lb build ...this works and I get an ISO image in that directory. But, instead doing this: $ mkdir live-images && cd live-images $ lb config --config https://salsa.debian.org/live-team/live-images.git::debian $ cd images/gnome-desktop $ sudo lb build (note the change in the 'cd' command) ...this does NOT work. The build command starts doing a lot of work, fetching & installing stuff, but then simply stops at this point (copy/paste of ~17 lines of build.log): v The following NEW packages will be installed: dctrl-tools 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 104 kB of archives. After this operation, 413 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian stretch/main amd64 dctrl-tools amd64 2.24-2+b1 [104 kB] Fetched 104 kB in 0s (1481 kB/s) Selecting previously unselected package dctrl-tools. (Reading database ... 9125 files and directories currently installed.) Preparing to unpack .../dctrl-tools_2.24-2+b1_amd64.deb ... Unpacking dctrl-tools (2.24-2+b1) ... Setting up dctrl-tools (2.24-2+b1) ... P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree... Reading state information... ^^^ No further output, it just quits. Same for cinnamon-desktop, kde-desktop and lxde-desktop. Comparing build.log from gnome-desktop with standard doesn't give me a clue to why it stops. In case it is relevant: I'm building on a Debian Buster 10.8 AMD64 machine, without any desktop (headless machine with ssh access only). Anyone here with a suggestion how to make "lb build" work for a gnome-desktop Debian config? Thanks! Matthijs
Re: Wheezy->Jessie upgrade: udev (pre)install issue
On Wed, Jul 08, 2015 at 08:13:18AM +0200, Wessel Nieboer wrote: > Did you fix this issue you were having? My udev is not installing properly > but the kernel is OK for me. Hi Wessel, Looking back to refresh my memory: Yes, this issue was easily fixed by following the advice in the first reply that I got: just forcing the installation of the new kernel. Kind regards, Matthijs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150708165617.ga19...@vanaalten.net
Re: Re: Boots into emergency mode. How to analyze?
On 06/26/2015 01:55 PM, Nick T. wrote: On 06/26/2015 12:55 PM, to...@tuxteam.de wrote: well and good until you find yourself in the situation this very thread is about: your root filesystem is broken and you can only log in as root. Then you need your root password. Ubuntu and debian can boot into recovery mode from the grub menu, from there it asks for the root password IF there is one, if not it just gives you a root shell. - Nick Not the case. Even in rescue mode I needed to supply the root login. I could use init=/bin/sh but I couln't find anything in the logs in /var/log, so I'm guessing systemd and journalctl keeps the journal in some other place (probably some binary format hidden in a database or something). I'm now back to having a root password, which allows me to use emergency mode. I'm unsure if having a root password (and an enabled root account) is better or worse, security-wise. If an attacker has access to the grub menu, you're probably screwed anyhow. Matthijs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558d4fb7.7080...@gmail.com
Re: Boots into emergency mode. How to analyze?
Hey everybody, I'm mailing this from my own system! That means it worked! I still have a few lines in the boot journal I might want to fix but now I can do it from the comfort of a running linux system. Feels great! Regards, Matthijs On 06/26/2015 02:56 PM, Matthijs Wensveen wrote: Hi, First of all, thanks for all the helpful replies!! I've setup a root password by using chroot on a livecd and I'm now able to use that pw in emergency mode, like The Wanderer suggested. I didn't have a root password because my user account has generous sudo permissions. Never needed one before, but I'm not sure how this specific problem should be handled in my case. Anyway, meanwhile in emergency mode, I can run journalctl -xb to see the boot journal. I found a line saying I should fsck /dev/sdc5 manually, which is where my /home partition lives, so I'm guessing that's the problem. I'll try that first. Best regards, Matthijs On 26-6-2015 5:39, Dave Thayer wrote: On Thu, Jun 25, 2015 at 01:54:56PM +0200, Matthijs Wensveen wrote: Hi, I'm running unstable / sid. Yesterday, I suddenly started booting into emergency mode and I'm unsure why. I had a hang the day before, right after a apt-get dist-upgrade, so it might be either one of those, or something else altogether. I had a similar problem after a recent sid upgrade. Normal booting lead to emergency mode. I was able to get to a GUI by going into the "Advanced options for Debian GNU/Linux" grub sub-menu and selecting the sysvinit version of the kernel instead of the systemd default. I did have some very long pauses in the init sequence, but I finally got to a graphic login. It turns out the cause of the emergency mode was some cruft I had in my fstab file, specifically a line containing "none /proc/bus/usb usbfs devmode=0666 0 0". Commenting this out cured the emergency mode problem. I'm not sure why this was in there in the first place, but a google search suggests it was some sort of kludge to get an ancient version of virtualbox to behave. hth dt -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558d4da7.3050...@gmail.com
Re: Re: Boots into emergency mode. How to analyze?
Hi, First of all, thanks for all the helpful replies!! I've setup a root password by using chroot on a livecd and I'm now able to use that pw in emergency mode, like The Wanderer suggested. I didn't have a root password because my user account has generous sudo permissions. Never needed one before, but I'm not sure how this specific problem should be handled in my case. Anyway, meanwhile in emergency mode, I can run journalctl -xb to see the boot journal. I found a line saying I should fsck /dev/sdc5 manually, which is where my /home partition lives, so I'm guessing that's the problem. I'll try that first. Best regards, Matthijs On 26-6-2015 5:39, Dave Thayer wrote: On Thu, Jun 25, 2015 at 01:54:56PM +0200, Matthijs Wensveen wrote: Hi, I'm running unstable / sid. Yesterday, I suddenly started booting into emergency mode and I'm unsure why. I had a hang the day before, right after a apt-get dist-upgrade, so it might be either one of those, or something else altogether. I had a similar problem after a recent sid upgrade. Normal booting lead to emergency mode. I was able to get to a GUI by going into the "Advanced options for Debian GNU/Linux" grub sub-menu and selecting the sysvinit version of the kernel instead of the systemd default. I did have some very long pauses in the init sequence, but I finally got to a graphic login. It turns out the cause of the emergency mode was some cruft I had in my fstab file, specifically a line containing "none /proc/bus/usb usbfs devmode=0666 0 0". Commenting this out cured the emergency mode problem. I'm not sure why this was in there in the first place, but a google search suggests it was some sort of kludge to get an ancient version of virtualbox to behave. hth dt -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558d4c14.7010...@gmail.com
Boots into emergency mode. How to analyze?
Hi, I'm running unstable / sid. Yesterday, I suddenly started booting into emergency mode and I'm unsure why. I had a hang the day before, right after a apt-get dist-upgrade, so it might be either one of those, or something else altogether. Booting into emergency mode doesn't help me, as I can neither login without a root password, nor continue to default mode with Ctrl-D because that just throws me back into emergency mode. I'm rather stuck on how to analyze the situation. I can mount and even chroot into the '/' partition from a live CD (LMDE 2) and even run apt-get update && apt-get upgrade, but the boot problem persists. I can also boot with init=/bin/sh, but I don't know what to look for. Any ideas on what I should try? Any help is much appreciated. Regards, Matthijs Wensveen
Re: Re: Unable to install nVidia driver on Debian 6 LTS - was - Re: How to boot without GUI
On 11-6-2015 7:13, Bret Busby wrote: On 11/06/2015, Ric Moore wrote: On 06/10/2015 03:45 PM, Bret Busby wrote: On 11/06/2015, Nick T. wrote: Oops, forgot to cc in the mailing list. - Nick On 06/10/2015 09:19 PM, Nick T. wrote: Install build-essential it should contain all the packages necessary to install the driver. Also you might want to install dkms if you don't want to reinstall the driver after every kernel update. - Nick Thank you for that. The driver installation appears to have subsequently succeeded. However, after rebooting, the system still does not see the external monitor (using System -> Preferences -> Monitors), and I don't think that will work. Try using nvidia-settings. As I had said, xwindows now no longer works on the system. What do I need to do, at the command line level, to get xwindows operable on the system? In the circumstances, it appears to be a congiuration or settings issue. Or, despite the information on the nvidia web site, perhaps the driver simply does not work with Debian 6. I note that the gcc version issues showed that the gcc version applicable to the driver, appeared to be an earlier version (4.3, I think) than the installed version when I installed gcc (4.4, I think) (but the discrepancy appeared to have been overcome in the procedure that I followed), indicating (I believe) that Debian 6 should not be a version to early for thenvidia driver. It might be that you need to generate an Xorg.conf file from scratch. Make sure to backup any existing configuration file first (/etc/X11/xorg.conf). You can generate one using the nvidia-xconfig package: https://wiki.debian.org/NvidiaGraphicsDrivers#Configuration - Matthijs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557abfdb.20...@gmail.com
Re: Problem installing nvidia-drivers
On 05/30/2015 04:18 PM, Stefan Malte Schumacher wrote:
Hello
I am trying to install the proprietary Nvidia-Drivers on my Laptop. I
have read
https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_8_.22Jessie.22
and have entered the following command according to the description:
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkms
As a result I get the the output following this section. How should I proceed?
Unfortunately using Noveau is not an alternative since the current version has
a bug which causes my screen to flicker, making it practically unreadable.
Thanks in advance
Stefan
root@deimos:~# aptitude -r install linux-headers-$(uname -r|sed
's,[^-]*-[^-]*-,,') nvidia-kernel-dkms
Die folgenden NEUEN Pakete werden zusätzlich installiert:
libegl1-nvidia{a} libgl1-nvidia-glx{ab} libgles1-nvidia{a}
libgles2-nvidia{a} libnvidia-eglcore{a} libnvidia-ml1{a} nvidia-alternative{ab}
nvidia-driver{ab} nvidia-driver-bin{a} nvidia-kernel-dkms{b}
nvidia-vdpau-driver{ab} xserver-xorg-video-nvidia{ab}
0 Pakete aktualisiert, 12 zusätzlich installiert, 0 werden entfernt und 0 nicht
aktualisiert.
23,8 MB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden
133 MB zusätzlich belegt sein.
Die folgenden Pakete haben verletzte Abhängigkeiten:
nvidia-alternative : Hängt ab von: glx-alternative-nvidia (>= 0.5), welches
ein virtuelles Paket ist.
Hängt ab von: nvidia-modprobe, welches ein virtuelles
Paket ist.
nvidia-driver : Hängt ab von: nvidia-support, welches ein virtuelles Paket
ist.
Hängt ab von (vorher): nvidia-installer-cleanup, welches ein
virtuelles Paket ist.
xserver-xorg-video-nvidia : Hängt ab von: nvidia-support (>= 20120630),
welches ein virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
libgl1-nvidia-glx : Hängt ab von: nvidia-support, welches ein virtuelles
Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup, welches
ein virtuelles Paket ist.
nvidia-kernel-dkms : Hängt ab von: nvidia-kernel-common (>= 20110213),
welches ein virtuelles Paket ist.
Hängt ab von (vorher): nvidia-installer-cleanup, welches
ein virtuelles Paket ist.
nvidia-vdpau-driver : Hängt ab von (vorher): nvidia-installer-cleanup,
welches ein virtuelles Paket ist.
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Beibehalten der folgenden Pakete in ihrer aktuellen Version:
1) libegl1-nvidia [Nicht installiert]
2) libgl1-nvidia-glx [Nicht installiert]
3) libgles1-nvidia [Nicht installiert]
4) libgles2-nvidia [Nicht installiert]
5) libnvidia-ml1 [Nicht installiert]
6) nvidia-alternative [Nicht installiert]
7) nvidia-driver [Nicht installiert]
8) nvidia-driver-bin [Nicht installiert]
9) nvidia-kernel-dkms [Nicht installiert]
10) nvidia-vdpau-driver [Nicht installiert]
11) xserver-xorg-video-nvidia [Nicht installiert]
Die folgenden Abhängigkeiten unaufgelöst lassen:
12) nvidia-driver empfiehlt libgles1-nvidia (= 340.65-2)
13) nvidia-driver empfiehlt libgles2-nvidia (= 340.65-2)
14) nvidia-driver-bin empfiehlt nvidia-driver
15) nvidia-kernel-dkms empfiehlt nvidia-driver (>= 340.65) | libcuda1 (>=
340.65)
16) nvidia-vdpau-driver empfiehlt nvidia-kernel-dkms (= 340.65-2) |
nvidia-kernel-340.65
17) xserver-xorg-video-nvidia empfiehlt nvidia-driver (>= 340.65)
18) xserver-xorg-video-nvidia empfiehlt nvidia-vdpau-driver (>= 340.65)
19) xserver-xorg-video-nvidia empfiehlt nvidia-kernel-dkms (= 340.65-2) |
nvidia-kernel-340.65
Hi,
Some questions:
- Which release are you running? Jessie?
- Do you have contrib and non-free included in your apt sources? Maybe
paste the contents of /etc/apt/sources.list here.
- Do you have other (3rd party) apt sources, maybe in sources.list.d?
glx-alternative-nvidia being a virtual package, strikes me as odd.
Best regards,
Matthijs
Re: Wheezy->Jessie upgrade: udev (pre)install issue
On 27-12-2014 20:45, Andrei POPESCU wrote: On Sb, 27 dec 14, 15:27:38, deb...@vanaalten.net wrote: version 3.4.9. But: that was a version I've compiled & installed myself some time ago. Although I didn't make any significant changes to the features during compilation, so I would expect no warning messages about this. You might want to check again, I just compared your error message with /boot/config-3.2.0-4-amd64 on a Wheezy install and all are set. Kind regards, Andrei You're right. I've checked my backup machine and 3.2 had all required flags set - and my home build 3.4.9 had all but CONFIG_FHANDLE set. So the error message was indeed valid: my kernel & the new udev would not be compatible. In the end I've also replaced the kernel by the Jessie-version, so that possible issue is solved - but: would it perhaps be better if the wheezy-jessie upgrade process creates "/etc/udev/kernel-upgrade" by default to prevent upgrade issues? Or is stopping the upgrade for these exotic cases better? (in other words: is a bugreport needed or not?) Kind regards, Matthijs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/549f1624.5000...@vanaalten.net
Re: Wheezy->Jessie upgrade: udev (pre)install issue
On 27-12-2014 19:12, Patrick Bartek wrote: On Sat, 27 Dec 2014, Matthijs wrote: [snip] Basically I followed the normal recipe: change /etc/apt/sources.list to read 'jessie' instead of 'wheezy', then apt-get update, then apt-get dist-upgrade. That's how I've done it since 2003 or so, never any big issues. [snip] Just curious. Why are you upgrading to Jessie now while it's still Testing and has potential problems? Why not wait until it's the new Stable? If you just want to try it out, a dual boot or virtual machine scenario would be safer. A dual boot was what I did with Wheezy while it was still Testing (Beta 4 Installer) to see if it would fill my needs. It did. And when it went Stable, it became my primary OS. No real good reason. I have the time to upgrade now, and in the past I've always migrated whenever 'testing' felt as approaching stability. 160 bugs for the next release, which is already a lot less than the current release. And, usually, I can solve any issues myself (with some google-help). Other than that: having newer packages available. "sabnzbdplus" already showed some issues that are probably solved in a new release; I recently had an issue with darwin calendar server (didn't want to communicate anymore with Thunderbird/Lightning, after those got upgraded). Also I started using OwnCloud - and I feel better using all from the Debian repositories instead of opensuse.org repository. And dual-boot is not very convenient for an always-on personal headless server :-) Kind regards, Matthijs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/549efc9e.8000...@vanaalten.net
Re: Wheezy->Jessie upgrade: udev (pre)install issue
On 27-12-2014 14:47, Sven Joachim wrote: Sorry if it sounds blunt, but have you actually read the messages you pasted above? They should give you information what is missing from your running kernel, and they also give advice how to force the udev upgrade anyway. If your kernel does not have CONFIG_FHANDLE (the most likely problem, since that was introduced only in 2.6.39), you can probably force the upgrade, since udev does not seem to actually need that feature. Cheers, Sven Yes, read those, got scared into asking advice. "At your own risk", "there is always a safer way to upgrade" and "do not try unless you understand what you're doing" were stopping me from creating the kernel-upgrade file: I thought it better to ask people with more expertise before making a bigger mess. I know that Jessie isn't released yet, but I did expect a more-or-less troublefree migration - there seem to be dependencies between the kernel, udev and systemd so I would expect that the dist-upgrade process would take care of the right order and creation of the kernel-upgrade file. Manually forcing an installation against some strong warnings was not what I expected to do. Anyway - this indeed did the trick. Thanks! Kind regards, Matthijs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/549ec1e0.1090...@vanaalten.net
Wheezy->Jessie upgrade: udev (pre)install issue
Hi all, Apologies in advance: I'm not a frequent mailing list user, but I seem to have messed up my system upgrade and hope someone here can help out with advice. Basically I followed the normal recipe: change /etc/apt/sources.list to read 'jessie' instead of 'wheezy', then apt-get update, then apt-get dist-upgrade. That's how I've done it since 2003 or so, never any big issues. After some time during the upgrade process I get the following error and upgrade stops: Unpacking replacement systemd ... dpkg: considering deconfiguration of udev, which would be broken by installation of consolekit ... dpkg: yes, will deconfigure udev (broken by consolekit) Preparing to replace consolekit 0.4.5-3.1 (using .../consolekit_0.4.6-5_amd64.deb) ... De-configuring udev ... Unpacking replacement consolekit ... Replacing files in old package udev ... Preparing to replace udev 175-7.2 (using .../archives/udev_215-8_amd64.deb) ... Since release 198, udev requires support for the following features in the running kernel: - inotify(2)(CONFIG_INOTIFY_USER) - signalfd(2) (CONFIG_SIGNALFD) - accept4(2) - open_by_handle_at(2) (CONFIG_FHANDLE) - timerfd_create(2) (CONFIG_TIMERFD) - epoll_create(2) (CONFIG_EPOLL) Please upgrade your kernel before or while upgrading udev. AT YOUR OWN RISK, you can force the installation of this version of udev WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file. There is always a safer way to upgrade, do not try this unless you understand what you are doing! dpkg: error processing /var/cache/apt/archives/udev_215-8_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/udev_215-8_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) The problem seems to be with unpacking the udev package. Googling a bit suggests to add "set -x" to the preinst script (/var/lib/dpkg/info/udev.preinst is the only one I could find, though I'm not entirely sure that's the right one) and then retry with "dpkg --configure --pending". But doesn't work: dpkg: dependency problems prevent configuration of systemd: systemd depends on udev (>= 208-8); however: Version of udev on system is 175-7.2. dpkg: error processing package systemd (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libpam-systemd:amd64: libpam-systemd:amd64 depends on systemd (= 215-8); however: Package systemd is not configured yet. dpkg: error processing package libpam-systemd:amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: systemd libpam-systemd:amd64 I've also tried "apt-get -f install" to get it to fix itself. This then upgraded several other unrelated/innocent packages, but always at some point stopped and failed at udev. Any suggestions? Kind regards, Matthijs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/549ea7ca.9090...@vanaalten.net
Etch: aide gives "onexit unknown error"
(apologies if this turns out to be a HTML-message - I haven't found an option to switch to plain text in windows live mail)Hello,I've recently installed Etch on my server, including package 'aide'.The daily cron job gives the following error:/etc/cron.daily/aide: line 117: onexit: command not found/etc/cron.daily/aide: line 61: onexit: command not foundrun-parts: /etc/cron.daily/aide exited with return code 127My scripting capabilities are limited, but according to/etc/cron.daily/aide, function 'onexit' is defined on line 135.Am I doing something wrong or should I report this as a bug to theaide maintainers?Thanks,-- Matthijs _ Windows Live Spaces is here! It’s easy to create your own personal Web site. http://spaces.live.com/signup.aspx
Re: [OT] Lotus Quoting (Was Re: Odp: Re: how to modify context ("right-click") menus in KDE ?)
On Fri, 25 Aug 2006 11:30:12 +0200, "Mumia W." <[EMAIL PROTECTED]> wrote: > On 08/25/2006 02:41 AM, Zbigniew Wiech wrote: > > User-Agent: Lotus Notes Release 6.5.1 January 21, 2004 > > I don't want to be overly critical, but the "quoting" style of > Lotus Notes leaves much to be desired. It is possible to get > the application to quote like a normal mail-reader? > > Also, as a courtesy to me and others, please don't top post. I'm force to use Lotus Notes at work and can tell from my experience that it's the lousiest mailclient available on the market. In my experience, it is almost impossible to get decent quoting in a reply. Also, top posting is about the best you can get. The only way you could get a decent quoted & bottom-posted reply is by manually going through the entire message, editing and placing quote characters in front of every line. Whenever I see a poorly quoted, top posted message from someone who has to use Lotus Notes, I feel pity, not anger. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
glibc & TwonkyMusic - which version to install?
I'm trying to install a beta version of TwonkyMusic on my server (Debian Sarge/Stable, Via M1 x86 motherboard). I know that I have to install at least the x86 version, but I have the choice between the glibc 2.2.5 or 2.3.3 version. A bit of googling suggests that Sarge uses a version in between (2.3.2?). Which version of TwonkyVision should I therefore install, glibc-2.2.5 or glibc-2.3.3? Thanks, -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ripping CD with SACD format seems impossible
On Sun, 21 May 2006 19:10:10 +0200, Adam Hardy <[EMAIL PROTECTED]> wrote: > Matthijs on 21/05/06 17:18, wrote: > > On Sun, 21 May 2006 18:10:11 +0200, Adam Hardy > > <[EMAIL PROTECTED]> wrote: > > > >> Cdparanoia rejects one of my CDs. I am pretty sure that it's due to the > >> SACD format of the CD. I get this error: > >> > > If it is a hybrid disc, it is dual-layer: it contains CD-layer and a > > DVD-like layer which contains the SACD information. I think CDparanoia > > might be confused by the second layer. > > > > Are you trying this with a CD-rom or DVD-rom drive? > > it's a dual-layer cd. Should have said, sorry. I'm playing it on a CD-ROM, no > DVD functionality. In that case the drive can't even see the SACD-layer, only the CD layer. If you *are* able to play the disc on an ordinary CD-player, my guess would be that the CD-layer is copy-protected by manipulating the Table-Of-Content. I have no idea how to solve that on a Linux-machine sorry. (Windows: Exact Audio Copy can rip that disc) -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ripping CD with SACD format seems impossible
On Sun, 21 May 2006 18:10:11 +0200, Adam Hardy <[EMAIL PROTECTED]> wrote: > Cdparanoia rejects one of my CDs. I am pretty sure that it's due to the SACD > format of the CD. I get this error: > > >>>>>>>>>> > cdparanoia III release 9.8 (March 23, 2001) > (C) 2001 Monty <[EMAIL PROTECTED]> and Xiphophorus > FreeBSD porting (c) 2003 > Simon 'corecode' Schubert <[EMAIL PROTECTED]> > > Report bugs to [EMAIL PROTECTED] > http://www.xiph.org/paranoia/ > > 004: Unable to read table of contents header > > Unable to open disc. Is there an audio CD in the drive? > <<<<<<<<<< Is it a hybrid disc or a pure SACD-only disc? Have you tried playing it in a normal stand-alone CD- or DVD-player, something *not* capable of playing SACD? If it is a pure SACD-only disc: give up. Your CD- or DVD-rom player is not capable of reading it and AFAIK no PC optical reader is. If it is a hybrid disc, it is dual-layer: it contains CD-layer and a DVD-like layer which contains the SACD information. I think CDparanoia might be confused by the second layer. Are you trying this with a CD-rom or DVD-rom drive? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: iptables at boot
On Sun, 02 Apr 2006 03:30:15 +0200, BTP <[EMAIL PROTECTED]> wrote: > I was wondering if someone would be able to give me the correct way of > disabling all network activity (iptables commands/script) during the > boot process so that my network is inoperable during bootup until I > activate it manually. > > I'm unsure in which startup script I would place this on debian. I'm not sure either (so someone with knowledge please comment!), but I've placed it in /etc/network/interfaces: --- # The loopback interface auto lo iface lo inet loopback # The first network card auto eth0 iface eth0 inet static pre-up /etc/iptables.scr address 192.168.1.3 netmask 255.255.255.0 gateway 192.168.1.1 broadcast 192.168.1.255 --- This way, I expect the iptables script to be run just before the network is activated. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Script challenge
On Sat, 14 Jan 2006 11:40:13 +0100, John Smith <[EMAIL PROTECTED]>
wrote:
> which heroe can tell me why the following does not work :
>
> #!/bin/sh
> cat <newscriptfile.sh
> #!/bin/sh
> NOWS=$(date +%S)
> NOWS=${NOWS#0}
> NOWM=$(date +%M)
> NOWM=${NOWM#0}
> NOWH=$(date +%H)
> NOWH=${NOWH#0}
> FROMNOW=$1
>
> MINUTE=$((${NOWM} + ${FROMNOW}))
> MINUTE=$((${MINUTE} % 60))
> HOUR=$((${NOWM} + ${FROMNOW}))
> HOUR=$((${HOUR} / 60))
> HOUR=$((${NOWH} + ${HOUR}))
> HOUR=$((${HOUR} % 24))
> echo $HOUR" "$MINUTE
> EOF
Exactly *what* doesn't work? If I execute is at 12:25 as follows:
> ./newscriptfile.sh 1
12 26
... seems correct to me. What error do you get?
--
Matthijs
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Compatable UPS?
On Mon, 19 Sep 2005 17:40:42 +0200, Jared Hall <[EMAIL PROTECTED]> wrote: > My backup network will only use a laptop and a desktop, and shouldn't > ever suck more than 300 watts. I'm looking for a cheap UPS with a usb > connection that is compatable with Debian. > > I guess all I really need is a link to a good website. Google has not > been very helpful. All I get is advertisment after advertisment, when > all I really want is to know how to find a Debian compatable UPS. > > Maybe let me know what you all are using. Please help me navigate the > sea of UPS. There's another discussion active here, more or less same subject - might be interesting for you. My own server (which uses only about 35Watt) has an APC Back-UPS CS-500 UPS, connected via USB. Debian compatible by using the apcupsd package. I get about 45 minutes of runtime before automatic shutdown. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: UPS recommendations?
On Sat, 17 Sep 2005 14:40:06 +0200, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: > I would like a UPS that warns me when power starts fluctuating and then > shuts down the system. Debian of course, Sarge now. > > Are there any recommendations out there? I've got an APC Back-UPS CS500. It's connected by USB and protects (and supplies) power to my mailserver, ADSL-modem & router. It's battery is good enough to keep the system running for at least 45 minutes (it's a real nice low-power system), then the system shuts down automatically (and boots up again when power is restored). Software used: apcupsd running on Debian Sarge. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mule client
On Sun, 21 Aug 2005 13:30:15 +0200, Arash Bijanzadeh <[EMAIL PROTECTED]> wrote: > Hi, I need a mule client for my Debian site, anybosy knows any thing? I'm using mldonkey, installed on my server and accessed through a webinterface or via telnet. Package mldonkey is available in unstable (not in stable, unfortunately) -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Migration to new HD: "unable to open an initial console"
On Wed, 20 Jul 2005 23:50:07 +0200, Marty <[EMAIL PROTECTED]> wrote: > Matthijs wrote: > > > I've followed the Debian harddisk-upgrade HowTo, changed fstab > > according to the above, installed grub on the new harddisk according > > to a posting here by Mitchell Laks (thanks for that!). > > > > Then I switched the machine off, removed the old harddisk, switched > > the new harddisk from slave to master and turned the machine on. > > > > Grub executed OK, there's a lot of info scrolling over the screen. At > > some point there's a message, something like 'mounting /dev/hda1 > > read-only' (don't know exactly since it isn't logged anywhere) > > > > The next message is where it ends: 'unable to open an initial > > console'. > > The problem seems to be that some console device is required before > any udev devices are created. > > I've solved this by copying all the devices from a live filesystem > onto /dev of the cloned drive, but you probably only need xconsole > or something similar. I thought about this after posting my original message and checked. Ouch! No /dev/console! OK, I thought I *did* copy everything from the original filesystem: > cp -ax / /new-disk ... and even checked when I ran into trouble whether /dev/console existed: > /ls -l /dev/console ... but I should have checked with > ls -l /new-disk/dev/console The directory /dev (and also /sys) are completely empty. Stupid me! I just copied everything in /dev and /sys again, booting the new filesystem right now... YES! Much better now! Thanks for the help! -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Migration to new HD: "unable to open an initial console"
On Wed, 20 Jul 2005 23:40:08 +0200, michael <[EMAIL PROTECTED]> wrote: > On Wed, 2005-07-20 at 22:53 +0200, Matthijs wrote: > > I'm in the process of migrating my server to a new harddisk - from a > > 3.5inch IDE to a new 2.5inch notebook IDE to save power & less noise. > > > > I thought I should take the opportunity to set up the system to use > > several partitions instead of one big partition. The new partition > > scheme should be as suggested by the 'hardening debian' HowTo. > > > > Old partitionscheme: > > > > /dev/hda1 / about 79GB (bootable) > > /dev/hda5 swap0.5GB > > > > New partitionscheme: > > /dev/hda1 / 5GB (bootable) > > /dev/hda2 swap0.5GB > > /dev/hda5 /tmp1GB > > /dev/hda6 /var1GB > > /dev/hda7 /var/mail 5GB > > /dev/hda8 /home about 67GB > > > > I've followed the Debian harddisk-upgrade HowTo, changed fstab > > according to the above, installed grub on the new harddisk according > > to a posting here by Mitchell Laks (thanks for that!). > > > > Then I switched the machine off, removed the old harddisk, switched > > the new harddisk from slave to master and turned the machine on. > > > > Grub executed OK, there's a lot of info scrolling over the screen. At > > some point there's a message, something like 'mounting /dev/hda1 > > read-only' (don't know exactly since it isn't logged anywhere) > > > > The next message is where it ends: 'unable to open an initial > > console'. > > > > I'm sure I followed the Howto's to the letter and Google doesn't give > > me any answers to this problem. > > > > I think the problem is that '/' is mounted read-only at first so that > > the rest (/tmp, /var, /home) can't be mounted anymore, but I'm not > > sure about that - what would that have to do with opening a console? > > And why didn't that give me problems with my 'old' harddisk? > > > > Relevant content of /boot/grub/menu.lst: > > title Debian GNU/Linux, kernel 2.6.8 > > root(hd0,0) > > kernel /boot/vmlinuz-2.6.8 root=/dev/hda1 ro vga=791 > > savedefault > > boot > > > > Would removing 'ro' in the kernel option line be a possible solution? > > > > Relevant content of /etc/fstab: > > proc/proc proc defaults0 0 > > /dev/hda1 / ext3 defaults,errors=remount-ro 0 1 > > /dev/hda2 noneswap sw 0 0 > > /dev/hda5 /tmpext3 defaults0 2 > > /dev/hda6 /varext3 defaults0 2 > > /dev/hda7 /var/mail ext3 defaults0 2 > > /dev/hda8 /home ext3 defaults0 2 > > > > Nothing wrong here, I think. > > This rings a tinsy winsy bell... but I think for me it was to do with > booting not finding my HD (since I have a SATA and moved from 2.4 (hde) > to 2.6 (sda))... Mmmm... not the case here, I think. I'm copying the original system, so same kernel (2.6.8-16, custom compiled). Also, the original HD was 'hda', the new HD is 'hdb' during installation but 'hda' when done. Also, at the beginning of the boot-process, I see a message that the harddisk including all partitions were found. -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Migration to new HD: "unable to open an initial console"
I'm in the process of migrating my server to a new harddisk - from a 3.5inch IDE to a new 2.5inch notebook IDE to save power & less noise. I thought I should take the opportunity to set up the system to use several partitions instead of one big partition. The new partition scheme should be as suggested by the 'hardening debian' HowTo. Old partitionscheme: /dev/hda1 / about 79GB (bootable) /dev/hda5 swap0.5GB New partitionscheme: /dev/hda1 / 5GB (bootable) /dev/hda2 swap0.5GB /dev/hda5 /tmp1GB /dev/hda6 /var1GB /dev/hda7 /var/mail 5GB /dev/hda8 /home about 67GB I've followed the Debian harddisk-upgrade HowTo, changed fstab according to the above, installed grub on the new harddisk according to a posting here by Mitchell Laks (thanks for that!). Then I switched the machine off, removed the old harddisk, switched the new harddisk from slave to master and turned the machine on. Grub executed OK, there's a lot of info scrolling over the screen. At some point there's a message, something like 'mounting /dev/hda1 read-only' (don't know exactly since it isn't logged anywhere) The next message is where it ends: 'unable to open an initial console'. I'm sure I followed the Howto's to the letter and Google doesn't give me any answers to this problem. I think the problem is that '/' is mounted read-only at first so that the rest (/tmp, /var, /home) can't be mounted anymore, but I'm not sure about that - what would that have to do with opening a console? And why didn't that give me problems with my 'old' harddisk? Relevant content of /boot/grub/menu.lst: title Debian GNU/Linux, kernel 2.6.8 root(hd0,0) kernel /boot/vmlinuz-2.6.8 root=/dev/hda1 ro vga=791 savedefault boot Would removing 'ro' in the kernel option line be a possible solution? Relevant content of /etc/fstab: proc/proc proc defaults0 0 /dev/hda1 / ext3 defaults,errors=remount-ro 0 1 /dev/hda2 noneswap sw 0 0 /dev/hda5 /tmpext3 defaults0 2 /dev/hda6 /varext3 defaults0 2 /dev/hda7 /var/mail ext3 defaults0 2 /dev/hda8 /home ext3 defaults0 2 Nothing wrong here, I think. Any suggestions? Thanks in advance! -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: VIA Epia M10000 & VT1211 hardware sensors
On Sun, 10 Jul 2005 16:30:12 +0200, James Vahn <[EMAIL PROTECTED]> wrote: > Matthijs wrote: > >> I'm trying to get the temperature sensors working on my Debian Sarge > >> box. The hardware is a VIA Epia M1 board running a custom compiled > >> 2.6.8-16 kernel. > > > > No suggestions, anyone? > > Two alternatives: mbmon and xmbmon > > ~# mbmon -Sf > > Temp.= 91.4, 98.6, 0.0; Rot.= 3169, 1442,0 > Vcore = 1.78, 2.56; Volt. = 3.26, 4.97, 12.10, -1.90, -1.30 > > For some reason if I don't use -S the message "Something Wrong in > detected VIA686 HWM!!" appears. Linux 2.6.11.10 Hmmm... thanks for the suggestion, but this didn't work for me. It probably still needs drivers to the hardware which I haven't selected in modconf. But looking into my original problem, I finally solved it! Short explanation: 'user stupidity'... I applied the vt1211 patch, but had to edit it a little bit to make it a perfect patch for kernel 2.6.8-16 ( I like a patch that works without fuzzyness). While editing it, I accidently removed the last two lines of vt1211.c which had something to do with initializing the driver... Of course, during compilation, I didn't notice the two resulting warnings between all other compile messages. Lesson learned: always pay attention during kernel compilation. Anyway, it works, 'sensors' now reports the CPU temperature. Good thing because I'm going to migrate the system to a fanless case very soon... -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: VIA Epia M10000 & VT1211 hardware sensors
On Sat, 09 Jul 2005 01:00:18 +0200, Matthijs <[EMAIL PROTECTED]> wrote: > I'm trying to get the temperature sensors working on my Debian Sarge > box. The hardware is a VIA Epia M1 board running a custom compiled > 2.6.8-16 kernel. > > As far as I know, the device driver for the VT1211 chip is not > included in the 2.6.8 kernel, so I followed the instructions on > http://hem.bredband.net/ekmlar/vt1211.html (including adding the two > lines for Debian 2.6.8 kernels). > > Everything, compiling and installing, went correctly - no strange > error messages or anything. > > I've used modconf to configure the modules to be loaded and included > i2c-isa and vt1211. According to the above mentioned webpage, there > should be a directory 0-6000 under /sys/devices/platform/i2c-0, but > unfortunately: > ls -l /sys/devices/platform/i2c-0 > total 0 > -rw-r--r-- 1 root root 4096 Jul 9 00:05 detach_state > -r--r--r-- 1 root root 4096 Jul 9 00:05 name > drwxr-xr-x 2 root root0 Jul 9 00:05 power > > report from lsmod: > Module Size Used by > vt1211 23108 0 > i2c_sensor 2880 1 vt1211 > via_agp 9056 1 > agpgart34600 1 via_agp > eth139421576 0 > via_rhine 22120 0 > mii 5024 1 via_rhine > ohci1394 35492 0 > ieee1394 111256 2 eth1394,ohci1394 > i2c_isa 1984 0 > i2c_core 24176 3 vt1211,i2c_sensor,i2c_isa > snd_pcm_oss55080 0 > snd_mixer_oss 20096 1 snd_pcm_oss > snd_via82xx28644 0 > snd_ac97_codec 69988 1 snd_via82xx > snd_pcm98728 2 snd_pcm_oss,snd_via82xx > snd_timer 25732 1 snd_pcm > snd_page_alloc 11752 2 snd_via82xx,snd_pcm > snd_mpu401_uart 7968 1 snd_via82xx > snd_rawmidi25124 1 snd_mpu401_uart > snd_seq_device 8200 1 snd_rawmidi > snd56388 9 snd_pcm_oss,snd_mixer_oss,snd_via82xx, > > snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart, > snd_rawmidi,snd_seq_device > ipchains 57152 0 > longhaul8080 0 > ide_cd 42336 0 > cdrom 40700 1 ide_cd > > > So it looks like both modules vt1211 and i2c_isa are loaded (although > i2c_isa doesn't appear to be used), but the directory 0-6000 (supposed > hardware address of i2c) isn't created. > > I've also tried sensors-detect. Final report: > Driver `eeprom' (should be inserted): > Detects correctly: > * Bus `SMBus Via Pro adapter at 0500' > Busdriver `i2c-viapro', I2C address 0x50 > Chip `SPD EEPROM' (confidence: 8) > > Driver `vt1211' (should be inserted): > Detects correctly: > * ISA bus address 0x6000 (Busdriver `i2c-isa') > Chip `VT1211 Super IO Sensors' (confidence: 9) > > Any suggestions what I'm doing wrong here? No suggestions, anyone? -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with apcupsd and kernel 2.6
On Sat, 09 Jul 2005 01:40:09 +0200, Martin Fuzzey <[EMAIL PROTECTED]> wrote: > I have recently upgraded my system from kernel 2.4 to 2.6.8 (with sarge). > > I have a APC Cyberfort 500 USB UPS managed with apcupsd. > > Initially I had no communication at all with the UPS. Installing the > hotplug package fixes this _however_ apcupsd still does not start > correctly at boot since it is started at level S12 wheras hotplug is S40. > > All works after a manual start. > > Is this a bug? (and if so in apcupsd or hotplug?) > Should I change the start up levels so that apcupsd comes after hotplug? > > Any other ideas? I'm afraid I can't help you much. I've got Debian Sarge, kernel 2.6.8, an APC back-ups 350 and no problems at all. As for the hotplug package: it's installed on my system: ~# dpkg -l | grep hotplug ii hotplug0.0.20040329-2 Linux Hotplug Scripts ... but I can't find it in the list of startup-scripts. My default runlevel is 2 (line in inittab: 'id:2:initdefault:'). Looking in /etc/rcS.d: ... lrwxrwxrwx 1 root root 17 Jul 12 2004 S40hotplug -> ../init.d/hotplug lrwxrwxrwx 1 root root 21 Apr 4 08:06 S41hotplug-net -> ../init.d/hotplug-net ... Looking in /etc/rc2.d: ... lrwxrwxrwx 1 root root 17 Feb 24 23:27 S13apcupsd ->../init.d/apcupsd ... Maybe I'm mistaken here (there's s much of Linux I still don't understand), but isn't the bootsequence for a default runlevel 2: - first run everything in numerical order in /etc/rcS.d - then run everything in numerical order in /etc/rc2.d ... because, in that case, S40hotplug in rcS.d would be run before S13apcupsd in rc2.d Hope this helps, -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
VIA Epia M10000 & VT1211 hardware sensors
I'm trying to get the temperature sensors working on my Debian Sarge box. The hardware is a VIA Epia M1 board running a custom compiled 2.6.8-16 kernel. As far as I know, the device driver for the VT1211 chip is not included in the 2.6.8 kernel, so I followed the instructions on http://hem.bredband.net/ekmlar/vt1211.html (including adding the two lines for Debian 2.6.8 kernels). Everything, compiling and installing, went correctly - no strange error messages or anything. I've used modconf to configure the modules to be loaded and included i2c-isa and vt1211. According to the above mentioned webpage, there should be a directory 0-6000 under /sys/devices/platform/i2c-0, but unfortunately: ls -l /sys/devices/platform/i2c-0 total 0 -rw-r--r-- 1 root root 4096 Jul 9 00:05 detach_state -r--r--r-- 1 root root 4096 Jul 9 00:05 name drwxr-xr-x 2 root root0 Jul 9 00:05 power report from lsmod: Module Size Used by vt1211 23108 0 i2c_sensor 2880 1 vt1211 via_agp 9056 1 agpgart34600 1 via_agp eth139421576 0 via_rhine 22120 0 mii 5024 1 via_rhine ohci1394 35492 0 ieee1394 111256 2 eth1394,ohci1394 i2c_isa 1984 0 i2c_core 24176 3 vt1211,i2c_sensor,i2c_isa snd_pcm_oss55080 0 snd_mixer_oss 20096 1 snd_pcm_oss snd_via82xx28644 0 snd_ac97_codec 69988 1 snd_via82xx snd_pcm98728 2 snd_pcm_oss,snd_via82xx snd_timer 25732 1 snd_pcm snd_page_alloc 11752 2 snd_via82xx,snd_pcm snd_mpu401_uart 7968 1 snd_via82xx snd_rawmidi25124 1 snd_mpu401_uart snd_seq_device 8200 1 snd_rawmidi snd56388 9 snd_pcm_oss,snd_mixer_oss,snd_via82xx, snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart, snd_rawmidi,snd_seq_device ipchains 57152 0 longhaul8080 0 ide_cd 42336 0 cdrom 40700 1 ide_cd So it looks like both modules vt1211 and i2c_isa are loaded (although i2c_isa doesn't appear to be used), but the directory 0-6000 (supposed hardware address of i2c) isn't created. I've also tried sensors-detect. Final report: Driver `eeprom' (should be inserted): Detects correctly: * Bus `SMBus Via Pro adapter at 0500' Busdriver `i2c-viapro', I2C address 0x50 Chip `SPD EEPROM' (confidence: 8) Driver `vt1211' (should be inserted): Detects correctly: * ISA bus address 0x6000 (Busdriver `i2c-isa') Chip `VT1211 Super IO Sensors' (confidence: 9) Any suggestions what I'm doing wrong here? -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.11 kernel in sarge?
On Fri, 08 Jul 2005 22:30:12 +0200, Bill Thompson <[EMAIL PROTECTED]> wrote: > On Fri, 8 Jul 2005 19:20:17 +0100 > Dave Ewart <[EMAIL PROTECTED]> wrote: > > > On Friday, 08.07.2005 at 20:09 +0200, Mikael Backman wrote: > > > > > Is there a way for me to download the debian 2.6.11 kernel and use it > > > in sarge? > > > > Yes, but it's not technically part of Sarge. Easiest way to do this is > > to add 'unstable' to your sources.list, download the latest Sid kernel, > > install it and make sure it's working, then remove 'unstable' from your > > sources.list. > > Please, Please, DO NOT do this! It may work now since stable and > unstable are not too far apart, but it could lead to disaster later > down the road. > > I STRONGLY encourage you to learn how to use the Debian kernel tools like > "make-kpkg" to compile custom kernels from the Debian or kernel.org > sources. I found the following on a Google search, but there are plenty of > other guides around: > http://newbiedoc.sourceforge.net/system/kernel-pkg.html In the APT-HowTo, I found a section on 'keeping a mixed system': http://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html#s-default-version Would that be a good & nice solution instead of compiling the kernel yourself? -- Matthijs (...currently compiling a kernel...) [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Once Sarge becomes stable...
On Mon, 06 Jun 2005 02:40:11 +0200, Steve Block <[EMAIL PROTECTED]> wrote: > On Sun, Jun 05, 2005 at 06:22:38PM -0400, Rick Friedman wrote: > >For me, also being rather new to Debian, this raises another question. > >Currently, I am running an "unstable" machine (I have unstable in > >sources.list). I will probably keep that. I'm just curious: If someone > >has "sid" in sources.list, does sid become the new testing? If so, what > >will be the distro name of unstable? > > Sid will still be unstable. The release name of the next testing > version will be etch. How long will Etch be in testing? I guess that somewhere, someone will decide to freeze Etch, then again a period with only bugfixing and finally releasing Etch as a new stable. When, and for what reasons, will Etch become frozen? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lynx doesn't dump to stdout?
On Sat, 16 Oct 2004 12:00:16 +0200, "Roozemond, D.A." <[EMAIL PROTECTED]> wrote: > > Example: > > lynx -dump > > http://www.ticketmaster.nl/html/searchResult.htmI?keyword=carlton&l=NL > > | grep resultaten > > > > There is a rather annoying thing happening here. Remember that commands > in bash ending with an ampersand sign & are executed in the background > (i.e. the command is executed and you get your prompt back rather than > having to wait). Ar! I get it now... > This is what's happening here. If you look carefully to the output, you > might notice there is something like '[1] 4822' at the beginning of the > suspected output, this means your job (lynx) is ran in the background > with PID 4822. Tried it again and you're right, I get a PID before the output... > No need to understand all the above - If you change the '&' in the > webpage address to '\&', it's working: And it is. I completely understand the above, I just didn't look into that direction. Thanks, great help! -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Lynx doesn't dump to stdout?
I'm trying to do some automation using lynx to get some websites for automated analysis. The problem is that it dumps the results to the terminal directly, a redirect doesn't work. Example: lynx -dump http://www.ticketmaster.nl/html/searchResult.htmI?keyword=carlton&l=NL | grep resultaten (line wrapped due to message width!) I would expect just a few lines containing the word 'resultaten', but I get the full webpage in my terminal. It's not really consistent: lynx -dump http://www.nl.debian.org | grep -i 'latest stable release' That command lists only one line on the output. I'm not sure if this is a bug in Lynx (although the browser links behaves similar) or if my terminal type (vt100 over a ssh connection) has something to do with it. Or perhaps there's a perfectly logical explanation for it. Does anyone know why this is happening and perhaps a workaround? -- Matthijs [EMAIL PROTECTED] No need to 'cc' me, I read the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
IPtables, netfilter, confusion...
After posting some info about portknocking security (see thread SSH cracking attempts) I looked a bit at iptables at my system. Result from 'iptables -L': FATAL: Module ip_tables not found. iptables v1.2.11: can't initialize iptables table `filter': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. I've found a lot of links with google, but nothing really useful. It seems that my kernel (self compiled 2.6.8) doesn't support iptables. I looked through the kernel config and found something under networking options: "network packet filtering (replaces ipchains)". But the help states that you should specify 'Y' for routers, 'N' for regular hosts - and 'N' if you're unsure. Well, I'm unsure right now... The system to protect is a Debian web/mail/ssh server, not a router. I'm not sure if I need a firewall but it won't hurt - plus, if I can run iptables, I can try the portknocking system. Can anyone explain firewalls & kernel 2.6? Can I still run iptables (and if yes, what should I change in my config or which module to load?) or is this network packet filtering 'the new thing'? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SSH Cracking Attempts
On Wed, 29 Sep 2004 23:10:11 +0200, Jacob S <[EMAIL PROTECTED]>
wrote:
> On Wed, 29 Sep 2004 21:55:59 +0200
> Matthijs <[EMAIL PROTECTED]> wrote:
>
> > It's not really what you're asking, but:
> > In the dutch computer magazine C't, I read an article a few months ago
> > about protecting your computer using a port knocking system. If I
> > remember correctly, you can close a port (your SSH port, for example)
> > and only open it when a pre-defined pattern of access attempts on a
> > pre-defined port (unused for applications) is applied. The SSH port
> > can then be set to open in your firewall, perhaps only for the
> > IP-adress that performed the knocking sequence.
>
> hmm... You're right, it's not what I'm looking for, but it still sounds
> like a good concept. I'd be interested in learning more about that, if
> not for this use with ssh, I have a couple other applications it could
> work with on servers.
Short note in advance: I've only read the article, I use neither this
portknocking stuff nor the iptables firewall (well, at least not that
I'm really aware of). So I can't be held responsible for mistakes in
the article that I've copied below...
OK, here's some info from the article (Dutch C't september 2004, page
112-114):
Port knocking project by Martin Krzywinski:
http://www.portknocking.org
Portknocking uses a predefined range of 255 ports to receive TCP
connection attempts ('knocks'). These ports do not need to be open for
incoming connections, the messages written by iptables in the system
log is enough to activate the portknocking software.
The portknocking package consists of two scripts, one for the client
and the other for the server. According to the article, a C, Python
and Perl version of the scripts exists but the focus of the article is
on the Perl version.
The firewall needs to guard a port range that is used for the
portknocking system and write connection attempts to a log file. A
command like:
iptables -I INPUT -p tcp -s 0/0 -d 0/0 dport 55000:55255 -j LOG
should do this.
The installation of the portknocking software itself is not well
described. I did notice that there is a debian package 'knockd', which
I think might be the same portknocking daemon described in the
article.
Configuration is done in the file knockdaemon.conf. The most important
part is the part that defines the knocking sequence. The default is an
8-part sequence where the first 4 values specify the IP-address of the
knocker, followed by a variable which could for instance indicate the
port to be opened, followed by some other random number. After this
sequence, the knocker should also send a checksum for verification.
There is a lot more possible including date-functions. With all the
possibilities, it should be possible to prevent a replay attack
(someone listening to the knocking sequence and replaying it to open a
port for themselves).
Also, it is possible to specify a closing sequence so you can close a
port after you're done with it.
The directive specifies the action to perform for a correct
knocking sequence. Normally that would be a command to open a port in
the firewall, but other not firewall related commands are also
possible.
Most important in the configuration is to specify the correct
portrange to scan in the logfile for knocking sequences. Look for the
attribute 'portspan'. The portknocking package is password protected,
but it may be wise to change the default password 'password'.
After configuration, the daemon can be started and will check every
500ms if something has been knocking on some ports.
The portknocking client is also written in Perl. The file
'knockclient.conf' needs to be modified before first use. The IP
address of the server with the knock daemon should be specified
(variable 'remote'). The knocking sequence should of course be
specified and be identical to the specification in the daemon's
configuration file.
Variable 'client' should specify the IP address of the client (which
will be knocked to the server); variable 'port' specifies the port
that must be opened.
Executing the knocking client should then sent a series of knocks to
the server's IP address. These will be written by iptables to a log
file. The portknocking daemon will read this log file and, if the
knocking sequence is correct, execute the required action like opening
the SSH port.
Of course this system is only an additional security layer and is not
a substitute for keeping your system up-to-date. Nevertheless, it is
recommended by cryptography expert Bruce Schneier:
http://www.schneier.com/crypto-gram-0403.html
Well, that's about it, really. Hope this stuff is helpful for you or
anyone else reading this thread!
--
Matthijs
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SSH Cracking Attempts
On Wed, 29 Sep 2004 21:10:24 +0200, Jacob S <[EMAIL PROTECTED]> wrote: > So, my question is this. Is there a way to tell ssh to refuse > connections from an ip address after a certain number of failed login > attempts, or is snort the only way to do something like this? So far > I've been taking the manual approach, blocking the ip address with > my firewall after I see it hitting the logs, but that can give them > about an hour to play before I notice it (e-mailed to me by logcheck). It's not really what you're asking, but: In the dutch computer magazine C't, I read an article a few months ago about protecting your computer using a port knocking system. If I remember correctly, you can close a port (your SSH port, for example) and only open it when a pre-defined pattern of access attempts on a pre-defined port (unused for applications) is applied. The SSH port can then be set to open in your firewall, perhaps only for the IP-adress that performed the knocking sequence. That way, the SSH port is closed and only someone who knows the appropriate port knocking sequence can open the port - and then set up an SSH session. Your ssh logfile should then no longer show up illegal access attempts. Some applications were named in the article - if you want, I can look them up and post the names. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED Re: How to build alsa-modules from source?
On Thu, 15 Jul 2004 06:00:08 +0200, "Arne Götje (???)" <[EMAIL PROTECTED]> wrote: > Found it myself. > > Cheers > Arne In case anyone else can use this: I've used http://www.d.kth.se/~d98-jas/debian/debian-install-alsa.txt a few times to compile alsa myself. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modprobe.conf missing
On Mon, 12 Jul 2004 17:50:12 +0200, Derrick 'dman' Hudson <[EMAIL PROTECTED]> wrote: > On Mon, Jul 12, 2004 at 06:29:58AM +0200, Matthijs wrote: > | Setup: Debian unstable, kernel 2.6.7, on a Via EPIA M1 board. > | > | The biggest problem I'm having: > | modconf wasn't installed by default, had to apt-get it myself. > > That's no problem, it isn't essential. > > | Now it > | only complains that modprobe.conf is missing. > > It must be out of date. The current module-init-tools don't use > /etc/modprobe.conf any more. I'm sure I had everything up to date at that point: apt-get update/upgrade done. Before I read you're reply, I decided to re-install Debian Sarge again from scratch, since it didn't went smoothly the first time. Yes, I know, I sound like a windows-user: re-installing the OS when something doesn't work... (Oh wait, I *am* a windows user...) ;-) Anyway, *that* problem with modconf was gone after the reinstall. The problem with my soundmodules & ALSA were still there. > I thought modconf only modified /etc/modules. You can edit that by > hand too -- it is just a simple listing of modules to load at boot > time. Just out of curiosity, does /etc/modprobe.conf contain > anything after you change something with modconf. I don't know for sure, but I think it stayed empty. > | they're automagically back after a reboot. > > What loads them? Is it /etc/modules? Is it hotplug? It's neither /etc/modules nor hotplug - but at least you pushed me in the right direction. /etc/modules was almost empty - so that wasn't the source of my problems. This hotplug system was completely new for me, so I needed to investigate this. > What modules are they? ALSA should "just work" if you have a > relatively recent sound card. (my SB Pro just works if I list > snd-sb8 in /etc/modules and the IO and IRQ parameters in > /etc/modprobe.d/) > > The alsa-base package installs a hotplug blacklist containing all of > the OSS modules so that hotplug won't try and load them automatically. > Perhaps the issue is that you don't have that blacklist. No, the old OSS modules were in the blacklist. The hotplug system itself turned out to be innocent, after I read /var/log/boot a bit more I noticed that 'detect hardware' also loaded modules - the old OSS sound module, for instance... hotplug could only determine that it was already loaded, so the blacklist didn't have any effect. This hardware detect thing was also new for me. After some searching I knew that I had to modify /etc/discover.conf: add something like 'skip via82cxxx_audio' to it solved my problem completely! > | Also, a minor problem: during boot it complains about a missing > | usb_uhci module. I know that this is a leftover from the 2.4 kernel, > | but I can't get rid of it. > > My first guess is that it is listed in /etc/modules. If it is, then > delete that line. Also solved with the new install. Number of problems left: 0! Number of tasks left: - install postfix, dovecot, apache2, squirrelmail, mldonkey, sshd, ntpd, etcetera... I'll probably be back with questions soon... Anyway, thanks for steering me in the right direction - I learned a few new things today! -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
modprobe.conf missing
Hello, Last morning, I accidently deleted /etc/rc* (great, find-command combined with rm -f... ) and decided to start a new installation. I do have all the directories /etc, /usr, /var copied to a safe place but they don't help me now. Setup: Debian unstable, kernel 2.6.7, on a Via EPIA M1 board. The biggest problem I'm having: modconf wasn't installed by default, had to apt-get it myself. Now it only complains that modprobe.conf is missing. If I do a touch /etc/modprobe.conf, it doesn't complain anymore but when I remove some audio modules with modconf, they're automagically back after a reboot. I think this may be one of the reasons ALSA won't work. Resources on the internet suggest this 'touch /etc/modprobe.conf' but that isn't the solution for me. I also read that modern installations don't need it. I also read about using generate-modprobe.conf script, but can't find it. Also, a minor problem: during boot it complains about a missing usb_uhci module. I know that this is a leftover from the 2.4 kernel, but I can't get rid of it. Any help, please? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Top-Posting (WAS: Re: is it possible to change apt-get's access priorities?)
On Sat, 10 Jul 2004 01:00:06 +0200, Thomas Adam <[EMAIL PROTECTED]> wrote: > --- "Monique Y. Mudama" <[EMAIL PROTECTED]> wrote: > > > Please note that top-quoting is not the preferred quoting method for > > mailing lists and newsgroups. By placing your replies after relevant > > I cannot agree more with this, Monique, but you and I (and others) both > know that such suggestions will just go un-heeded, and people will _still_ > continue to top-post. I personally delete all top-posted e-mails and > refuse to answer them. I agree with you, top-posting makes postings unreadable, but: some people subscribed to a mailinglist do this for their work. It is likely that their employer decides which program to use for e-mail, and I know for a fact (unfortunately...) that some employers have chosen to use Lotus Notes as the only installed e-mail program on employee's computers. In case you don't know Lotus Notes: the user interface is written in such a way that it is almost impossible to post messages in the correct style - you're almost forced to top-post. With something like Outlook, you're only stimulated to top-post, with Lotus Notes you simply don't have much choice. For this reason, I'm not as harsh as you, I do accept top-posted e-mails because the poster might not have had a choice. Although I think Lotus Notes user should start their message with an apology and explanation for their behaviour... -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: squirrelmail configuration problem
On Wed, 07 Jul 2004 14:20:08 +0200, Henry Hollenberg <[EMAIL PROTECTED]> wrote: > If I click on squirrelmail I get: > > Index of /squirrelmail > > NameLast modified Size Description > > Parent Directory07-Jul-2004 05:59 - > attach/ 03-Feb-2004 10:09 - > class/ 03-Jul-2004 21:41 - > config/ 03-Jul-2004 21:43 - > functions/ 03-Jul-2004 21:41 - > help/ 03-Jul-2004 21:41 - > images/ 03-Jul-2004 21:41 - > include/03-Jul-2004 21:41 - > index.php 03-Feb-2004 10:09 1k > locale/ 03-Jul-2004 21:41 - > plugins/03-Jul-2004 21:41 - > po/ 03-Jul-2004 21:41 - > src/03-Jul-2004 21:41 - > themes/ 03-Jul-2004 21:41 - > > Apache/1.3.29 Ben-SSL/1.53 Server at www.rcwm.com Port 443 > > I guess I have something misconfigured and have examined /etc/squirrelmail and > still don't grok what's going on. Any ideas? Thanks, hgh. What happens when you click on index.php? If it attempts to download/save the php-file instead of executing it, I would guess that PHP isn't installed correctly in your apache config-file. Or perhaps it is installed correctly for apache non-secure, but not installed for apache-ssl? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ACPI and VIA C3
On Sun, 27 Jun 2004 03:50:06 +0200, Ludwig Meyerhoff <[EMAIL PROTECTED]> wrote: > What processor do You have (cat /proc/cpuinfo) and what does ACPI say > (modprobe processor; cat /proc/acpi/processor/CPU0/power)? My processor is not the same as yours - I've got a C3 Nehemiah processor: /proc/cpuinfo: processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 9 model name : VIA Nehemiah stepping: 5 cpu MHz : 999.937 cache size : 64 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr mtrr pge cmov mmx fxsr sse rng rng_en bogomips: 1974.27 modprobe processor: ACPI: Processor [CPU0] (supports C1 C2, 2 throttling states) /proc/acpi/processor/CPU0/power: active state:C2 default state: C1 bus master activity: states: C1: promotion[C2] demotion[--] latency[000] usage[0440] *C2: promotion[--] demotion[C1] latency[090] usage[00069438] C3: -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ACPI and VIA C3
On Sat, 26 Jun 2004 19:40:10 +0200, Ludwig Meyerhoff <[EMAIL PROTECTED]> wrote: > I have a VIA C3 (Ezra) processor. It is very nice for "normal" > applications, as it takes only a few watt. > > Now: does anyone know how I can achieve full ACPI support for my > processor in a more recent kernel than 2.4.20? In special I would like > to use frequency scaling/throttling, as most of the time my small > computer does nothing. I also have a VIA C3 machine, installed kernel 2.6.6 on it. I have absolutely no knowledge of ACPI and all, but perhaps the following link will provide the information you need: http://www3.sympatico.ca/howlettfamily/epia/epia_howto/index.html According to section 8.1, it is possible to get frequency throttling to work, but with kernel 2.6.6 you need to patch the source and compile from scratch. I have done this, compiled the kernel 'the Debian way' with help from: http://www.desktop-linux.net/debkernel.htm ... and use the '.config' from the link supplied in section 11.1 from the first URL I wrote above. Good luck, -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: newbie postfix/mta question
On Mon, 14 Jun 2004 19:30:24 +0200, Ignatz Sol <[EMAIL PROTECTED]> wrote: > I have set up postfix on a machine to send/receive mail. Normal > install and seems fine EXCEPT that I don't think that port 110 is open > for POPing. I can send mail fine but I can't get into the machine to > download mail. I can't figure out what the problem is. I cannot > telnet into the machine on port 110. > > Can anyone clue me in to where I can start looking for the problem? As far as I know, Postfix by itself does not handle the POPping of messages - you need a separate program for this. I've installed courier-pop, qpopper, cyrus-pop3d and dovecot-pop3d are some possible alternatives. Perhaps you should issue a ps -fe | grep -i pop ... and see if there's a pop3-server already running or not. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Logcheck warning: UDP packet from outside my network?
On Fri, 04 Jun 2004 20:20:09 +0200, "Bojan Baros" <[EMAIL PROTECTED]> wrote: > Matthijs said: > > Jun 4 07:30:54 MyMail kernel: UDP: short packet: 24.5.180.234:10030 > > 2167/119 to 192.168.1.2:10768 > > > > I'm not really interested in what these packets are for (I guess some > > kind of worm/DoS related packets), but I'm more interested in the > > source of the packets: 24.5.180.234 is *outside* my network. > > > > This Linux machine is located behind a hardware router with build-in > > SPI firewall (Linksys WRT54G, in case you're interested). It should > > prevent unwanted packets to uninteresting ports to enter my network. > > I've just double-checked the port-forwarding section and packets to > > 10768 or 10030 are definitely NOT forwarded. > > > > Can anybody explain what is going on here? > > > > Try playing with nmap from another location. Will ask a friend to do that, in the near future... > It is common that firewalls do not block UDP packages because they are > considered harmless, since they do not establish a connection. That is, > until slammer came around. That last sentence worries me a bit. What would you advice: - Just ignore it & keep my software up to date; - Add (another) firewall to my system, especially for UDP packets; - Just add a firewall program to this Linux machine; Anyway, thanks for the explanation! -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Logcheck warning: UDP packet from outside my network?
On Fri, 04 Jun 2004 19:50:10 +0200, Paul Johnson <[EMAIL PROTECTED]> wrote: > Matthijs <[EMAIL PROTECTED]> writes: > > > Jun 4 07:30:54 MyMail kernel: UDP: short packet: 24.5.180.234:10030 > > 2167/119 to 192.168.1.2:10768 > > > > I'm not really interested in what these packets are for (I guess some > > kind of worm/DoS related packets), but I'm more interested in the > > source of the packets: 24.5.180.234 is *outside* my network. > > So? Some applications use UDP instead of TCP, what's the problem with > that? I've got no problem at all with packets using UDP or TCP - my problem was that they seem to originate from *outside* my network, while I thought my system was shielded with a hardware firewall. According to a post from Bojan Baros, I thought wrong here: it's likely (haven't tested it yet) that my firewall doesn't protect me from UDP-packets. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Logcheck warning: UDP packet from outside my network?
Since a few days, Logcheck sometimes e-mails me the following warning: Jun 4 07:30:54 MyMail kernel: UDP: short packet: 24.5.180.234:10030 2167/119 to 192.168.1.2:10768 I'm not really interested in what these packets are for (I guess some kind of worm/DoS related packets), but I'm more interested in the source of the packets: 24.5.180.234 is *outside* my network. This Linux machine is located behind a hardware router with build-in SPI firewall (Linksys WRT54G, in case you're interested). It should prevent unwanted packets to uninteresting ports to enter my network. I've just double-checked the port-forwarding section and packets to 10768 or 10030 are definitely NOT forwarded. Can anybody explain what is going on here? Thanks, -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sed question.
On Fri, 04 Jun 2004 17:30:28 +0200, Ralph Crongeyer
<[EMAIL PROTECTED]> wrote:
> Carlos Hanson wrote:
>
> >On Fri, 04 Jun 2004 10:31:07 -0400
> >Ralph Crongeyer <[EMAIL PROTECTED]> wrote:
> >
> >>I need to do a pattern match with sed of "(" and ")". I need to replace
> >>every ( with "(" and every ) with ")" on every line.
> >
> >sed 's/[()]/"&"/g'
> >
> Carlos, Thanks!
> By the way, what does the & mean?
Substitute the previously found string. So in this case, sed will
search (letter 's') for either a ( or a ) (character class [()]) and
replace it with a double quote, the previously found open or close
bracket and another double quote.
My advice: do some reading on regular expressions. For me, the book
'mastering regular expressions' by O'Reilly was really helpful.
There's SO much that you can do more effectively with regular
expressions and sed...
Last week, I had to extract a few lines of useful information from an
850MB logfile. My favorite editor (NEdit) had some memory problems and
refused to open it, but a small awk-program and a lot of regular
expressions with sed and grep got the job done in a matter of minutes.
--
Matthijs
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SSH display problem
This may not be Debian related - other than that the system I'm accessing is installed with Debian Linux - so if anybody has a better suggestion for a newsgroup to post this to, let me know... I've got a server here running sshd. I can access it from my Windows PC using PuTTY - no problem at all with the display. At work, I'm working on a HP-UX Unix machine. When I log into my own server from there, I've got no problems except that the display is not working correctly when I'm using programs like nano, vi or mutt. It's difficult to describe exactly. When I start mutt and I've got four e-mails to read, only 1 is displayed, the others become visible when I scroll the cursor down. When I open a textfile with nano, almost nothing is visible, but when I scroll the cursor to the right, the characters become visible one by one. It's totally impossible to work this way and I'm forced to edit textfiles using sed... The xterms at work are monochrome - but switching the colours of nano to monochrome didn't fix it. I used to have a ssh login on the server of my previous ISP. When I logged in from work on my ISP's server, I had no display problems at all, so I suspect that I should be able to solve the problem on my own server - I just don't have a clue as to how to solve it. Any suggestions? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hangs on Nforce2 & kernel 2.6.4
I've now got an old machine working with Linux as web- and mailserver, and I'm now thinking of migrating my desktop PC to Linux as well. It's an nforce-2 based machine, so when I read this: On Thu, 08 Apr 2004 11:20:07 +0200, Dominique Dumont <[EMAIL PROTECTED]> wrote: > Pim Bliek <[EMAIL PROTECTED]> writes: > > Anyone else experienced this problem? Or maybe someone knows how I can dig > > deeper into this problem? I am a bit lost... > > Yes. It turned out that the default DMA setting was too high on my machine > (Asus A7n8x deluxe nforce2). I'm wondering: was the DMA setting too high for your hard disk? I.e. a UDMA-3 hard disk running on UDMA-5, or is there a problem in the kernel that it can't run UDMA-4/5 on NForce2-boards? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 'su by nobody' - should I be worried?
On Wed, 31 Mar 2004 00:40:19 +0200, Martin Dickopp <[EMAIL PROTECTED]> wrote: > Matthijs <[EMAIL PROTECTED]> writes: > > > Since a few days, Logcheck reports a lot of messages like this: > > > > - > > Security Violations for su > > =-=-=-=-=-=-=-=-=-=-=-=-=- > > Mar 30 06:25:02 MyMail su[13083]: (pam_unix) session opened for user > > nobody by (uid=0) > > - > > > > The only way I can read this messages is that user 'nobody' has done a > > 'su' - become root. > > No, it's the other way around: 'root' has used 'su' to become 'nobody'. > This is probably part of a script (run by a cronjob?). Ah, I interpreted the word 'for' in the report incorrectly! Indeed a cronjob, something that is executed precisely at 06:25. I sleep much better now - thanks! -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exim & squirrelmail
On Thu, 01 Apr 2004 18:40:16 +0200, "Bojan Baros" <[EMAIL PROTECTED]> wrote: > > I am using Exim default configure with Qpopper. Now I am try to > > configure > > squirrelmail but when I try to login into squirrelmail it prompt me an > > error. > > > > ERROR : Could not complete request. > > Query:SELECT "INBOX" > > Reason Given: Mailbox does not exist > > > > ERROR : Could not complete request. > > Query:CREATE "INBOX.Sent" > > Reason Given: Permission denied > > First of all, SquirrelMail is an IMAP client, not POP3. The > difference is that IMAP client browses mail on the mail server, while > POP3 downloads it to the local machine. > > Is this what you originally intended? If so, you have to download an > IMAP server for your email server. apt-get install cyrus-imap should > get you started. I've gone through the same pain two days ago (switched from mailfiles to maildirs) and got the same error message. I don't know exactly what I did to get it working (apart from using strong language...), but: - I switched to courier-imap (cyrus should also be possible, but didn't work out-of-the-box for me); - execute /etc/squirrelmail/conf.pl, option 'D' 'set pre-defined settings for specific IMAP servers', select courier. Hope this helps, -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Stable, Unstable, Testing
On Tue, 30 Mar 2004 23:50:12 +0200, Matt Krause <[EMAIL PROTECTED]> wrote: > You rule! Finally! Man, I'm not sure what to think of Debian yet. I'm > having a hard time picking up the package management system for some reason. You're welcome! I think I'm as much a newbie as you are and recognize you're problem with the package management. I'm used to a windows environment. You want a new application? Go to the website, download the setup.exe and execute - you're done. I'm not here to start an OS-war (I would probably lose... :-), but switching to the package management system from Debian is quite a big step. > While, I am at it, I will throw this out. Does squirrelmail work over > 993? I know it is supposed to, but haven't gotten it working yet. I > compiled from source. Don't know. I don't use IMAP, I POP3. -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
'su by nobody' - should I be worried?
Since a few days, Logcheck reports a lot of messages like this: - Security Violations for su =-=-=-=-=-=-=-=-=-=-=-=-=- Mar 30 06:25:02 MyMail su[13083]: (pam_unix) session opened for user nobody by (uid=0) - I've had similar messages for various users for cron and sshd. Should I be worried? The only way I can read this messages is that user 'nobody' has done a 'su' - become root. I don't know what the 'pam_unix' part means. So: does this mean my server has been compromised? If not, what does it mean? If so, how? How can I find the hole - or should I re-install everything? Thanks, -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Stable, Unstable, Testing
On Tue, 30 Mar 2004 20:10:09 +0200, Matt Krause <[EMAIL PROTECTED]> wrote: > So, I have having problems getting unstable and testing versions of > uw-impad Debian packages working. The version numbers are > 7:2002edebian1-3 and 7:2002ddebian1-4 respectivly. With these two > packages installed (uw-imapd and uw-imapd-ssl), I can only connect to > the imap server via SSL or port 993. > > I have a old stable box lying around running 4:2001adebian uw-imapd-ssl. > The Debian uw-imapd package is not installed on it. That box works > great on 143 or 993. I verifed this by installing uw-imapd-ssl > 4:2001adebian on my stable box and it works over both ports as well. > > So, does the newest version of uw-imapd and uw-imapd-ssl capable of > working over both 143 and 993, and if so, how? Sounds to me like you've got the same problem that I had two weeks ago - only my problem was with POP3 access. It seems that they have disabled plain-text login in the newer versions of uw-imapd (and ipopd). You can do some reading: they've explained some of this in /usr/share/doc/libc-client(...)/README.Debian. The part between brackets is, for me, something like 2002edebian - verify this for your setup. The README file might be compressed. Anyway, the suggestion is to put the line 'set disable-plaintext nil' in /etc/c-client.cf. That didn't completely work for me, I have the following two lines: I accept the risk set disable-plaintext nil Since I only POP3 behind a router/firewall, I think the risk for me is acceptable. Also, I needed to do: dpkg-reconfigure libc-client2002edebian (again, verify this last part for your setup. Good luck, -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sitecom networkcard not working after kernel upgrade
On Mon, 22 Mar 2004 02:40:04 +0100, Kent West <[EMAIL PROTECTED]> wrote: > Matthijs wrote: > > >Today, I decided to upgrade my kernel from 2.2 to 2.4.25 (Debian > >system). I didn't compile it, just installed using apt-get. > >Reason for upgrade: I wanted USB support. > > > >Booting is fine, but my network connection is gone. During boot, I see > >eth0 related error messages (beginning of a line, something like > >'eth0: ERROR '. > > > >The network card is a simple Sitecom card, with a sitecom chip on it: > >http://www.sitecom.com/products_info.php?product_id=185&grp_id=5 > > > I believe that's the tulip module you want. Run "modconf" and select the > tulip driver. Then restart networking with "/etc/init.d/networking restart". Mmmm... "Reconfiguring network interfaces...SIOCDELRT: No such process". Then 'depmod -a' seems to fix that one. Installing the PC down in the basement, rebooting... YES! 'modconf' & the tulip driver did the trick! If it wasn't for google and this newsgroup, kernel upgrading is no job for newbies like me... Thanks a lot! -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sitecom networkcard not working after kernel upgrade
Today, I decided to upgrade my kernel from 2.2 to 2.4.25 (Debian system). I didn't compile it, just installed using apt-get. Reason for upgrade: I wanted USB support. Booting is fine, but my network connection is gone. During boot, I see eth0 related error messages (beginning of a line, something like 'eth0: ERROR '. The network card is a simple Sitecom card, with a sitecom chip on it: http://www.sitecom.com/products_info.php?product_id=185&grp_id=5 Unfortunately, I can't find the errors in any of the logfiles in /var/log. It's also not listed in the report from dmesg. modprobe -c: nothing network related is listed; lsmod: nothing network related is listed; ifconfig: Only the loopback interface 'lo' is listed; lspci -v: 00:0e.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11). ... and some more information. I'm afraid I'm too much of a newbie to fix this problem. Anyone out there who can help me out? -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ipopd and "unknown authorization state command"
On Sun, 21 Mar 2004 07:00:10 +0100, "Jaldhar H. Vyas" <[EMAIL PROTECTED]> wrote: > On Sat, 20 Mar 2004, Matthijs wrote: > > > - Then, using squirrelmail, I accessed my Inbox (which under the hood > > uses IMAP. Logged in without problems, no mail in my Inbox > > - A few seconds later, I tried to access my Inbox again via > > squirrelmail but got a vague error: > > ERROR : Could not complete request. > > Query: SELECT "INBOX" > > Reason Given: Internal error [2004-03-20 12:59:13] > > - From then on, POPping was also not possible anymore. > > If you check you mbox with a text editor you will probably find one or > more messages with double From lines (not From:) Can't verify this anymore: I went back to an old version of ipopd, retrieved and sent mail since. I just installed dovecot again and it has worked flawlessly since. > > > Is /etc/c-client.cf properly set up? See > > > /usr/share/doc/libc-client*/README.Debian > > > > Good tip. Probably plain text passwords are not enabled. > > Probably in the previous version of ipod (packaged with Debian > > stable), plain tex passwords were enabled but disabled in later > > versions. > > Yep, that's exactly what happened. dpkg-reconfigure libc-client2003debian ... and 'set disable-plaintext nil' in /etc/c-client.cf. Works! Great! So now I got both dovecot and ipopd (recent versions) working on my system. For now, I'll stay with dovecot, but it's nice to have a choice if a bug pops up... Thanks for all the help, -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ipopd and "unknown authorization state command"
On Thu, 18 Mar 2004 23:40:11 +0100, "Jaldhar H. Vyas" <[EMAIL PROTECTED]> wrote: > On Wed, 17 Mar 2004, Matthijs wrote: > > > As far as I know, ipopd is the only(?) pop3-server that can also pop > > IMAP accounts. > > Dovecot also supports POP3 and IMAP. Mmmm... I've given it a try, but: - When POPping from my windows-PC on the same network, I get: "Connection to host broken (last commands sent were: "PASS", "STAT")" - When using telnet: telnet 192.168.1.2 110 +OK dovecot ready. user +OK pass +OK Logged in. Connection to host lost. ... so directly after logging in, the connection is lost. Strange though, immediately after I installed it, it worked for a short time: - First I POPped from my windows PC without problems (no new mail retrieved); - Then, using squirrelmail, I accessed my Inbox (which under the hood uses IMAP. Logged in without problems, no mail in my Inbox - A few seconds later, I tried to access my Inbox again via squirrelmail but got a vague error: ERROR : Could not complete request. Query: SELECT "INBOX" Reason Given: Internal error [2004-03-20 12:59:13] - From then on, POPping was also not possible anymore. Dovecot version: 0.99.10.4-3 Debian unstable > Is /etc/c-client.cf properly set up? See > /usr/share/doc/libc-client*/README.Debian Good tip. Probably plain text passwords are not enabled. Probably in the previous version of ipod (packaged with Debian stable), plain tex passwords were enabled but disabled in later versions. I'll see if I can get this configured correctly... Thanks! -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ipopd and "unknown authorization state command"
Yesterday I upgraded to Debian 'unstable', and unfortunately ipopd is broken. When I connect from another machine in my LAN via telnet: telnet 192.168.1.2 110 ... and then issue 'user vanaalten', I get the message Unknown AUTHORIZATION state command User 'vanaalten' is a valid user. >From what I read on the net, this may not be a bug but intentional, to prevent non-ssl communication with ipopd. I think I've got a good reason to use ipopd instead of qpopper: When I use the webmail client (squirrelmail) on the machine, all mail is transfered to an IMAP account. At some point however, I want to POP all my mail (including the mail in the IMAP account) to another PC. As far as I know, ipopd is the only(?) pop3-server that can also pop IMAP accounts. Any suggestions on how to solve this problem? -- Matthijs [EMAIL PROTECTED] -- Matthijs [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody install loops after asking for password
> Now I only had to fix sources.list since the installer put "stable" instead > of "testing" there, but I guess that will be right for the final release. I noticed the same thing, is this a known bug? Matthijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody install loops after asking for password
> Hello,
>
> I tried to install woody via the net. I downloaded the compact-boot and
> compact-root 1.44MB floppies, version 3.0.22-2002-04-03, bootet the
machine
> and installed everything else from the net (using ftp.de.debian.org as a
> mirror).
>
> Everything works fine until the newly booted system asks for timezone and
> password settings. After the last password-related question ("create
normal
> user account?"), it loops back to the first question ("is the system clock
> set to GMT?"). This repeats endless.
>
> I have this behaviour on two different machines, both using english and
> german as the language for the installation process.
>
> It seems that /sr/sbin/base-config is running the different config
scripts,
> and starting wirh 25pcmcia, they fail and return with error code 10,
because
> db_get fails somehow - I could ot trace this further because I do not know
> how this database mechanism is supposed to work.
I had the same problem, drew the same conclusions as you did, and decided to
visit [EMAIL PROTECTED], where I found this link:
http://wiki.debian.net/DebianWiki/DebianWiki/WoodyNetinstBaseconfigLoop
It worked for me, I have advanced further in the install process (still not
finished, though)
Hope this helps,
Matthijs
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
