Debian with docking station

[apadoly2]

 

Good evening to all,

The docking station of a laptop computer can
to disrupt you the functioning of a distribution LINUX (DEBIAN).

In
term of material, I think of a former DELL mobile D430 and its docking
station PR09

Regards.

Alex PADOLY

 

Re: need help with approx-gc

[Gene Heskett]

On Sunday 10 May 2015 00:27:45 Paul E Condon wrote:
> On 20150509_1832-0600, Bob Proulx wrote:
> > Paul E Condon wrote:
> > > The following is just a few examples from kern.log:
> > > May  8 11:32:49 cmn kernel: [4880283.861051] end_request: I/O
> > > error, dev sda, sector 16136192
> >
> > Ouch!  You have a disk that is crying out for help.  Oh the pain and
> > suffering of it!
> >
> > > All of them have the same sector number. This is the sda drive,
> > > which is formatted as ext4. Is there some way that the automatic
> > > reallocate could the repaired by a forced manual fsck? and is the
> > > rescue function on the netinst CD adequate for this?
> >
> > I have often been in your same situation.  I would ensure that the
> > backup is current and valid and then replace the disk.  That is me. 
> > I have seen disks get worse very quickly after they have exhibited
> > failures.  Modern disk controllers keep internal spares.  By the
> > time the disk is showing errors externally the internal spares have
> > probably all been consumed with other failures.
> >
Absolutely.  Get a new drive, set that one as sdb & the new one as sda, 
install on sda, then mount sdb's partitions and copy off the data you 
need to maintain the path thru life you are on.

> > Problems like this will quickly make you a believer in RAID.  I
> > pretty much raid everything these days just to avoid being in this
> > situation.  In a RAID the bad disk would have already been kicked
> > out of the raid array.  It would then be left running in degraded
> > mode on the remaining drives.  The system would keep running without
> > problems.  Replacing the failing drive and backfilling the raid
> > array can all occur while the system is up and online.
> >
> > > Not running SMART.
> > > What Debian package provides smartctl ?
> >
> >   apt-get install smartmontools
> >   smartctl -l error /dev/sda
> >
> > I expect that to show errors.
> >
> >   smartctl -t short /dev/sda
> >   sleep 120
> >   smartctl -l selftest /dev/sda
> >
> > I expect that to show errors.
> >
> > > I don't think the following tests will make the reallocation
> > > problem go away.
> >
> > Nope.  Seems like a disk failure to me.
> >
> > > I was planning to do something else this weekend, Oh well.
> >
> > RAID.  I can't say enough good things about it in these situations.
> > And backup.
> >
> > BTW...  I have a low priority machine that is crying right now that
> > SMART selftests are failing.  It hasn't gotten to the actual I/O
> > failure error stage yet but it is only a matter of time.  It is a
> > low priority machine so I haven't actually done anything yet.  It is
> > still up and running.  But I have a disk and as soon as I get a few
> > spare minutes this weekend I am going to go swap out the failing
> > disk for another.  But tomorrow looks pretty busy for me.  I
> > probably won't get to it until Monday.  And I have no stress about
> > it because it is a raid and the other disk is healthy.  Plus backups
> > are current.
> >
> > Bob
>
> Bob,
>
> I have no doubt that raid is the right way to go, but my personal
> situation is that I am working with old hardware, and I can't buy a
> state of the art new computer unless prices suddenly crash. I'm quite
> sure that I have daily backups going back to before I switched to
> Jessie well before its release. I won't be able to get replacement
> parts for the current box except by mail order, and I don't know if it
> can hold more than one drive (It is an old Dell packaged in one of
> their tiny desktop cases.)  As I write, I am thinking I should turn
> off the failing machine, and learn to live without it for a few weeks.
> It has been running approx and cups (It is the old box with Centronix
> connector that figured in another thread here.) I have another old
> Dell with a slightly bigger case. How many independent HDrives are
> needed?
>
> Thanks
> --
> Paul E Condon
> pecon...@mesanetworks.net

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201505100038.23197.ghesk...@wdtv.com

Re: need help with approx-gc

[Paul E Condon]

On 20150509_1832-0600, Bob Proulx wrote:
> Paul E Condon wrote:
> > The following is just a few examples from kern.log:
> > May  8 11:32:49 cmn kernel: [4880283.861051] end_request: I/O error, dev 
> > sda, sector 16136192
> 
> Ouch!  You have a disk that is crying out for help.  Oh the pain and
> suffering of it!
> 
> > All of them have the same sector number. This is the sda drive,
> > which is formatted as ext4. Is there some way that the automatic
> > reallocate could the repaired by a forced manual fsck? and is the
> > rescue function on the netinst CD adequate for this?
> 
> I have often been in your same situation.  I would ensure that the
> backup is current and valid and then replace the disk.  That is me.  I
> have seen disks get worse very quickly after they have exhibited
> failures.  Modern disk controllers keep internal spares.  By the time
> the disk is showing errors externally the internal spares have
> probably all been consumed with other failures.
> 
> Problems like this will quickly make you a believer in RAID.  I pretty
> much raid everything these days just to avoid being in this
> situation.  In a RAID the bad disk would have already been kicked out
> of the raid array.  It would then be left running in degraded mode on
> the remaining drives.  The system would keep running without
> problems.  Replacing the failing drive and backfilling the raid array
> can all occur while the system is up and online.
> 
> > Not running SMART.
> > What Debian package provides smartctl ?
> 
>   apt-get install smartmontools
>   smartctl -l error /dev/sda
> 
> I expect that to show errors.
> 
>   smartctl -t short /dev/sda
>   sleep 120
>   smartctl -l selftest /dev/sda
> 
> I expect that to show errors.
> 
> > I don't think the following tests will make the reallocation problem
> > go away.
> 
> Nope.  Seems like a disk failure to me.
> 
> > I was planning to do something else this weekend, Oh well.
> 
> RAID.  I can't say enough good things about it in these situations.
> And backup.
> 
> BTW...  I have a low priority machine that is crying right now that
> SMART selftests are failing.  It hasn't gotten to the actual I/O
> failure error stage yet but it is only a matter of time.  It is a low
> priority machine so I haven't actually done anything yet.  It is still
> up and running.  But I have a disk and as soon as I get a few spare
> minutes this weekend I am going to go swap out the failing disk for
> another.  But tomorrow looks pretty busy for me.  I probably won't get
> to it until Monday.  And I have no stress about it because it is a
> raid and the other disk is healthy.  Plus backups are current.
> 
> Bob
Bob,

