Re: Decentralized reliable instant messaging?
I think you looking for TOX! Visit TOX Project website: https://tox.chat On Sat, Aug 13, 2016 at 7:19 AM, Stefan Monnier wrote: > I'm looking for a decentralized instant message system (e.g. XMPP, SIP, > ...) where I can be sure that I receive all messages, even if I'm not > connected when the message is sent [ Obviously, I'll only receive them > when I'm back online. ] > > IIUC there is some XMPP features that allow such reliable delivery, but > it seems that it's not widely supported by clients. What Debian > clients, using which protocols, can provide reliable instant messaging? > > > Stefan > > > PS: Bonus points if that feature is also available on an Android > application that's Free Software. > >
Bash crashed in a alias to view markdown
Hello guys,
This alias caused bash to crash:
http://sprunge.us/PMhe
The alias is now corrected to check if `$1` is empty (*), but still, bash
should not crash like this.
I'm not opening a bug report because I don't really know (nor have the time
to find out) how/where this things are correlated. Anyway, I still think
this information would be useful to those who are working closely to bash
maintainers, so here it is, shared with you.
I hope this helps.
Thank you,
Beco.
PS. All I did was calling the alias without an argument (a file to open)
and pressing CONTROL-C to interrupt it, twice in a row. And bang, crash.
(*) The new alias, in case someone finds it useful to view markdown files:
alias mdless='_mdless() { if [ -n "$1" ] ; then if [ -f "$1" ] ; then cat
<(echo ".TH $1 7 `date --iso-8601` Dr.Beco Markdown") <(pandoc -t man $1 )
| groff -K utf8 -t -T utf8 -man 2>/dev/null | less ; fi ; fi ;}; _mdless '
Just add to your ~/.bash_aliases ;)
--
Dr Beco
A.I. researcher
"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan
GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09
Re: Decentralized reliable instant messaging?
rhkra...@gmail.com writes: > On Tuesday, August 16, 2016 10:47:35 AM Stefan Monnier wrote: > > >> I'm looking for a decentralized instant message system (e.g. XMPP, SIP, > > >> ...) where I can be sure that I receive all messages, even if I'm not > > >> connected when the message is sent [ Obviously, I'll only receive them > > >> when I'm back online. ] > > > > > > I believe that's called "electronic mail" or "email". > > > > There's that, and there are SMS messages as well, indeed. SMS probably does not count as a decentralised system in the sense the original poster is seeking. > Google Voice Google's services are highly centralised to a single vendor. -- \ “Pray, v. To ask that the laws of the universe be annulled in | `\ behalf of a single petitioner confessedly unworthy.” —Ambrose | _o__) Bierce, _The Devil's Dictionary_, 1906 | Ben Finney
Re: Decentralized reliable instant messaging?
On Tuesday, August 16, 2016 10:47:35 AM Stefan Monnier wrote: > >> I'm looking for a decentralized instant message system (e.g. XMPP, SIP, > >> ...) where I can be sure that I receive all messages, even if I'm not > >> connected when the message is sent [ Obviously, I'll only receive them > >> when I'm back online. ] > > > > I believe that's called "electronic mail" or "email". > > There's that, and there are SMS messages as well, indeed. > But email is a lot more heavyweight and drowned in spam (e.g. most > people don't get notified right away when they receive an email > message), and SMS is basically limited to cell-phone only (you can find > services that let you send SMS messages from something like a SIP > account, but I haven't found any corresponding service for the > reception of SMS messages, except some that just drop the SMS message > if the SIP delivery cannot be performed because you're not connected). Google Voice can send and receive text messages (to and from cell phones or other google voice users)--iiuc, those are SMS messages. Currently I don't have anything set up to notify me, but I asume (I know) that can be done within a web browser.
Re: exim4 under jessie vs wheezy
> What it does under jessie: > > (1) and (3) still work. (2) does not. I have never seen any mail to root but > the people who maintain smtp.ecn.purdue.edu claim that mail to root on my > machines gets sent to root@empty. ^^^ meaning precisely? (ie using quotes if necessary). I'd have to get back to you on this. I had asked this question of our sysadmins and they gave me the above answer. I'll ask them for a more precise answer. Here is their reply: It was literally "root@empty", according to the mail server logs. The mail servers could not resolve "empty" as a host name and rejected the message. Jeff (http://engineering.purdue.edu/~qobi)
ISO Verif: Is the "default 512 block size" == "I/O sector" size?
Thomas, You said earlier that 512 is the default block size. But I looked up that "bs" also refers to block size. e.g. "dd bs=1M count=613" Analyzing: bs=1M; 1M = 1Mibibyte; 1Mibibyte = 1048576 bytes; 1048576 bytes / 512 bytes/block = 2048 blocks Thus 1M = 2048 blocks of 512 bytes/block 613 * 2048 = 1255424. So it appears that we have two "block sizes". "dd" has its block size, "bs"; and then there is some foreign "other" block size. But after perusing the stats of my sdb drive: [code] $ fdisk -l ... Disk /dev/sdb: 16.4 GB, 16358768640 bytes 255 heads, 63 sectors/track, 1988 cylinders, total 31950720 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x6350107e Device Boot Start End Blocks Id System /dev/sdb1 * 0 1255423 627712 0 Empty /dev/sdb2 8196 8803 304 ef EFI (FAT-12/16/32) [/code] it seems that the 512 bytes/block isn''t some foreign "other" block size (not changeable), but is the "I/O" or "sector" size. This seems to inherently be 512 bytes/sector. More specifically from the above stats: [code] 255 heads, 63 sectors/track, 1988 cylinders, total 31950720 sectors Units = sectors of 1 * 512 = 512 bytes [/code] we can calculate 255 * 63 * 1988 = 31937220, which is really close to the above "31950720", and then 31937220 * 512 = 16351856640, where "16351856640" is really close to the above 16358768640. Is my hypothesis that the "512 block size" is the "I/O" or "sector" size correct? Sincerely, Andrew F Comly Original Message Subject: Re: [off list] iso verification: results - successful but still bewildered Local Time: August 15, 2016 11:57 AM UTC Time: August 15, 2016 11:57 AM From: scdbac...@gmx.net To: andrew.co...@protonmail.com Hi, > May I organize this info and post Be invited. But take care not to produce misleading rumors in this swamp of fuzzy image ends and various block sizes. The decisive point with checksumming from CD, DVD, or USB stick is to process exactly the original size as it was when Debian computed its checksum lists. This size can be learned from the size of the ISO image file, if you have it in reach: $ ls -l debian-8.5.0-i386-lxde-CD-1.iso -rw-r--r-- 1 thomas thomas 642777088 Jun 4 16:11 debian-8.5.0-i386-lxde-CD-1.iso Your number came from dd's count when copying the ISO onto USB stick. That's equivalent to the "ls -l" way of learning the size. Or you take it from the inner info of the ISO 9660 filesystem if you only have some media where it is stored beginning at block 0: $ /sbin/isosize /dev/sdb 642777088 $ /sbin/isosize /dev/sr0 642777088 These counts are in bytes and would make an awfully slow read run if used as block count with program "dd": $ dd if=/dev/sdb bs=1 count=642777088 | sha512sum We can safely divide it by 2048 and use bs=2048, because 2048 is the block size which the entrails of the ISO use for addressing data and counting the filesystem size. $ expr 642777088 / 2048 313856 $ dd if=/dev/sdb bs=2048 count=313856 | sha512sum Larger blocksizes are suitable only if they yield no remainder when they divide the byte size. (Caution, "expr" does not show division remainders or fractions.) If you want, we can explore why the script check_debian_iso did not work for you and enhance it for the next user with the same issue. I'd then ask Steve McIntyre to find it some place on the Debian servers and to change the wiki link. Have a nice day :) Thomas
Re: exim4 under jessie vs wheezy
Thanks for your help. > # mail sent by smarthost; received via SMTP or fetchmail > # default hostname > # default 127.0.0.1 ; ::1 > # blank > # blank > # smtp.ecn.purdue.edu > # yes > # purdue.edu > # no > # mbox format in /var/mail > # no What do you actually have here? (ie which ends up in /etc/mailname) Note that I didn't change this. I accepted the default when the question was asked. qobi@upplysingaoflun>all+n cat /etc/mailname tlamachilistli: tlamachilistli.ecn.purdue.edu zhineng: zhineng.ecn.purdue.edu chino: chino.ecn.purdue.edu buddhi: buddhi.ecn.purdue.edu seykhl: seykhl.ecn.purdue.edu maniishaa: maniishaa.ecn.purdue.edu alykkyys: alykkyys.ecn.purdue.edu mohio: mohio.ecn.purdue.edu seulki: seulki.ecn.purdue.edu rongovosai: rongovosai.ecn.purdue.edu faisneis: faisneis.ecn.purdue.edu jalitusteabe: jalitusteabe.ecn.purdue.edu cuddwybodaeth: cuddwybodaeth.ecn.purdue.edu istihbarat: istihbarat.ecn.purdue.edu wywiad: wywiad.ecn.purdue.edu upplysingaoflun: upplysingaoflun.ecn.purdue.edu verstand: verstand.ecn.purdue.edu arivu: arivu.ecn.purdue.edu perisikan: perisikan.ecn.purdue.edu aruco: aruco.ecn.purdue.edu save: save.ecn.purdue.edu akili: akili.ecn.purdue.edu aql: aql.ecn.purdue.edu qobi@upplysingaoflun> > What it does under jessie: > > (1) and (3) still work. (2) does not. I have never seen any mail to root but > the people who maintain smtp.ecn.purdue.edu claim that mail to root on my > machines gets sent to root@empty. ^^^ meaning precisely? (ie using quotes if necessary). I'd have to get back to you on this. I had asked this question of our sysadmins and they gave me the above answer. I'll ask them for a more precise answer. (The Purdue maintained machines run Windows/MacOS/RHEL. This includes smtp.ecn.purdue.edu and the whole email infrastructure. The Purdue sysadmins don't know Debian. They are kind enough to let me maintain my own machines.) > What has changed from wheezy to jessie? As far as I can tell I am configuring > everything the same. > > How do I get mail to root to forward to q...@purdue.edu? Is there anything significant in /etc/mailnames ? I have no file named /etc/mailnames I only have a file named /etc/mailname The full contents of this file on each of my machines is shown above. Jeff (http://engineering.purdue.edu/~qobi)
Re: Compiling Canon LiDE 220 driver from source
On Tue 16 Aug 2016 at 22:45:29 +0100, Lisi Reisz wrote: [...Snip... The history is in previous mails]. > After a lot more wrong turnings and much agonising, thinking instead of > panicking (at last!) and retrying: > > root@Eros:/home/lisi/Sane-Files# scanimage -L > device `genesys:libusb:001:003' is a Canon LiDE 220 flatbed scanner > root@Eros:/home/lisi/Sane-Files# > > Thank you so much Brian and didier, especially for your patience. A splendid outcome and a victory for backporting! Thank you for the feedback and sticking with it until the end.
Re: Compiling Canon LiDE 220 driver from source
On Tuesday 16 August 2016 17:27:10 Brian wrote: > On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote: > > On Tuesday 16 August 2016 13:49:48 Brian wrote: > > > Mea culpa. Please see the apt-get manual: build-dep (no "s"). > > > > Thanks, both. :-) > > > > Everything now built, though there was an error at the end: > > > > Now running lintian... > > warning: the authors of lintian do not recommend running it with root > > privileges! > > You built the packages as root? Lintian would then run as root. There is > a warning about this. Can be ignored but 'debuild -us -uc' should be run > as a user. > > > W: libsane: package-name-doesnt-match-sonames libsane1 > > N: 2 tags overridden (1 error, 1 warning) > > Finished running lintian. > > root@Eros:/home/lisi/Sane-Files/sane-backends-1.0.25# > > Probably nothing to worry about when it comes to using sane. But I am no > expert here. > > Five .debs are built; only libsane, libsane-common and sane-utils need > to be installed with 'dpkg -i'. > > > And although sane-find-scanner continued to be able to see the scanner, > > scanimage -L continues determinedly not to see it. > > > > The Canon LiDE 220 is explicitly mentioned as being supported in the file > > sane-genesys.5, which is in /etc/sane.d > > At least 'sane-find-scanner' works. :) Note that its purpose is only to > find a scanner. The purpose of 'scanimage -L' is to discover whether > there is a backend which will drive the found scanner. As you say, it > should find yours is supported in genesys.conf. > > Check that 0x04a9 0x1906 in genesys.conf is matched by what the output > of 'lsusb' should show (04a9 1906). > > Make it easy for 'scanimage -L' and not have it have to search for a > backend to use: comment out or delete every line in dll.conf apart from > "genesys" and restart the sane service. > > Change USB ports for the scanner. USB2 or USB3? After a lot more wrong turnings and much agonising, thinking instead of panicking (at last!) and retrying: root@Eros:/home/lisi/Sane-Files# scanimage -L device `genesys:libusb:001:003' is a Canon LiDE 220 flatbed scanner root@Eros:/home/lisi/Sane-Files# Thank you so much Brian and didier, especially for your patience. Lisi
Re: Decentralized reliable instant messaging?
On Tue, Aug 16, 2016 at 10:47:35AM -0400, Stefan Monnier wrote: > >> I'm looking for a decentralized instant message system (e.g. XMPP, SIP, > >> ...) where I can be sure that I receive all messages, even if I'm not > >> connected when the message is sent [ Obviously, I'll only receive them > >> when I'm back online. ] > > I believe that's called "electronic mail" or "email". > > There's that, and there are SMS messages as well, indeed. > But email is a lot more heavyweight and drowned in spam (e.g. most > people don't get notified right away when they receive an email I consider this an absolute pro not a con. All os vendors seem that ADD is the way to go. Interrupting you with benign nonsense every 10 seconds. No wonder that the average attention span is ~ 2 seconds. The only advantage of most messaging protocols is presence awareness. In every other aspect e-mail is superior. > message), and SMS is basically limited to cell-phone only (you can find > services that let you send SMS messages from something like a SIP > account, but I haven't found any corresponding service for the > reception of SMS messages, except some that just drop the SMS message > if the SIP delivery cannot be performed because you're not connected). > > > Stefan > -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up
Thanks Pascal! On Aug 16, 2016, at 12:59 AM, Pascal Hambourg wrote: > Le 16/08/2016 à 09:03, Rick Thomas a écrit : >> >> Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces... >> Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on >> /run/network/ifstate.eth0 >> Aug 14 17:02:49 sheeva ifup[893]: RTNETLINK answers: File exists > > "RTNETLINK answers: File exists" typically happens when you try to add an > address or a route which is already exists with "ip", which is the tool used > internally by ifup. > >> However the interface *is* up: > > Yes but the configuration may not be complete. It happens that it is complete, but I understand that it might not be. > >> - /etc/network/interfaces >> # This file describes the network interfaces available on your system >> # and how to activate them. For more information, see interfaces(5). >> >> # The loopback network interface >> auto lo eth0 >> iface lo inet loopback >> >> # The primary network interface >> allow-hotplug eth0 >> iface eth0 inet static >> address 192.168.3.111 >> netmask 255.255.240.000 >> network 192.168.0.0 >> broadcast 192.168.15.255 >> gateway 192.168.1.1 > > Note that the network and broadcast options are not required. If missing, > they will be calculated from the address and net mask values. Thanks. I’ll keep that in mind for next time. No harm in leaving them in though, right? > >> iface eth0 inet6 static >> address 2001:1234:2d2:1:f2ad:4eff:fe00:3077 >> netmask 64 > > This IPv6 address looks like an autoconfigured address calculated from the > MAC address. You should not statically assign this kind of address. You are correct. I assumed that when the IPv4 address needed to be static, the same was true for the IPv6 address as well. I further assumed that declaring it to be inet6 static would prevent it from getting any address from the RA. Apparently not. Why do you say that I should not statically assign this kind of address? As long as it’s the same as it would be getting dynamically, is there any harm? (other than the one we’re observing here?) > > If a router in your network sends IPv6 Router Advertisements (RA) with the > prefix 2001:1234:2d2:1::/64, then the kernel may autoconfigure the same > address, so this could be the duplicate. > > “ip -6 addr" shows whether an IPv6 address was statically or dynamically > assigned. It seems that it is getting a dynamic address from the RA (Yes, it’s the same address as I am statically assigning.) Prior to the most recent Sid update, it did not get a dynamic address. Is that a bug? If so, is the bug in the previous behavior or the current behavior? can someone explain what the purpose of the change was? In any case, I commented out the inet6 stanza and now it boots without error. Also, IPv6 gets configured OK (dynamically). > > Note for Hans : the network and broadcast addresses are consistent with the > netmask. > Yes, for historical reasons I have machines on this LAN whose IPv4 addresses have 3rd octets in the range 0-15. The RFC1918 (192.168.xx.xx) address range is a true class B ( or “/16”, if you prefer cider notation) and it can be carved up any way you want. It’s often used as a bunch of class Cs ( or “/24”s) but that’s not mandatory. Rick PS: I’d like to leave this bug open until we can be sure we understand the reason that the behavior changed. This may be a hint that points to a timing glitch in the way systemd configures network interfaces that could cause more serious problems down the road.
Re: exim4 under jessie vs wheezy
On Tue 16 Aug 2016 at 09:19:48 (-0400), Jeffrey Mark Siskind wrote: > Appologies for the repost. I sent this yesterday and it hasn't yet appeared. > It may have been filtered out for some reason. > > I would appreciate some help configuring exim4. > > What I want: > > I have multiple machines that I maintain and have root access on. They have > domain ecn.purdue.edu and names like upplysingaoflun.ecn.purdue.edu and > tlamachilistli.ecn.purdue.edu. They have static IP addresses over > ethernet. Outgoing mail should go through smtp.ecn.purdue.edu which is a > machine that I don't maintain and don't have root access to. Incoming mail is > addressed to q...@purdue.edu (and alternatively q...@ecn.purdue.edu) and comes > to q...@dynamo.ecn.purdue.edu which is a machine that I have a user account on > but don't maintain and don't have root access on. I'd like to read it on, say, > upplysingaoflun.ecn.purdue.edu as user qobi. When I send mail from any machine > that I maintain, I'd like it to appear with a from: header of > q...@purdue.edu. Since my published email address is q...@purdue.edu (which > forwards to q...@ecn.purdue.edu and then to q...@dynamo.ecn.purdue.edu by > mechanisms that I have no control over). I have a .procmailrc file on > dynamo.ecn.purdue.edu that I want all email to go through. I also want all > mail to root on all of the machines that I maintain to go to q...@purdue.edu. > > What I have been doing until now: > > I have been running Debian on the machines that I maintain for a decade. I > recently upgraded from wheezy to jessie. I set up jessie with the same > configuration I had been using in wheezy and prior. > > All of the machines that I maintain have: > > root@tlamachilistli:~# cat /etc/exim4/update-exim4.conf.conf > # /etc/exim4/update-exim4.conf.conf > # > # Edit this file and /etc/mailname by hand and execute update-exim4.conf > # yourself or use 'dpkg-reconfigure exim4-config' > # > # Please note that this is _not_ a dpkg-conffile and that automatic changes > # to this file might happen. The code handling this will honor your local > # changes, so this is usually fine, but will break local schemes that mess > # around with multiple versions of the file. > # > # update-exim4.conf uses this file to determine variable values to generate > # exim configuration macros for the configuration file. > # > # Most settings found in here do have corresponding questions in the > # Debconf configuration, but not all of them. > # > # This is a Debian specific file > > dc_eximconfig_configtype='smarthost' > dc_other_hostnames='' > dc_local_interfaces='127.0.0.1 ; ::1' > dc_readhost='purdue.edu' > dc_relay_domains='' > dc_minimaldns='false' > dc_relay_nets='' > dc_smarthost='smtp.ecn.purdue.edu' > CFILEMODE='644' > dc_use_split_config='false' > dc_hide_mailname='true' > dc_mailname_in_oh='true' > dc_localdelivery='mail_spool' > root@tlamachilistli:~# > > The was obtained by running dpkg-reconfigure exim4-config and answering the > questions with the following: > > # mail sent by smarthost; received via SMTP or fetchmail > # default hostname > # default 127.0.0.1 ; ::1 > # blank > # blank > # smtp.ecn.purdue.edu > # yes > # purdue.edu > # no > # mbox format in /var/mail > # no What do you actually have here? (ie which ends up in /etc/mailname) > I set up /etc/exim4/passwd.client to have the password needed for > smtp.ecn.purdue.edu. > > I also set up /etc/aliases to forward root mail to q...@purdue.edu. > > root@tlamachilistli:~# cat /etc/aliases > # /etc/aliases > mailer-daemon: postmaster > postmaster: root > nobody: root > hostmaster: root > usenet: root > news: root > webmaster: root > www: root > ftp: root > abuse: root > noc: root > security: root > root: q...@purdue.edu > root@tlamachilistli:~# > > I run fetchmail as user qobi on upplysingaoflun to fetch mail from > dynamo.ecn.purdue.edu. > > Everything else is left at the default. > > What I do now: the same as I have done before. > > What it used to do under wheezy and before: > > 1. Mail from user qobi on any machine that I maintained would get a from: > header q...@purdue.edu. > 2. Mail to root on any machine that I maintained would get sent to > q...@purdue.edu. > 3. All mail to q...@purdue.edu gets put in /var/spool/mail/qobi on > upplysingaoflun.ecn.purdue.edu. > > What it does under jessie: > > (1) and (3) still work. (2) does not. I have never seen any mail to root but > the people who maintain smtp.ecn.purdue.edu claim that mail to root on my > machines gets sent to root@empty. ^^^ meaning precisely? (ie using quotes if necessary). > What has changed from wheezy to jessie? As far as I can tell I am configuring > everything the same. > > How do I get mail to root to forward to q...@purdue.edu? Is there anything
Re: Compiling Canon LiDE 220 driver from source
On Tuesday 16 August 2016 17:27:10 Brian wrote: > Five .debs are built; only libsane, libsane-common and sane-utils need > to be installed with 'dpkg -i'. Ah! I don't know about senior moments. I need a rest, some sleep and a new brain. Lisi
Re: Decentralized reliable instant messaging?
>> I'm looking for a decentralized instant message system (e.g. XMPP, SIP, >> ...) where I can be sure that I receive all messages, even if I'm not >> connected when the message is sent [ Obviously, I'll only receive them >> when I'm back online. ] > I believe that's called "electronic mail" or "email". There's that, and there are SMS messages as well, indeed. But email is a lot more heavyweight and drowned in spam (e.g. most people don't get notified right away when they receive an email message), and SMS is basically limited to cell-phone only (you can find services that let you send SMS messages from something like a SIP account, but I haven't found any corresponding service for the reception of SMS messages, except some that just drop the SMS message if the SIP delivery cannot be performed because you're not connected). Stefan
Re: Compiling Canon LiDE 220 driver from source
On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote: > On Tuesday 16 August 2016 13:49:48 Brian wrote: > > > > Mea culpa. Please see the apt-get manual: build-dep (no "s"). > > Thanks, both. :-) > > Everything now built, though there was an error at the end: > > Now running lintian... > warning: the authors of lintian do not recommend running it with root > privileges! You built the packages as root? Lintian would then run as root. There is a warning about this. Can be ignored but 'debuild -us -uc' should be run as a user. > W: libsane: package-name-doesnt-match-sonames libsane1 > N: 2 tags overridden (1 error, 1 warning) > Finished running lintian. > root@Eros:/home/lisi/Sane-Files/sane-backends-1.0.25# Probably nothing to worry about when it comes to using sane. But I am no expert here. Five .debs are built; only libsane, libsane-common and sane-utils need to be installed with 'dpkg -i'. > And although sane-find-scanner continued to be able to see the scanner, > scanimage -L continues determinedly not to see it. > > The Canon LiDE 220 is explicitly mentioned as being supported in the file > sane-genesys.5, which is in /etc/sane.d At least 'sane-find-scanner' works. :) Note that its purpose is only to find a scanner. The purpose of 'scanimage -L' is to discover whether there is a backend which will drive the found scanner. As you say, it should find yours is supported in genesys.conf. Check that 0x04a9 0x1906 in genesys.conf is matched by what the output of 'lsusb' should show (04a9 1906). Make it easy for 'scanimage -L' and not have it have to search for a backend to use: comment out or delete every line in dll.conf apart from "genesys" and restart the sane service. Change USB ports for the scanner. USB2 or USB3?
Re: Compiling Canon LiDE 220 driver from source
On Tuesday 16 August 2016 13:49:48 Brian wrote: > On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote: > > On Monday 15 August 2016 14:25:58 Brian wrote: > > > A good guide to backporting is at > > > > > > > > > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/ > > > > > > A deb-src line in sources.list for unstable is needed to do > > > > > > apt-get source libsane-common/unstable > > > > > > Then > > > > > > apt-get build-deps libsane-common/unstable > > > > > > should get the dependencies from stable to build libsane-common and > > > libsane. > > > > I have got stuck. Only slightly further on than I had already got stuck. > > (apt-get said it wasn't downloading what I had already downloaded!) > > > > root@Eros:/home/lisi/Sane-Files# apt-get build-deps > > libsane-common/testing E: Invalid operation build-deps > > Mea culpa. Please see the apt-get manual: build-dep (no "s"). Thanks, both. :-) Everything now built, though there was an error at the end: Now running lintian... warning: the authors of lintian do not recommend running it with root privileges! W: libsane: package-name-doesnt-match-sonames libsane1 N: 2 tags overridden (1 error, 1 warning) Finished running lintian. root@Eros:/home/lisi/Sane-Files/sane-backends-1.0.25# And although sane-find-scanner continued to be able to see the scanner, scanimage -L continues determinedly not to see it. The Canon LiDE 220 is explicitly mentioned as being supported in the file sane-genesys.5, which is in /etc/sane.d So it is there. Somewhere. But not being found. There is a lot of gumph there from my various efforts, and I am afraid of just deleting anything because I don't know what should be there! I haven't googled much yet. My husband is asking why I don't just upgrade to Stretch. Good question!! But this should be soluble reasonably easily. Lisi
exim4 under jessie vs wheezy
Appologies for the repost. I sent this yesterday and it hasn't yet appeared. It may have been filtered out for some reason. I would appreciate some help configuring exim4. What I want: I have multiple machines that I maintain and have root access on. They have domain ecn.purdue.edu and names like upplysingaoflun.ecn.purdue.edu and tlamachilistli.ecn.purdue.edu. They have static IP addresses over ethernet. Outgoing mail should go through smtp.ecn.purdue.edu which is a machine that I don't maintain and don't have root access to. Incoming mail is addressed to q...@purdue.edu (and alternatively q...@ecn.purdue.edu) and comes to q...@dynamo.ecn.purdue.edu which is a machine that I have a user account on but don't maintain and don't have root access on. I'd like to read it on, say, upplysingaoflun.ecn.purdue.edu as user qobi. When I send mail from any machine that I maintain, I'd like it to appear with a from: header of q...@purdue.edu. Since my published email address is q...@purdue.edu (which forwards to q...@ecn.purdue.edu and then to q...@dynamo.ecn.purdue.edu by mechanisms that I have no control over). I have a .procmailrc file on dynamo.ecn.purdue.edu that I want all email to go through. I also want all mail to root on all of the machines that I maintain to go to q...@purdue.edu. What I have been doing until now: I have been running Debian on the machines that I maintain for a decade. I recently upgraded from wheezy to jessie. I set up jessie with the same configuration I had been using in wheezy and prior. All of the machines that I maintain have: root@tlamachilistli:~# cat /etc/exim4/update-exim4.conf.conf # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='purdue.edu' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='smtp.ecn.purdue.edu' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='true' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' root@tlamachilistli:~# The was obtained by running dpkg-reconfigure exim4-config and answering the questions with the following: # mail sent by smarthost; received via SMTP or fetchmail # default hostname # default 127.0.0.1 ; ::1 # blank # blank # smtp.ecn.purdue.edu # yes # purdue.edu # no # mbox format in /var/mail # no I set up /etc/exim4/passwd.client to have the password needed for smtp.ecn.purdue.edu. I also set up /etc/aliases to forward root mail to q...@purdue.edu. root@tlamachilistli:~# cat /etc/aliases # /etc/aliases mailer-daemon: postmaster postmaster: root nobody: root hostmaster: root usenet: root news: root webmaster: root www: root ftp: root abuse: root noc: root security: root root: q...@purdue.edu root@tlamachilistli:~# I run fetchmail as user qobi on upplysingaoflun to fetch mail from dynamo.ecn.purdue.edu. Everything else is left at the default. What I do now: the same as I have done before. What it used to do under wheezy and before: 1. Mail from user qobi on any machine that I maintained would get a from: header q...@purdue.edu. 2. Mail to root on any machine that I maintained would get sent to q...@purdue.edu. 3. All mail to q...@purdue.edu gets put in /var/spool/mail/qobi on upplysingaoflun.ecn.purdue.edu. What it does under jessie: (1) and (3) still work. (2) does not. I have never seen any mail to root but the people who maintain smtp.ecn.purdue.edu claim that mail to root on my machines gets sent to root@empty. What has changed from wheezy to jessie? As far as I can tell I am configuring everything the same. How do I get mail to root to forward to q...@purdue.edu? Thanks, Jeff (http://engineering.purdue.edu/~qobi)
Re: Compiling Canon LiDE 220 driver from source
On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote: > On Monday 15 August 2016 14:25:58 Brian wrote: > > > > A good guide to backporting is at > > > > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/ > > > > A deb-src line in sources.list for unstable is needed to do > > > > apt-get source libsane-common/unstable > > > > Then > > > > apt-get build-deps libsane-common/unstable > > > > should get the dependencies from stable to build libsane-common and > > libsane. > > I have got stuck. Only slightly further on than I had already got stuck. > (apt-get said it wasn't downloading what I had already downloaded!) > > root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing > E: Invalid operation build-deps Mea culpa. Please see the apt-get manual: build-dep (no "s").
usedlaptopsinhyderabad
thanks for sharing information http://usedlaptopsinhyderabad.in/ -- View this message in context: http://debian.2.n7.nabble.com/Gigabyte-BRIX-with-Debian-Linux-tp3422783p3912426.html Sent from the Debian User mailing list archive at Nabble.com.
Re: Compiling Canon LiDE 220 driver from source
Le 16/08/2016 à 13:57, Lisi Reisz a écrit : > I have got stuck. Only slightly further on than I had already got stuck. > (apt-get said it wasn't downloading what I had already downloaded!) > > root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing > E: Invalid operation build-deps [...] build-dep without s :-)
Re: Compiling Canon LiDE 220 driver from source
On Monday 15 August 2016 14:25:58 Brian wrote: > On Mon 15 Aug 2016 at 14:23:36 +0200, didier gaumet wrote: > > Le 15/08/2016 à 12:42, Lisi Reisz a écrit : > > > Thanks, didier. That is nice to know. > > > > > > So it should be in the up-to-date tar ball, if I were to succeed in > > > sorting that out. But are you suggesting that I would do better to > > > backport from Stretch? I had decided that the tar ball would be > > > simpler and more sure. But perhaps now is the time to learn to > > > backport!! > > > > > > Lisi > > > > being lazy nowadays, if possible I avoid any source code compilation ;-) > > > > libsane-common unavailable in backports, I don't know if this could be > > profitable to you to backport it yourself. > > A good guide to backporting is at > > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/ > > A deb-src line in sources.list for unstable is needed to do > > apt-get source libsane-common/unstable > > Then > > apt-get build-deps libsane-common/unstable > > should get the dependencies from stable to build libsane-common and > libsane. I have got stuck. Only slightly further on than I had already got stuck. (apt-get said it wasn't downloading what I had already downloaded!) root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing E: Invalid operation build-deps root@Eros:/home/lisi/Sane-Files# dpkg-checkbuilddeps. bash: dpkg-checkbuilddeps.: command not found root@Eros:/home/lisi/Sane-Files# aptitude show apt Package: apt Essential: yes State: installed Automatically installed: no Version: 1.0.9.8.3 And somewhere while googling (I can't find it again!) I saw that build-deps is only in apt >= to 0.5. So I should have it. I'm going to go and get lunch. :-( I have an invalid husband. The last thing I need is him back in hospital. Thanks for the help. I'll google some more after lunch. Lisi > > > you could test a stable/testing mix in your sources.list with pinning > > preferences to follow sane in testing. > > or you could stay stable and try a quick and dirty trick in jessie by > > jnserting: > > > > # Canon LiDE 220 > > usb 0x04a9 0x190f > > > > in your /etc/sane.d/genesys.conf: I don't know how is designed the > > genesys backend, so maybe it is sufficient to obtain a functionning > > scanner, minus the LiDE220 specificities? > > I reckon the second approach will not work because the libraries need > an adjustment too.
Re: LibreOffice calc - slowdown
On Mon, 15 Aug 2016 23:17:15 +0200 Rene Engelhard wrote: Hello Rene, >ihttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832495, maybe? Yes, that's the one. Thanks for the pointer. I'm clearly going to have to improve my search skills on the BTS, as that bug existed when I looked for info. Obviously, I failed to find it. >Wait for 5.2.1 (rcX). Given it will need a round through NEW I'll Wait it is. Thank you once again, Rene. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Walking through town is quite scary I Predict A Riot - Kaiser Chiefs pgppJ84OfyMsv.pgp Description: OpenPGP digital signature
Re: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up
Le 16/08/2016 à 09:03, Rick Thomas a écrit : Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces... Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on /run/network/ifstate.eth0 Aug 14 17:02:49 sheeva ifup[893]: RTNETLINK answers: File exists "RTNETLINK answers: File exists" typically happens when you try to add an address or a route which is already exists with "ip", which is the tool used internally by ifup. However the interface *is* up: Yes but the configuration may not be complete. - /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo eth0 iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.168.3.111 netmask 255.255.240.000 network 192.168.0.0 broadcast 192.168.15.255 gateway 192.168.1.1 Note that the network and broadcast options are not required. If missing, they will be calculated from the address and netmask values. iface eth0 inet6 static address 2001:1234:2d2:1:f2ad:4eff:fe00:3077 netmask 64 This IPv6 address looks like an autoconfigured address calculated from the MAC address. You should not statically assign this kind of address. If a router in your network sends IPv6 Router Advertisements (RA) with the prefix 2001:1234:2d2:1::/64, then the kernel may autoconfigure the same address, so this could be the duplicate. "ip -6 addr" shows whether an IPv6 address was statically or dynamically assigned. Note for Hans : the network and broadcast addresses are consistent with the netmask.
Re: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up
Hi Thomas, yes, had this problem some time ago, but forgot about the reason. I believe, it was something with my network settings and network-manager. Your interfaces looks strange, is this correct? See my comments at your configuration, but maybe I am wrong: > Anybody else seen this? (Submitted as Bug#834376) > > - /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo eth0 > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > iface eth0 inet static > address 192.168.3.111 > netmask 255.255.240.000 > network 192.168.0.0 > broadcast 192.168.15.255 > gateway 192.168.1.1 > Shouldn't it be so? network 192.168.3.0 broadcast 192.168.3.255 gateway 192.168.3.1 Looks somehow weired for me, but on the other side I do not know your environment, of course, and maybe your settings are correct. Good luck! Hans
ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up
Anybody else seen this? (Submitted as Bug#834376) Updated to latest debian Sid After boot is completed we see: rbthomas@sheeva:~$ systemctl status networking.service * networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/networking.service.d `-50-insserv.conf-$network.conf Active: failed (Result: exit-code) since Sun 2016-08-14 17:02:50 PDT; 39min ago Docs: man:interfaces(5) Main PID: 893 (code=exited, status=1/FAILURE) Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces... Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on /run/network/ifstate.eth0 Aug 14 17:02:49 sheeva ifup[893]: RTNETLINK answers: File exists Aug 14 17:02:49 sheeva ifup[893]: Failed to bring up eth0. Aug 14 17:02:50 sheeva systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Aug 14 17:02:50 sheeva systemd[1]: Failed to start Raise network interfaces. Aug 14 17:02:50 sheeva systemd[1]: networking.service: Unit entered failed state. Aug 14 17:02:50 sheeva systemd[1]: networking.service: Failed with result 'exit-code'. However the interface *is* up: rbthomas@sheeva:~$ /sbin/ifconfig eth0: flags=4163 mtu 1500 inet 192.168.3.111 netmask 255.255.240.0 broadcast 192.168.15.255 inet6 2001:1234:2d2:1:f2ad:4eff:fe00:3077 prefixlen 64 scopeid 0x0 inet6 fe80::f2ad:4eff:fe00:3077 prefixlen 64 scopeid 0x20 ether f0:ad:4e:00:30:77 txqueuelen 1000 (Ethernet) RX packets 6897 bytes 738138 (720.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4556 bytes 427016 (417.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 85 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1 (Local Loopback) RX packets 2 bytes 98 (98.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 98 (98.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Here is a possibly relevant config file - /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo eth0 iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.168.3.111 netmask 255.255.240.000 network 192.168.0.0 broadcast 192.168.15.255 gateway 192.168.1.1 iface eth0 inet6 static address 2001:1234:2d2:1:f2ad:4eff:fe00:3077 netmask 64 - /etc/network/interfaces
