date:20161203


On 12/03/2016 07:32 PM, Fred wrote:

On 12/03/2016 01:20 PM, Brian wrote:

On Sat 03 Dec 2016 at 19:20:18 +, Lisi Reisz wrote:


On Saturday 03 December 2016 18:09:50 Jape Person wrote:

Hi,

I'm replying to myself at the top of the thread because I saw
-- out of the corner of my eye -- that there were two recent
additions to the thread.

Unfortunately, a) I use POP3 and download all my mail
immediately from the server, b) my neighbor's Maine Coon cat,
Mr. Potay-Toes, just visited me and ran all 28 of his toes
across my keyboard. (Yes, he's polydactyl, and about 25 pounds
at that.) Somehow he managed a permanent deletion of all the
mail I had just downloaded.

These posts were made within the past 12 hours. If the kind
people who made those posts could be troubled to re-issue them
I'd appreciate it. Or, at least be aware that I'm not ignoring
your messages. I just don't have them any more.

Best, JP

You can read them in the archives:
https://lists.debian.org/debian-user/2016/11/msg00783.html

And here is another one signed by you:
https://lists.debian.org/debian-user/2016/11/msg00842.html

Or the thread itself:
https://lists.debian.org/debian-user/2016/11/thrd2.html#00842

Eminently sensible. as usual. Replete with information and
guidance. The advice cannot be faulted.

But has any thought been given to the cat's feelings? It must be
suffering terrible pangs of regret and remorse. I do not think we
should put it through any more humiliation than it has suffered
already after realising it had inadvertantly deleted one of my
mails.

Just don't let it get anywhere near apt cat /dev/zero > ...


A cat is the center of the Universe.  It doesn't have pangs of regret
or remorse.  I recommend:  mv cat >/dev/null

Fred B.



Mr. Potay-Toes is a cuddler, and I don't have the heart to turn him 
away. It's just as well. He weighs somewhere around 25 pounds and has 28 
claw-laden toes. I've never had a dispute with him, but I suspect he 
would best me in armed combat if it came to that.


On the other hand, he has a fine temperament and is one of the few cats 
I've known who enjoys a bath followed by a hair dryer. Though he's large 
he's always careful to avoid upsetting items on the window sill or book 
shelf and has a dainty touch when seating himself on a person. He's 
quite civilized, if a bit of a bother around a keyboard.


He spends more time on my lap in our condo than he does in his mistress' 
condo. My wife says it's because I'm large and warm. It's possible that 
cats view humans as heated furniture.


Those of us who are fortunate enough to know cats must be prepared to 
accept an occasional inconvenience in exchange for the privilege.

Re: hplip and use of the "driver plugin"

2016-12-03 Thread Fred


On 12/03/2016 01:20 PM, Brian wrote:

On Sat 03 Dec 2016 at 19:20:18 +, Lisi Reisz wrote:


On Saturday 03 December 2016 18:09:50 Jape Person wrote:

Hi,

I'm replying to myself at the top of the thread because I saw -- out of
the corner of my eye -- that there were two recent additions to the thread.

Unfortunately, a) I use POP3 and download all my mail immediately from
the server, b) my neighbor's Maine Coon cat, Mr. Potay-Toes, just
visited me and ran all 28 of his toes across my keyboard. (Yes, he's
polydactyl, and about 25 pounds at that.) Somehow he managed a permanent
deletion of all the mail I had just downloaded.

These posts were made within the past 12 hours. If the kind people who
made those posts could be troubled to re-issue them I'd appreciate it.
Or, at least be aware that I'm not ignoring your messages. I just don't
have them any more.

Best,
JP

You can read them in the archives:
https://lists.debian.org/debian-user/2016/11/msg00783.html

And here is another one signed by you:
https://lists.debian.org/debian-user/2016/11/msg00842.html

Or the thread itself:
https://lists.debian.org/debian-user/2016/11/thrd2.html#00842

Eminently sensible. as usual. Replete with information and guidance.
The advice cannot be faulted.

But has any thought been given to the cat's feelings? It must be
suffering terrible pangs of regret and remorse. I do not think we
should put it through any more humiliation than it has suffered
already after realising it had inadvertantly deleted one of my
mails.

Just don't let it get anywhere near apt cat /dev/zero > ...

A cat is the center of the Universe.  It doesn't have pangs of regret or 
remorse.  I recommend:  mv cat >/dev/null


Fred B.

packages from http://snapshot.debian.org/ would not install (then did with dpkg)

2016-12-03 Thread Felix Miata

Using Jessie, as I was unable to discover how to install a pair of 
interdependent .debs from looking at the man pages for dpkg, gdebi, apt or 
aptitude, I tried to first fetch them with wget and then set up a local apt repo 
from them after finding

https://wiki.debian.org/HowToSetupADebianRepository
but it was no better help. Neither the string 'local file' nor the string 'local 
.deb' are to be found on that page. Trying various suggestions from web searches 
had me going in a circle of various errors. Somewhere along the way I saw 
something about finding out why various errors get generated trying, but I 
couldn't even find that again after finding a purpose for doing it. Among the 
errors: "Dependency is not satisfiable". The rest I don't remember. Eventually I 
stumbled onto the fact that 'dpkg install' does not equate to 'dpkg -i', and got 
the latter to install the two updates.


However, I'd still like to know:

1-how to capture the responsible why of a 'held back' or a 'Dependency is not 
satisfiable'


2-what part(s) of the lengthy HowToSetupADebianRepository page describe 
configuring use of already downloaded .deb files


3-whether one hold operation can be sufficient for getting either apt-get update 
or aptitude update to obey it, and if so, how/which

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: OT disco NTFS inmontable

2016-12-03 Thread Ricardo Delgado

El 3/12/2016 17:42, "Felix Perez"  escribió:
>
> El día 3 de diciembre de 2016, 15:57, martin ayos
>  escribió:
> > El día 3 de diciembre de 2016, 11:13, Rivera Valdez
> >  escribió:
> >> Una herramienta que en este tipo de situaciones me ha salvado y
> >> permitido acceder/recuperar todos los datos en dispositivos que tenían
> >> comportamientos como el que mencionas:
> >>
> >> http://www.cgsecurity.org/wiki/TestDisk
> >>
> >> «[TestDisk] was primarily designed to help recover lost partitions
> >> and/or make non-booting disks bootable again when these symptoms are
> >> caused by faulty software: certain types of viruses or human error
> >> (such as accidentally deleting a Partition Table). Partition table
> >> recovery using TestDisk is really easy. (...)»
> >>
> >> Me parece que incluso está en los repositorios de Debian, si no
recuerdo mal.
> >
> > Hola, gracias. Porbé test disk pero necesita escribir datos en el
> > disco y temo que se borren archivos.-
> >
>
> Si no tomaron precauciones anteriores es obvio que deberás correr riesgos.
>
> Probaste sacando una imagen y trabajar sobre la imagen?
>
>
> --
> usuario linux  #274354
> normas de la lista:  http://wiki.debian.org/es/NormasLista
> como hacer preguntas inteligentes:
> http://www.sindominio.net/ayuda/preguntas-inteligentes.html
>

A mi me suele ayudar ntfsfix en casos similares

Re: LVM RAID vs LVM over MD

2016-12-03 Thread Sven Hartge

Kamil Jońca  wrote:

> So far I used lvm with raid1 device as PV.

