I want to somehow "crack" the Uefi "Bios" screen of my packard bell ENLG81BA Notebook

[David]

I want to somehow "crack" the Uefi "Bios" screen of my ENLG81BA Notebook.

For example for looking into the Boot order or editing it.

The question is how I can use a grml CD / DVD / USB-Stick (I have 
already downloaded the grml iso image).


Or is it possible even without grml through a command line when GRUB is 
starting?


The F2 key that during boot opens the Uefi "Bios" screen does not work.

The F12 that normally unlocks the F2, also does not work.

Loading the Debian efivars kernel module which is necessary to execute 
the programs efivar and efibootmgr is impossible, it results in 
following error message:


***

modprobe: ERROR: could not insert 'efivars': No such device

***

... the assumption is that the ENLG81BA is very, very good protected 
against opening the Uefi "Bios" screen.


I no longer have Windows on it, under Windows 10 I could install the 
"easyUEFI" Program and use the menu command


reboot into Uefi screen.

But because I no longer have Windows I can no longer use that program.

***

I want to even know more about my computer. The next question is: can 
the computer, when executing update-grub and the old Windows 7 disk 
attached through usb, find it?


And if it finds it - can it then even boot the externally attached 
Windows 7 disk?


This is an hpdv9000 harddisk and I found that no cases are available; I 
had to order - through ebay - a case which is shipped directly from 
China, delivery time one to two months, which is not for usb cable but 
fits into the CD / DVD slot, do not know when I will receive it and 
whether it will work or not.


***

Hope there is somebody out there who has the exact same computer model 
as me, and exact knowledge about its use and configuration under Debian. 
Debian itself - it is the "stretch" (testing) distribution - boots and 
works fine.

Re: dd - proper use or more suitable program

[Richard Owlett]

On 11/11/2016 10:45 PM, Andy Smith wrote:

Hi Richard,

On Fri, Nov 11, 2016 at 03:31:21PM -0600, Richard Owlett wrote:

How big might the logfile be when trying to recover a known flaky 300
GB drive. I've lots of space? Some convienient, some not.


TL;DR: this depends on how many bad sectors you expect to find. If
the number is likely to be low then the map file should be a matter
of kilobytes in size.


Based on your example calculations I should be in good shape. 
Only one partition [the old c: drive] seems to be in bad shape. 
I've found some tutorial material that clears up enough that I'm 
confident of running safely even if not optimized.







I've never looked into this before as it's never been an issue for
me, but looking at:

 
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html#Mapfile-structure

The header of the map file looks like:

  # Mapfile. Created by GNU ddrescue version 1.21
  # Command line: ddrescue -d -c18 /dev/fd0 fdimage mapfile
  # Start time:   2015-07-21 09:37:44
  # Current time: 2015-07-21 09:38:19
  # Copying non-tried blocks... Pass 1 (forwards)
  # current_pos  current_status
  0x0012 ?
  #  possize  status

…which is 304 bytes.

After that there is one line for each range of blocks depending on
their status (finished, not tried yet, failed etc).

I am thinking that the absolute worst case in terms of maximal
number of lines in this file would be if every other sector were
failed, so you'd have an alternating sequence of:

0x  0x0001  +
0x0001  0x0001  -
0x0002  0x0001  +
0x0003  0x0001  -

for the entire device. That's 52 bytes for every two blocks.

The default block size is 512 bytes in ddrescue, so two blocks
covers 1024 bytes of your device.

If your device is 300 gigabytes in size—and I'll assume that is SI
power of ten giga- (not binary power of two gibi-) as is common with
drive manufacturers, so 300,000,000,000 bytes—then that's
300,000,000,000 / 1,024 = 292,968,750. That times 54 bytes is
15,820,312,500 bytes. Or 14.73GiB. Plus a ~304 byte header.

As far as I can see that is the absolute worst case and for a more
realistic scenario of a device with only a couple of bad sectors
you'd be looking at mere kilobytes of map file size.

For example, if merely 1% of the sectors were bad (and I would
suggest that even that would represent a catastrophically damaged
device that you will find very difficult to extract any sense out
of) then you'd still only be looking at a map file with 5,859,375
bad blocks in it (5,859,375 bad sectors out of 585,937,500 total
512-byte sectors in a 300,000,000,000 byte device). This would
require 5,859,376 different ranges in the map file, with each range
being 27 bytes, so 27 * 5,859,376 = 158,203,152 bytes = 150.9MiB.

I doubt you will see 5.9 million bad sectors on your 300G drive!

Basically whenever my destination has had noticeably more space than
the source device I haven't spared a thought to this so have never
worked it out before. I think the above is correct but look forward
to a correction from anyone who knows better.

Also do note that should you run out of space when writing the map
file, you still have the map file that has been written to date, so
you can extricate yourself from the situation and rerun ddrescue,
safe in the knowledge that it will pick up from where it got to.

If you are expecting serious numbers of bad sectors then your most
precious resource may actually be time. ddrescue tries REALLY HARD
to read a bad sector with each try potentially taking 2 or more
minutes. So on the hypothetical "1% broken" drive with 5.9 million
bad sectors, a single pass could take upwards of 10 million minutes
(19 years). And sometimes multiple passes are required to read a bad
sector.

Cheers,
Andy

Ich möchte damit aufhören, so falsch herum zu funktionieren,

[David]

JanDavid, Alkoholiker und Zwanghafter Schuldenmacher.

Wenn ich an Geldmangel leide, dann ist der Geldmangel meist selbst 
verschuldet durch schlechte Geldeinteilung.


Er ist zum Teil nicht selbst verschuldet, denn ich bin eine Person mit 
sehr niedrigem Einkommen.



Gleichgültig, ob der Geldmangel selbst verschuldet ist oder nicht, 
reagiere ich immer wie folgt:


die Gedanken, wo kann ich mir Geld leihen, wo kann ich mir Geld leihen, 
wie kann ich überziehen, wie kann ich überziehen (kann ich de facto 
nicht mehr, weil P-Konto) sind bekanntermaßen ständig da. Die werden 
immer intensiver und noch intensiver und noch intensiver.


An Möglichkeiten mein niedriges Einkommen aufzustocken, also hinzu zu 
verdienen, denke ich dann gar nicht mehr.


Ich funktioniere also genau falsch herum.

***

Immer wenn ich im Stress bin - es gibt auch andere Stressoren - auch 
solche, die nicht selbst verschuldet sind - ist die Möglichkeit, Geld zu 
*verdienen* anstatt mir welches zu leihen, ganz, gaanz weit weg.


Ich möchte damit aufhören, so falsch herum zu funktionieren, und bitte 
meine höhere Macht darum, dass ich fähig werde wozu ich bislang nicht 
fähig bin, nämlich bei Geldmangel zusätzliche Einnahmen zu erwirtschaften.


***

Zum Glück wurde ich durch einen Bekannten aufmerksam gemacht auf eine 
Möglichkeit, geringfügige zusätzliche Einnahmen zu erzielen, die ich vor 
einem Monat noch im Kopf hatte, aber die letzten paar Wochen dauernd weg 
war. Die Möglichkeit war vollkommen vergessen.


g24h

Re: I want to somehow "crack" the Uefi "Bios" screen of my packard bell ENLG81BA Notebook

[Sven Joachim]

On 2016-11-12 09:02 +0100, David wrote:

> I want to somehow "crack" the Uefi "Bios" screen of my ENLG81BA Notebook.
>
> For example for looking into the Boot order or editing it.
>
> The question is how I can use a grml CD / DVD / USB-Stick (I have
> already downloaded the grml iso image).
>
> Or is it possible even without grml through a command line when GRUB
> is starting?

There should be "System setup" in the grub menu.  If it isn't there, use
'c' to get a commandline and type "fwsetup".

Cheers,
   Sven

