Hosting Provided By

debian-user-digest Digest V2007 #2257

From: <debian-user-digest-request(at)lists.debian.org>
Date: Mon Aug 27 2007 - 06:44:48 EDT

Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 2257

Today's Topics:

  xterm won't start                     [ Paul Scott  ]
  Re: why is debian coreutils so old?   [ Miles Bader  ]
  Re: USB question                      [ Miles Bader  ]
  Re: USB question                      [ Dave Thayer  ]
  Re: LVM partition full (was:what is   [ "Richard Lyons"  ]
  Re: using a remote IMAP server and s  [ "Richard Lyons"  ]
  which videcard for dual-monitor setu  [ Tinus Nijmeijers  ]
  Re: xterm won't start                 [ Vincent Lefevre  ]
  capture real audio stream             [ Lorenzo Bettini  ]
  SATA vs PATA                          [ Dan H  ]

Date: Sun, 26 Aug 2007 19:44:12 -0700
From: Paul Scott <waterhorse@ultrasw.com> To: Debian User <debian-user@lists.debian.org> Subject: xterm won't start

Message-ID: <46D23A7C.2020708@ultrasw.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Old laptop (i386) running Debian sid. With 2.6.17 stock kernel xterm is fine.

Installed 2.6.22 kernel and built module for USB wireless card. Starting xterm gives:

xterm: Error 32, errno 2: No such file or directory Reason: get_pty: not enough ptys

Do you need help?

CONFIG_UNIX98_PTYS=y

for both kernels but only:

CONFIG_LEGACY_PTYS=Y
CONFIG_LEGACY_PTY_COUNT+256 is only for the 2.6.17 kernel that works.

Other term's don't work either.

Googling suggests "MAKEDEV pty" but it's not clear when to do that or what the Debian way is. It also seems that reinstalling some package ought to fix it.

TIA for any ideas.

Paul Scott

Do you need more help?

Date: Mon, 27 Aug 2007 13:50:52 +0900
From: Miles Bader <miles.bader@necel.com> To: debian-user@lists.debian.org
Subject: Re: why is debian coreutils so old? Message-Id: <buoveb11syb.fsf@dhapc248.dev.necel.com> Content-Type: text/plain; charset=us-ascii

bob@proulx.com (Bob Proulx) writes:
>> You should probably ask the package maintainer directly. Some
>> information is available at [1].
>> [1] http://bugs.debian.org/422279
>
> That particular issue mostly has to do with UTF-8 support. So far all
> of the patch suggestions for it (used by other distros) are quite ugly
> with a lot of duplicated code and has been rejected by the upstream
> maintainer. There really should be a better way to do this.
>
> The inclusion of UTF-8 support and the issues surrounding the upgrade
> to a newer coreutils in Debian are mostly independent. However even I
> am not aware of the issues the Debian maintainer has with moving to a
> newer coreutils. I would like to see it happen too.

I've just sent another followup to 422279 asking the original question again, since the bug thread seems to have gotten sidetracked by the utf-8 issue.

-Miles

-- 
Occam's razor split hairs so well, I bought the whole argument!

Date: Mon, 27 Aug 2007 14:02:43 +0900 From: Miles Bader <miles.bader@necel.com> To: Brad Rogers <brad@fineby.me.uk> Cc: debian-user@lists.debian.org Subject: Re: USB question Message-Id: <buops191sek.fsf@dhapc248.dev.necel.com> Content-Type: text/plain; charset=us-ascii Brad Rogers <brad@fineby.me.uk> writes:
> Not lsmod, but lsusb. Fingers faster than brain, today. :-x
BTW, is lsusb known to be broken these days? I have a USB thumb drive that works just fine, but "lsusb" doesn't show it, even while it's mounted and I'm doing I/O to it! Indeed, lsusb doesn't seem to show much of anything... lsusb shows nothing very useful: $ lsusb -v $ lsusb --version lsusb (usbutils) 0.72 $ lsusb -v -t Bus# 3 `-Dev# 1 Vendor 0x0000 Product 0x0000 `-Dev# 3 Vendor 0x04bb Product 0x0c45 Bus# 2 `-Dev# 1 Vendor 0x0000 Product 0x0000 Bus# 1 `-Dev# 1 Vendor 0x0000 Product 0x0000 `-Dev# 2 Vendor 0x046d Product 0xc00e But udev found the drive: $ udevinfo --name=sda1 --query=all P: /block/sda/sda1 N: sda1 S: disk/by-id/usb-I-O_DATA_USB_Flash_Disk_A0E0C772300014-0:0-part1 S: disk/by-path/pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0-part1 S: disk/by-uuid/1E1B-2835 E: ID_VENDOR=I-O_DATA E: ID_MODEL=USB_Flash_Disk E: ID_REVISION=A2C E: ID_SERIAL=I-O_DATA_USB_Flash_Disk_A0E0C772300014-0:0 E: ID_SERIAL_SHORT=A0E0C772300014 E: ID_TYPE=disk E: ID_INSTANCE=0:0 E: ID_BUS=usb E: ID_PATH=pci-0000:00:1d.7-usb-0:2:1.0-scsi-0:0:0:0 E: ID_FS_USAGE=filesystem E: ID_FS_TYPE=vfat E: ID_FS_VERSION=FAT16 E: ID_FS_UUID=1E1B-2835 E: ID_FS_UUID_ENC=1E1B-2835 E: ID_FS_LABEL= E: ID_FS_LABEL_ENC= E: ID_FS_LABEL_SAFE= And it's even mounted: $ mount | grep sda1 /dev/sda1 on /media/usb type vfat (rw,noexec,nosuid,nodev,noatime,user=miles) IIRC, lsusb used to be much more useful than this... Thanks, -Miles -- (\(\ (^.^) (")") *This is the cute bunny virus, please copy this into your sig so it can spread.

Date: Sun, 26 Aug 2007 23:36:09 -0600 From: Dave Thayer <dave@thayer-boyle.com> To: debian-user@lists.debian.org Subject: Re: USB question Message-ID: <20070827053609.GB10425@thayer-boyle.com> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 24, 2007 at 02:08:40PM +0200, Dan H wrote:
> Hello,
>
> one quick question: Does each and every USB device that gets plugged
> into the computer generate a console message?
>
> Background: I'm trying to get an HP scanner (6200C) to work, but the
> sane tools won't recognize it. And when I look at the root console
> when I connect the USB cable, I see no message. In contrast, when I
> plug in my memory stick, my portable disk or my camera, the kernel
> always spits out some message.
>
> This looks as if the scanner (or at least the USB interface) is shot,
> hardware-wise. Valid conclusion?
>
Make sure that you have the appropriate line uncommented in /etc/sane.d/hp.conf: # HP ScanJet 62X0C usb 0x03f0 0x0201 Here's what shows up in /var/log/syslog when I plug in my 6200c: Aug 26 22:47:26 hedorah kernel: ohci_hcd 0000:00:02.0: wakeup Aug 26 22:47:26 hedorah kernel: usb 2-1: new full speed USB device using ohci_hcd and address 3 Aug 26 22:47:37 hedorah kernel: usb 2-1: configuration #1 chosen from 1 choice lsusb says: Bus 003 Device 002: ID 0764:0501 Cyber Power System, Inc. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 003: ID 03f0:0201 Hewlett-Packard ScanJet 6200c Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 sane-find-scanner -q says: found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0201 [HP ScanJet 6200C]) at libusb:002:004 and scanimage --list-devices says: device hp:libusb:002:004' is a Hewlett-Packard ScanJet 62x0C flatbed scanner I'm running sid with kernel 2.6.18-2-k7. FWIW, I've found the 6200c's USB performance to be somewhat flaky; sometimes I have to power-cycle the scanner to avoid getting error messages from scanimage. HTH dt -- Dave Thayer | Whenever you read a good book, it's like the Denver, Colorado USA | author is right there, in the room talking to dave@thayer-boyle.com | you, which is why I don't like to read | good books. - Jack Handey "Deep Thoughts"

Date: Mon, 27 Aug 2007 07:34:15 +0100 (BST) From: "Richard Lyons" <richard@the-place.net> To: "debian-user " <debian-user@lists.debian.org> Subject: Re: LVM partition full (was:what is /command directory?) Message-ID: <44680.83.67.89.134.1188196455.squirrel@www.the-place.net> Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, August 27, 2007 01:44, Douglas A. Tutty wrote:
> On Sun, Aug 26, 2007 at 05:38:27PM +0100, Richard Lyons wrote:
>>
[...]
>> I've just read the lvm howto and other stuff on 'Changing the Size of
>> the LVM-Partitions' -- and I don't like the sound of it a bit. Lots
>> of talk of "if something goes wrong", and very complicated. I think
>> I'll go back to the old way as soon as I have energy to do the moving.
>> There is room on my second hard drive to copy the whole system off,
>> repartition the first drive, and copy it back. With boot on a non-LVM
>> partition, I assume it will all reboot quite happily afterwards. (Ment=
al
>> note: I must remember to remove everything lvm from /etc/rc*.d. before
>> rebooting)
>>
>
> Here there be dragons. Remember that your initrd will be set up to
> start your LVM system so that it can find the root device for the
> kernel. Since I've never had to tweak an initramfs it could get
> interesting. So with / on LVM, lvm will be started before init even
> gets a chance to run anything in /etc/rc*.d.
>
You are right of course. I'll have to re-install from scratch in order to get a working initrd. And then copy back the /home and /usr partitions and most of the / partition... Or just maybe there is a rescue boot on the netinstall disk which just maybe will allow me to create a new initrd...
> As for LVM being complicated and warnings of "if something goes wrong",
> remember that you are dealing with your data on disk. A HOWTO for any
> regular partitioner would also be full of warnings. Be sober and well
> rested before you touch your partitions of whatever stripe (so to
> speak). The other thing to remember is that things are layered. You
> have files in filesystems on logical partitions in volume groups made u=
p
> of one or more physical volumes. The concept can be complicated but th=
e
> design of those concepts is well tested in real-life use on many OSs.
> Linux implimentation of those concepts is somewhat newer but it does
> work.
>
> However, I do agree that from the user/admin's perspective it is
> complicated. It offers many advantages to compensate for that. The
> most obvious is that you do have at your fingertips the ability to twea=
k
> the sizes of your partitions which you would not have with normal
> partitions.
I've always found it easy and quick with fdisk and parted. But maybe the new way is easier than it looks in the documents. Perhaps I should try first, just for the experience. Thanks. --=20 richard

Date: Mon, 27 Aug 2007 08:29:40 +0200 From: Sven Joachim <svenjoac@gmx.de> To: debian-user@lists.debian.org Subject: Re: possible to "apt-get -b source everything" Message-ID: <87wsvhsd63.fsf@gmx.de> Content-Type: text/plain; charset=us-ascii Rogelio Bastardo <scubacuda@gmail.com> writes:
> Apologies if this is not the best place to ask this question, but if
> I've apt-get'd some packages and then later want to recompile those
> from source (using something like apt-get -b source packagename), is
> that possible?
Yes. You may need to call apt-get build-dep packagename first.
> And what if I want to do that for everything that I've already
> downloaded? That is, all of my packages are installed the "normal
> way" (apt-get install package), and I'd like to, if possible, mass
> install everything from source.
Have a look at the "srcinst" package, it does exactly that. Sven

Can we help you?

Date: Mon, 27 Aug 2007 08:41:36 +0100 (BST) From: "Richard Lyons" <richard@the-place.net> To: "debian-user " <debian-user@lists.debian.org> Subject: Re: using a remote IMAP server and smarthost Message-ID: <52156.83.67.89.134.1188200496.squirrel@www.the-place.net> Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Sun, August 26, 2007 22:53, Florian Kulzer wrote: [...]
> Maybe the smarthost does not use TLS (an encryption wrapper) because it
> is only dealing with internal connections from trusted VMs. I would
> start simple on the VM, with this ~/.msmtprc:
>
> #-------------------------
> tls off
> host FULLY_QUALIFIED_DOMAIN_NAME_OR_IP_OF_SMARTHOST
> from YOUR_EMAIL_ADDRESS
> auth plain
> user YOUR_USERNAME
> password YOUR_PASSWORD
> #-------------------------
Done that. Sending from the VM, now I get msmtp: the server does not support DSN msmtp: could not send mail (account default from /home/richard/.msmtprc) I tried with no auth and with auth off and get the identical result, unexpectedly. Reading the manual again, I see that DSN is Delivery Status Notification. Although it is the default, I have tried specifying dsn_notify off, but still get the same error. Info on the ISP's smarthost from their site: and we will relay messages that fulfill the following criteria: * The envelope MAIL FROM: address must be routable (i.e. exist and have a valid MX record) * The envelope RCPT TO: address must also be routable. * To connect to the relay your host IP address must be in the Bytemar= k IP range. * The message must be 20MB or smaller. * Your machine is not sending more than 240 messages every 6 hours. Only the first two could be a problem AFAICS. How do I get to see the envelope msmtp is trying to send? I also ran msmtp -S which gives: SMTP server at smtp.bytemark.co.uk (tallyho.bytemark.co.uk [80.68.81.166]), port 25: tallyho.bytemark.co.uk ESMTP Exim 4.50 Mon, 27 Aug 2007 08:29:32 +010= 0 Capabilities: SIZE 20971520: Maximum message size is 20971520 bytes =3D 20.00 MB PIPELINING: Support for command grouping for faster transmission Where now? --=20 richard --=20

Date: Mon, 27 Aug 2007 10:29:55 +0200 (CEST) From: "Olivier Cant" <olivier@exxoss.com> To: debian-user@lists.debian.org Subject: raidutil adaptec 2120S Message-ID: <51680.81.246.105.189.1188203395.squirrel@webmail.exxoss.net> Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I'm having trouble getting the raidutil package to work on debian stable.= =20 I've installed the package using apt-get and get this following error : db:/dev# raidutil -L all Engine connect failed: COMPATIBILITY number db:/dev# osdIOrequest : File /dev/dpti17 Could Not Be Opened I went trouch the FAQ of the raidutil website and checked that the module was compiled and loaded (i2o_config) and that alla device where created and everything seems ok I find it wierd the raidutil tools complains about /dev/dpti17 failing to open, aren't these device from the legacy dpt_i2o subsystem ? I'm runing out of ideas... Thanks for your help Olivier

Date: Mon, 27 Aug 2007 10:42:42 +0200 From: Tinus Nijmeijers <mlists@deephosting.com> To: debian-user@lists.debian.org Subject: which videcard for dual-monitor setup? Message-Id: <1188204162.24461.3.camel@newrainbow.ztnc.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit hi list, which videocard is recommended if I want a system with 2 screens attached? or even 4 screens if that's at all possible. gr. tinus

Date: Mon, 27 Aug 2007 11:53:54 +0300 From: Avi Rozen <avi.rozen@mobileye.com> To: Nigel Henry <cave.dnb@tiscali.fr> Cc: debian-user@lists.debian.org Subject: Re: Strange 224.0.0.251 address being accessed on bootup Message-ID: <46D29122.1090502@mobileye.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Looks like zeroconf traffic (avahi/mdns), maybe try: /etc/init.d/avahi-daemon stop and see what happens. HTH, Avi. Nigel Henry wrote:
> I've had this problem for a while. When booting Debian Lenny, and perhaps Etch
> as well. When booting up I've had the following output trying to access
> 224.0.0.251.
>
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> NET: Registered protocol family 10
> lo: Disabled Privacy Extensions
> lp0: using parport0 (interrupt-driven).
> ppdev: user-space parallel port driver
> eth0: no IPv6 routers present
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0
> TTL=1 ID=0 DF OPT (94040000) PROTO=2
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=257 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=237
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=257 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=237
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=257 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=237
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=239 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=219
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=136 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=136 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=136 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=225 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=205
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=195 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=175
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=225 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=205
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=200 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=180
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=91 TOS=0x00 PREC=0x00
> TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=71
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=225 TOS=0x00
> PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=205
> DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0
> TTL=1 ID=0 DF OPT (94040000) PROTO=2
>
>
> According to RFC 3171 this block of addresses (224.0.0.x) is reserved for
> special purposes.
>
> 192.168.0.8 is the static address of my Lenny install, and 224.0.0.251 is the
> mystery address.
>
> There are 2 daemons that are running and looking for a response at bootup.
> Ntpd is directed towards my other machine that is getting it's time from the
> Internet. That is across the LAN, not the Internet. That's not the problem.
>
> The only thing accessing the Internet at boot up is freshclam, and that once
> the ethernet connection is up.
>
> Any help, suggestions would be really welcome.
>
> Nigel.
>
>
>
>
>
>
>
-- "If you are an expert in the intricacies of C++, please consider this knowledge a kind of martial art - something a real master never uses."

Date: Mon, 27 Aug 2007 10:54:12 +0200 From: Vincent Lefevre <vincent@vinc17.org> To: debian-user@lists.debian.org Subject: Re: xterm won't start Message-ID: <20070827085412.GN1292@prunille.vinc17.org> Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-08-26 19:46:29 -0700, Paul Scott wrote:
> Installed 2.6.22 kernel and built module for USB wireless card.
> Starting xterm gives:
>
> xterm: Error 32, errno 2: No such file or directory
> Reason: get_pty: not enough ptys
I've had a pty-related error with xterm on PowerPC in the past. I had to use the following workaround in my app-defaults file for XTerm: ! On ay (PPC), ones needs to set eightBitInput to true to avoid the error ! "xterm: fatal pty error 23 (errno=3D22) on tty /dev/pts/...". Therefore ! metaSendsEscape needs to be set to true, to allow non-ASCII characters. *metaSendsEscape: true *eightBitInput: true BTW, this may still be the case, as ttyrec doesn't work on PowerPC as it currently uses pty's.
> CONFIG_LEGACY_PTYS=3DY
> CONFIG_LEGACY_PTY_COUNT+256
>
> is only for the 2.6.17 kernel that works.
I see that # CONFIG_LEGACY_PTYS is not set on my PowerPC machine, while it is set on my i386 machine (both with 2.6.18 kernel). So, it may be the problem. Is your 2.6.22 kernel an official Debian kernel? If not, the solution would be to recompile it with this option set. --=20 Vincent Lef=E8vre <vincent(at)vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Date: Mon, 27 Aug 2007 11:14:20 +0200 From: Tinus Nijmeijers <mlists@deephosting.com> To: debian-user@lists.debian.org Subject: Re: raidutil adaptec 2120S Message-Id: <1188206060.24461.6.camel@newrainbow.ztnc.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit On Mon, 2007-08-27 at 10:29 +0200, Olivier Cant wrote:
> Hi,
>
> I'm having trouble getting the raidutil package to work on debian stable.
> I've installed the package using apt-get and get this following error :
>
> db:/dev# raidutil -L all
>
> Engine connect failed: COMPATIBILITY number
> db:/dev# osdIOrequest : File /dev/dpti17 Could Not Be Opened
>
> I went trouch the FAQ of the raidutil website and checked that the module
> was compiled and loaded (i2o_config) and that alla device where created
> and everything seems ok
>
> I find it wierd the raidutil tools complains about /dev/dpti17 failing to
> open, aren't these device from the legacy dpt_i2o subsystem ?
>
> I'm runing out of ideas...
>
> Thanks for your help
>
> Olivier
>
see: http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg329016.html worked for me. gr. tinus

Date: Mon, 27 Aug 2007 11:29:42 +0200 From: Guido Heumann <listguido@web.de> To: Shams Fantar <sfantar@snurf.info> Cc: debian-user@lists.debian.org Subject: Re: hda: DMA timeout error, is it a problem ? Message-ID: <46D29986.2060805@web.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Shams Fantar schrieb:
> I think that the hard disk really has a hardware problem. I'm going to
> change it.
>
> Subject closed. ;-)
>
> Thank you for your help.
>
> Regards,
>
Another thing you could try before replacing the harddrive is replacing the IDE cable. I once had strange disk error messages caused by a flaky cable connection. cheers, Guido