I have no doubt that raid is the right way to go, but my personal
situation is that I am working with old hardware, and I can't buy a
state of the art new computer unless prices suddenly crash. I'm quite
sure that I have daily backups going back to before I switched to
Jessie well before its release. I won't be able to get replacement
parts for the current box except by mail order, and I don't know if it
can hold more than one drive (It is an old Dell packaged in one of
their tiny desktop cases.)  As I write, I am thinking I should turn
off the failing machine, and learn to live without it for a few weeks.
It has been running approx and cups (It is the old box with Centronix
connector that figured in another thread here.) I have another old
Dell with a slightly bigger case. How many independent HDrives are
needed?

Thanks
-- 
Paul E Condon   
pecon...@mesanetworks.net


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150510042745.ga13...@big.lan.gnu

Re: Temporarily hold a package............

[Bob Proulx]

Michael Biebl wrote:
> Bob Proulx:
> > Charlie wrote:
> >> I had never even known about apt-mark and when Matthias pointed it out,
> >> tried it, read the man page and was amazed.
> > 
> > The functionality of 'apt-mark hold' was new in Wheezy 7.  Squeezy 6
> > didn't include that functionality.
> 
> Sort of.
> In Squeeze and earlier releases you could already use
> dpkg --get-selections > file
> edit file and s/install/hold/ for the desired package
> dpkg --set-selections < file
> 
> This had the same effect as "apt-mark hold". Arguably, apt-mark provides
> the nicer interface :-)

Right.  New in apt-mark.  Has existed in dpkg --set-selections and
get-selections for a long time.  It is slightly easier to use in
apt-mark now.  A good improvement.

> If you're interested which packages are currently put on hold, run
> dpkg --get-selections | grep hold

Or now in the new apt-mark run:

  apt-mark showhold

Bob



signature.asc
Description: Digital signature

Re: Open ports

[Bob Proulx]

Christian Seiler wrote:
> Bill wrote:
> > what uses them and why shouldn't I close them?
> > (I'm assuming there must be a good reason to have wide open ports.)

It is debatable whether the old Sun RPC services should be installed
by default.  I do use and manage NFS but I wouldn't install it by
default on any machine not using it.  If you are not serving NFS then
you don't need it.  If you are serving NFS then it will get installed
as a matter of course.

> rpcbind is started from /etc/init.d/rpcbind. If you don't use NFS or NIS
> at all, you don't need to have that running. To disable it under Wheezy,
> use:
> 
> update-rc.d rpcbind disable
> 
> After that, it won't be started anymore at boot.

Instead of disabling it I am of the opinion that it should be removed
if it isn't going to be used.  If in the future someone were going to
set up an NFS server on the system then it can trivially be installed
again.  So easy to install that removing it instead of disabling it
seems like the better way to go in my opinion.  One less package that
might need a security upgrade at some point.  One less package on the
disk to manage.  Just simplify.

  # apt-get purge rcpbind

Bob


signature.asc
Description: Digital signature

Re: ssh tunnels or openvpn/IPsec?

[Bob Proulx]

Petter Adsen wrote:
> Now the question becomes; AFAIK, I could do this with ssh tunnels and
> forward the ports on my router/firewall, or I could use something like
> openvpn or IPsec (strongswan).

Yes.  Exactly.

Also 'stunnel4' is useful too.

I would avoid IPsec.  Last I looked there were more than 55 RFCs that
had some impact on IPsec.  It has traditionally been rather of a messy
thing.

> The problem is that I haven't really messed with any of these before
> - what would be the best choice in this situation?
>
> Note that I'm not asking for a complete configuration, all I want is
> some advice as to which of these technologies I should begin to read up
> on. The IPsec article on the Debian wiki is from Sarge, so it is quite
> outdated, but the openvpn article is recent and seems helpful.
> 
> Any insights/advice/links, etc?

Using ssh tunnels will get you 80% with 20% of the work.  Using
OpenVPN will get you 100% with 100% of the work.  Using 'autossh' to
manage ssh tunnels is very reliable to run and very quick and easy to
set up.

I use all of autossh/ssh tunnels, stunnel4, openvpn in different
places.  I tend to like and use the autossh/ssh tunnels because they
are quick and easy and work well enough that I can move along to
something else without spending a lifetime managing them.  It doesn't
require any routing table modifications.

I like stunnel4 for some things because it also is very easy to set up
and very reliable.  Either ssh or stunnel would seem to be good simple
effective choices for remote sysloging.  I might lean toward stunnel
for this.  It all depends.  Using stunnel benefits if you have signed
https ssl certificates already that can be verified by stunnel.

Both ssh and stunnel use TCP which means that in terms of ultimate
performance and ultimate efficiency you are ending up with TCP over
TCP and that isn't perfect.  TCP over TCP will use some resources and
time transporting packets somewhat inefficiently.  I think for your
example of using remote syslog logging I wouldn't worry about it.  It
is a non-interactive task and the machines won't care when talking to
each other.  No one will ever notice the inefficiency.

When operating interactively such as working from my laptop to my
remote servers I am usually interactive.  That is when transport
artifacts of latency become noticeable and annoying.  There I have put
in the extra work to set up openvpn for the 100% solution.  It uses
UDP for the transport avoiding the TCP over TCP issues.  It is more
work to set up initially due to dealing with setting up ssl
certificates and routing.  But having set it up it is a high
performance solution that does 100% of the job.

I would probably start your remote syslog task using autossh/ssh and
then worry about doing something more when the need for more arises
and not before.

Bob


signature.asc
Description: Digital signature

Re: Temporarily hold a package............

[Michael Biebl]

Am 10.05.2015 um 02:34 schrieb Bob Proulx:
> Charlie wrote:
>> I had never even known about apt-mark and when Matthias pointed it out,
>> tried it, read the man page and was amazed.
> 
> The functionality of 'apt-mark hold' was new in Wheezy 7.  Squeezy 6
> didn't include that functionality.

Sort of.
In Squeeze and earlier releases you could already use
dpkg --get-selections > file
edit file and s/install/hold/ for the desired package
dpkg --set-selections < file

This had the same effect as "apt-mark hold". Arguably, apt-mark provides
the nicer interface :-)