Re: set domain name in Debian `

[Glenn English]

(Resend. Accidentally sent to a human instead of to the list...)


> On Nov 11, 2016, at 11:45 PM, Andy Smith  wrote:
> 
> Okay. So I think we should focus on why "hostname -f" returns the
> wrong/outdated info. I'm not sure yet.
> 
> Out of interest what does "hostname -d" return?

slsware.dmz

(Wrong)

> Should be just the
> domain name part

It is. Of the wrong FQDN.

> And what is the contents of /etc/hostname and /etc/hosts?

cat /etc/hostname: srv

(Right) 

This is what plain hostname returns, and this is the CLI prompt, too. But 
hostname -f claims the hostname is 'www'. Must be coming from different places.

/etc/hosts, see below.

> I'm assuming you have actually rebooted at least once after changing
> /etc/hostname and /etc/hosts, yes?

At least once. But I didn't change /etc/hostname -- nothing wrong with it.

-- 
Glenn English

> # Host Database
> # localhost is used to configure the loopback interface
> # sudo cp hosts /etc ; dist `pwd`/hosts /etc all hosts
> # The following lines are desirable for IPv6 capable hosts
> # when the system is booting.  Do not change this entry.
> #   
> ::1   ip6-localhost   ip6-loopback
> fe00::0   ip6-localnet
> ff00::0   ip6-mcastprefix
> ff02::1   ip6-allnodes
> ff02::2   ip6-allrouters
> ff02::3   ip6-allhosts
> 
> 127.0.0.1 localhost localhost.localdomain lh lcl
> 
> # misc ne'r-do-wells
> 127.0.0.2   ad.doubleclick.net
> 127.0.0.2   mmv.admob.com
> 
> # Pasadena
> 206.135.251.11rrserv.richeyrentals.comrrrc rrc rrserv
> 
> $ an indra IP
> 209.169.0.5   indra.net   indra inc
> 
> # a FRII IP
> 216.17.135.75 www.frii.netfrii
> 
> 
> # pass I slsware.org -- all routable IPs; no NAT
> 216.17.203.64 slsware.org
> 216.17.203.65 out.slsware.org oso
> 216.17.203.66 srv.slsware.org sso
> 216.17.203.67 gobook.slsware.org  gso gbo
> 216.17.203.68 unused0.slsware.org u0so
> 216.17.203.69 unused1.slsware.org u1so
> 216.17.203.70 printer.slsware.org pso
> 216.17.203.71 broadcast.slsware.org   bso
> 
> 
> # around the router
> 192.168.0.5   brouterloopback.slsware.per brouterloopback blsp blo
> 192.168.0.9   brouter2.slsware.perbrouter2 b2sp
> 
> # perimeter boxen
> 192.168.1.1   brouter.slsware.per brouter bsp
> 192.168.1.2   firewall.slsware.perfsp pixp
> 
> 192.168.1.3   1721.slsware.perlrsp lsp
> 192.168.1.4   gobook.slsware.per  gsp 
> 
> # .net DMZ
> 192.168.2.1   firewall.slsware.dmzfsd pixd
> 
> 192.168.2.150 rpd0.slsware.dmzrpd0
> 192.168.2.151 rpd1.slsware.dmzrpd1
> 192.168.2.152 rpd2.slsware.dmzrpd2
> 192.168.2.153 rpd3.slsware.dmzrpd3
> 
> 192.168.2.201 outgoing.slsware.dmzosd
> 192.168.2.202 ns2.slsware.dmz ns2
> # 192.168.2.203   srv.slsware.dmz srv
> 192.168.2.203 www.slsware.dmz wsd srv
> 192.168.2.203 mail.slsware.dmzmsd srv
> 192.168.2.203 ntp.slsware.dmz ntp srv
> 192.168.2.203 ns1.slsware.dmz ns1dns1 srv
> # 192.168.2.204   server.slsware.dmz  ssd
> 192.168.2.205 log.slsware.dmz lsd 
> 192.168.2.205 ns0.slsware.dmz ns0 lsd
> 
> 192.168.2.9   gobook.slsware.dmz  gsd
> 
> # virtuals
> 192.168.2.203 www.bouldermedicaladvocate.com  bma
> 
> # LAN
> 192.168.3.1   firewall.slsware.lanfsl pixl
> 
> # DMZ on the LAN 192.168.3.150..55
> # the unused rpi mark3B
> 192.168.3.150 rpl0.slsware.lanrpl0
> # the piPile -- .151 is 1 3B, the others are 2Bs
> 192.168.3.151 rpl1.slsware.lanrpl1
> 192.168.3.152 rpl2.slsware.lanrpl2
> 192.168.3.153 rpl3.slsware.lanrpl3
> # the HP/3.5" screen
> 192.168.3.154 rpl4.slsware.lanrpl4
> # the main sls server
> 192.168.3.155 supermicro.slsware.lan  sml sm5
> 
> 192.168.3.2   timecapsule.slsware.lan tsl
> 192.168.3.3   lanserver.slsware.lan   lsl
> 192.168.3.4
> 192.168.3.5   4240n.slsware.lan   4240 printer
> 192.168.3.6   maxi.slsware.lanmaxi msl
> 192.168.3.7
> 192.168.3.8
> 192.168.3.9   gobook.slsware.lan  gbl
> # 192.168.3.10gobook wifi (below)
> 192.168.3.11
> 192.168.3.12  sbox.slsware.lansbox ssl
> 192.168.3.13
> 192.168.3.14  lmaxi.slsware.lan   lmaxi lmsl
> 192.168.3.15
> 192.168.3.16  air.slsware.lan air asl
> 192.168.3.17  mini.slsware.lanminisl
> ;
> 192.168.3.22  se30.slsware.lansesl
> 192.168.3.25  tv.slsware.lan  tvsl
> 192.168.3.26  bd.slsware.lan  bdsl
> 
> # Juniper firewall - WAN
> 
> # Juniper firewall - DMZ
> 
> # Juniper firewall - LAN 192.168.3.50..59
> 192.168.3.50  ssg50.slsware.l

[SOLVED]Re: wheezy, cannot change the address of eth1

[Gene Heskett]

On Friday 11 November 2016 23:49:18 Andy Smith wrote:

> Hello,
>
> On Fri, Nov 11, 2016 at 09:13:26PM +, Darac Marjal wrote:
> > To cut a long story short, you can't add a default route if you
> > already have one (well, technically you can, but you'd need to
> > provide more information). You probably have a default route sending
> > traffic over eth0.
>
> Yes, I concur. He needs to remove the "gateway" line from his eth1
> stanza as he does not need another default route going out of that
> interface.
>
> Cheers,
> Andy

Done that, on eth0:1 now. and I can talk to it. But its slow, darned 
slow, clicking on a menu item takes 7 or 8 seconds to see the result. 

The first thing I want to do is put a newer firmware in it, 12 revisions 
newer.  I registered it with netgear, so I'll ding their LL Monday as 
while I have downloaded and unpacked the file, there is not any 
instructions about how that is done. I may have found that menu function 
but I don't want to brick it if its something else, so we'll let tech 
support tell me how.

It claims to be able to do dhcp, and my dd-wrt router has a server, but I 
also have a mac address list it restriction is not on yet so thats being 
rejected.  Attempts to put it manually on my local networks address 
block have failed, but some of their menu's may as well be in swahili 
since I have never dealt with a ""managed" switch before.  I expect the 
first thing to do after the firmware is updated, is add its MAC to 
dd-wrt's list so dhcpd works.

What I want it to be is a basic 8 port hub, plugged into a non managed 
switch via about a 60 foot cable plugged into the switch here in this 
room, and currently hooking up one machine in the garage.  The garage is 
growing more machines, probably 2 more r-pi's before I am fully hooked 
to a lathe I am cnc'ing.

So the instant problem is solved, and I thank the several people who did 
respond with helpfull links, you know who you are.

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 

Re: Problem attempting to use xorriso

[Curt]

On 2016-11-11, Gene Heskett  wrote:
> On Friday 11 November 2016 05:07:42 Curt wrote:
>
>> On 2016-11-10, Richard Owlett  wrote:
>> > It may be close, I pre-date the Harvard MarkI. I am definitely
>> > older than Linus Torvalds father ;)
>>
>> Is this the senile equivalent of a pissing contest? Or the pissing
>> equivalent of a senile contest?
>
> And at 82, I suspect I am the older, but with a psa in the 10+ range, I 
> don't enter any pissing contests. :(

Well, I think the general rule is there's always somebody older than you
no matter how old you are, unless you find yourself in the
exceptional case of being the oldest in the whole wide world (a fate I
would wish upon you, except that I've remarked that those in the running
pushing 120 years, wheel-chair ridden and pretty much deaf, blind and
toothless, seem to be enjoying a fate I wouldn't wish on anyone).

> How the heck did this thread degenerate to this?

I degenerated it, I'm afraid.

> Cheers, Gene Heskett


-- 
“It is enough that the arrows fit exactly in the wounds that they have made.”
Franz Kafka

Re: set domain name in Debian `

[Andy Smith]

Hi,

On Sat, Nov 12, 2016 at 02:00:11AM -0700, Glenn English wrote:
> (Resend. Accidentally sent to a human instead of to the list...)

I responded off-list to Glenn since that one arrived first and I
wasn't sure if Glenn intended the contents of their /etc/hosts to be
private. Later I saw this copy on-list.

> > On Nov 11, 2016, at 11:45 PM, Andy Smith  wrote:
> > 
> > Okay. So I think we should focus on why "hostname -f" returns the
> > wrong/outdated info. I'm not sure yet.
> > 
> > Out of interest what does "hostname -d" return?
> 
> slsware.dmz

The system thinks Glenn's domain name is "slsware.dmz". Glenn wants it
to be "slsware.org" (I think).

> cat /etc/hostname: srv

Glenn has set the host name to be "srv".

I am 95% confident that the reason that Glenn's system thinks the
FQDN is "www.slsware.dmz" is because the first instance of "srv" in
the /etc/hosts is:

> > 192.168.2.203   www.slsware.dmz wsd srv

"hostname" returns what is in /etc/hostname (unless changed agfter
system startup).

"hostname -f" returns the part up to the first dot from whatever is
returned by resolving "hostname" against /etc/hosts.

"hostname -d" returns the part after the first dot from whatever is
returned by resolving "hostname" against /etc/hosts.

I think that if Glenn placed a line higher up that read:

192.168.2.203   srv.slsware.org srv

then the desired result would be achieved.

I would also add that this is a fairly large hosts file which is
ripe for causing confusion. I would generally recommend keeping
hosts files small, containing only enough information as needed for
bootstrapping, and using DNS for everything else. The rest of the
systems on the Internet (and maybe intranet) will be using DNS, and
it is desirable for there to be one source of truth.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Problem attempting to use xorriso

[Thomas Schmitt]

Hi,

[pissing contest and associated difficulties]

Gene Heskett wrote:
> > How the heck did this thread degenerate to this?

Curt wrote:
> I degenerated it, I'm afraid.

An uprise of the progressive youth against us old farts ?

https://s-media-cache-ak0.pinimg.com/564x/53/ca/af/53caafee1d123414aa9d431aab2ca414.jpg


Maybe one should install a warning sign at the archive to tell
future readers that there is nearly no info about xorriso in this
thread.


Have a nice day :)

Thomas

Re: Problem attempting to use xorriso

[Gene Heskett]

On Saturday 12 November 2016 05:50:42 Thomas Schmitt wrote:

> Hi,
>
> [pissing contest and associated difficulties]
>
> Gene Heskett wrote:
> > > How the heck did this thread degenerate to this?
>
> Curt wrote:
> > I degenerated it, I'm afraid.
>
> An uprise of the progressive youth against us old farts ?

Probably.  Now where did I put my LART. :)

> https://s-media-cache-ak0.pinimg.com/564x/53/ca/af/53caafee1d123414aa9
>d431aab2ca414.jpg
>
>
> Maybe one should install a warning sign at the archive to tell
> future readers that there is nearly no info about xorriso in this
> thread.
>
>
> Have a nice day :)
>
> Thomas


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 

Re: set domain name in Debian `

[Brian]

On Sat 12 Nov 2016 at 10:25:16 +, Andy Smith wrote:

> Glenn has set the host name to be "srv".
> 
> I am 95% confident that the reason that Glenn's system thinks the
> FQDN is "www.slsware.dmz" is because the first instance of "srv" in
> the /etc/hosts is:
> 
> > > 192.168.2.203 www.slsware.dmz wsd srv

Do you fancy adding 5% to that figure?
 
> "hostname" returns what is in /etc/hostname (unless changed agfter
> system startup).
> 
> "hostname -f" returns the part up to the first dot from whatever is
> returned by resolving "hostname" against /etc/hosts.
> 
> "hostname -d" returns the part after the first dot from whatever is
> returned by resolving "hostname" against /etc/hosts.
> 
> I think that if Glenn placed a line higher up that read:
> 
> 192.168.2.203   srv.slsware.org srv
> 
> then the desired result would be achieved.

I'd use

127.0.0.1   localhost
127.0.1.1   srv.slsware.org srv

-- 
Brian.

Re: Problem attempting to use xorriso

[Lisi Reisz]

On Saturday 12 November 2016 10:50:42 Thomas Schmitt wrote:
> Maybe one should install a warning sign at the archive to tell
> future readers that there is nearly no info about xorriso in this
> thread.

17 about xorriso and permissions (presenting problem often not the real 
problem, and that may apply also to archive searchers)

6 definitely entirely OT and/or unsuitable for sensitive ears.

Lisi

Re: Gparted will not label an existing FAT32 partition

[Lisi Reisz]

On Friday 11 November 2016 21:58:58 Brian wrote:
> Not installing a recommended package on a default Debian would be a bug.

Aptitude on my current almost vanilla temporary Jessie install doesn't install 
recommends.  But it makes a big point of telling me a) that they are 
recommended and b) that they are not going to be installed.  I then often, 
but not always, install them.  It doesn't strike me as a bug.  This is Debian 
not Ubuntu.

I could, of course, reset aptitude.  I am quite happy with the status quo.

> Not installing a suggested package isn't.

Lisi

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Sat 12 Nov 2016 at 13:45:38 +, Lisi Reisz wrote:

> On Friday 11 November 2016 21:58:58 Brian wrote:
> > Not installing a recommended package on a default Debian would be a bug.
> 
> Aptitude on my current almost vanilla temporary Jessie install doesn't 
> install 
> recommends.  But it makes a big point of telling me a) that they are 
> recommended and b) that they are not going to be installed.  I then often, 
> but not always, install them.  It doesn't strike me as a bug.  This is Debian 
> not Ubuntu.
> 
> I could, of course, reset aptitude.  I am quite happy with the status quo.

Never really used aptitude but I've just installed it and ran the curses
variety of the program. "options" at the top of the screen shows

Option:  Apt::Install-Recommends
Default: True
Value:   True

The behaviour of your aptitude is presumably because you have adjusted
the default behaviour in some way. The new behaviour is not a bug.

Also, a default Debian doesn't have aptitude but apt-get. which installs
recommended packages by default.

-- 
Brian.

Re: set domain name in Debian `