> Recently I have to extend my VG
> (https://lists.debian.org/debian-user/2016/11/msg00909.html)

> and I read some about lvm.  If I understand correctly, LVM have
> builtin RAID1 functionality.  And I wonder about migrating lvm over md
> --> (lvm with raid1) over physical hard drive partitions.

My last information on the RAID1 code in LVM is, that it is inferior to
the one in MD.

The MD code for example is able to fix broken sectors by reading the data
from the other disk, overwriting the sector on the broken disk with the
correct data, trying to get the drive to remap the sector.

Also, the last time I checked (which was a few years ago, so take my
advise with a bit of caution) the LVM code had no feature to do a
regular scrubbing of the RAID, detecting bit-rot in advance.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

2016-12-03 Thread Steven Mainor

Yeah the card I was referring to was just a simple microSD card like what you 
would put in your camera. I was running a normal install of debian without any 
kind of "live" or ram disk setup. Not ideal for flash without wear leveling


On December 3, 2016 7:59:48 AM EST, Jochen Spieker  
wrote:
>deloptes:
>> Steven Mainor wrote:
>> 
>>> I don't know if this helps answer #3 or not. I have ran Debian from
>a
>>> microSD flash card before but the card reader was attached via USB.
>>> 
>>> It didn't last very long before the flash card degraded. I think
>running
>>> an operating system on flash used up the read/write cycles too
>quickly.
>>> I eventually decided to find another solution. But it may not be an
>>> issue for your use case.
>>> 
>> I don't think so. I have a low power industrial pc used as firewall.
>It runs
>> on Compact Flash card for >6y now. I recall there were at least
>10
>> write cycles per sector and self diagnostic, so I would suspect
>something
>> else would be the problem.
>
>CF cards were much more clever from the beginning compared to cheaper
>alternatives (like SSD or MMC cards). I would expect them to have
>better
>wear levelling than a common SD card.
>
>J.
>-- 
>When I get home from the supermarket I don't know what to do with all
>the
>plastic.
>[Agree]   [Disagree]
>

--
Steven Mainor

Re: LVM RAID vs LVM over MD

2016-12-03 Thread Henrique de Moraes Holschuh

On Sat, 03 Dec 2016, Kamil Jońca wrote:
> If I understand correctly, LVM have builtin RAID1 functionality.
> And I wonder about migrating
> lvm over md --> (lvm with raid1) over physical hard drive partitions.
> 
> Any cons?

Yes, many.  Don't do it.

-- 
  Henrique Holschuh

Re: package version searching

2016-12-03 Thread Frank


Op 03-12-16 om 21:54 schreef Felix Miata:

1-How can I get similar results from apt as I get from zypper?


No idea whether that's possible.


2-How can I discover if versions between 4.8.13 and 4.8.18 are available
somewhere?


I would look here: http://snapshot.debian.org/package/mc/

Regards,
Frank

Re: package version searching

2016-12-03 Thread Joe

On Sat, 3 Dec 2016 15:54:55 -0500
Felix Miata  wrote:

> I'm looking to see what version(s) of mc are present in enabled repos
> on a Jessie installation. In openSUSE, I get desired results as
> follows:
> 
> # zypper se -s mc | grep 4.8
> il | mc| package| 4.8.17-114.1 | x86_64 | (System
> Packages) vl | mc| package| 4.8.15-5.1   | x86_64
> | Update vl | mc| package| 4.8.14-3.8   | x86_64
> | OSS | mc| srcpackage | 4.8.15-5.1   | noarch |
> Update l | mc-lang   | package| 4.8.15-5.1   | noarch |
> Update l | mc-lang   | package| 4.8.14-3.8   | noarch |
> OSS
> 
> I can see by looking on
> http://mirrors.us.kernel.org/debian/pool/main/m/mc/
> that 4.8.13 and 4.8.18 are present.
> 
> I have
> deb http://ftp.debian.org/debian jessie-backports main
> in /etc/apt/sources.list.d/backports.list
> but attempts to find anything other than 4.8.13 with apt-cache, apt
> list or apt show have proven futile.
> 
> 1-How can I get similar results from apt as I get from zypper?
> 
> 2-How can I discover if versions between 4.8.13 and 4.8.18 are
> available somewhere?
> 
> My underlying problem is 4.8.13 and 4.8.18 have problem bugs that are
> solved or not yet arisen in 4.8.15 thru 4.8.17.

http://snapshot.debian.org/binary/mc/

-- 
Joe

package version searching

2016-12-03 Thread Felix Miata

I'm looking to see what version(s) of mc are present in enabled repos on a 
Jessie installation. In openSUSE, I get desired results as follows:


# zypper se -s mc | grep 4.8
il | mc| package| 4.8.17-114.1 | x86_64 | (System Packages)
vl | mc| package| 4.8.15-5.1   | x86_64 | Update
vl | mc| package| 4.8.14-3.8   | x86_64 | OSS
   | mc| srcpackage | 4.8.15-5.1   | noarch | Update
 l | mc-lang   | package| 4.8.15-5.1   | noarch | Update
 l | mc-lang   | package| 4.8.14-3.8   | noarch | OSS

I can see by looking on
http://mirrors.us.kernel.org/debian/pool/main/m/mc/
that 4.8.13 and 4.8.18 are present.

I have
deb http://ftp.debian.org/debian jessie-backports main
in /etc/apt/sources.list.d/backports.list
but attempts to find anything other than 4.8.13 with apt-cache, apt list or apt 
show have proven futile.


1-How can I get similar results from apt as I get from zypper?

2-How can I discover if versions between 4.8.13 and 4.8.18 are available 
somewhere?

My underlying problem is 4.8.13 and 4.8.18 have problem bugs that are solved or 
not yet arisen in 4.8.15 thru 4.8.17.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: OT disco NTFS inmontable

2016-12-03 Thread Felix Perez

El día 3 de diciembre de 2016, 15:57, martin ayos
 escribió:
> El día 3 de diciembre de 2016, 11:13, Rivera Valdez
>  escribió:
>> Una herramienta que en este tipo de situaciones me ha salvado y
>> permitido acceder/recuperar todos los datos en dispositivos que tenían
>> comportamientos como el que mencionas:
>>
>> http://www.cgsecurity.org/wiki/TestDisk
>>
>> «[TestDisk] was primarily designed to help recover lost partitions
>> and/or make non-booting disks bootable again when these symptoms are
>> caused by faulty software: certain types of viruses or human error
>> (such as accidentally deleting a Partition Table). Partition table
>> recovery using TestDisk is really easy. (...)»
>>
>> Me parece que incluso está en los repositorios de Debian, si no recuerdo mal.
>
> Hola, gracias. Porbé test disk pero necesita escribir datos en el
> disco y temo que se borren archivos.-
>

Si no tomaron precauciones anteriores es obvio que deberás correr riesgos.

Probaste sacando una imagen y trabajar sobre la imagen?


-- 
usuario linux  #274354
normas de la lista:  http://wiki.debian.org/es/NormasLista
como hacer preguntas inteligentes:
http://www.sindominio.net/ayuda/preguntas-inteligentes.html

Re: hplip and use of the "driver plugin"


On 12/03/2016 03:20 PM, Brian wrote:

On Sat 03 Dec 2016 at 19:20:18 +, Lisi Reisz wrote:


On Saturday 03 December 2016 18:09:50 Jape Person wrote:

Hi,

I'm replying to myself at the top of the thread because I saw --
out of the corner of my eye -- that there were two recent
additions to the thread.

Unfortunately, a) I use POP3 and download all my mail immediately
from the server, b) my neighbor's Maine Coon cat, Mr. Potay-Toes,
just visited me and ran all 28 of his toes across my keyboard.
(Yes, he's polydactyl, and about 25 pounds at that.) Somehow he
managed a permanent deletion of all the mail I had just
downloaded.

These posts were made within the past 12 hours. If the kind
people who made those posts could be troubled to re-issue them
I'd appreciate it. Or, at least be aware that I'm not ignoring
your messages. I just don't have them any more.

Best, JP


You can read them in the archives:
https://lists.debian.org/debian-user/2016/11/msg00783.html

And here is another one signed by you:
https://lists.debian.org/debian-user/2016/11/msg00842.html

Or the thread itself:
https://lists.debian.org/debian-user/2016/11/thrd2.html#00842


Eminently sensible. as usual. Replete with information and guidance.
The advice cannot be faulted.

But has any thought been given to the cat's feelings? It must be
suffering terrible pangs of regret and remorse. I do not think we
should put it through any more humiliation than it has suffered
already after realising it had inadvertantly deleted one of my
mails.

Just don't let it get anywhere near apt cat /dev/zero > ...



The cat has expressed no remorse and, in fact, appears to be completely 
satisfied with himself. When he visits he interposes himself between me 
and my keyboard, countering every typing move with a ploy for physical 
attention.


Interestingly enough, this interference usually results in my messages 
containing fewer typos, probably because I have to be very deliberate in 
my efforts.


The creature is amazingly strong and agile, qualities which may have 
been enhanced by his almost continuous practice of tai cheese.


Oh well, no business shall be accomplished today.

Re: hplip and use of the "driver plugin"

2016-12-03 Thread Brian

On Sat 03 Dec 2016 at 19:20:18 +, Lisi Reisz wrote:

> On Saturday 03 December 2016 18:09:50 Jape Person wrote:
> > Hi,
> >
> > I'm replying to myself at the top of the thread because I saw -- out of
> > the corner of my eye -- that there were two recent additions to the thread.
> >
> > Unfortunately, a) I use POP3 and download all my mail immediately from
> > the server, b) my neighbor's Maine Coon cat, Mr. Potay-Toes, just
> > visited me and ran all 28 of his toes across my keyboard. (Yes, he's
> > polydactyl, and about 25 pounds at that.) Somehow he managed a permanent
> > deletion of all the mail I had just downloaded.
> >
> > These posts were made within the past 12 hours. If the kind people who
> > made those posts could be troubled to re-issue them I'd appreciate it.
> > Or, at least be aware that I'm not ignoring your messages. I just don't
> > have them any more.
> >
> > Best,
> > JP
> 
> You can read them in the archives:
> https://lists.debian.org/debian-user/2016/11/msg00783.html
> 
> And here is another one signed by you:
> https://lists.debian.org/debian-user/2016/11/msg00842.html
> 
> Or the thread itself:
> https://lists.debian.org/debian-user/2016/11/thrd2.html#00842