If you're interested which packages are currently put on hold, run
dpkg --get-selections | grep hold

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Temporarily hold a package............

[Bob Proulx]

Charlie wrote:
> I had never even known about apt-mark and when Matthias pointed it out,
> tried it, read the man page and was amazed.

The functionality of 'apt-mark hold' was new in Wheezy 7.  Squeezy 6
didn't include that functionality.  Squeeze 6 only included controls
to mark and unmark the automatically installed flag used by 'apt-get
autoremove'.  So relatively new for people who have been using Debian
for a while.

Bob


signature.asc
Description: Digital signature

Re: need help with approx-gc

[Bob Proulx]

Paul E Condon wrote:
> The following is just a few examples from kern.log:
> May  8 11:32:49 cmn kernel: [4880283.861051] end_request: I/O error, dev sda, 
> sector 16136192

Ouch!  You have a disk that is crying out for help.  Oh the pain and
suffering of it!

> All of them have the same sector number. This is the sda drive,
> which is formatted as ext4. Is there some way that the automatic
> reallocate could the repaired by a forced manual fsck? and is the
> rescue function on the netinst CD adequate for this?

I have often been in your same situation.  I would ensure that the
backup is current and valid and then replace the disk.  That is me.  I
have seen disks get worse very quickly after they have exhibited
failures.  Modern disk controllers keep internal spares.  By the time
the disk is showing errors externally the internal spares have
probably all been consumed with other failures.

Problems like this will quickly make you a believer in RAID.  I pretty
much raid everything these days just to avoid being in this
situation.  In a RAID the bad disk would have already been kicked out
of the raid array.  It would then be left running in degraded mode on
the remaining drives.  The system would keep running without
problems.  Replacing the failing drive and backfilling the raid array
can all occur while the system is up and online.

> Not running SMART.
> What Debian package provides smartctl ?

  apt-get install smartmontools
  smartctl -l error /dev/sda

I expect that to show errors.

  smartctl -t short /dev/sda
  sleep 120
  smartctl -l selftest /dev/sda

I expect that to show errors.

> I don't think the following tests will make the reallocation problem
> go away.

Nope.  Seems like a disk failure to me.

> I was planning to do something else this weekend, Oh well.

RAID.  I can't say enough good things about it in these situations.
And backup.

BTW...  I have a low priority machine that is crying right now that
SMART selftests are failing.  It hasn't gotten to the actual I/O
failure error stage yet but it is only a matter of time.  It is a low
priority machine so I haven't actually done anything yet.  It is still
up and running.  But I have a disk and as soon as I get a few spare
minutes this weekend I am going to go swap out the failing disk for
another.  But tomorrow looks pretty busy for me.  I probably won't get
to it until Monday.  And I have no stress about it because it is a
raid and the other disk is healthy.  Plus backups are current.

Bob


signature.asc
Description: Digital signature

nosh version 1.14

[Jonathan de Boyne Pollard]

nosh is now up to version 1.14

* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html

These particular changelog entries are a big deal for Debian Linux.

  * The previous regular sockets, sysinit services, and standard 
targets packages are now all merged into the bundles package.
  * There is now a new user VT package that runs new-style user VT 
services.
  * There is now a new kernel VT package that runs old-style kernel VT 
services.
  * The nosh-systemd-services package now automatically runs various 
nosh subsystems under systemd.


I've taken the list of Debian packages available for download off the 
infobox at the side of the blurb page and set up a page devoted 
specifically to the Debian packages, explaining what they contain and 
are for in more detail than could fit into that infobox.


* 
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/debian-binary-packages.html


There's a known bug that I'm working on.  Because the preset conversion 
is a little too aggressive, and because getttynam() exists on Debian 
Linux, you'll currently need a dummy BSD /etc/ttys file that presets the 
ttylogin@.service services that you want. Something like:


tty1 /bin/false linux on secure
tty5 /bin/false linux on secure
tty7 /bin/false linux off secure
vc0-tty /bin/false linux on secure
vc1-tty /bin/false linux on secure
vc2-tty /bin/false linux on secure

Those "vcN-tty" lines are user-mode virtual terminals.  As you can 
probably work out from this, on the BSD side the nosh user-mode virtual 
terminal system is able to pull terminal login service enable/disable 
information from the existing /etc/ttys configuration mechanism.  (It 
also can pull from /etc/rc.conf and does "onifconsole" too.)