[Henrique de Moraes Holschuh]

On Fri, 11 Nov 2016, Glenn English wrote:
> /proc/sys/domainname says "(none)". hostname -f gives the old domain

/proc/sys/domainname is the kernel's idea of a domain name, which is
only used by some network filesystems (kernel-based NFS, I think),
AFAIK.

Nothing else needs it.  And if you set up such a filesystem, the
userspace utilities should set the kernel domainname properly by
themselves.

Note that the kernel also needs to know the node name (host name without
a domain)... and _this_ is used everywhere.

> name (where does it get it). grep -ir doesn't find the old name string
> anywhere in /etc or in /lib.

hostname -f does this:

1. Asks glibc for the hostname, using gethostname().

2. Does an IP lookup on the hostname, using getaddrinfo() and the
   hostname it got from gethostname(), and returns the result from
   getaddrinfo().

Since it uses glibc for the host name lookup, it is subject to the glibc
name resolver, which is configured through /etc/nsswitch.conf.

Now, gethostname() works like this [in glibc]: it calls the uname()
syscall, and uses the node name returned.  I.e. it looks up the
*hostname* the kernel was set to.

So, glibc's gethostname() will match the output of "uname -n".  This
information was set on the kernel by either systemd, or by the
initscripts.

Initscripts use /etc/hostname to set this information.  I am not well
versed on how exactly systemd persists this information, but it likely
uses /etc/hostname as well.

> I know it must be simple to do -- the installer does it without
> downloading a C library, but it must be in a secret place I don't know
> about...

1. Set /etc/hostname to the *node name* (i.e. just the host name,
   without the domain)

2. Ensure the *node name* _locally_ resolves to an IPv4/IPv6.  Usually
   this is done by adding it to /etc/hosts, so that things will not
   break when the network is down.

   Do it like this in /etc/hosts:
 

   For example:

   /etc/hostname:
   examplehost

   /etc/hosts:
   192.0.2.42  examplehost.example.com  examplehost

   Refer to the item (3) below for the reasoning.

   Full answer:  anything that is resolvable locally when piped by
   glibc through the "hosts" nss module pipeline configured in
   /etc/nsswitch.conf will do.  /etc/hosts is a configuration
   file processed for the "files" nss module typically used in
   /etc/nsswitch.conf.

3. Ensure the IPv4/IPv6 you used for the *node name* resolves to
   the full host name (FQDN).

   Now, there is a trick to doing this when using /etc/hosts.  You
   *must* list the FQDN first in /etc/hosts, as it will return just the
   first match when doing a "reverse lookup".

   The complete answer is: ensure the "hosts" nss module pipeline
   configured in /etc/nsswitch.conf will return as the *first* match,
   for the *node name*'s IPv4/IPv6, the FQDN of the host.


There, this is a bit harder to understand than other answers you got,
but it should get the details right and might be helpful in more
convoluted scenarios.

"man nsswitch.conf" for mode details about /etc/nsswitch.conf.
"man hosts" for more details about /etc/hosts

and each libc function I mentioned also has its own manpage.

-- 
  Henrique Holschuh

Re: Does hdparm not run at startup anymore?

[Alex Mestiashvili]

On 11/12/2016 08:37 AM, Rainer Dorsch wrote:
> + Alexandre, hdparm maintainer
>
> On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
>> Hi,
>>
>> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, 
>> apm does not change. Interesting enough a /etc/init.d/hdparm restart fixes 
>> the problem:
>>
>>
>> root@Silberkiste:~# cat /etc/hdparm.conf

>> /dev/sdb {
>>  apm = 64
>>  spindown_time = 5
>> }
>>
>> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>> Advanced power management level: 254
>> root@Silberkiste:~# /etc/init.d/hdparm restart
>> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
>> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>> Advanced power management level: 64
>> root@Silberkiste:~#
>>
>>
>> Any insight, why I need the /etc/init.d/hdparm restart is very welcome.
>>
>> Thanks
>> Rainer
>>
>>
Hi Rainer,
I can not reproduce this problem on my machine:

lsb_release -c
Codename:jessie

hdparm -V
hdparm v9.43

egrep -v "^$|^#" /etc/hdparm.conf
/dev/sdc {
 apm = 64
 acoustic_management = 250
}
/dev/sdd {
 apm = 128
}
/dev/sdf {
 apm = 48
}


for disk in sdc sdd sdf; do echo $disk; hdparm -I /dev/$disk | egrep
"level:|acoustic"; done
sdc
Advanced power management level: 64
Recommended acoustic management value: 254, current value: 250
sdd
Advanced power management level: disabled
Recommended acoustic management value: 128, current value: 128
sdf
Advanced power management level: 48
Recommended acoustic management value: 208, current value: 0

The values are set after reboot or after init script restart.

Best,
Alex

Re: set domain name in Debian `

[Glenn English]

> On Nov 12, 2016, at 3:25 AM, Andy Smith  wrote:
> 
> The system thinks Glenn's domain name is "slsware.dmz". Glenn wants it
> to be "slsware.org" (I think).

Correct.

> Glenn has set the host name to be "srv".

Correct.

> I am 95% confident that the reason that Glenn's system thinks the
> FQDN is "www.slsware.dmz" is because the first instance of "srv" in
> the /etc/hosts is:
> 
>>> 192.168.2.203   www.slsware.dmz wsd srv

But that isn't the first; it's the fourth. A grep of the hosts file:

> root@srv:~# egrep srv /etc/hosts
> 127.0.0.1 srv.slsware.org
> 216.17.203.66 srv.slsware.org sso
> # 192.168.2.203   srv.slsware.dmz srv
> 192.168.2.203 www.slsware.dmz wsd srv
> 192.168.2.203 mail.slsware.dmzmsd srv
> 192.168.2.203 ntp.slsware.dmz ntp srv
> 192.168.2.203 ns1.slsware.dmz ns1dns1 srv
> 216.17.134.203srv.slsware.net ssn

The first mentions of srv are at the top, both with IPs that could have been 
used to grab the correct domain.

It never occurred to me that something might be looking at aliases; I thought 
the IP address was the important thing. And the srv...dmz entry is commented 
out because I thought it might somehow be used.

I'll remove all mentions of srv (and lots of others to make it shorter) and 
see. 

The hosts file is now:

> root@srv:~# cat /etc/hosts
> # /etc/hosts:  This file describes a number of hostname-to-address
> #
> # This is to be sent to all hosts that need a hosts file
> # (don't really know how yet...)
> #  
> # Host Database
> # localhost is used to configure the loopback interface
> # sudo cp hosts /etc ; dist `pwd`/hosts /etc all hosts
> # The following lines are desirable for IPv6 capable hosts
> # when the system is booting.  Do not change this entry.
> #   
> ::1   ip6-localhost   ip6-loopback
> fe00::0   ip6-localnet
> ff00::0   ip6-mcastprefix
> ff02::1   ip6-allnodes
> ff02::2   ip6-allrouters
> ff02::3   ip6-allhosts
> 
> 127.0.0.1 localhost localhost.localdomain lh lcl
> 
> # pass I slsware.org -- all routable IPs; no NAT
> 216.17.203.64 slsware.org
> 216.17.203.65 out.slsware.org oso
> 216.17.203.66 srv.slsware.org sso
> 216.17.203.67 gobook.slsware.org  gso gbo
> 216.17.203.68 unused0.slsware.org u0so
> 216.17.203.69 unused1.slsware.org u1so
> 216.17.203.70 printer.slsware.org pso
> 216.17.203.71 broadcast.slsware.org   bso
> 
> # misc ne'r-do-wells
> 127.0.0.2   ad.doubleclick.net
> 127.0.0.2   mmv.admob.com

The *only* mention of srv is with the right domain and the right IP.

After a reboot:

> root@srv:~# hostname
> srv
> root@srv:~# hostname -f
> hostname: Name or service not known

And just in case it's the IP:

> root@srv:~# ifconfig
> eth0  Link encap:Ethernet  HWaddr 00:25:90:d5:16:34  
>  inet addr:216.17.203.66  Bcast:216.17.203.71  Mask:255.255.255.248
>  inet6 addr: fe80::225:90ff:fed5:1634/64 Scope:Link
>  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>  RX packets:459 errors:0 dropped:0 overruns:0 frame:0
>  TX packets:470 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:0 txqueuelen:1000 
>  RX bytes:47597 (46.4 KiB)  TX bytes:49637 (48.4 KiB)
>  Interrupt:16 Memory:fbce-fbd0 
> 
> eth1  Link encap:Ethernet  HWaddr 00:25:90:d5:16:35  
>  inet addr:192.168.3.66  Bcast:192.168.3.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)
>  Interrupt:17 Memory:fbde-fbe0 
> 
> 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:68 errors:0 dropped:0 overruns:0 frame:0
>  TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:0 txqueuelen:0 
>  RX bytes:17189 (16.7 KiB)  TX bytes:17189 (16.7 KiB)

And:

> root@srv:~# cat /proc/sys/kernel/domainname 
> (none)

It doesn't give the www answer anymore; it must have been doing something (odd) 
with hosts. But now it claims it can't find anything.

> "hostname" returns what is in /etc/hostname (unless changed agfter
> system startup).
> 
> "hostname -f" returns the part up to the first dot from whatever is
> returned by resolving "hostname" against /etc/hosts.

The 2 dots after resolving hostname, maybe? That does sound very reasonable, 
but it doesn't seem to be working. And how does /proc get a domainname.

-- 
Glenn English
-- 
Glenn English
Did you just click Reply?
If so, change the send
address from gmail to
g...@slsware.net

Re: set domain name in Debian `

[Glenn English]

> On Nov 12, 2016, at 8:46 AM, Henrique de Moraes Holschuh  
> wrote:
> 
> hostname -f does this:
> 
> 1. Asks glibc for the hostname, using gethostname().
> 
> 2. Does an IP lookup on the hostname, using getaddrinfo() and the
>   hostname it got from gethostname(), and returns the result from
>   getaddrinfo().
> 
> Since it uses glibc for the host name lookup, it is subject to the glibc
> name resolver, which is configured through /etc/nsswitch.conf.
> 
> Now, gethostname() works like this [in glibc]: it calls the uname()
> syscall, and uses the node name returned.  I.e. it looks up the
> *hostname* the kernel was set to.
> 
> So, glibc's gethostname() will match the output of "uname -n".  This
> information was set on the kernel by either systemd, or by the
> initscripts.
> 
> Initscripts use /etc/hostname to set this information.  I am not well
> versed on how exactly systemd persists this information, but it likely
> uses /etc/hostname as well.

Bingo! I had a feeling it was convoluted.