Eminently sensible. as usual. Replete with information and guidance.
The advice cannot be faulted.

But has any thought been given to the cat's feelings? It must be
suffering terrible pangs of regret and remorse. I do not think we
should put it through any more humiliation than it has suffered
already after realising it had inadvertantly deleted one of my
mails.

Just don't let it get anywhere near apt cat /dev/zero > ...

-- 
Debian - the Universal Opurrating System.
Brian.

Re: hplip and use of the "driver plugin"


On 12/03/2016 02:20 PM, Lisi Reisz wrote:

On Saturday 03 December 2016 18:09:50 Jape Person wrote:

Hi,

I'm replying to myself at the top of the thread because I saw -- out of
the corner of my eye -- that there were two recent additions to the thread.

Unfortunately, a) I use POP3 and download all my mail immediately from
the server, b) my neighbor's Maine Coon cat, Mr. Potay-Toes, just
visited me and ran all 28 of his toes across my keyboard. (Yes, he's
polydactyl, and about 25 pounds at that.) Somehow he managed a permanent
deletion of all the mail I had just downloaded.

These posts were made within the past 12 hours. If the kind people who
made those posts could be troubled to re-issue them I'd appreciate it.
Or, at least be aware that I'm not ignoring your messages. I just don't
have them any more.

Best,
JP


You can read them in the archives:
https://lists.debian.org/debian-user/2016/11/msg00783.html

And here is another one signed by you:
https://lists.debian.org/debian-user/2016/11/msg00842.html

Or the thread itself:
https://lists.debian.org/debian-user/2016/11/thrd2.html#00842

Lisi


Thanks, Lisi, but those parts of the archive didn't contain all of the 
messages. A couple of people in the thread replied directly to me and to 
other participants in the thread as well as to the thread itself. I'm 
guessing they may have used a method that broke the thread. I can't find 
the missing stuff in the archive, but I'm not going to try very hard. I 
have a horrible time reading this stuff through a browser interface.

Re: hplip and use of the "driver plugin"

2016-12-03 Thread Lisi Reisz

On Saturday 03 December 2016 18:09:50 Jape Person wrote:
> Hi,
>
> I'm replying to myself at the top of the thread because I saw -- out of
> the corner of my eye -- that there were two recent additions to the thread.
>
> Unfortunately, a) I use POP3 and download all my mail immediately from
> the server, b) my neighbor's Maine Coon cat, Mr. Potay-Toes, just
> visited me and ran all 28 of his toes across my keyboard. (Yes, he's
> polydactyl, and about 25 pounds at that.) Somehow he managed a permanent
> deletion of all the mail I had just downloaded.
>
> These posts were made within the past 12 hours. If the kind people who
> made those posts could be troubled to re-issue them I'd appreciate it.
> Or, at least be aware that I'm not ignoring your messages. I just don't
> have them any more.
>
> Best,
> JP

You can read them in the archives:
https://lists.debian.org/debian-user/2016/11/msg00783.html

And here is another one signed by you:
https://lists.debian.org/debian-user/2016/11/msg00842.html

Or the thread itself:
https://lists.debian.org/debian-user/2016/11/thrd2.html#00842

Lisi

Re: hplip and use of the "driver plugin"

2016-12-03 Thread Brian

On Fri 02 Dec 2016 at 18:38:12 -0500, Jape Person wrote:



> On 11/30/2016 10:57 AM, do...@mail.com wrote: 
> 
>   
> 
> >If you want you could try the Bother brand, there Linux support is
> >getting good from what I've read.
> >>
> Yes, I settled for a Brother MFC (MFC9340CDW) which is listed on
> openprinting.org as being supported, though still not officially included
> within foomatic. I suspect that their report of "perfect" support refers
> only to the printer, but I can make do with a printer and a copier if need
> 

The report (a user-contributed entry) says "works Perfectly". If you
were expecting "perfect" to mean "no non-free blobs" you are likely to  

be disappointed. Support for printing is offered by Brother. When you   

download their software you will agree that 



 ... Brother shall have no liability to disclose and/or distribute  

 the source code of the Software to User under any circumstances.   

 In no case shall the above license by Brother to modify, alter,

 translate or otherwise prepare derivative works of the Software be 

 construed as Brother's implied agreement or undertakings to

 disclose and/or distribute the source code of the Software.



Frying pan >>> Fire 



> be. The thing even does direct scanning to and printing from Android  
> 
> devices, so my wife's evil tablet can grab us a scan, if need be. And I do
> 
> know that -- if I change my mind about using a proprietary driver -- I can
> 
> always use the one that Brother supplies. 
> 
>   
> 
> I had found an HP MFC that didn't require the plugin, but by then I was kind  
> 
> of appalled by the direction that HP seems to be taking, and the Brother was
> cheaper and got very good reviews from CNET and PC Mag. Only time will tell   
> 
> if it was a good choice.  
> 


Pragmatism in action.   



-- 
Feline Felicitations
Brian.

LVM RAID vs LVM over MD

2016-12-03 Thread Kamil Jońca

So far I used lvm with raid1 device as PV.