The list of 157 things that I have to convert in order to fully replace 
BSD /etc/rc.d is discussed in detail on the FreeBSD Hackers mailing 
list.  We have long since passed the point where it's possible to have 
an entirely nosh-managed FreeBSD/PC-BSD system, though.  The list of 
things that I have to convert before I can likewise run my Debian Linux 
system fully under the nosh system-manager is down to about a handful, 
and is mainly the likes of service bundles for dbus and udev.  If you 
already have daemontools-style run scripts for those, or eudev, or mdev, 
or whatever you enjoy, then you can race ahead of me.  (-:


The page also warns about the nosh-bundles package potentially enabling 
a lot of services.  It's a package of over 400 service bundles.  One way 
of avoiding this is to go the only-enable-what-I-permit route, and use 
this 99-default.preset:


disable *.service
disable *.socket

With something like this 00-administrator.preset alongside:

enablecyclog@acpid.service
enablecyclog@atd.service
enablecyclog@console-fb-realizer@*.service
enablecyclog@console-multiplexor@*.service
enablecyclog@gnucron.service
enablecyclog@kerneloops.service
enablecyclog@ModemManager.service
enablecyclog@NetworkManager.service
enablecyc...@org.cups.cups*.service
enablecyclog@polkitd.service
enablecyclog@terminal-emulator@*.service
enablecyclog@ttylogin@*.service
enablecyclog@update-binfmts.service
enablecyclog@wpa_supplicant.service
enableacpid.service
enableatd.service
enableconsole-fb-realizer@*.service
enableconsole-multiplexor@*.service
enablegnucron.service
enablekerneloops.service
enableModemManager.service
enableNetworkManager.service
enableorg.cups.cups*.service
enablepolkitd.service
enableterminal-emulator@*.service
enablettylogin@*.service
enableupdate-binfmts.service
enablewpa_supplicant.service

Adjust according to taste, of course.  Mine also enables various 
additional service bundles including dnscache, tinydns, http6d, 
rabbitmq-server, and epmd (and their concomitant logging services) for 
example.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/554e93af.3070...@ntlworld.com

Re: GUI won't start after wheezy upgrade [SOLVED]

[John Aten]

The release notes said that monitors must support 3D graphics, which should be 
most monitors made within the last 10 years. My laptop is about that old, so I 
figured that must be it. I installed KDE, and it works fine. 

I also changed my sources.list to avoid a surprise like this in the future. 

Thanks for the help!

On May 3, 2015, at 12:23 PM, Liam O'Toole wrote:

> On 2015-05-03, John Aten  wrote:
>> 
>> --Apple-Mail-2--756983614
>> Content-Transfer-Encoding: quoted-printable
>> Content-Type: text/plain;
>>  charset=us-ascii
>> 
>> I am not in fact running wheezy. I got confused, it is Jesse.=20
>> 
>> /etc/apt/sources.list:
>> # Debian packages for stable
>> deb http://ftp.us.debian.org/debian/ stable main contrib
>> # Uncomment the deb-src line if you want 'apt-get source'
>> # to work with most packages.
>> # deb-src http://ftp.us.debian.org/debian/ stable main contrib
>> 
>> # Security updates for stable
>> deb http://security.debian.org/ stable/updates main contrib
>> 
>> # Added October 1, to install newer Zotero
>> deb http://http.debian.net/debian wheezy-backports main
> 
> Yes, you are running jessie /now/, and the upgrade you described was an
> upgrade from wheezy to jessie. The reason for that is that you identify
> the release in your sources.list file as 'stable'. Up to last weekend,
> stable meant wheezy; now it means jessie.
> 
> I suggest you consult the release notes[1] and check that the upgrade is
> complete. There might be some housekeeping to do.
> 
> I also suggest that you change occurrences of 'stable' in sources.list to
> 'jessie'. That will prevent inadvertent release upgrades in future. You
> have about two years to do that. :-)
> 
> -- 
> 
> Liam
> 
> 1: https://www.debian.org/releases/jessie/releasenotes
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/slrnmkcmdd.hdd.liam.p.otoole@dipsy.tubbynet
> 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/10af49da-297f-4140-8a65-b574d4c40...@gmail.com

Re: Botched upgrade to jessie (solved)

[Leandro Guimarães Faria Corcete DUTRA]

Le mercredi 29 avril 2015 à 11:58 -0300, Guimarães Faria Corcete DUTRA,
Leandro a écrit :
> I had completed apt-get upgrade alright, but then the computer was
> turned off during apt-get dist-upgrade.  Now I tried apt-get -f
> upgrade:
[…]
> GLib-GObject-CRITICAL **:
> /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You
> forgot to call g_type_init() at
> /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 210, <> line
> 602.
> GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed at
> /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 210, <> line
> 602.
>
> Is there any way of recovering?

After so many years using Debian (from around v1.2) it should have been
obvious I had a broken Gnome installation, and it sufficed to force the
dialog dpkg frontend.

In this case, debian-user-portuguese helped me.


-- 
skype:leandro.gfc.dutra?chat  Yahoo!: ymsgr:sendIM?lgcdutra
+55 (61) 3546 7191  gTalk: xmpp:leand...@jabber.org
+55 (61) 9302 2691ICQ/AIM: aim:GoIM?screenname=61287803
BRAZIL GMT-3  MSN: msnim:chat?contact=lean...@dutra.fastmail.fm



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1431201882.1455.2.ca...@dutras.org

Re: need help with approx-gc

[Curt]

On 2015-05-09, Paul E Condon  wrote:
>
> Not running SMART.
> What Debian package provides smartctl ?
> I don't think the following tests will make the reallocation problem
> go away.
>

curty@einstein:~$ apt-cache search smartctl
gsmartcontrol - graphical user interface for smartctl
smartmontools - control and monitor storage systems using S.M.A.R.T.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmksppc.4ar.cu...@einstein.electron.org

Re: need help with approx-gc

[Paul E Condon]

On 20150508_1446-0600, Bob Proulx wrote:
> Paul E Condon wrote:
> > I run approx on one of my local jessie machines. The approx installation
> > is strictly by using the approx deb, which includes a weekly run of
> > approx-gc , which should just clean out the local repository of debs that
> > are no longer useful. But approx-gc has started reporting I/O errors.
> 
> It is reporting I/O errors as in the disk drive is failing types of
> errors?  As in hardware errors outside of the software?
> 
> What is reported?  Are the errors in the /var/log/syslog or
> /var/log/kern.log files?  What types of errors?


The following is just a few examples from kern.log:

May  8 11:32:49 cmn kernel: [4880283.861027] sd 2:0:0:0: [sda]  
May  8 11:32:49 cmn kernel: [4880283.861032] Add. Sense: Unrecovered read error 
- auto reallocate failed
May  8 11:32:49 cmn kernel: [4880283.861036] sd 2:0:0:0: [sda] CDB: 
May  8 11:32:49 cmn kernel: [4880283.861038] Read(10): 28 00 00 f6 38 00 00 00 
08 00
May  8 11:32:49 cmn kernel: [4880283.861051] end_request: I/O error, dev sda, 
sector 16136192
 
May  8 11:32:10 cmn kernel: [4880244.912960] 00 f6 38 00 
May  8 11:32:10 cmn kernel: [4880244.912967] sd 2:0:0:0: [sda]  
May  8 11:32:10 cmn kernel: [4880244.912971] Add. Sense: Unrecovered read error 
- auto reallocate failed
May  8 11:32:10 cmn kernel: [4880244.912975] sd 2:0:0:0: [sda] CDB: 
May  8 11:32:10 cmn kernel: [4880244.912977] Read(10): 28 00 00 f6 38 00 00 00 
08 00
May  8 11:32:10 cmn kernel: [4880244.912990] end_request: I/O error, dev sda, 
sector 16136192