> root@srv:~# host srv.slsware.org
> srv.slsware.org has address 216.17.203.66
> root@srv:~# hostname
> srv
> root@srv:~# hostname -f
> srv.slsware.org
> root@srv:~# hostname -d
> slsware.org

I edited /etc/resolv.conf to point the nameserver at the host's IP instead of 
pointing at localhost (this host is the (temporary) DNS server for the .org 
domain).

Now all is well. Except for /proc, which I'll ignore in the future.

Just why the IP worked and 'localhost' didn't is another question -- I assume 
it has something to do with machinations in glibc. I'm not afraid of C, but 
things are working and I've got more interesting things to do today.

Thanks all. It's been quite a ride. Now everybody write it down: it has nothing 
to do with what's in /etc/hosts or /etc/resolv.conf. There has to be a live, 
accessible DNS server for the domain somewhere. At least at slsware.org there 
does.

What idiot designed that?

It does seem that /etc/hosts should work, though...


No, I take it back. I don't think DNS is the whole story. It worked in this 
case, but how does the installer get a domainname?

-- 
Glenn English

Re: Gparted will not label an existing FAT32 partition

[Lisi Reisz]

On Saturday 12 November 2016 15:45:28 Brian wrote:
> The behaviour of your aptitude is presumably because you have adjusted
> the default behaviour in some way. The new behaviour is not a bug.

No, I haven't.  This is a temporary machine, which I have not been using long.  
I have adjusted very little.  I don't remember claiming that anything was a 
bug.

> Also, a default Debian doesn't have aptitude but apt-get. which installs
> recommended packages by default.

Varies with time.  Sometimes it is there and sometimes it isn't.  When 
aptitude isn't there, I install it.  But I don't configure it.

So, after some exploring (aptitude show and aptitude search), in this 
installation (Jessie, 8.6 - I installed Jessie 8.5) aptitude was *not* 
automatically installed and the recommends of aptitude *were* automatically 
installed.  I must watch for next time I have to install/not install some 
recommends and see why and when.

Interesting.  Thanks.

Lisi

Re: dd - proper use or more suitable program

[Richard Owlett]

On 11/12/2016 2:29 AM, Richard Owlett wrote:

On 11/12/2016 1:31 AM, Christian Seiler wrote:

On 11/11/2016 10:38 PM, Richard Owlett wrote:

I was wondering about that.
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
is
not first time user friendly. Will re-read after a good night's
sleep. Will also look for appropriate tutorials. Suggestions?


Well, I would suggest not dumping the result on another partition
but rather into an image file. In that case you'd have the old
drive (not mounted), let's call it /dev/sda, and the new drive
with a partition on it and mounted on /mnt with sufficient free
disk space there.

In the simplest case you'd do:

ddrescue /dev/sda /mnt/defective_drive.img
/mnt/defective_drive.log


I can't get that performing correctly. I have a strong suspicion 
I'm even more confused about mounting than the group suspects :<


Can this be run as a user, or are root permissions required.

May I have a little hand-holding please?
My defective drive is /dev/sdc .
Partition /dev/sdb6 {formatted ext4} is much larger than the 
defective drive.

/dev/sdb is a 1 TB rotating platter drive connected via USB.
How do I mount it and run ddrescue?
I'm tired and likely going in circles. Need to get groceries, 
will be back soon.


Thank you for patience.

Symlinking or hard linking additional storage to /home directories

[Robert Menes]

Hello everyone,

My current desktop setup currently has a Debian installation on a 120GB
SSD, which
is mounted with both the EFI system partition and as / for my rig. I have a
3TB HDD
which I had mounted as /home during install.

As my desktop case still has enough space in it, I was contemplating
getting another
pair of 3TB (or maybe even 4TB!) HDDs, and have them be symlinked or hard
linked
(whichever works better) to my ~/Music and ~/Videos folders. This setup is
currently
has only one user on it (my account, aside from root). I want to do this so
that I have
more space for my media, functioning as a backup for a NAS and for keeping
larger
project files for any audio and video work I do.

My question is this: which is the better path to take? Symlinking or hard
linking another
drive to ~/Music and ~/Videos? I understand that I will need to edit
/etc/fstab and all;
that's fine. Just curious as to whether symlinks or hard links are the way
to go.

Thanks!

--Robert

-- 
Nobody's ever lost in life...they're merely taking the scenic route.
==
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
==
-BEGIN GEEK CODE BLOCK-
Version: 3.1.2
GCS/S/M/MU d- s+: a37 C++(+++) UL>$ P++ L+++ E+ W+ N+ o+ K++ w--- O-
M !V PS+ PE Y+ PGP(+) t+ 5++ X++ R tv b+++ DI+++ D++(---) G++ e+ h-
r++ y+
--END GEEK CODE BLOCK--

Re: Symlinking or hard linking additional storage to /home directories

[Nicolas George]

Le duodi 22 brumaire, an CCXXV, Robert Menes a écrit :
> My question is this: which is the better path to take? Symlinking or hard
> linking another drive to ~/Music and ~/Videos? I understand that I
> will need to edit /etc/fstab and all; that's fine. Just curious as to
> whether symlinks or hard links are the way to go.

You can not do hardlinks across different filesystems, so that part is
settled.

You could not do hardlinks on directories either, you would have to work
plain file per plain file. That would be a pain.

You could use bind mounts, but I really do not recommend it.

I suggest mounting the extra storage somewhere like /data and using
symlinks; that is what I do.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: Symlinking or hard linking additional storage to /home directories

[Lars Noodén]

On 11/12/2016 08:09 PM, Robert Menes wrote:
[snip]
> My question is this: which is the better path to take? Symlinking or hard
> linking another
> drive to ~/Music and ~/Videos? 
[snip]

Directories can only be symlinked.  But you might be interested in mount
instead, especially the --bind option.

Regards,
Lars

Re: Symlinking or hard linking additional storage to /home directories

[Lars Noodén]

On 11/12/2016 08:15 PM, Nicolas George wrote:
[snip]
> You could use bind mounts, but I really do not recommend it.
[snip]

What are the disadvantages of bind mounts?

Regards,
Lars

Re: dd - proper use or more suitable program

[Pascal Hambourg]

Le 12/11/2016 à 18:22, Richard Owlett a écrit :



ddrescue /dev/sda /mnt/defective_drive.img /mnt/defective_drive.log

(...)

Can this be run as a user, or are root permissions required.


Unless the user has read permission on the raw device, it must be run as 
root.



My defective drive is /dev/sdc .
Partition /dev/sdb6 {formatted ext4} is much larger than the defective
drive.
/dev/sdb is a 1 TB rotating platter drive connected via USB.
How do I mount it and run ddrescue?


Mount what ?
You don't mount anything from the defective drive.
You mount the filesystem which will receive the disk image file anywhere 
you like with mount. In the above example it was expected to be mounted 
on /mnt, the usual temporary mount point. So :


mount /dev/sdb6 /mnt

The file manager of your desktop environment may have already mounted it 
for you elsewhere in /media/. Check df or mount.

Re: Symlinking or hard linking additional storage to /home directories

[Nicolas George]

Le duodi 22 brumaire, an CCXXV, Lars Noodén a écrit :
> What are the disadvantages of bind mounts?

They require root privileges for any change.

They are also more expensive than any individual symlink, but it does
not matter much if there are only a few.

But I can reverse the question: what advantages do you see to bind
mounts in that particular circumstance?


signature.asc
Description: Digital signature

Re: set domain name in Debian `

[Henrique de Moraes Holschuh]

On Sat, 12 Nov 2016, Glenn English wrote:
> Thanks all. It's been quite a ride. Now everybody write it down: it
> has nothing to do with what's in /etc/hosts or /etc/resolv.conf. There
> has to be a live, accessible DNS server for the domain somewhere. At
> least at slsware.org there does.

Maybe for the install.

But the whole thing really doesn't need any DNS servers *as long as*
everything you need is resolved statically by some module in
/etc/nsswitch.conf... such as the default "files" module, which reads
/etc/hosts.

At which point, it boils down to a complete enough, correct /etc/hosts

> It does seem that /etc/hosts should work, though...

It does work, provided that you have "files" first in the list of NSS
modules, and you have both the nodename and the FQDN in /etc/hosts for
the correct IPs and in the correct order.  Otherwise, it depends.

> No, I take it back. I don't think DNS is the whole story. It worked in
> this case, but how does the installer get a domainname?

The *installer* either asks the user for the FQDN and gets the nodename,
domain name and FQDN from that (and it *should* write them to /etc/hosts
and /etc/hostname appropriately), or gets information from DHCP/DHCPv6
and the DNS while autoconfiguring.

Now, *what* the DHCP/DHCPv6 and DNS will answer, well, that's up to your
local network.

-- 
  Henrique Holschuh

Re: set domain name in Debian `

[sunrise]

Hi Glenn,


On Sat, 12 Nov 2016 08:50:46 -0700
Glenn English  wrote:

...

>
>It never occurred to me that something might be looking at aliases; I thought 
>the IP
>address was the important thing. And the srv...dmz entry is commented out 
>because I
>thought it might somehow be used.
>
>I'll remove all mentions of srv (and lots of others to make it shorter) and 
>see. 
>
>The hosts file is now:
>
>> root@srv:~# cat /etc/hosts
>> # /etc/hosts:  This file describes a number of hostname-to-address
>> #
>> # This is to be sent to all hosts that need a hosts file
>> #(don't really know how yet...)
>> #  
>> # Host Database
>> # localhost is used to configure the loopback interface
>> # sudo cp hosts /etc ; dist `pwd`/hosts /etc all hosts
>> # The following lines are desirable for IPv6 capable hosts
>> # when the system is booting.  Do not change this entry.
>> #   
>> ::1  ip6-localhost   ip6-loopback
>> fe00::0  ip6-localnet
>> ff00::0  ip6-mcastprefix
>> ff02::1  ip6-allnodes
>> ff02::2  ip6-allrouters
>> ff02::3  ip6-allhosts
>> 
>> 127.0.0.1localhost localhost.localdomain lh lcl
>> 
>> # pass I slsware.org -- all routable IPs; no NAT
>> 216.17.203.64slsware.org
>> 216.17.203.65out.slsware.org oso
>> 216.17.203.66srv.slsware.org sso

This might be your problem??   ^
I suspect the above line should be:

216.17.203.66   srv.slsware.org srv

with the last field matching the hostname.
-Jason