Recently I have to extend my VG
(https://lists.debian.org/debian-user/2016/11/msg00909.html)

and I read some about lvm.
If I understand correctly, LVM have builtin RAID1 functionality.
And I wonder about migrating
lvm over md --> (lvm with raid1) over physical hard drive partitions.


Any cons?

KJ

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Wiesz, tryb tekstowy w Linuksie ma się tak do DOSu
jak F-117A do paralotni. (c) Dawid Kuroczko

Re: OT disco NTFS inmontable

2016-12-03 Thread martin ayos

El día 3 de diciembre de 2016, 11:13, Rivera Valdez
 escribió:
> Una herramienta que en este tipo de situaciones me ha salvado y
> permitido acceder/recuperar todos los datos en dispositivos que tenían
> comportamientos como el que mencionas:
>
> http://www.cgsecurity.org/wiki/TestDisk
>
> «[TestDisk] was primarily designed to help recover lost partitions
> and/or make non-booting disks bootable again when these symptoms are
> caused by faulty software: certain types of viruses or human error
> (such as accidentally deleting a Partition Table). Partition table
> recovery using TestDisk is really easy. (...)»
>
> Me parece que incluso está en los repositorios de Debian, si no recuerdo mal.

Hola, gracias. Porbé test disk pero necesita escribir datos en el
disco y temo que se borren archivos.-

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

Richard Owlett:
> On 12/3/2016 7:05 AM, Jochen Spieker wrote:
>> 
>> https://forums.lenovo.com/t5/ThinkPad-T61-and-prior-T-series/Boot-T61p-from-SD-card/m-p/261121/highlight/true#M41072
>> looks like you are out of luck.
>> 
> 
> Maybe. May be not. I suspect most of what I was thinking of by having
> Grub/LILO/??? reside on the HDD. The behind the scenes motivation is create
> a "project" that will serve as a learning experience.

Oh, sorry, in that case you should be able to simply install to your SD
cards. You just have to make sure not to confuse your boot loader,
especially when the configuration is automatically recreated while the
SD card is absent.

J.
-- 
I often blame my shortcomings on my upbringing.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

Pascal Hambourg:
> Le 03/12/2016 à 13:59, Jochen Spieker a écrit :
>> 
>> CF cards were much more clever from the beginning compared to cheaper
>> alternatives (like SSD or MMC cards). I would expect them to have better
>> wear levelling than a common SD card.
> 
> I would be surprised that a CF card be more clever than a SSD.

Sure. I meant to write "SD or MMC cards".

J.
-- 
It is not in my power to change anything.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

2016-12-03 Thread David Christensen


On 12/02/16 10:07, Richard Owlett wrote:

I have a well used Lenovo R61 Thinkpad whose sole raison d'etre is to
serve as a test platform for experiments which may spectacularly fail.

To quote a product description, it has:
  Card Reader
4 in 1 card reader
Supported Flash Memory
Memory Stick PRO, MultiMediaCard, SD Memory Card, xD-Picture Card

My local supplier has 32GB cards in stock. Not sure which of the above
flavors, as I just asked him what he had available that were compatible
with my hardware.

I'm pondering an application that could be accomplished with USB flash
drives.
It would be much "NICER" if that x GB were physically "inside" the
laptop's profile.

My questions:
  1. Can Debian (and to what extent) make use of that storage?
  2. Can Debian itself reside on that medium?
 I'm thinking in terms of changing look/feel/function/capabilities/...
 of the machine by swapping media before "power up".
 [The BIOS *DOES* have some capability to specify precedence of boot
devices.]
  3. Any Debian people using this capability who would care to comment?
 ["off list" replies fine]


I discovered that Debian can be installed to USB flash drives a few 
years ago, and now use them as a poor man's SSD system drive in my file 
server and backup server.



My favorite are SanDisk Ultra Fit 3.0 16 GB -- they have a compact form 
factor that only sticks out of the port ~1/4", they seek faster than a 
HDD (so random reads are faster than a HDD), and they write fast enough. 
 The downside is that they run hot and the machine can stutter when 
multitasking.  I provision them using 90% capacity (0.5 GB boot, 0.5 GB 
encrypted swap, 13.4 GB encrypted root) per SSD under-provisioning 
recommendations, but haven't done any benchmarking to see if it has any 
effect.  AFAIK there is no such thing as trim or secure erase on USB 
flash drives.  I haven't seen any problems with worn out blocks (yet).



As others have commented, I don't think SDHC cards are designed for a 
lot of erase/ write cycles.  STFW for the specifications to be sure.



I worked on a wearable computer product in late 2001 with a Windows 2000 
CF system drive.  The CF cards were chosen for motion/ vibration/ impact 
resistance and were expected to last at least as long as a HDD sitting 
in a desktop.  Again, STFW for specifications.



David

Re: hplip and use of the "driver plugin"


Hi,

I'm replying to myself at the top of the thread because I saw -- out of 
the corner of my eye -- that there were two recent additions to the thread.


Unfortunately, a) I use POP3 and download all my mail immediately from 
the server, b) my neighbor's Maine Coon cat, Mr. Potay-Toes, just 
visited me and ran all 28 of his toes across my keyboard. (Yes, he's 
polydactyl, and about 25 pounds at that.) Somehow he managed a permanent 
deletion of all the mail I had just downloaded.


These posts were made within the past 12 hours. If the kind people who 
made those posts could be troubled to re-issue them I'd appreciate it. 
Or, at least be aware that I'm not ignoring your messages. I just don't 
have them any more.


Best,
JP

Jessie upgrade without systemd [was: Debian *not very good]


Joe:

A fair number of wheezy systems will be servers, upgraded many times. 
Mine started out as sarge. What are the odds of such a system making 
the change to systemd without problems?




It depends.  But my own experience is that *if they were already using 
systemd* on Debian 7, it was a certainty that Debian bug #774153 will 
rear its ugly head in an upgrade to Debian 8.  I personally hit it with 
every single such system that I upgraded. I hit it on test systems 
first, of course.  So I had to put retaining shell access during the 
upgrade, to wait for the indeterminate point somewhere in the midst of 
about seven hundred package upgrades (alas, not at the same point on 
every machine) that one needs to go in and hand-run "daemon-reexec", 
into the upgrade procedure.

Re: Cómo activar placa de red (notebook)

2016-12-03 Thread José María


El 03/12/16 a las 15:05, Rivera Valdez escribió:

1) Muchas gracias a todos por la ayuda y orientación.

2) Efectivamente, la placa wireless ahora está funcionando y el
problema era que estaba bloqueada por hardware (en esta notebook es
especialmente incómodo porque las teclas F1, F2, etc., tienen
incorporadas acciones "multimedia", pero hay que elegir al bootear si
serán usadas como "multimedia" o como "función", de modo que hay que
bootear como "multimedia", activar la placa wireless, rebootear y
volver las teclas al modo normal... Creo que se pueden mapear
correctamente para que hagan una o la otra cosa añadiendo el uso de
una tecla "Fn" que tiene el teclado, pero ya es un laburo extra).

3) Sigue sin funcionar la placa de red. Y tengo la sospecha de que el
problema pase porque el nombre está duplicado. Fíjense:

root@debian:/home/user# lshw

   *-network
description: Wireless interface
product: Centrino Wireless-N 1030 [Rainbow Peak]
vendor: Intel Corporation
physical id: 0
bus info: pci@:03:00.0
logical name: wlan0
version: 34
serial: ac:72:89:0b:a1:2b
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi
driverversion=3.16.0-4-amd64 firmware=18.168.6.1 ip=10.0.0.8 latency=0
link=yes multicast=yes wireless=IEEE 802.11bgn
resources: irq:55 memory:f1b0-f1b01fff

   *-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit
Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@:06:00.0
logical name: eth0
version: 06
serial: 14:fe:b5:b8:11:13
size: 10Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master
cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt
1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes
driver=r8169 driverversion=2.3LK-NAPI duplex=half
firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes
port=MII speed=10Mbit/s
resources: irq:41 ioport:2000(size=256)
memory:f1804000-f1804fff memory:f180-f1803fff