May  8 11:32:10 cmn kernel: [4880244.912990] end_request: I/O error, dev sda, 
sector 16136192

All of them have the same sector number. This is the sda drive, which is
formatted as ext4. Is there some way that the automatic reallocate could the
repaired by a forced manual fsck? and is the rescue function on the netinst CD
adequate for this?

> 
>   less /var/log/kern.log
> 
> Are you running SMART?  What do the SMART error logs say?

Not running SMART.
What Debian package provides smartctl ?
I don't think the following tests will make the reallocation problem
go away.

I was planning to do something else this weekend, Oh well.
Thanks ;-)

> 
>   smartctl -l error /dev/sda
>   smartctl -l selftest /dev/sda
> 
> Are you running selftests?  If not try running a SMART selftest and
> seeing what is the result of it.
> 
>   smartctl -t short /dev/sda
>   sleep 120  # or whatever is predicted above
>   smartctl -l selftest /dev/sda
> 
> If short is okay then try a 'long' test.  If you are seeing I/O errors
> then I would be worried the disk is failing.  In which case the SMART
> would confirm it.  (SMART isn't a good predictor.  But it can confirm
> a diagnosis.)
> 
> Bob



-- 
Paul E Condon   
pecon...@mesanetworks.net


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150509184055.ga7...@big.lan.gnu

Re: ipset

[Ulf Volmer]

On 05/09/2015 06:58 PM, Gokan Atmaca wrote:
> The Loop gives error as follows.
> 
> # for g in 'gawk '{print $2}' facebook.com-ip'; do ipset add  face $g; done
 ^ ^
replace this single quotes with backticks

# for g in `gawk '{print $2}' facebook.com-ip`; do ipset add  face $g; done

regrads
Ulf


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/554e4850.4090...@u-v.de

Re: ipset

[shawn wilson]

On May 9, 2015 12:59 PM, "Gokan Atmaca"  wrote:
>
> The Loop gives error as follows.
>
> # for g in 'gawk '{print $2}' facebook.com-ip'; do ipset add  face $g;
done
>
> ipset v6.23: Syntax error: cannot parse gawk: resolving to IPv4 address
failed
> ipset v6.23: Syntax error: cannot parse }: resolving to IPv4 address
failed
>

IIRC you need to define the set first and it's telling you the data isn't
an IP address. You should show some data.

Re: ipset

[Gokan Atmaca]

The Loop gives error as follows.

# for g in 'gawk '{print $2}' facebook.com-ip'; do ipset add  face $g; done

ipset v6.23: Syntax error: cannot parse gawk: resolving to IPv4 address failed
ipset v6.23: Syntax error: cannot parse }: resolving to IPv4 address failed





On Sat, May 9, 2015 at 7:36 PM, Gokan Atmaca  wrote:
> Hello;
>
> I bought according to the IP address you want to embed list of AS numbers 
> ipset.
>
> Example:
> awk '{print $ 2}' facebook-ip.list> ipset-facebook
>
> How can I do this?
>
> Thanks


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAHg8tECCNhTcFQh4boDg-=1ue25-ghoprlnkavwl_42rcoj...@mail.gmail.com

Re: (script) Re: Rediscovering a forgotten command

[Richard Owlett]

David Wright wrote:

Quoting Richard Owlett (rowl...@cloud85.net):

A few months ago I came across a command which would save all
keyboard input to the current console and all output displayed on
that console. That information would be saved to a default file or
to a user specified file. IIRC the documentation implied it had
originally been targeted at classroom environment.

Can anyone identify this?


script, but I find it quite useful to have a bash function defined as

scrip ()
{
 script typescript-${HOSTNAME}-$(date +%Y-%m-%d-%H-%M-%S)-$1
}

so that you get a host/timestamp in the unique filename and a
string to remember why you used it.

Cheers,
David.



Thanks to Peter and David. That is what I was trying to remember.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/554e3aeb.9000...@cloud85.net

ipset

[Gokan Atmaca]

Hello;

I bought according to the IP address you want to embed list of AS numbers ipset.

Example:
awk '{print $ 2}' facebook-ip.list> ipset-facebook

How can I do this?

Thanks


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAHg8tEC9dn5tmjFYUKnW20g6-jza8e=hgf_7vaksg5fyrf+...@mail.gmail.com

(script) Re: Rediscovering a forgotten command

[David Wright]

Quoting Richard Owlett (rowl...@cloud85.net):
> A few months ago I came across a command which would save all
> keyboard input to the current console and all output displayed on
> that console. That information would be saved to a default file or
> to a user specified file. IIRC the documentation implied it had
> originally been targeted at classroom environment.
> 
> Can anyone identify this?

script, but I find it quite useful to have a bash function defined as

scrip ()
{
script typescript-${HOSTNAME}-$(date +%Y-%m-%d-%H-%M-%S)-$1
}

so that you get a host/timestamp in the unique filename and a
string to remember why you used it.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150509162249.GA24101@alum

Re: Rediscovering a forgotten command

[Petter Adsen]

On Sat, 09 May 2015 10:34:36 -0500
Richard Owlett  wrote:

> A few months ago I came across a command which would save all 
> keyboard input to the current console and all output displayed on 
> that console. That information would be saved to a default file 
> or to a user specified file. IIRC the documentation implied it 
> had originally been targeted at classroom environment.
> 
> Can anyone identify this?

"script"?

Petter

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."


pgpZ2UQrbC3jf.pgp
Description: OpenPGP digital signature

Rediscovering a forgotten command

[Richard Owlett]

A few months ago I came across a command which would save all 
keyboard input to the current console and all output displayed on 
that console. That information would be saved to a default file 
or to a user specified file. IIRC the documentation implied it 
had originally been targeted at classroom environment.


Can anyone identify this?

TIA



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/554e290c.4040...@cloud85.net

Re: Default virtualhost on Debian Jessie with Apache 2.4.10

[Daniel Bareiro]

On 04/05/15 05:21, Georgi Naplatanov wrote:

>> Currently I have a unique site in sites-enabled which is accessed only
>> via HTTPS. Hoping to have an access error when trying to access this
>> site via HTTP, Apache sends me to the default site which is "It's
>> works!" page in /var/www/html.
>>
>> I was looking in the Apache configuration files where is configured the
>> default site but I have not found it. This was set at low level in the
>> compilation of the service?

> Hi,

Hi, Georgi.

> all your configuration files in /etc/apache2/sites-enabled/
>  and /etc/apache2/sites-available/ should end with ".conf" string e.g.
> "mysite.com.conf".
> 
> For default site you can use "_default_" key word, see
> http://httpd.apache.org/docs/2.4/vhosts/examples.html.

Yes. After tests it seems that the solution is heading towards the use
of _default_.

Thanks for your reply.


Best regards,
Daniel




signature.asc
Description: OpenPGP digital signature

Re: Default virtualhost on Debian Jessie with Apache 2.4.10

[Daniel Bareiro]

Hi, Bob.

On 08/05/15 16:54, Bob Proulx wrote:

> Daniel Bareiro submitted the problem that he could not disable the
> default web server on port 80.  That has been the topic of this
> thread.
> 
> I see now that you did say you wanted to have the mailman site
> enabled.  I didn't see that before since we were focused on Daniel's
> problem of trying to disable the port 80 web site.

My original question was aimed at preventing that Apache gives a default
response if the site name does not match exactly (regardless of the
ports that were enabled).

Given the circumstances, I think the way to do this would be using
_default_ in the definition of VirtualHost. I think the definitions
mentioned in a previous mail could be consolidated as follows:


RedirectMatch 404 (.*)


Although it might be interesting to achieve a similar behavior to the
444 of Nginx mentioned in a previous email.


Best regards,
Daniel




signature.asc
Description: OpenPGP digital signature

Re: Default virtualhost on Debian Jessie with Apache 2.4.10

[Daniel Bareiro]

On 09/05/15 10:19, Daniel Bareiro wrote:

> I would prefer using _default_ because that way it will return 404 when
> there is not a match for the site name.

A curious question about this: Is there any way that Apache responds
similarly to the way it does Nginx with its error code 444 (the server
returns no information to the client and closes the connection):


server {
listen  80 default_server;
server_name _;
return  444;
}

I was investigating whether it is possible to generate this behavior for
Apache default site, but could not find the way to do it yet.


Best regards,
Daniel




signature.asc
Description: OpenPGP digital signature

blackbox: where is bbkeys package?

[Rodolfo Medina]

Hi to all Debian users.

I installed blackbox in order to choose it as my window manager, but read that,
to use keystrokes in it, the bbkeys package is needed.  But it seems to be
absent from Debian Stable, whereas in Sid there is but aptitude won't install
it or it is already there but doesn't run from command line.

Please help whoever can.

Thanks in advance,

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87y4kx3mkh@gmail.com

Re: Default virtualhost on Debian Jessie with Apache 2.4.10

[Daniel Bareiro]

Hi, Marco.

On 07/05/15 04:29, Marco Stoecker wrote:

> But what happens to the mailman site, if I disable listening on port 80?
> Will the mailman site still be available?

This suggests that you have Mailman listening on port 80 not https. So
here I think the alternative to avoid behavior "catch-all" of the
default host on port 80 would be to use _default_ as mentioned in the
example of the above email (or put Mailman as the default site, as Bob
said).

I would prefer using _default_ because that way it will return 404 when
there is not a match for the site name.


Best regards,
Daniel




signature.asc
Description: OpenPGP digital signature

Re: Default virtualhost on Debian Jessie with Apache 2.4.10

[Daniel Bareiro]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/05/15 14:22, Marco Stoecker wrote:

> Hi Bob

Hi, Bob and Marco.

Bob, I appreciate your interest and time spent in testing.

> thanks for your help. I did it the other way. Just installed wheezy
> on a 2nd machine, installed apache2, disabled the default site and
> still, if I call http://192.168.10.16, it shows the default site.
> So I was wrong, saying wheezy did different. But is where can I
> disable the default completely (I guess somewhere to change the
> DocumentRoot in the main config)?

I also tested on a new installation with Wheezy in a LXC container and
the behavior was the same as in Jessie. I would have underwritten that
some time it was different. Sorry for the confusion.

Under these circumstances, I believe that the only alternative would
be to use _default_ in the VirtualHost directive. Maybe something like
this?


RedirectMatch 404 (.*)



RedirectMatch 404 (.*)




Best regards,
Daniel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlVOAjsACgkQZpa/GxTmHTddFgCeMdyVDgxV79fs5QNvtbIFaKgR
Pk8AniVS0DyGwDLzwLVJ6ccxuFSaK/Cu
=8Kk/
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/554e023b.8030...@gmx.net

Re: Open ports

[Christian Seiler]

On 05/09/2015 01:25 PM, Bill wrote:
> I'm still running wheezy but noticed a couple of open ports the other
> day. This is just a simple laptop - no nfs access needed, no need for a
> networked port mapper, and certainly not a dns server.
> 
> So why are they there,

Well, Debian's policy for daemons generally is that if they are
installed, they are enabled by default.