>> 216.17.203.67gobook.slsware.org  gso gbo
>> 216.17.203.68unused0.slsware.org u0so
>> 216.17.203.69unused1.slsware.org u1so
>> 216.17.203.70printer.slsware.org pso
>> 216.17.203.71broadcast.slsware.org   bso
>> 
>> # misc ne'r-do-wells
>> 127.0.0.2   ad.doubleclick.net
>> 127.0.0.2   mmv.admob.com
>
>The *only* mention of srv is with the right domain and the right IP.
>
>After a reboot:
>
>> root@srv:~# hostname
>> srv
>> root@srv:~# hostname -f
>> hostname: Name or service not known
>
>And just in case it's the IP:
>
>> root@srv:~# ifconfig
>> eth0  Link encap:Ethernet  HWaddr 00:25:90:d5:16:34  
>>  inet addr:216.17.203.66  Bcast:216.17.203.71  Mask:255.255.255.248
>>  inet6 addr: fe80::225:90ff:fed5:1634/64 Scope:Link
>>  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>  RX packets:459 errors:0 dropped:0 overruns:0 frame:0
>>  TX packets:470 errors:0 dropped:0 overruns:0 carrier:0
>>  collisions:0 txqueuelen:1000 
>>  RX bytes:47597 (46.4 KiB)  TX bytes:49637 (48.4 KiB)
>>  Interrupt:16 Memory:fbce-fbd0 
>> 
>> eth1  Link encap:Ethernet  HWaddr 00:25:90:d5:16:35  
>>  inet addr:192.168.3.66  Bcast:192.168.3.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)
>>  Interrupt:17 Memory:fbde-fbe0 
>> 
>> 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:68 errors:0 dropped:0 overruns:0 frame:0
>>  TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
>>  collisions:0 txqueuelen:0 
>>  RX bytes:17189 (16.7 KiB)  TX bytes:17189 (16.7 KiB)
>
>And:
>
>> root@srv:~# cat /proc/sys/kernel/domainname 
>> (none)
>
>It doesn't give the www answer anymore; it must have been doing something 
>(odd) with
>hosts. But now it claims it can't find anything.
>
>> "hostname" returns what is in /etc/hostname (unless changed agfter
>> system startup).
>> 
>> "hostname -f" returns the part up to the first dot from whatever is
>> returned by resolving "hostname" against /etc/hosts.
>
>The 2 dots after resolving hostname, maybe? That does sound very reasonable, 
>but it
>doesn't seem to be working. And how does /proc get a domainname.
>

Re: Gparted will not label an existing FAT32 partition

[Tixy]

On Sat, 2016-11-12 at 17:19 +, Lisi Reisz wrote:
> On Saturday 12 November 2016 15:45:28 Brian wrote:
> > The behaviour of your aptitude is presumably because you have adjusted
> > the default behaviour in some way. The new behaviour is not a bug.
> 
> No, I haven't.  This is a temporary machine, which I have not been using 
> long.  
> I have adjusted very little.  I don't remember claiming that anything was a 
> bug.
> 
> > Also, a default Debian doesn't have aptitude but apt-get. which installs
> > recommended packages by default.
> 
> Varies with time.  Sometimes it is there and sometimes it isn't.  When 
> aptitude isn't there, I install it.  But I don't configure it.
> 
> So, after some exploring (aptitude show and aptitude search), in this 
> installation (Jessie, 8.6 - I installed Jessie 8.5) aptitude was *not* 
> automatically installed and the recommends of aptitude *were* automatically 
> installed.  I must watch for next time I have to install/not install some 
> recommends and see why and when.

I'm pretty sure installing recommends is Debian's default. I remember it
changing, and dug up this 2007 announcement of the fact...

https://lists.debian.org/debian-devel-announce/2007/08/msg0.html

I also have as the very first step in my personal notes for installing
Debian instructions to disable that...

Create /etc/apt/apt.conf.d/20norecommends containing

APT {
Install-Recommends "false";
};

-- 
Tixy

trouble setting up raid1

[Bill]

Hi,

I'm trying to install a twelfth raid 1 partition on Jessie 8.5 and a 5 
TB HDD using gpt. Raid partitions 0 through 10 have presented no 
problem, but the twelfth pair of partitions won't pair up.


After I've selected /dev/sda12 and /dev/sdb12, Continue and then Finish 
from the menu, I've still only got Raid device numbers 0-10. /dev/sda12 
and /dev/sdb12 remain unlocked and available for reconfiguration - 
unlike devices 0-10 which show up on the main menu as Raid devices.


I'd guess that it's highly unlikely that there's a maximum number of 
Raid partitions, although I could live with it, but why is Partman 
rejecting my overtures?


And BTW is there any way to unlock or back out of a raid setup during 
configuration just in case I need to change something. How can I delete 
a raid device and start over if I have to? fdisk?


Bill

Re: Symlinking or hard linking additional storage to /home directories

[Lars Noodén]

On 11/12/2016 08:30 PM, Nicolas George wrote:
> Le duodi 22 brumaire, an CCXXV, Lars Nood�n a �crit�:
>> What are the disadvantages of bind mounts?
> 
> They require root privileges for any change.
> 
> They are also more expensive than any individual symlink, but it does
> not matter much if there are only a few.
> 
> But I can reverse the question: what advantages do you see to bind
> mounts in that particular circumstance?

It fits with the /etc/fstab approach, and since Robert mentioned
/etc/fstab mount comes to mind.  Adding the user option there allows a
non-root user to mount or unmount the pair of directories.  However, as
far as technical advantages proper, I don't know.

Regards,
Lars