Date: Mon, 27 Aug 2007 11:45:56 +0200 From: Lorenzo Bettini <bettini@dsi.unifi.it> To: Debian User Mailing List <debian-user@lists.debian.org> Subject: capture real audio stream Message-ID: <46D29D54.7090104@dsi.unifi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi I'd like to capture some audio stream from a web radio. I know about streamripper, but it does not work for real audio. And in particular, if possible, I'd like to record what is being played, without knowing the address of the real audio file (which I actually don't know: bbc radio just starts the real player plugin in the web page). any clue please? thanks in advance Lorenzo -- Lorenzo Bettini, PhD in Computer Science, DSI, Univ. di Firenze ICQ# lbetto, 16080134 (GNU/Linux User # 158233) HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com http://www.myspace.com/supertrouperabba BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com http://www.gnu.org/software/src-highlite http://www.gnu.org/software/gengetopt http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

Can't find what you're looking for?

Date: Mon, 27 Aug 2007 11:44:38 +0200 From: Florian Kulzer <florian.kulzer+debian@icfo.es> To: debian-user@lists.debian.org Subject: smtp to bytemark.co.uk smarthost (was: using a remote IMAP server and smarthost) Message-ID: <20070827094438.GA4316@localhost> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [ I have changed the subject to get the attention of other bytemark users who might be able to help us with this problem: Richard has an account on a bytemark VM and he wants to send emails via the their smarthost. At the moment we are trying to configure msmtp properly on the VM for this task; suggestions for a better tool for this job are welcome. The goal is to have a sendmail-equivalent command working on the VM so that it can be used with mutt, executed remotely via ssh or by using port forwarding. ] On Mon, Aug 27, 2007 at 08:41:36 +0100, Richard Lyons wrote:
> On Sun, August 26, 2007 22:53, Florian Kulzer wrote:
> [...]
> > Maybe the smarthost does not use TLS (an encryption wrapper) because it
> > is only dealing with internal connections from trusted VMs. I would
> > start simple on the VM, with this ~/.msmtprc:
> >
> > #-------------------------
> > tls off
> > host FULLY_QUALIFIED_DOMAIN_NAME_OR_IP_OF_SMARTHOST
> > from YOUR_EMAIL_ADDRESS
> > auth plain
> > user YOUR_USERNAME
> > password YOUR_PASSWORD
> > #-------------------------
>
> Done that. Sending from the VM, now I get
>
> msmtp: the server does not support DSN
> msmtp: could not send mail (account default from /home/richard/.msmtprc)
>
> I tried with no auth and with auth off and get the identical result,
> unexpectedly.
>
> Reading the manual again, I see that DSN is Delivery Status
> Notification. Although it is the default, I have tried specifying
> dsn_notify off, but still get the same error.
Maybe you need "dsn_notify never" and/or "dsn_return off". I am not sure if this is really the reason for the failure or just a warning message.
> Info on the ISP's smarthost from their site:
>
> and we will relay messages that fulfill the following criteria:
>
> * The envelope MAIL FROM: address must be routable (i.e. exist and
> have a valid MX record)
> * The envelope RCPT TO: address must also be routable.
> * To connect to the relay your host IP address must be in the Bytemark
> IP range.
> * The message must be 20MB or smaller.
> * Your machine is not sending more than 240 messages every 6 hours.
>
> Only the first two could be a problem AFAICS. How do I get to see the
> envelope msmtp is trying to send?
Adding "logfile ~/.msmtp.log" to .msmtprc should give you more information. These first two requirements are very basic; essentially they are just saying that sender and recipient addresses cannot be completely bogus. (The "from" line in the config file should take care of MAIL_FROM and mutt should specify the recipient's email address as the argument when it invokes msmtp.) The MX record specifies the servers for incoming mail; you can check it like this: dig MX the-place.net (Dig is part of the "dnsutils" package.)
> I also ran msmtp -S which gives:
>
> SMTP server at smtp.bytemark.co.uk (tallyho.bytemark.co.uk
> [80.68.81.166]), port 25:
> tallyho.bytemark.co.uk ESMTP Exim 4.50 Mon, 27 Aug 2007 08:29:32 +0100
> Capabilities:
> SIZE 20971520:
> Maximum message size is 20971520 bytes = 20.00 MB
> PIPELINING:
> Support for command grouping for faster transmission
At least we know now that they have Exim listening on port 25 and that "tls off" is correct. What we are doing should work in principle. (Famous last words...)
> Where now?
It might be time to contact bytemark's technical support. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian |

Date: Mon, 27 Aug 2007 12:04:46 +0200 From: Shams Fantar <sfantar@snurf.info> To: debian-user@lists.debian.org Subject: Re: hda: DMA timeout error, is it a problem ? Message-ID: <46D2A1BE.3060106@snurf.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Guido Heumann wrote:
> Shams Fantar schrieb:
>
>> I think that the hard disk really has a hardware problem. I'm going to
>> change it.
>>
>> Subject closed. ;-)
>>
>> Thank you for your help.
>>
>> Regards,
>>
>>
>
> Another thing you could try before replacing the harddrive is replacing
> the IDE cable. I once had strange disk error messages caused by a flaky
> cable connection.
>
Already done. This test changes nothing. ;-)
> cheers,
> Guido
>
>
Shams -- Shams Fantar (http://snurf.info)

Date: Mon, 27 Aug 2007 12:05:42 +0200 From: Dan H <dunno@stoptrick.com> To: Debian User Mailing List <debian-user@lists.debian.org> Subject: SATA vs PATA Message-ID: <20070827120542.04ef3476@kir.physnet.uni-hamburg.de> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello, now I have this camcorder and want to dump/edit some family videos on it, and before I know it my 160GB harddisk is full. So I need some extra GB. Should I go Serial-ATA or good ol' Parallel-ATA? How do the two compare in terms of data throughput and Linux kernel support? Just went and checked my local dealer online -- PATA seems to be as good as gone. Haven't bought any computer stuff lately. So it's probably gonna be SATA anyway, but maybe someone has some experience to share. Kernel is some current Debian 2.6.-k7 flavour. Thanks, --D. End of debian-user-digest Digest V2007 Issue #2257 ************************************************** Received on Mon Aug 27 06:39:09 2007

This message: [ Message body ]
Next message: debian-user-digest-request(at)lists.debian.org: "debian-user-digest Digest V2007 #2259"
Previous message: debian-user-digest-request(at)lists.debian.org: "debian-user-digest Digest V2007 #2256"

Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ] [ By messages with attachments ]

This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 07:54:12 EDT