root@debian:/home/user# ifconfig -a

eth0  Link encap:Ethernet  HWaddr 14:fe:b5:b8:11:13
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:857 errors:0 dropped:0 overruns:0 frame:0
  TX packets:857 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:145861 (142.4 KiB)  TX bytes:145861 (142.4 KiB)

wlan0 Link encap:Ethernet  HWaddr ac:72:89:0b:a1:2b
  inet addr:10.0.0.8  Bcast:10.0.0.255  Mask:255.255.255.0
  inet6 addr: fe80::ae72:89ff:fe0b:a12b/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:18545 errors:0 dropped:0 overruns:0 frame:0
  TX packets:16154 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:20507322 (19.5 MiB)  TX bytes:2233434 (2.1 MiB)

root@debian:/home/user# iwconfig

lono wireless extensions.

wlan0 IEEE 802.11bgn  ESSID:"Los Tanukis"
  Mode:Managed  Frequency:2.412 GHz  Access Point: 38:22:9D:0C:56:51
  Bit Rate=54 Mb/s   Tx-Power=15 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:4C61-5265-696E-6154-616E-756B-69
  Power Management:off
  Link Quality=54/70  Signal level=-56 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:6  Invalid misc:488   Missed beacon:0

eth0  no wireless extensions.


Aparece otra eth0 entre las interfaces wireless, ¿puede ser que al
estar el nombre duplicado el sistema no sepa qué hacer y la ignore?
¿Cómo puedo anular/eliminar la entrada eth0 de la lista de wireless
(iwconfig) para ver si es ese el problema?

4) Esta es la salida de interfaces:

root@debian:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback




Vale, eso es lo que normalmente debe tener ese archivo.




Les vuelvo a agradecer a todos. Ya es medio problema resuelto volver a
tener conexión (wireless), y si consigo resolver lo

Re: Manually installed packages

2016-12-03 Thread kamaraju kusumanchi

On Thu, Dec 1, 2016 at 2:06 PM, Greg Wooledge  wrote:
>
> P.S. http://wooledge.org/~greg/ds will sort the installed packages by
> size for you.  As you can see, many of us have been there, done that.
>

I would like to mention couple of things

1) You can do this by running dpigs in the debian-goodies package. For example

 % dpigs -H -n 5
 284.0M rstudio
 228.2M valgrind-dbg
 180.7M google-chrome-stable
 164.0M gcompris-data
 155.9M linux-image-3.16.0-4-amd64

where -H lists the size in human readable format, -n specifies the
number of packages to be listed.

BTW there is nothing wrong with having your own script. I do it all
the time:). But I thought it might help users who are not aware of
this functionality in Debian itself.

2) The results from your script and dpigs are not consistent. The
dpigs utility shows valgrind-dbg but your script does not show it.

% perl ds | head -n 5
rstudio   290867
google-chrome-stable  184994
gcompris-data 167973
linux-image-3.16.0-4-amd64159681
chromium  158398

 % dpigs -n 5
290867 rstudio
233675 valgrind-dbg
184994 google-chrome-stable
167973 gcompris-data
159681 linux-image-3.16.0-4-amd64

3) Please consider putting these type of scripts in a public
repository hosting services such as gitlab or github? They make it
easier for others to collaborate by reducing the barrier to report
bugs, suggest features, provide patches etc.,

thanks
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Document and LBC (Was: Debian *not very good)


Anonymous:

The error message:"A start job is running for LSB: Raise 
network interface (xx sec/no limit)". Where xx is a count up in 
seconds that never ends.




Greg Wooledge:

"LSB" stands for Linux Standard Base [...] I don't know what LSB has 
to do with Debian's boot process waiting for the network interfaces to 
be configured before proceeding.




The systemd doco doesn't cover it.  Here you go:

* http://unix.stackexchange.com/a/233581/5132

* http://unix.stackexchange.com/a/326354/5132

So xe has an old van Smoorenburg rc script whose description is "Raise 
network interface", and that old rc script not completing its work is 
the problem.

Re: Cómo activar placa de red (notebook)

> A ver, no pierdas el rumbo...
> iwconfig muestra las interfaces de red y si no tienen extensiones wifi
> te lo dice.
> Eso está bien, no es ninguna repetición.
>
> ¿Cómo configuras  la red?  usas networkmanger o el fichero interfaces a mano.
> Tendrás que ir al programita de configuración de red  y volver a
> configurar la red cableada que seguro que en su momento tocaste algo.

Según recuerdo, no, en su momento no toqué nada.
De hecho, la configuración de red (por networkmanager) que usaba,
sigue figurando igual que antes (pero no levanta, desde ya).
Algo puntual debe haber sucedido, porque incluso booteando Debian en
modo vivo, la conexión cableada no levanta automáticamente. De hecho,
se ve acá:

root@debian:/home/user# ifconfig -a

eth0  Link encap:Ethernet  HWaddr 14:fe:b5:b8:11:13
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:1863 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1863 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:234313 (228.8 KiB)  TX bytes:234313 (228.8 KiB)

wlan0 Link encap:Ethernet  HWaddr ac:72:89:0b:a1:2b
  inet addr:10.0.0.8  Bcast:10.0.0.255  Mask:255.255.255.0
  inet6 addr: fe80::ae72:89ff:fe0b:a12b/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:132718 errors:0 dropped:0 overruns:0 frame:0
  TX packets:109863 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:149460983 (142.5 MiB)  TX bytes:14652790 (13.9 MiB)

root@debian:/home/user# ifconfig eth0 10.0.0.3 netmask 255.255.255.0

root@debian:/home/user# route add default gateway 10.0.0.2

SIOCADDRT: File exists

root@debian:/home/user# ifconfig -a

eth0  Link encap:Ethernet  HWaddr 14:fe:b5:b8:11:13
  inet addr:10.0.0.3  Bcast:10.0.0.255  Mask:255.255.255.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:1863 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1863 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:234313 (228.8 KiB)  TX bytes:234313 (228.8 KiB)

wlan0 Link encap:Ethernet  HWaddr ac:72:89:0b:a1:2b
  inet addr:10.0.0.8  Bcast:10.0.0.255  Mask:255.255.255.0
  inet6 addr: fe80::ae72:89ff:fe0b:a12b/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:133185 errors:0 dropped:0 overruns:0 frame:0
  TX packets:110364 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:149686946 (142.7 MiB)  TX bytes:14716813 (14.0 MiB)

root@debian:/home/user# iwconfig

lono wireless extensions.

wlan0 IEEE 802.11bgn  ESSID:"xxx"
  Mode:Managed  Frequency:2.437 GHz  Access Point: 38:22:9D:0C:56:51
  Bit Rate=48 Mb/s   Tx-Power=15 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:4C61-5265-696E-6154-616E-756B-69
  Power Management:off
  Link Quality=57/70  Signal level=-53 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:149   Missed beacon:0

eth0  no wireless extensions.


Estoy conectado por wireless pero la conexión por cable sigue sin
activarse ni aparecer en Wicd (que además está setteado para cambiar
automáticamente a la conexión cableada si está disponible).

Re: systemd-resolved ipv6 resolving issue

2016-12-03 Thread Henning Follmann