Re: set domain name in Debian `

[Glenn English]

> On Nov 12, 2016, at 11:17 AM, sunr...@mailbug.com wrote:
> 
> 
> Hi Glenn,
> 
> 
> On Sat, 12 Nov 2016 08:50:46 -0700
> Glenn English  wrote:
> 
> ...
>>> 216.17.203.65   out.slsware.org oso
>>> 216.17.203.66   srv.slsware.org sso
> 
> This might be your problem??   ^
> I suspect the above line should be:
> 
> 216.17.203.66 srv.slsware.org srv
> 
> with the last field matching the hostname.

Don't think so. sso stands for srv.slsware.org. I've been making aliases like 
that for years.

The problem was fixed by futzing with DNZ and resolv.conf. But it's not a good 
solution if you're trying to understand how Debian really works.

-- 
Glenn English



-- 
Glenn English
Did you just click Reply?
If so, change the send
address from gmail to
g...@slsware.net

Re: dd - proper use or more suitable program

[Richard Owlett]

On 11/12/2016 12:26 PM, Pascal Hambourg wrote:

Le 12/11/2016 à 18:22, Richard Owlett a écrit :



ddrescue /dev/sda /mnt/defective_drive.img
/mnt/defective_drive.log

(...)

Can this be run as a user, or are root permissions required.


Unless the user has read permission on the raw device, it must be
run as root.


I have a STRONG suspicion that by "raw device" you refer to the 
defective device which is enumerated as /dev/sdc . *ALL* 
documentation and tutorials I found make a *MAJOR POINT* of *NOT* 
mounting the defective device. "Permissions" therefor are a murky 
issue. Point of fact, the specific physical defective object 
predates me having more than casual interest in *nix.


There's a reason I asked for "hand holding" and specifically 
asked for tolerance.
In a "user to user" support enviroment ther is an expectation of 
querent doing his due diligence. I tried. I failed. M'aidez s'il 
vous plait.





My defective drive is /dev/sdc .
Partition /dev/sdb6 {formatted ext4} is much larger than the
defective
drive.
/dev/sdb is a 1 TB rotating platter drive connected via USB.
How do I mount it and run ddrescue?


Mount what ?


Whatever that needs to be mounted.
There *IS* a reason I explicitly stated that I needed an atypical 
amount of hand holding!



You don't mount anything from the defective drive.
You mount the filesystem which will receive the disk image file
anywhere you like with mount. In the above example it was
expected to be mounted on /mnt, the usual temporary mount point.
So :

mount /dev/sdb6 /mnt

The file manager of your desktop environment may have already
mounted it for you elsewhere in /media/. Check df or mount.



I've gone to lenghts to defeat Debian's attempts to out-M$ Wm Gates.
I predate the 8085 when it was acceptable manufacturing practice 
to cut/jumper etchs to "reprogram" 7400 series devices.


Tolerant help please.

Re: dd - proper use or more suitable program

[Ben Caradoc-Davies]

On 13/11/16 08:25, Richard Owlett wrote:

I've gone to lenghts to defeat Debian's attempts to out-M$ Wm Gates.


Redmond is now our ally against the closed garden at Cupertino, with 
cloud image support, open-sourced language platforms, and even Ubuntu 
integration on the desktop.


We've always been at war with Eastasia.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: dd - proper use or more suitable program

[Brian]

On Sun 13 Nov 2016 at 08:54:05 +1300, Ben Caradoc-Davies wrote:

> On 13/11/16 08:25, Richard Owlett wrote:
> >I've gone to lenghts to defeat Debian's attempts to out-M$ Wm Gates.
> 
> Redmond is now our ally against the closed garden at Cupertino, with cloud
> image support, open-sourced language platforms, and even Ubuntu integration
> on the desktop.
> 
> We've always been at war with Eastasia.

I imagine Richard Owlett's comment has attracted this sort of response.
Neither helps with a solution to the issue.

-- 
Brian.

Re: Does hdparm not run at startup anymore?

[Rainer Dorsch]

Hi Alex,

thank you for your reply and your testing.

On Saturday 12 November 2016 16:40:40 Alex Mestiashvili wrote:
> On 11/12/2016 08:37 AM, Rainer Dorsch wrote:
> > + Alexandre, hdparm maintainer
> >
> > On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
> >> Hi,
> >>
> >> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the 
> >> system, apm does not change. Interesting enough a /etc/init.d/hdparm 
> >> restart fixes the problem:
> >>
> >>
> >> root@Silberkiste:~# cat /etc/hdparm.conf
> 
> >> /dev/sdb {
> >>  apm = 64
> >>  spindown_time = 5
> >> }
> >>
> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
> >> Advanced power management level: 254
> >> root@Silberkiste:~# /etc/init.d/hdparm restart
> >> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
> >> Advanced power management level: 64
> >> root@Silberkiste:~#
> >>
> >>
> >> Any insight, why I need the /etc/init.d/hdparm restart is very welcome.
> >>
> >> Thanks
> >> Rainer
> >>
> >>
> Hi Rainer,
> I can not reproduce this problem on my machine:
> 
> lsb_release -c
> Codename:jessie
> 
> hdparm -V
> hdparm v9.43
> 
> egrep -v "^$|^#" /etc/hdparm.conf
> /dev/sdc {
>  apm = 64
>  acoustic_management = 250
> }
> /dev/sdd {
>  apm = 128
> }
> /dev/sdf {
>  apm = 48
> }
> 
> 
> for disk in sdc sdd sdf; do echo $disk; hdparm -I /dev/$disk | egrep
> "level:|acoustic"; done
> sdc
> Advanced power management level: 64
> Recommended acoustic management value: 254, current value: 250
> sdd
> Advanced power management level: disabled
> Recommended acoustic management value: 128, current value: 128
> sdf
> Advanced power management level: 48
> Recommended acoustic management value: 208, current value: 0
> 
> The values are set after reboot or after init script restart.
> 

Hmm...since hdparm works for me if I do a 

# /etc/init.d/hdparm restart

after boot (or even in /etc/rc.local, is it possible that hdparm runs for my 
system for whatever reason too early (though it is not special setup, all SATA 
SSDs and HDDs)?

Rainer


-- 
Rainer Dorsch
http://bokomoko.de/

Re: Layers for the package manager

[Nicolas George]

Le primidi 21 brumaire, an CCXXV, Eduardo M KALINOWSKI a écrit :
> docker does not work as you describe (and I know of nothing that does
> anything close to your idea), but it does suit some of the uses you
> mentioned (the ones quoted).

If I understand correctly how Docker works, its images are big blobs
that contain the program they are meant to distribute plus all its
dependencies. Am I mistaken?

If it works like that, that means when the next OpenSSL security issue
is found, we have to cross our fingers very tightly and hope whoever
released the image will release an update with a fixed library. With
what I have in mind, unless the maintainer of the third-party repository
did something very wrong, its packages will be dynamically linked with
OpenSSL from the base system, and benefit from the updates immediately.

It makes a big difference: in one case, you have to trust the third
party to do a good job and continue that way in the future, on the other
case you only have to trust it to do a not-bad job once.

Personally, I would rather unpack a dynamically-linked binary somewhere
in /opt and install the dependencies myself than use a package system
with bundled libraries. Or, of course, install from source.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: Layers for the package manager

[Eduardo M KALINOWSKI]

On 12-11-2016 18:18, Nicolas George wrote:
> If I understand correctly how Docker works, its images are big blobs
> that contain the program they are meant to distribute plus all its
> dependencies. Am I mistaken?
>
> If it works like that, that means when the next OpenSSL security issue
> is found, we have to cross our fingers very tightly and hope whoever
> released the image will release an update with a fixed library. With
> what I have in mind, unless the maintainer of the third-party repository
> did something very wrong, its packages will be dynamically linked with
> OpenSSL from the base system, and benefit from the updates immediately.
>
> It makes a big difference: in one case, you have to trust the third
> party to do a good job and continue that way in the future, on the other
> case you only have to trust it to do a not-bad job once.
>
> Personally, I would rather unpack a dynamically-linked binary somewhere
> in /opt and install the dependencies myself than use a package system
> with bundled libraries. Or, of course, install from source.
>

The end result is indeed, for practical purposes, a big package with
everything needed to run an application. But I don't expect you to
simply download pre-built blobs, but rather to build your own.

It's easier to understand from an example. Take a look at this
Dockerfile:
https://gist.github.com/rmoehn/1d82f433f517e3002124df52f7a73678 .
Basically it says "start with a minimal debian stable system, install
some packages, then make some necessary configurations". Docker
downloads the base image (the minimal debian system), and executes the
rest of the commands to create a new image that includes the installed
packages, resulting in a self-contained image that allows execution of
the application in question.

[That's a huge simplification, but the end result is roughly as
described. We need not concern with the internals.]

[If you don't want to trust the creator of the base image, you can
create your own.]

I've used that Dockerfile to run anki (which is currently broken in
testing). It's kind of a chroot, but with more isolation. Also, if I
wanted to run another program from stable, I could build another docker
image for that, but due to the clever way docker works, there'd be only
one copy of the base system plus two layers, one for each image, with
only the applications in question. That's a big advantage in relation to
chroots or virtual machines.

And yet, even if a base layer is shared, docker images are completely
isolated from one another and from the host system. If you want to share
data, you need to explicitly configure that.

That does solve the isolation problem, and allows you to run packages
from different repositories simultaneously, with different versions of
libraries if necessary; and allows you to install packages from
untrusted sources (or that are not available as .deb's) without messing
with your "real" system.

It does not solve the problem you mention: if there is an update of
OpenSSL, the images will continue to use the old version unless you
rebuild them. The process can be automated, but at least you'll need to
run a command to rebuild the images, and this can be time consuming.

Now might be a good time to dive into some of the internals, such as how
the images and layers work:
https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
That might give you some ideas for your solution. Take a look also at
the pages "AUFS storage driver in practice" and "OverlayFS storage in
practice". While you won't be able to do what you want with docker,
perhaps you can get some ideas. I'd guess you'd need some kind of
layering like done by docker, but sometimes changing the bottom layers
(which is not possible with docker - only the topmost layer is ever
changed).


-- 
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: dd - proper use or more suitable program

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Nov 12, 2016 at 01:25:50PM -0600, Richard Owlett wrote:
> On 11/12/2016 12:26 PM, Pascal Hambourg wrote:
> >Le 12/11/2016 à 18:22, Richard Owlett a écrit :
> >>
> ddrescue /dev/sda /mnt/defective_drive.img
> /mnt/defective_drive.log
> >(...)
> >>Can this be run as a user, or are root permissions required.
> >
> >Unless the user has read permission on the raw device, it must be
> >run as root.
> 
> I have a STRONG suspicion that by "raw device" you refer to the
> defective device which is enumerated as /dev/sdc . *ALL*
> documentation and tutorials I found make a *MAJOR POINT* of *NOT*
> mounting the defective device. "Permissions" therefor are a murky
> issue.

In this case, the permissions on /dev/sdc were meant (as opposed
to the permissions on the files whithin the file system in /dev/sdc,
which don't count in this case)

> Point of fact, the specific physical defective object
> predates me having more than casual interest in *nix.

Yes: I remember there's a DOS file system in the disk in question,
so no permissions in there anyway. But as stated above, this doesn't
matter, because you're looking at the container: access to that
is ruled by the permissions on the device file, i.e. /dev/sdc.

> There's a reason I asked for "hand holding" and specifically asked
> for tolerance.
> In a "user to user" support enviroment ther is an expectation of
> querent doing his due diligence. I tried. I failed. M'aidez s'il
> vous plait.

In a nutshell: you mount your *new* disk to a directory of your
choice (let's say /mnt). Possibly your OS is set up to do that
for you: it'll typically end then somewhere in /media/blah (for
some suitable value of "blah"). Let's use /mnt as a placeholder.

Then you insert you defective disk, which (let's say) appears
as /dev/sdc. Make sure the OS doesn't mount it automatically,
otherwise unmount yourself.

Then you do

  dd if=/dev/sdc of=/mnt/my-disk-backup bs=4096 count=100

(this is over-simplified: you'll probably use ddrescue instead
of dd, or at least use the option 'noerror').

An image of your disk will hopefully appear on 'my-disk-backup'.
You need read access to /dev/sdc and write access to the directory
/mnt (either by doing sudo, I'd do that or by other means).

Those steps are a rough sketch. Many details already flew back
and forth in this thread, so I didn't want to bloat the thing
too much. Feel free to ask where things are unclear.

Regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlgngikACgkQBcgs9XrR2kYjmACeJyeAvYCCrcfx2UuSglH7Dnvb
eg0An14EEu9c0jwQTcjF5/4bNCm9qHTV
=c2+e
-END PGP SIGNATURE-

iptables question

[deloptes]

Hi,
I need some help and I'll appreciate it.

I have a firewall with iptables behind the modem.
on this firewall I have 
eth0 with ip 10..1 to the modem ip: 10..12
eth1 with ip 192..1 to the intranet

iptables is doing SNAT from 192..1 to 10..1

I wonder how I can ssh from 192..NN to 10..NN
What magic should I apply to make it happen?

Thanks in advance

Re: set domain name in Debian `

[Glenn English]

> On Nov 12, 2016, at 11:31 AM, Henrique de Moraes Holschuh  
> wrote:
> 
> But the whole thing really doesn't need any DNS servers *as long as*
> everything you need is resolved statically by some module in
> /etc/nsswitch.conf... such as the default "files" module, which reads
> /etc/hosts.

> root@srv:~# cat /etc/nsswitch.conf 
> # /etc/nsswitch.conf
> #
> # Example configuration of GNU Name Service Switch functionality.
> # If you have the `glibc-doc-reference' and `info' packages installed, try:
> # `info libc "Name Service Switch"' for information about this file.
> 
> passwd: compat
> group:  compat
> shadow: compat
> gshadow:files
> 
> hosts:files dns
> networks:   files
> 
> protocols:  db files
> services:   db files
> ethers: db files
> rpc:db files
> 
> netgroup:   nis

If I understand this, it looks at hosts first.

With bind9 stopped, ping sso works and says it's pinging 216.17.203.66, 
srv.slsware.org.

> At which point, it boils down to a complete enough, correct /etc/hosts
> 
>> It does seem that /etc/hosts should work, though...
> 
> It does work, provided that you have "files" first in the list of NSS
> modules, and you have both the nodename and the FQDN in /etc/hosts for
> the correct IPs and in the correct order.  Otherwise, it depends.

The nodename is another word for hostname, right? (I'd never heard that word 
before. Wikipedia said it just meant hostname.)

/etc/hosts, as I said before:

> root@srv:~# cat /etc/hosts
> # /etc/hosts:  This file describes a number of hostname-to-address
> #
> # This is to be sent to all hosts that need a hosts file
> # (don't really know how yet...)
> #  
> # Host Database
> # localhost is used to configure the loopback interface
> # sudo cp hosts /etc ; dist `pwd`/hosts /etc all hosts
> # The following lines are desirable for IPv6 capable hosts
> # when the system is booting.  Do not change this entry.
> #   
> ::1   ip6-localhost   ip6-loopback
> fe00::0   ip6-localnet
> ff00::0   ip6-mcastprefix
> ff02::1   ip6-allnodes
> ff02::2   ip6-allrouters
> ff02::3   ip6-allhosts
> 
> 127.0.0.1 localhost localhost.localdomain lh lcl
> 
> # pass I slsware.org -- all routable IPs; no NAT
> 216.17.203.64 slsware.org
> 216.17.203.65 out.slsware.org oso
> 216.17.203.66 srv.slsware.org sso
> 216.17.203.67 gobook.slsware.org  gso gbo
> 216.17.203.68 unused0.slsware.org u0so
> 216.17.203.69 unused1.slsware.org u1so
> 216.17.203.70 printer.slsware.org pso
> 216.17.203.71 broadcast.slsware.org   bso
> 
> # misc ne'r-do-wells
> 127.0.0.2   ad.doubleclick.net
> 127.0.0.2   mmv.admob.com

Here's the line:

> 216.17.203.66 srv.slsware.org sso

That's OK, right?

hosts ought to work. But it doesn't -- not on this machine, not today. I've had 
the FQDN way down in hosts before, and hostname -f found it with no trouble. 
For many years, I had a CVS playpen to be sure exactly the same hosts file was 
on all my machines, and as far as I know, there was never a problem.

Many years ago I wrote a big shell script to set up iptables (ipchains back 
then). It uses hostname -f to find out which machine it's on, and how the 
filter should be configured -- if that command fails, iptables won't be set up 
on the machine. It's a very important command here. If it gives the wrong 
answer, it'll be filter the wrong stuff.

> The *installer* either asks the user for the FQDN and gets the nodename,
> domain name and FQDN from that (and it *should* write them to /etc/hosts
> and /etc/hostname appropriately),

It always has, all of them. I use the curses netinst expert, and it's always 
worked flawlessly.

This is the first time I've had trouble with the domain. I think I may need to 
do a little more investigation. Apparently, hosts is supposed to work...

> or gets information from DHCP/DHCPv6
> and the DNS while autoconfiguring.

I don't use DHCP or autoconfig, so that's never come up.


I disabled bind, put the big hosts file (with slsware.org at the top) back, 
rebooted, and -f said srv.slsware.dmz.

I removed all but one occurrence of 'srv' from the big hosts, rebooted, and -f 
was correct.

I replaced the big hosts file.

I retyped the srv...org line at the top if the file, rebooted, and -f said 
srv...dmz.

I moved slsware.org to the bottom of the file, rebooted, and -f said srv...dmz.