> what uses them and why shouldn't I close them?
> (I'm assuming there must be a good reason to have wide open ports.)
>>># netstat -nplt
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address   Foreign Address State  
> PID/Program name
> tcp0  0 0.0.0.0:111 0.0.0.0:* LISTEN 
> 1904/rpcbind
> tcp0  0 0.0.0.0:51062   0.0.0.0:* LISTEN 
> 1935/rpc.statd

rpc.statd will be started unless you set NEED_STATD=no in
/etc/default/nfs-common. Since you said you don't use NFSv3, you can
safely do that.

rpcbind is started from /etc/init.d/rpcbind. If you don't use NFS or NIS
at all, you don't need to have that running. To disable it under Wheezy,
use:

update-rc.d rpcbind disable

After that, it won't be started anymore at boot.

Christian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/554df48d.9090...@iwakd.de

Open ports

[Bill]

Hi,
I'm still running wheezy but noticed a couple of open ports the other 
day. This is just a simple laptop - no nfs access needed, no need for a 
networked port mapper, and certainly not a dns server.


So why are they there, what uses them and why shouldn't I close them?
(I'm assuming there must be a good reason to have wide open ports.)

Thanks,

b.

>># netstat -nplt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address 
State   PID/Program name
tcp0  0 0.0.0.0:111 0.0.0.0:* 
LISTEN  1904/rpcbind
tcp0  0 0.0.0.0:51062   0.0.0.0:* 
LISTEN  1935/rpc.statd



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/554deeab.8000...@uniserve.com

Re: Temporarily hold a package............

[Charlie]

On Sat, 9 May 2015 10:45:06 +0200 Jean-Marc sent:

> > I have been looking through the man pages for: apt-get, apt-get
> > upgrade, but I'm certain I don't understand how I might hold a
> > package for a while?
> >   
> 
> apt-mark hold openssl
> 
> man apt-mark
> 
> Cheers,
> 
> Jean-Marc 

Thank you.

I had never even known about apt-mark and when Matthias pointed it out,
tried it, read the man page and was amazed.

Thank you both.
Charlie

-- 
Registered Linux User:- 329524
***

"What is man without the beasts? If all the beasts were gone,
men would die from a great loneliness of spirit." 
Attributed to Chief Seattle - Suquamish Crisis Chief

***

Debian GNU/Linux - Magic indeed.

-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150509212835.23cbdb13@taogypsy

run wireshark as non-root

[mudongliang]

First,My version of wireshark is Version 1.12.1 (Git Rev Unknown from
unknown),I search it in the debian packages of Jessie , the version is
right , but the content of brackets is out of my understanding! 

Second, I want to run wireshark as non-root ! So I search it in
Google ,the webpage
(http://blog.binarymist.net/2013/04/13/running-wireshark-as-non-root-user/)
tells me do the following procedure :

1.from your console:
  sudo dpkg-reconfigure wireshark-common
You’ll be prompted: Configuring wireshark-common

2.Respond yes.
The wireshark group will be added

The help text also warns about a security risk which isn’t an issue
because setuid isn’t used. Rather what actually happens is the
following:
addgroup --quiet --system wireshark
chown root:wireshark /usr/bin/dumpcap
setcap cap_net_raw,cap_net_admin=eip /usr/bin/dumpcap

3.You will then have to manually add your user to the wireshark group.
sudo adduser kim wireshark # replacing kim with your user
or
usermod -a -G wireshark kim # replacing kim with your user

log out then back in again.
Third , I do not restart my computer , and it does not take effect! 
I find everything is right! The group wireshark exists, my account is in
the group and the dumpcap(/usr/bin) is root wireshark!
Why I need to restart my computer?
And is the procedure above right or suitable for Debian Jessie???

mudongliang 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/blu436-smtp253566c90126a3fb5e98d3cbc...@phx.gbl

ssh tunnels or openvpn/IPsec?

[Petter Adsen]

I have a VPS running Jessie, and would like to set up rsyslog to
forward log messages to another Jessie box at home. At the same time, I
want to set up a munin node and collectd also on the VPS, and grab data
from those.

Now the question becomes; AFAIK, I could do this with ssh tunnels and
forward the ports on my router/firewall, or I could use something like
openvpn or IPsec (strongswan). The problem is that I haven't really
messed with any of these before - what would be the best choice in this
situation?

Note that I'm not asking for a complete configuration, all I want is
some advice as to which of these technologies I should begin to read up
on. The IPsec article on the Debian wiki is from Sarge, so it is quite
outdated, but the openvpn article is recent and seems helpful.

Any insights/advice/links, etc?

Petter

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."


pgpdTRx_JqQ6t.pgp
Description: OpenPGP digital signature

Re: Temporarily hold a package............

[Jean-Marc]

Sat, 9 May 2015 13:20:40 +1000
Charlie  écrivait :

> 
>   From my keyboard:
>
> I have been looking through the man pages for: apt-get, apt-get upgrade,
> but I'm certain I don't understand how I might hold a package for a
> while?
> 

apt-mark hold openssl

man apt-mark

Cheers,

Jean-Marc 


pgpO3biF3Ixm1.pgp
Description: PGP signature

Re: Help with ddrescue

[Bob Proulx]

German wrote:
> Bob Proulx wrote:
> >   ddrescue if=/dev/sdX of=/dev/sdY /var/tmp/rescuelogfile
> 
> Hmm.. The Wanderer suggest that *if= and of=* is the wrong syntax.

Argh!  I have made two typos in the space of the last two messages.  I
can't believe I made a mistake this silly.

> He says that this should be simple as this:
> 
> ddrescue /dev/sdX /dev/sdY /path/to/logfile
> 
> Who is right?

The Wanderer is correct.  The if= and of= is 'dd' syntax not
'ddrescue'.  I goofed up the suggestion.  With ddrescue there are
three arguments, infile, outfile and logfile.

When reading postings such as these one should always read the
official documentation.  That would clear all of it up
authoritatively.  For ddrescue here is the documentation online.

  http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html

Bob


signature.asc
Description: Digital signature

Jessie installer fails on Acer C720

[Juha Heinanen]

Jessie installer (in debian-8.0.0-amd64-netinst.iso) fails on Acer C720.
After selecting Install screen goes blank and Jessie installer gets
restarted by Seabios.  This has been reported earlier on this thread:

https://lists.debian.org/debian-boot/2015/01/msg00300.html

but no reason or fix has been given.  Strange thing is that Wheezy
installer and various Ubuntu installers work fine on Acer C720.

Someone has suggested that perhaps this has something to do with the
Linux kernel version included in the ISO file.

Is it somehow possible to replace the kernel of the ISO file?  I do have
a perfectly working linux-image-3.17.7_amd64.deb that I could give a
try.

-- Juha


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/21837.47866.97960.807...@tutpro.com

Re: Temporarily hold a package............

[Charlie]

On Sat, 09 May 2015 09:11:29 +0200 Matthias Bodenbinder sent:

> or hold a package
>   sudo apt-mark hold package_name

Thanks again Matthias

Worked a treat.

Charlie
-- 
Registered Linux User:- 329524
***

Pity the man who has a character to support -- it is worse than
a large family -- he is silent poor indeed. - Henry David
Thoreau

***

Debian GNU/Linux - Magic indeed.

-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150509173629.75894c73@taogypsy

Re: Temporarily hold a package............

[Charlie]

On Sat, 09 May 2015 09:11:29 +0200 Matthias Bodenbinder sent:

> Hi Charlie,
> 
> you could either pin a package in /etc/apt/preferences.d/ 
>   Package: hello
>   Pin: release n=lenny
>   Pin-Priority: 995
>   ..
>   see
> http://blog.opperschaap.net/2009/12/12/using-the-preferences-file-on-debian-and-debian-based-distributions/
>  
> or hold a package
>   sudo apt-mark hold package_name
>   ..
>   see
> http://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package
> 
> Matthias


Thank you Mathias.

-- 
Registered Linux User:- 329524
***

I am not afraid of storms, because I am learning to sail my
ship. .Louise May Alcot.

***

Debian GNU/Linux - Magic indeed.

-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150509173158.4f54afa6@taogypsy

Re: Temporarily hold a package............

[Matthias Bodenbinder]

Am 09.05.2015 um 05:20 schrieb Charlie:
> 
>   From my keyboard:
>
> I have been looking through the man pages for: apt-get, apt-get upgrade,
> but I'm certain I don't understand how I might hold a package for a
> while?
> 
> Anyone who can and is inclined to help, might assist me for the whole
> testing cycle in this case with their advice.
> 
> I get this when I attempt an upgrade of stretch:
> 
> Retrieving bug reports...
> 
> Done Parsing Found/Fixed information... 
> 
> Done serious bugs of openssl (1.0.1k-3 → 1.0.2a-1) 
>  b1 - #770605 - openssl: Removes symbol without SONAME bump
>
> Merged with: 768476 768522 769023 770278 771169 771993 781094 781929
> 
> Summary:
> openssl(1 bug)
> 
> Are you sure you want to install/upgrade the above packages?
> [Y/n/?/...] n
> **
> ** Exiting with an error in order to stop the installation. **
> ** :


Hi Charlie,

you could either pin a package in /etc/apt/preferences.d/ 
Package: hello
Pin: release n=lenny
Pin-Priority: 995
..
see 
http://blog.opperschaap.net/2009/12/12/using-the-preferences-file-on-debian-and-debian-based-distributions/

or hold a package
sudo apt-mark hold package_name
..
see 
http://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package

Matthias


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mikbv1$rc$1...@ger.gmane.org

Re: Help with ddrescue

[German]

On Fri, 08 May 2015 19:52:04 -0400
The Wanderer  wrote:

> On 05/08/2015 at 07:33 PM, German wrote:
> 
> > On Fri, 08 May 2015 19:20:37 -0400
> > The Wanderer  wrote:
> > 
> >> On 05/08/2015 at 07:08 PM, German wrote:
> 
> >>> That's what I got:
> >>> 
> >>> spore@asterius:~$ lsblk
> >>> NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
> >>> sda  8:00 119.2G  0 disk 
> >>> ├─sda1   8:10   512M  0 part /boot/efi
> >>> ├─sda2   8:20 111.3G  0 part /
> >>> └─sda3   8:30   7.4G  0 part [SWAP]
> >>> sdb  8:16   0 465.8G  0 disk 
> >>> sdc  8:32   0   1.8T  0 disk /media/spore/9F86-0131
> >>> sdd  8:48   0   1.8T  0 disk 
> >>> └─sdd1   8:49   0   1.8T  0 part 
> >>> 
> >>> Where sdd is my failed drive. sdc is my spare drive. The correct
> >>> procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ?
> >> 
> >> No. That might potentially work (except that, if I'm reading the
> >> ddrescue man page correctly, the syntax is wrong), but it wouldn't
> >> be correct.
> >> 
> >> First, unmount /dev/sdc.
> 
> Note for the record: The other steps will erase any data which is
> presently on /dev/sdc. I figure you probably already know that, but I
> just want to be explicit about it.
> 
> >> Then do one of two things:
> >> 
> >> 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or
> >> parted or whatever partitioning tool you choose), and then run
> >> 
> >> ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log
> >> 
> >> 2) run
> >> 
> >> ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log
> > 
> > Ok, I think I am getting closer. How big is a log file?
> 
> The size of the log file depends on two things: the size of the data
> source which is being copied/rescued, and the number of errors which
> occur while attempting to read that data source.
> 
> It can be very small, or it can be moderately large. Even in a
> ridiculous case, however, I wouldn't expect it to be more than a few
> hundred megs - unless the source drive is so bad that you're not going
> to be getting any data back off of it anyway.
> 
> > Can it be anywhere on all drives that have enough space? For
> > instance:
> > 
> > ddrescue /dev/sdd /dev/sdc /dev/sda2/ddrescue.log will work?
> 
> Not quite. /dev/sda2/ is not a directory; it's a device node.
> 
> Since /dev/sda2 is mounted to / (the root filesystem), the correct
> equivalent to this command would be:
> 
> ddrescue /dev/sdd /dev/sdc /ddrescue.log
> 
> and although I wouldn't advise storing a log file in the root
> directory, the command should work.
> 
> The log file itself can be placed in any writable location which has
> enough space.
> 

UPDATE: Digging into it more, I found out Gentoo small tutorial and it
was almost as you suggested, but with -f and -n flag. Here it is:

Disk to Disk

In this scenario the hard disk drive /dev/sdb is about to fail and we want to 
create an exact copy on a new hard disk drive /dev/sdc, which should be at 
least the same size as the source drive.

First round, we just copy every block without read error and log the errors 
into /root/rescue.log

Warning
All data on /dev/sdc will be lost and also are the partitions or partition 
table, if any.
root #ddrescue -f -n /dev/sdb /dev/sdc /root/rescue.log

Second round, we copy only the bad blocks and try 3 times to read from 
source before we give up

root #ddrescue -d -f -r3 /dev/sdb /dev/sdc /root/rescue.log

Now the new drive could be mounted and the file system checked for 
corruption



I am running ddrescue now for 7 hours. 595000 mb rescued. The speed
fell off for some reason. In the beginning, it was about 54000, now
just 6000. Have no idea why this is.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150509030944.284b7...@asterius.asterius.net