On Fri, Dec 02, 2016 at 09:33:48AM -0500, Henning Follmann wrote:
> Hello,
> 
> I do have a weird issue. First the story.
> 
> I switch a new debian install (jessie) from the /etc/network/interfaces
> setup over to systemd-networkd. In addition I also enabled systemd-resolvd.
> The address assignment happens via DHCP and the nameserver is correctly
> entered into /run/systemd/resolve/resolv.conf which is linked to
> /etc/resolv.conf. Great!
> 
> This setup works as expected. I do have connectivity and I can resolve
> names.
> One thing changed, the host picked up a link local ipv6 ( FE80::/10).
> 
> 
> Now almost everything works, postfix has an issue though.
> postfix delivers everything via a smarthost and here it fails.
> The mails are stuck in the mailq and the error message is that it could not
> get a  record for the smarthost. That is actually correct because the
> smarthost has no  record in the zone it has however a A record.
> This I do not understand. Why is postfix stuck with a ipv6 nxdomain while
> it could resolv the normal ipv4 address.
> I checked with nslookup on that host. It resolves just fine. 
> ===
> nslookup -querytype= mail.itcfollmann.com
> Server: 10.0.11.212
> Address:10.0.11.212#53
> 
> *** Can't find mail.itcfollmann.com: No answer
> ===
> nslookup  mail.itcfollmann.com
> Server: 10.0.11.212
> Address:10.0.11.212#53
> 
> Name:   mail.itcfollmann.com
> Address: 52.7.212.38
> ==
> 
> Why does postfix even try to get the  record. Documentation states
> actually that if not provided t defaults to:
> inet_protocols = ipv4
> 
> 
> 

I solved this issue. It had nothing to do with ipv6.
However it had to do with the fact that systemd-resolved now is in control
of /etc/resolv.conf. 
And Postfix, at start up, copies this file into its chroot environment.
It however does not update when resolved updates.

Well in my first case the resolv.conf had no nameserver listed. So any
lookup failed. It just so happend to be an ipv6 of the smarthost. Thus the
error message that it could not find the server.


-H




-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Cómo activar placa de red (notebook)

2016-12-03 Thread fernando sainz

2016-12-03 15:05 GMT+01:00 Rivera Valdez :
> 1) Muchas gracias a todos por la ayuda y orientación.
>
> 2) Efectivamente, la placa wireless ahora está funcionando y el
> problema era que estaba bloqueada por hardware (en esta notebook es
> especialmente incómodo porque las teclas F1, F2, etc., tienen
> incorporadas acciones "multimedia", pero hay que elegir al bootear si
> serán usadas como "multimedia" o como "función", de modo que hay que
> bootear como "multimedia", activar la placa wireless, rebootear y
> volver las teclas al modo normal... Creo que se pueden mapear
> correctamente para que hagan una o la otra cosa añadiendo el uso de
> una tecla "Fn" que tiene el teclado, pero ya es un laburo extra).
>
> 3) Sigue sin funcionar la placa de red. Y tengo la sospecha de que el
> problema pase porque el nombre está duplicado. Fíjense:
>
> root@debian:/home/user# lshw
>
>*-network
> description: Wireless interface
> product: Centrino Wireless-N 1030 [Rainbow Peak]
> vendor: Intel Corporation
> physical id: 0
> bus info: pci@:03:00.0
> logical name: wlan0
> version: 34
> serial: ac:72:89:0b:a1:2b
> width: 64 bits
> clock: 33MHz
> capabilities: pm msi pciexpress bus_master cap_list
> ethernet physical wireless
> configuration: broadcast=yes driver=iwlwifi
> driverversion=3.16.0-4-amd64 firmware=18.168.6.1 ip=10.0.0.8 latency=0
> link=yes multicast=yes wireless=IEEE 802.11bgn
> resources: irq:55 memory:f1b0-f1b01fff
>
>*-network
> description: Ethernet interface
> product: RTL8111/8168/8411 PCI Express Gigabit
> Ethernet Controller
> vendor: Realtek Semiconductor Co., Ltd.
> physical id: 0
> bus info: pci@:06:00.0
> logical name: eth0
> version: 06
> serial: 14:fe:b5:b8:11:13
> size: 10Mbit/s
> capacity: 1Gbit/s
> width: 64 bits
> clock: 33MHz
> capabilities: pm msi pciexpress msix vpd bus_master
> cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt
> 1000bt-fd autonegotiation
> configuration: autonegotiation=on broadcast=yes
> driver=r8169 driverversion=2.3LK-NAPI duplex=half
> firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes
> port=MII speed=10Mbit/s
> resources: irq:41 ioport:2000(size=256)
> memory:f1804000-f1804fff memory:f180-f1803fff
>
> root@debian:/home/user# ifconfig -a
>
> eth0  Link encap:Ethernet  HWaddr 14:fe:b5:b8:11:13
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:857 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:857 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:145861 (142.4 KiB)  TX bytes:145861 (142.4 KiB)
>
> wlan0 Link encap:Ethernet  HWaddr ac:72:89:0b:a1:2b
>   inet addr:10.0.0.8  Bcast:10.0.0.255  Mask:255.255.255.0
>   inet6 addr: fe80::ae72:89ff:fe0b:a12b/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:18545 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:16154 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:20507322 (19.5 MiB)  TX bytes:2233434 (2.1 MiB)
>
> root@debian:/home/user# iwconfig
>
> lono wireless extensions.
>
> wlan0 IEEE 802.11bgn  ESSID:"Los Tanukis"
>   Mode:Managed  Frequency:2.412 GHz  Access Point: 38:22:9D:0C:56:51
>   Bit Rate=54 Mb/s   Tx-Power=15 dBm
>   Retry short limit:7   RTS thr:off   Fragment thr:off
>   Encryption key:4C61-5265-696E-6154-616E-756B-69
>   Power Management:off
>   Link Quality=54/70  Signal level=-56 dBm
>   Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>   Tx excessive retries:6  Invalid misc:488   Missed beacon:0
>
> eth0  no wireless extensions.
>
>
> Aparece otra eth0 entre las interfaces wireless, ¿puede ser que al
> estar el nombre duplicado el sistema no sepa qué hacer y la ignore?
> ¿Cómo puedo anular/eliminar la entrada eth0 de la lista de wireless
> (iwconfig) para ver si es ese el problema?
>
> 4) Esta es la salida de interfaces:
>
> root@debian:~# cat

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

2016-12-03 Thread Richard Owlett

On 12/3/2016 7:05 AM, Jochen Spieker wrote:

Richard Owlett:

On 12/2/2016 4:21 PM, Jochen Spieker wrote:

Beware that this might slightly increase power usage / reduce battery
life. That's at least my observation from a couple of years ago.
Depenging on the hardware, an SD card can keep a bus alive that could be
put to sleep otherwise. But if I would have to guess this is not an
issue for your use case.

No problem for medium term. It will sit on my desk next to my "regular"
machine.

That's what I thought.

2. Can Debian itself reside on that medium?
I'm thinking in terms of changing look/feel/function/capabilities/...
of the machine by swapping media before "power up".
[The BIOS *DOES* have some capability to specify precedence of boot
devices.]

Debian doesn't really care, but you would have to test whether your BIOS
can really boot from SD cards.

If it "looks" the same as a USB flash device, there should be no problem.