I removed the srv.slsware.dmz line, moved the slsware.org collection back to 
the top, rebooted, and -f said www...dmz.

I give up. This is acting like I've never seen it -- there's never been a 
problem with hosts before. I have to have those alien FQDNs and aliases and IPs 
in there so I can SSH to them during the switchover.

-- 
Glenn English

Re: iptables question

[Joe]

On Sat, 12 Nov 2016 22:15:45 +0100
deloptes  wrote:

> Hi,
> I need some help and I'll appreciate it.
> 
> I have a firewall with iptables behind the modem.
> on this firewall I have 
> eth0 with ip 10..1 to the modem ip: 10..12
> eth1 with ip 192..1 to the intranet
> 
> iptables is doing SNAT from 192..1 to 10..1
> 
> I wonder how I can ssh from 192..NN to 10..NN
> What magic should I apply to make it happen?
> 
> Thanks in advance
> 
> 

Can we take it that this does not work now? If that is the case, are
you sure that iptables is preventing it? There are other possible
reasons for a new ssh link not to work.

A typical simple iptables script will allow what you want to do to
happen already, so there must either be some iptables restriction in
place now, or there is some other reason for ssh not working. Are you
able to connect to the modem web configuration page from the 192.
network?

The SNAT should not be an issue, it can handle all protocols
transparently, and ssh uses the same tcp protocol as http.

If there are iptables restrictions on outgoing protocols, you need to
find the rule permitting tcp/80 to be forwarded, copy it and replace 80
with 22. Once this is working, we can restrict the destination to the
10. network, as presumably any existing port 80 rule allows connection
to anywhere and you may not want that for ssh.

-- 
Joe

libvirt-bin on Stretch

[Van Nelle]

Hi!
I am trying to follow this https://wiki.debian.org/KVM tutorial but i cant
find libvirt-bin on Stretch.

Is there any replacement of this package or i must follow an updated
tutorial?

LENOVO IdeaPad 100S 11.6" Laptop

[Lisi Reisz]

I am thinking of buying one of these for use with Debian and TDE.  What was 
said the other day gave me a slight pause for thought, but I was partly 
reassured.

Comments please!

Lenovo 11.6 Inch Ideapad 100s Intel Atom 2GB 32GB 
http://www.argos.co.uk/product/5163519

Thank you.

Lisi

Re: LENOVO IdeaPad 100S 11.6" Laptop

[Michael Lange]

Hi,

On Sat, 12 Nov 2016 23:04:21 +
Lisi Reisz  wrote:

> I am thinking of buying one of these for use with Debian and TDE.  What
> was said the other day gave me a slight pause for thought, but I was
> partly reassured.
> 
> Comments please!
> 
> Lenovo 11.6 Inch Ideapad 100s Intel Atom 2GB 32GB 
> http://www.argos.co.uk/product/5163519

when it's to be used with debian, this one is currently only for the
brave ;-)
I own such a device, currently internal wifi works well enough with a
third party driver. If you care about bluetooth, you're so far totally
out of luck. Sound does not work yet either. Suspend / Hibernate does not
work. Occasionally the screen freezes, forcing the user to do a hard
reset. Plus the 32-bit Efi troubles to make the install media boot.

Considering the price I think the device would not be bad, if they would
be able to fix these issues. From what I have been reading, it seems like
people from Intel are working on linux fixes for this and similar
devices, but even if things go well some patience is required. 

See also here (not sure if this page will be updated if the situation
changes, though): https://bugzilla.kernel.org/show_bug.cgi?id=113151

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

"Get back to your stations!"
"We're beaming down to the planet, sir."
-- Kirk and Mr. Leslie, "This Side of Paradise",
   stardate 3417.3

Two Chromebooks: was Re: LENOVO IdeaPad 100S 11.6" Laptop

[Lisi Reisz]

On Saturday 12 November 2016 23:23:09 Michael Lange wrote:
> Hi,
>
> On Sat, 12 Nov 2016 23:04:21 +
>
> Lisi Reisz  wrote:
> > I am thinking of buying one of these for use with Debian and TDE.  What
> > was said the other day gave me a slight pause for thought, but I was
> > partly reassured.
> >
> > Comments please!
> >
> > Lenovo 11.6 Inch Ideapad 100s Intel Atom 2GB 32GB
> > http://www.argos.co.uk/product/5163519
>
> when it's to be used with debian, this one is currently only for the
> brave ;-)
> I own such a device, currently internal wifi works well enough with a
> third party driver. If you care about bluetooth, you're so far totally
> out of luck. Sound does not work yet either. Suspend / Hibernate does not
> work. Occasionally the screen freezes, forcing the user to do a hard
> reset. Plus the 32-bit Efi troubles to make the install media boot.
>
> Considering the price I think the device would not be bad, if they would
> be able to fix these issues. From what I have been reading, it seems like
> people from Intel are working on linux fixes for this and similar
> devices, but even if things go well some patience is required.
>
> See also here (not sure if this page will be updated if the situation
> changes, though): https://bugzilla.kernel.org/show_bug.cgi?id=113151

Thanks, Michael.  Very helpful.  I don't mind about having to struggle a 
little, and Bluetooth doesn't worry me, but sound is a bit of a killer. 

What about either of these Chromebooks:
Acer Chromebook 11.6 Inch Celeron 2GB 16GB
http://www.argos.co.uk/product/5487972

Asus Chromebook C201 11.6 Inch 2GB 16GB
http://www.argos.co.uk/product/5763830
?

Can anyone speak to these?
Thanks!

Lisi

Re: Two Chromebooks: was Re: LENOVO IdeaPad 100S 11.6" Laptop

[Doug]

On 11/12/2016 05:51 PM, Lisi Reisz wrote:

On Saturday 12 November 2016 23:23:09 Michael Lange wrote:

Hi,

On Sat, 12 Nov 2016 23:04:21 +

Lisi Reisz  wrote:

I am thinking of buying one of these for use with Debian and TDE.  What
was said the other day gave me a slight pause for thought, but I was
partly reassured.

Comments please!

Lenovo 11.6 Inch Ideapad 100s Intel Atom 2GB 32GB
http://www.argos.co.uk/product/5163519

when it's to be used with debian, this one is currently only for the
brave ;-)
I own such a device, currently internal wifi works well enough with a
third party driver. If you care about bluetooth, you're so far totally
out of luck. Sound does not work yet either. Suspend / Hibernate does not
work. Occasionally the screen freezes, forcing the user to do a hard
reset. Plus the 32-bit Efi troubles to make the install media boot.

Considering the price I think the device would not be bad, if they would
be able to fix these issues. From what I have been reading, it seems like
people from Intel are working on linux fixes for this and similar
devices, but even if things go well some patience is required.

See also here (not sure if this page will be updated if the situation
changes, though): https://bugzilla.kernel.org/show_bug.cgi?id=113151

Thanks, Michael.  Very helpful.  I don't mind about having to struggle a
little, and Bluetooth doesn't worry me, but sound is a bit of a killer.

What about either of these Chromebooks:
Acer Chromebook 11.6 Inch Celeron 2GB 16GB
http://www.argos.co.uk/product/5487972

Asus Chromebook C201 11.6 Inch 2GB 16GB
http://www.argos.co.uk/product/5763830
?

Can anyone speak to these?
Thanks!

Lisi




I don't know what these Chromebooks sell for, and of course you know 
that they are diskless
(which is maybe what you want) but there are frequently sales of 
refurbished used Dell laptops
in the $120 to $160 price range, and they are 14" or 15" with at least 
256 GiB drives and 4 GiB ram.
Try and get one with something other than Broadcom wifi--it's a real 
challenge to make it work,

unless you want to run Windows.

--doug

Re: iptables question

[deloptes]

Joe wrote:

> On Sat, 12 Nov 2016 22:15:45 +0100
> deloptes  wrote:
> 
>> Hi,
>> I need some help and I'll appreciate it.
>> 
>> I have a firewall with iptables behind the modem.
>> on this firewall I have
>> eth0 with ip 10..1 to the modem ip: 10..12
>> eth1 with ip 192..1 to the intranet
>> 
>> iptables is doing SNAT from 192..1 to 10..1
>> 
>> I wonder how I can ssh from 192..NN to 10..NN
>> What magic should I apply to make it happen?
>> 
>> Thanks in advance
>> 
>> 
> 
> Can we take it that this does not work now? If that is the case, are
> you sure that iptables is preventing it? There are other possible
> reasons for a new ssh link not to work.
> 

Yes, it is not working and yes it might be a different issue. So here is
some additional information, if you wish.

>From one computer ip 10..6 I can ssh to 10..7 and vv.
I also see that iptables forwards to the output, but in the output nothing
happens. So it is either in the output chain, or the back route blocks.

> A typical simple iptables script will allow what you want to do to
> happen already, so there must either be some iptables restriction in
> place now, or there is some other reason for ssh not working. Are you
> able to connect to the modem web configuration page from the 192.
> network?
> 

Yes I forgot to mention that I can connect from 192..NN to the modem ip via
ssh lets say 10..200.

On the modem there is also firewall. I tried disableing it but it did not
help.

And you can bet there is restriction - basically it is pretty tight and is
opened only what is needed to intranet and basically all to modem net

> The SNAT should not be an issue, it can handle all protocols
> transparently, and ssh uses the same tcp protocol as http.
> 
> If there are iptables restrictions on outgoing protocols, you need to
> find the rule permitting tcp/80 to be forwarded, copy it and replace 80
> with 22. Once this is working, we can restrict the destination to the
> 10. network, as presumably any existing port 80 rule allows connection
> to anywhere and you may not want that for ssh.

there is nothing regarding the output - no rules based on ports

thanks

Re: Two Chromebooks: was Re: LENOVO IdeaPad 100S 11.6" Laptop

[Michael Lange]

On Sat, 12 Nov 2016 23:51:46 +
Lisi Reisz  wrote:

> I don't mind about having to struggle
> a little, and Bluetooth doesn't worry me, but sound is a bit of a
> killer. 

I just looked again at https://bugzilla.kernel.org/show_bug.cgi?id=117141
where the sound issue is being discussed, there is now a link pointing to
https://github.com/torvalds/linux/commit/a68bc0d43e1b96c374c4b03eb9baa662778357b3#diff-ad362ef9a62cab4653b68cafab76824b
which may or may not fix the sound problems with kernel 4.9, I think I'll
try this out one of these days.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Pain is a thing of the mind.  The mind can be controlled.
-- Spock, "Operation -- Annihilate!" stardate 3287.2

Re: libvirt-bin on Stretch

[Christian Seiler]

On 11/12/2016 11:15 PM, Van Nelle wrote:
> I am trying to follow this https://wiki.debian.org/KVM tutorial but i cant
> find libvirt-bin on Stretch.
> 
> Is there any replacement of this package

The package was split into two parts:

libvirt-daemon-system
libvirt-clients

In most cases you probably want both of them at the same time.

While the Debian packaging was changed, the configuration
and administration of libvirt is still very similar to that
of previous versions, so the rest of the tutorial is probably
going to still work on Stretch.

Regards,
Christian

Re: install recommended by default? (was: Gparted will not label...)

[Felix Miata]

Brian composed on 2016-11-12 15:45 (UTC):


On Sat 12 Nov 2016 at 13:45:38 +, Lisi Reisz wrote:



Brian wrote:



> Not installing a recommended package on a default Debian would be a bug.



Aptitude on my current almost vanilla temporary Jessie install doesn't install
recommends.  But it makes a big point of telling me a) that they are
recommended and b) that they are not going to be installed.  I then often,
but not always, install them.  It doesn't strike me as a bug.  This is Debian
not Ubuntu.



I could, of course, reset aptitude.  I am quite happy with the status quo.



Never really used aptitude but I've just installed it and ran the curses
variety of the program. "options" at the top of the screen shows



Option:  Apt::Install-Recommends
Default: True
Value:   True


I'd like to know how you found the above. Running aptitude 0.6.11 on vtty3 
here as root in 8.6 I'm unable to find anything like that from its Options 
menu, or anywhere else.



The behaviour of your aptitude is presumably because you have adjusted
the default behaviour in some way. The new behaviour is not a bug.



Also, a default Debian doesn't have aptitude but apt-get. which installs
recommended packages by default.


I booted 5 of 6 Jessie installations here in recent minutes. All contain

APT::Install-Recommends "false";

in /etc/apt/apt.conf.d/00InstallRecommends. Timestamp on the file on the 
currently booted installation is 366 days old, same as on the previous one or 
two booted (timestamp not noticed on the first two or three).


All my Jessie installations were made via HTTP, started from Grub, including 
the following on the cmdline:


...tasks=standard base-installer/install-recommends=false...

What a "default" Debian installation includes or not I may never have seen, 
at least not since my first, Etch, as all since, and maybe Etch too, have 
been installed in same manner.

--
"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: Symlinking or hard linking additional storage to /home directories

[David Christensen]

On 11/12/2016 10:09 AM, Robert Menes wrote:
> My current desktop setup currently has a Debian installation on a 120GB
> SSD, which
> is mounted with both the EFI system partition and as / for my rig. I have a
> 3TB HDD
> which I had mounted as /home during install.
> 
> As my desktop case still has enough space in it, I was contemplating
> getting another
> pair of 3TB (or maybe even 4TB!) HDDs, and have them be symlinked or hard
> linked
> (whichever works better) to my ~/Music and ~/Videos folders. This setup is
> currently
> has only one user on it (my account, aside from root). I want to do this so
> that I have
> more space for my media, functioning as a backup for a NAS and for keeping
> larger
> project files for any audio and video work I do.
> 
> My question is this: which is the better path to take? Symlinking or hard
> linking another
> drive to ~/Music and ~/Videos? I understand that I will need to edit
> /etc/fstab and all;
> that's fine. Just curious as to whether symlinks or hard links are the way
> to go.

I mount my drives under /mnt/drivename and symlink into those.  In my
file server, I bind mount subdirectories under /var/local and
/var/cache.  I mount Samba client shares under /mnt/sharename and
/home/username/sharename, and symlink into those.


David

Invoking ddrescue

[Richard Owlett]

On 11/12/2016 2:57 PM, to...@tuxteam.de wrote:

[*SNIP*]
Those steps are a rough sketch. Many details already flew back
and forth in this thread, so I didn't want to bloat the thing
too much. Feel free to ask where things are unclear.



I'm tangled up !! I plead for 5 or 6 lines to copy-n-paste.
On my left hand I have a defective hard disk - AKA /dev/sdc .
On my right hand I have a partitioned device waiting for data - 
AKA /dev/sdb6 .

Automount has been disabled explicitly.
I have been EXPLICITLY told that ddrescue is the appropriate tool.
Reading 
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html 
and a half dozen "tutorials" convinces me of that. Clear 
explanations given in those documents why dd and other tools 
*NOT* suitable for my circumstances.



How do I prepare to invoke
   ddrescue /dev/sdc /mnt/repaired.img /mnt/repaired.log


Help. Please. Thank you.

Re: install recommended by default? (was: Gparted will not label...)

[David Wright]

On Sat 12 Nov 2016 at 20:27:37 (-0500), Felix Miata wrote:
> Brian composed on 2016-11-12 15:45 (UTC):
> 
> >On Sat 12 Nov 2016 at 13:45:38 +, Lisi Reisz wrote:
> 
> >>Brian wrote:
> 
> >>> Not installing a recommended package on a default Debian would be a bug.
> 
> >>Aptitude on my current almost vanilla temporary Jessie install doesn't 
> >>install
> >>recommends.  But it makes a big point of telling me a) that they are
> >>recommended and b) that they are not going to be installed.  I then often,
> >>but not always, install them.  It doesn't strike me as a bug.  This is 
> >>Debian
> >>not Ubuntu.
> 
> >>I could, of course, reset aptitude.  I am quite happy with the status quo.
> 
> >Never really used aptitude but I've just installed it and ran the curses
> >variety of the program. "options" at the top of the screen shows
> 
> >Option:  Apt::Install-Recommends
> >Default: True
> >Value:   True
> 
> I'd like to know how you found the above. Running aptitude 0.6.11 on
> vtty3 here as root in 8.6 I'm unable to find anything like that from
> its Options menu, or anywhere else.

I type "?" which gives a list of key bindings. About 30 lines down it says
   Control-t:Activate or deactivate the menu.
so I "q" back to the View and press "Ctrl-T" which pulls down the leftmost
menu (Actions). Use ← or → to get to the sixth menu which is Options.
Select the first item, Preferences and you get UI Options. Again, about
30 ↓ keystrokes gets to the line with, and when you're on it, the lower
pane displays as above and gives a few lines of explanation. The line is
[X] Install recommended packages automatically
Where in that sequence does your aptitude behave differently?

> >The behaviour of your aptitude is presumably because you have adjusted
> >the default behaviour in some way. The new behaviour is not a bug.
> 
> >Also, a default Debian doesn't have aptitude but apt-get. which installs
> >recommended packages by default.
> 
> I booted 5 of 6 Jessie installations here in recent minutes. All contain
> 
>   APT::Install-Recommends "false";
> 
> in /etc/apt/apt.conf.d/00InstallRecommends. Timestamp on the file on
> the currently booted installation is 366 days old, same as on the
> previous one or two booted (timestamp not noticed on the first two
> or three).
> 
> All my Jessie installations were made via HTTP, started from Grub,
> including the following on the cmdline:
> 
>   ...tasks=standard base-installer/install-recommends=false...
> 
> What a "default" Debian installation includes or not I may never
> have seen, at least not since my first, Etch, as all since, and
> maybe Etch too, have been installed in same manner.

I don't understand what you mean by "via HTTP, started from Grub".
I install Debian systems either by upgrading from a previous version,
or by booting up a CD, normally a netinst version. The latter always
boots straight into the screen where one can choose "Advanced Options"
and "Expert Install" (my choices) or other options. I don't even recall
whether Grub is doing the booting, or one of those other methods like
syslinux etc. It all just flashes by.

Cheers,
David.

Re: Symlinking or hard linking additional storage to /home directories

[David Wright]

On Sat 12 Nov 2016 at 19:15:29 (+0100), Nicolas George wrote:
> Le duodi 22 brumaire, an CCXXV, Robert Menes a écrit :
> > My question is this: which is the better path to take? Symlinking or hard
> > linking another drive to ~/Music and ~/Videos? I understand that I
> > will need to edit /etc/fstab and all; that's fine. Just curious as to
> > whether symlinks or hard links are the way to go.
> 
> You can not do hardlinks across different filesystems, so that part is
> settled.
> 
> You could not do hardlinks on directories either, you would have to work
> plain file per plain file. That would be a pain.
> 
> You could use bind mounts, but I really do not recommend it.
> 
> I suggest mounting the extra storage somewhere like /data and using
> symlinks; that is what I do.

I agree with all that, but I avoid making symlinks. If I do a
recursive search of my home directory, there's really no point
in trawling through 300GB of photographs, so they're all under
/home/photos. I put them under /home just to avoid adding
directories to / but they're not users in the normal sense:
I own all the files. Similarly video, sound etc.

Cheers,
David.

Re: install recommended by default?

[Felix Miata]

David Wright composed on 2016-11-12 22:09 (UTC-0600):


On Sat 12 Nov 2016 at 20:27:37 (-0500), Felix Miata wrote:



Brian composed on 2016-11-12 15:45 (UTC):



Never really used aptitude but I've just installed it and ran the curses
variety of the program. "options" at the top of the screen shows



Option:  Apt::Install-Recommends
Default: True
Value:   True



I'd like to know how you found the above. Running aptitude 0.6.11 on
vtty3 here as root in 8.6 I'm unable to find anything like that from
its Options menu, or anywhere else.



I type "?" which gives a list of key bindings. About 30 lines down it says
   Control-t:Activate or deactivate the menu.


I open the menu with F10.


so I "q" back to the View and press "Ctrl-T" which pulls down the leftmost
menu (Actions). Use ← or → to get to the sixth menu which is Options.


Same my way.


Select the first item, Preferences and you get UI Options. Again, about
30 ↓ keystrokes gets to the line with, and when you're on it, the lower
pane displays as above and gives a few lines of explanation. The line is
[X] Install recommended packages automatically
Where in that sequence does your aptitude behave differently?


There are two panes, upper and lower, each about half a screen. I assumed 
that the last item showing was the last available option under preferences. 
Now that I know about the additional options, I see, and it does indeed 
report that the default is True.


I suppose it must be that my installer cmdline option 
install-recommends=false must be taken into account, but I'm perplexed that 
multiple Jessie installations have the same Nov. 2015 timestamp on 
/etc/apt/apt.conf.d/00InstallRecommends while including False instead of the 
reported default True.



I booted 5 of 6 Jessie installations here in recent minutes. All contain



APT::Install-Recommends "false";



in /etc/apt/apt.conf.d/00InstallRecommends. Timestamp on the file on
the currently booted installation is 366 days old, same as on the
previous one or two booted (timestamp not noticed on the first two
or three).



All my Jessie installations were made via HTTP, started from Grub,
including the following on the cmdline:



...tasks=standard base-installer/install-recommends=false...



What a "default" Debian installation includes or not I may never
have seen, at least not since my first, Etch, as all since, and
maybe Etch too, have been installed in same manner.



I don't understand what you mean by "via HTTP, started from Grub".


A recent installation's boot menu stanza:

title Install Debian via HTTP
kernel (hd0,2)/debian/linux showopts vga=791 --- 
netcfg/disable_dhcp=true netcfg/get_hostname=myhost tasks=standard 
base-installer/install-recommends=false splash=0

initrd (hd0,2)/debian/initrd.gz

All my machines are multiboot. Virtually all my installations begin as 
minimal, so that I can configure to not install optional packages as a matter 
of course, keeping space required low, and updates time and bandwidth minimized.


Normally when I want to install any distro, I fetch the installation kernel 
and initrd from an appropriate location on the Internet, if I haven't done so 
already and saved on the LAN. Isos represent a lot of downloading of packages 
that won't be installed here. Release isos don't get updated, so HTTP gets 
latest available packages instead of installing multiple versions of various 
packages or leaving a fresh installation in need of update. Similar is 
commonly the reasoning with pre-release isos.

--
"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/