For Linux the bus doesn't really matter. But again, for your BIOS it
does. As far as I understand, that's hardware specific. Some card
readers are internally wired to USB which gives you a good chance to
boot from it. As far as I can see on the ThinkWiki
(http://www.thinkwiki.org/wiki/Category:R61 pointing to
http://www.thinkwiki.org/wiki/Ricoh_R5C843), the R61 is different.

https://forums.lenovo.com/t5/ThinkPad-T61-and-prior-T-series/Boot-T61p-from-SD-card/m-p/261121/highlight/true#M41072
looks like you are out of luck.

Maybe. May be not. I suspect most of what I was thinking of by
having Grub/LILO/??? reside on the HDD. The behind the scenes
motivation is create a "project" that will serve as a learning
experience.

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

2016-12-03 Thread Pascal Hambourg


Le 03/12/2016 à 13:59, Jochen Spieker a écrit :

deloptes:

Steven Mainor wrote:


I don't know if this helps answer #3 or not. I have ran Debian from a
microSD flash card before but the card reader was attached via USB.

It didn't last very long before the flash card degraded. I think running
an operating system on flash used up the read/write cycles too quickly.
I eventually decided to find another solution. But it may not be an
issue for your use case.


I don't think so. I have a low power industrial pc used as firewall. It runs
on Compact Flash card for >6y now. I recall there were at least 10
write cycles per sector and self diagnostic, so I would suspect something
else would be the problem.


CF cards were much more clever from the beginning compared to cheaper
alternatives (like SSD or MMC cards). I would expect them to have better
wear levelling than a common SD card.


I would be surprised that a CF card be more clever than a SSD.
However 10 erase/write cycles/block implies the use of NOR or SLC 
NAND flash memory chips, the types with highest endurance but lowest 
density. I doubt you can find this in SD cards. MLC NAND endurance can 
be 100 times lower.

Re: OT disco NTFS inmontable

Una herramienta que en este tipo de situaciones me ha salvado y
permitido acceder/recuperar todos los datos en dispositivos que tenían
comportamientos como el que mencionas:

http://www.cgsecurity.org/wiki/TestDisk

«[TestDisk] was primarily designed to help recover lost partitions
and/or make non-booting disks bootable again when these symptoms are
caused by faulty software: certain types of viruses or human error
(such as accidentally deleting a Partition Table). Partition table
recovery using TestDisk is really easy. (...)»

Me parece que incluso está en los repositorios de Debian, si no recuerdo mal.

2016-12-02 15:28 GMT+00:00 Ariel Alvarez :
> y no probaste:
>
> mount -t ntfs-3g /dev/sdb1 /mnt/disco
>
> ? asumiendo que tengas en /mnt/el directorio (disco) creado y ntfs-3g
> instalado.
>
>
> El 02-12-16 10:18, Juan Manuel Acuña escribió:
>
> Hola.
>
> A mi me pasó algo similar con un disco externo de un TB conectado por usb,
> que tenía ntfs. El disco era imposible de montarse ni en linux (diferentes
> distros) ni en mac, me daba errores de entrada / salida. El problema con
> este disco (al parecer) es que fue desconectado a la mala (sin desmontarse),
> en medio de un proceso de lectura / escritura en un equipo windows. Después
> de muchos intentos, la única solución que encontré fue conectarlo a una
> máquina con windows, donde el sistema, después de un buen rato (más de una
> hora), logró montarlo, y ya montado lo expulsé y pude usarlo en otros
> sistemas.
>
> Espero te sirva.
>
> Saludos!
>
>
> El vie., 2 de dic. de 2016 a la(s) 08:46, martin ayos
>  escribió:
>>
>> Buenas, camaradas: me pasaron un disco de 3TB que no puedo montar en
>> debian. En realidad, es inmomtable en cualquier SO. El disco tiene dos
>> particiones sin formato al principio y al final. Con fdisk -l puedo verlo
>> como /dev/sdb1 pero si ejecuto mount -t ntfs-3g /mnt/disco me dice que tiene
>> un error de entrada/salida. Esruve probando varias opciones que trae sysrem
>> rescue. Pero no hay posibilidad de verlo.sin alterat los datos. Saben de
>> algo? El duscontienen 3TB de datos sensibles qu no se pueden alterar. Es un
>> disco externo conectado vía usb. Muchas gracias. Martin.
>
>
>
> - Consejo
> Nacional de Casas de Cultura http://www.casasdecultura.cult.cu

Re: Cómo activar placa de red (notebook)

> Aparece otra eth0 entre las interfaces wireless, ¿puede ser que al
> estar el nombre duplicado el sistema no sepa qué hacer y la ignore?
> ¿Cómo puedo anular/eliminar la entrada eth0 de la lista de wireless
> (iwconfig) para ver si es ese el problema?

Por las dudas les recuerdo que cuando booteo con otras distros que
asignan el nombre enp6s0 a la placa de red, esta se conecta sin
problemas por cable; de ahí mi sospecha de que el asunto pase por
estar eth0 duplicada (como interfaz cableada y wireless).

Re: Cómo activar placa de red (notebook)

1) Muchas gracias a todos por la ayuda y orientación.

2) Efectivamente, la placa wireless ahora está funcionando y el
problema era que estaba bloqueada por hardware (en esta notebook es
especialmente incómodo porque las teclas F1, F2, etc., tienen
incorporadas acciones "multimedia", pero hay que elegir al bootear si
serán usadas como "multimedia" o como "función", de modo que hay que
bootear como "multimedia", activar la placa wireless, rebootear y
volver las teclas al modo normal... Creo que se pueden mapear
correctamente para que hagan una o la otra cosa añadiendo el uso de
una tecla "Fn" que tiene el teclado, pero ya es un laburo extra).

3) Sigue sin funcionar la placa de red. Y tengo la sospecha de que el
problema pase porque el nombre está duplicado. Fíjense:

root@debian:/home/user# lshw

   *-network
description: Wireless interface
product: Centrino Wireless-N 1030 [Rainbow Peak]
vendor: Intel Corporation
physical id: 0
bus info: pci@:03:00.0
logical name: wlan0
version: 34
serial: ac:72:89:0b:a1:2b
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi
driverversion=3.16.0-4-amd64 firmware=18.168.6.1 ip=10.0.0.8 latency=0
link=yes multicast=yes wireless=IEEE 802.11bgn
resources: irq:55 memory:f1b0-f1b01fff

   *-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit
Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@:06:00.0
logical name: eth0
version: 06
serial: 14:fe:b5:b8:11:13
size: 10Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master
cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt
1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes
driver=r8169 driverversion=2.3LK-NAPI duplex=half
firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes
port=MII speed=10Mbit/s
resources: irq:41 ioport:2000(size=256)
memory:f1804000-f1804fff memory:f180-f1803fff

root@debian:/home/user# ifconfig -a

eth0  Link encap:Ethernet  HWaddr 14:fe:b5:b8:11:13
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:857 errors:0 dropped:0 overruns:0 frame:0
  TX packets:857 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:145861 (142.4 KiB)  TX bytes:145861 (142.4 KiB)

wlan0 Link encap:Ethernet  HWaddr ac:72:89:0b:a1:2b
  inet addr:10.0.0.8  Bcast:10.0.0.255  Mask:255.255.255.0
  inet6 addr: fe80::ae72:89ff:fe0b:a12b/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:18545 errors:0 dropped:0 overruns:0 frame:0
  TX packets:16154 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:20507322 (19.5 MiB)  TX bytes:2233434 (2.1 MiB)

root@debian:/home/user# iwconfig

lono wireless extensions.

wlan0 IEEE 802.11bgn  ESSID:"Los Tanukis"
  Mode:Managed  Frequency:2.412 GHz  Access Point: 38:22:9D:0C:56:51
  Bit Rate=54 Mb/s   Tx-Power=15 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:4C61-5265-696E-6154-616E-756B-69
  Power Management:off
  Link Quality=54/70  Signal level=-56 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:6  Invalid misc:488   Missed beacon:0

eth0  no wireless extensions.


Aparece otra eth0 entre las interfaces wireless, ¿puede ser que al
estar el nombre duplicado el sistema no sepa qué hacer y la ignore?
¿Cómo puedo anular/eliminar la entrada eth0 de la lista de wireless
(iwconfig) para ver si es ese el problema?

4) Esta es la salida de interfaces:

root@debian:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback


Les vuelvo a agradecer a todos. Ya es medio problema resuelto volver a
tener conexión (wireless), y si consigo resolver lo de la placa de red
sería un éxito total :)

Saludos

Re: Manually installed packages

2016-12-03 Thread Rodolfo Medina

Greg Wooledge  writes:

> On Thu, Dec 01, 2016 at 06:38:45PM +, Rodolfo Medina wrote:
>> Suppose that, during months and years, you have installed many packages in
>> your Debian system that you no more want and no more use, and that you want
>> to free some space on disk because your machine is old with a small hard
>> disk.  The problem is what packages you can be really sure and safe to
>> remove.
>
> At some point you actually have to *know* what a package does.  Go through
> the list sorted by size and skip everything you know is useful.  When you
> get to one that you think is not useful, or which you don't recognize
> *at all*, dig into it and find out what it does.  Then consider removing
> it, but be prepared to put it back if you break something.
>
> This is how you learn.
>
> P.S. http://wooledge.org/~greg/ds will sort the installed packages by
> size for you.  As you can see, many of us have been there, done that.


Very useful.  Thanks.

Rodolfo

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

Richard Owlett:
> On 12/2/2016 4:21 PM, Jochen Spieker wrote:
>> 
>> Beware that this might slightly increase power usage / reduce battery
>> life. That's at least my observation from a couple of years ago.
>> Depenging on the hardware, an SD card can keep a bus alive that could be
>> put to sleep otherwise. But if I would have to guess this is not an
>> issue for your use case.
> 
> No problem for medium term. It will sit on my desk next to my "regular"
> machine.

That's what I thought.

>>>   2. Can Debian itself reside on that medium?
>>>  I'm thinking in terms of changing look/feel/function/capabilities/...
>>>  of the machine by swapping media before "power up".
>>>  [The BIOS *DOES* have some capability to specify precedence of boot
>>> devices.]
>> 
>> Debian doesn't really care, but you would have to test whether your BIOS
>> can really boot from SD cards.
> 
> If it "looks" the same as a USB flash device, there should be no problem.

For Linux the bus doesn't really matter. But again, for your BIOS it
does. As far as I understand, that's hardware specific. Some card
readers are internally wired to USB which gives you a good chance to
boot from it. As far as I can see on the ThinkWiki
(http://www.thinkwiki.org/wiki/Category:R61 pointing to
http://www.thinkwiki.org/wiki/Ricoh_R5C843), the R61 is different.

https://forums.lenovo.com/t5/ThinkPad-T61-and-prior-T-series/Boot-T61p-from-SD-card/m-p/261121/highlight/true#M41072
looks like you are out of luck.

J.
-- 
If I could have anything in the world it would have to be more money.
[Agree]   [Disagree]

signature.asc
Description: Digital signature

Re: {Debian (>=Jessie)} AND { MultiMediaCard, SD Memory Card, etc}

deloptes:
> Steven Mainor wrote:
> 
>> I don't know if this helps answer #3 or not. I have ran Debian from a
>> microSD flash card before but the card reader was attached via USB.
>> 
>> It didn't last very long before the flash card degraded. I think running
>> an operating system on flash used up the read/write cycles too quickly.
>> I eventually decided to find another solution. But it may not be an
>> issue for your use case.
>> 
> I don't think so. I have a low power industrial pc used as firewall. It runs
> on Compact Flash card for >6y now. I recall there were at least 10
> write cycles per sector and self diagnostic, so I would suspect something
> else would be the problem.

CF cards were much more clever from the beginning compared to cheaper
alternatives (like SSD or MMC cards). I would expect them to have better
wear levelling than a common SD card.

J.
-- 
When I get home from the supermarket I don't know what to do with all the
plastic.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: nosh version 1.29

Bloody Thunderbird!  Here's that again, I hope without the surprise 
reformatting after pressing "send" this time:


The nosh package is now up to version 1.29.

* http://jdebp.eu./Softwares/nosh/
* 
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project

* http://jdebp.info./Softwares/nosh/

There's been a lot going on since version 1.28 .

2016 leap second


The TAI to UTC conversions know about the forthcoming leap second.

service bundles
---

As usual, there are several new service bundles, from powerd++ through 
zfsd to fwknopd.  The new fs-servers target allows one to order the 
initialization of NFS servers before loop-to-self NFS mounts.  The new 
multi-user-pre target is another ordering target that allows services 
such as the motd file updater to be ordered before TTY login services.  
The instantiated kdm@tty7 and kdm@ttyv6 services have been replaced with 
a single kdm service, with a view to dealing with display managers 
better in the future.  I have some plans in this area.


The Samba service names have been fixed.  Debian calls them nmb, smb, 
and winbind; but the Samba doco and most places on the WWW call them 
nmbd, smbd, and winbindd.  The latter names are used in the service 
bundles package, with aliases pointing to them from the Debian names.


doco


The doco has been improved and kept up-to-date in various places, 
including correct descriptions of set-service-env and print-service-env 
after one confused user got in touch.  PC-BSD is now named as TrueOS 
where the reference is not historical.


code review
---

As a result of some code review that was offered, std::auto_ptr is now 
gone and a rare memory corruption bug in safe_execvp() has been fixed.  
Building from scratch when one doesn't have a prior daemontools or 
freedt toolset installed also no longer hits a bug.


configuration import improvements
-

In an effort to clear those last few remaining items on the nosh 
roadmap, a whole load of configuration import (pppd, sppp, rfcomm_ppp, 
dhclient, wpa_supplicant, natd, and hostapd) has been consolidated under 
the umbrella of static-networking.  I plan to expand this further in 
1.31, given how much is already in 1.30.


Linux kernel VTs


Management of Linux kernel virtual terminals has some improvements, 
including setting UTF-8 canonical mode editing and keyboard composition 
modes, and emitting the control sequences that set up the screen saver.


tai64nlocal changes
---

tai64nlocal has adopted a minor but important change from the BSD and 
GNU C libraries: before reading the start of a line it flushes its 
output.  This came from trying to use it as a co-process in GNU awk.  To 
prevent deadlocks, GNU awk co-processes need to be in what is 
effectively line buffered output mode even though their standard inputs 
and outputs are not terminal devices.  This is now the case for 
tai64nlocal and it can be used to convert TAI64N timestamps as a GNU awk 
co-process.


FreeBSD and TrueOS packaging


The largest change, however, is in the FreeBSD/TrueOS and OpenBSD packaging.

This is a change that is going to happen in the Debian packaging in a 
later version.  It's partly to simplify the package maintenance, and 
partly a step towards having OpenBSD packages that work.  A single 
package description is fed to both the new pkg tool that exists on 
FreeBSD/TrueOS and the old pkg tool that exists on OpenBSD.  It's not 
perfect, as there are things that are easy with the new pkg tool that 
are hard with the old one; and the OpenBSD packages are still not fully 
functional.  But things are better than they were.  The OpenBSD service 
bundles package now almost properly sets up per-service user accounts 
and log directories, for example.


===
===  IMPORTANT UPGRADE NOTE FOR FreeBSD/TrueOS: ===
===

An important consequence of the aforementioned is that the semantics of 
the nosh-bundles package have changed.  In earlier versions, the various 
nosh-run-* packages were how one set services running, except for a 
small rump set of services that were set up by the nosh-bundles 
package.  This is now no longer the case.  The nosh-bundles package now 
presets and starts no services at all. *All* running of services must be 
achieved with the nosh-run-* packages or some other sets of scripts and 
presets.


To this end, there are now two new packages, 
nosh-run-freebsd-desktop-base and nosh-run-freebsd-server-base. These 
parallel the already existing nosh-run-trueos-desktop-base and 
nosh-run-trueos-server-base packages; except that they do not start any 
of the services that exist in TrueOS but do not exist in FreeBSD, such 
as the various pc-* services.


You must

nosh version 1.29