Hardware detection issue with debian

[Mo Some One]

I can not do this via bur report because I could not select a valid
package. I have researched this and was unable to find a solved case under
exact condition. The issue was mostly discussed as an mtp or mounting
problem, but I dug a bit farther into the problem. When it comes to a
certain model, hardware is not even detected.

Thank you for all your dedicated work,
Mo




Following is the issue

When connecting a "Galaxy S3 mini"  via usb, it is not detected at all;
however if connected during installation, it is temporarily detected as a
"usb mass storage device" before CDrom is detected.


Here are some general information about the system:

# cat /etc/debian_version
9.6
# gcc --version
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
# uname -a
Linux dreams 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
GNU/Linux




When Galaxy S3 mini is connected via usb:

$ ls -l /dev /dev/mapper | grep
brw-rw 1 root disk 254, 0 Dec 15 10:53 dm-0
brw-rw 1 root disk 254, 1 Dec 15 10:53 dm-1

brw-rw  1 root disk254,   2 Dec 15 10:53 dm-2
brw-rw  1 root disk254,   3 Dec 15 10:53 dm-3
brw-rw  1 root disk254,   4 Dec 15 10:53 dm-4
brw-rw  1 root disk254,   5 Dec 15 10:53 dm-5
brw-rw  1 root disk  8,   0 Dec 15 10:53 sda
brw-rw  1 root disk  8,   1 Dec 15 10:53 sda1
brw-rw  1 root disk  8,   2 Dec 15 10:53 sda2
brw-rw  1 root disk  8,   5 Dec 15 10:53 sda5
brw-rw+ 1 root cdrom11,   0 Dec 15 12:39 sr0 l

$ lsblk -o KNAME,TYPE,SIZE,MODEL gives
KNAME TYPESIZE MODEL
sda   disk  223.6G CT240BX200SSD1
sda1  part243M
sda2  part  1K
sda5  part  223.3G
sr0   rom 4.4G DVD+-RW UJ8A2
dm-0  crypt 223.3G
dm-1  lvm23.3G
dm-2  lvm 9.3G
dm-3  lvm15.9G
dm-4  lvm 1.9G
dm-5  lvm 173G

# mtp-detect
libmtp version: 1.1.13

Listing raw device(s)
   No raw devices found.

# ls -l /sys/bus/usb/devices/
total 0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 1-0:1.0 ->
../../../devices/pci:00/:00:1a.0/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 1-1 ->
../../../devices/pci:00/:00:1a.0/usb1/1-1
lrwxrwxrwx 1 root root 0 Dec 18 11:24 1-1:1.0 ->
../../../devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 1-1.5 ->
../../../devices/pci:00/:00:1a.0/usb1/1-1/1-1.5
lrwxrwxrwx 1 root root 0 Dec 18 11:24 1-1.5:1.0 ->
../../../devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 1-1.5:1.1 ->
../../../devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-0:1.0 ->
../../../devices/pci:00/:00:1d.0/usb2/2-0:1.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1:1.0 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.2 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.2
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.2:1.0 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.5 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.5
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.5:1.0 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.5:1.1 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.8 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.8
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.8:0.0 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:0.0
lrwxrwxrwx 1 root root 0 Dec 18 11:24 2-1.8:0.1 ->
../../../devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8:0.1
lrwxrwxrwx 1 root root 0 Dec 18 11:24 usb1 ->
../../../devices/pci:00/:00:1a.0/usb1
lrwxrwxrwx 1 root root 0 Dec 18 11:24 usb2 ->
../../../devices/pci:00/:00:1d.0/usb2

#lsusb | sort
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 1bcf:2b83 Sunplus Innovation Technology Inc.
Laptop Integrated Webcam FHD
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 04f2:0939 Chicony Electronics Co., Ltd
Bus 002 Device 004: ID 8087:07dc Intel Corp.
Bus 002 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure
Applications Processor


But when an LG is connected:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 1bcf:2b83 Sunplus Innovation Technology Inc.
Laptop Integrated Webcam FHD
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate M

Re: Is there a list contains all debian packages and it's license ?

[Yanhao Mo]

On Sat, Sep 23, 2017 at 02:32:36PM +0800, Paul Wise wrote:
> On Sat, Sep 23, 2017 at 8:38 AM, Yanhao Mo wrote:
> 
> > but what I really want to know is that is there such a list that display
> > all debian packages with their licenses, just like the following link
> > about rhel[1].
> 
> There is no single list of licenses for each Debian package,
> just the individual copyright files in each source/binary package.
I see. Thanks for answering.
> What are you doing that requires a single list for all packages?
Nothing, I was just curious. :P


signature.asc
Description: PGP signature

Is there a list contains all debian packages and it's license ?

[Yanhao Mo]

Hi,

I do known how to find license info about packages those have been
installed on my system and how to generate a list about it.
but what I really want to know is that is there such a list that display
all debian packages with their licenses, just like the following link
about rhel[1].

[1] 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Package_Manifest/index.html

Yanhao,


signature.asc
Description: PGP signature

It there a way to file a complaint against a package maintainer?

[J Mo]

Hello!

Is there any standard method for filing a complaint against a Debian 
package maintainer?


Unfortunately, a package that is important to me has been picked up by a 
new maintainer after the old one abandoned it.


This new maintainer has caused a lot of problems because they, 
admittedly, don't use the package themselves and don't really understand 
it. The person is a mediocre programmer and has trouble with bash 
scripts. The motives for why this person adopted this package are not clear.


The new maintainer has broken lots of things, mass-closed all old bugs 
without having resolved anything (even bugs that had recent 
comments/updates), and is generally causing a lot of grief for us users 
of the package.


Anyone have any advice?

Re: router solutions based on Debian?

[J Mo]

Please excuse my late reply.

I am network engineer (Cisco and Juniper big routers/switches) and I 
recently did a review of about eight router-type Linux/BSD distros, all 
run under KVM on a virtual test network. I also recently started 
contributing some code to LEDE (OpenWRT). I do router-y/switch-y kinds 
of things on a daily basis.


I found that almost all of these router distros pretty much suck. The 
web UIs were not functional/practical and they often had web UIs that 
looked like they were straight out of the 90s. I'm not talking about 
minimalism -- I'm talking about bad design and poor judgement.


PFsense was overwhelmingly the best and was the only one that I had a 
positive opinion on or would otherwise consider using in a business 
environment. It's FreeBSD based.


Untangle is Debian based but it's basically for-profit garbage that has 
confused a router with an iPhone.


Endian was interesting but also locks you out of some features unless 
you buy a support contract. Might be as good as PFsense some day if they 
keep trying, but I doubt it. Also Debian based I think.


IPfire, IPcop, and Shorewall all looked like they ten years old and 
there was obvious missing functionality in the web UI. They looked more 
like weekend projects than anything professional like PFsense.


When it comes to router-web-UI distros, the only thing I could recommend 
was was PFSense. Everything else was disappointing.


That being said, a regular old Debian box would make a fine router if 
you are a command-line oriented person. There is plenty of ITX-sized and 
smaller hardware out there to meet your needs. This seems to be the way 
you were headed anyhow.


It should be noted that Ubiquiti firewall/routers are Debian based and 
drop you right into a bash shell. They are worth looking at. Their 
web-UI isn't bad either, but it doesn't have feature-parity with command 
line yet (maybe never will). I would highly recommend any network 
engineer to pick up their little $50 ERX to play with.


As several people have already mentioned PCEngines boards are awesome 
and I think they even have models that have a SFP for optical.


Good luck! Come back and share what you get and how you feel about it.



On 11/23/2016 06:54 AM, Daniel Pocock wrote:


My ISP is upgrading my connection to gigabit on Friday and I suspect my
current router may struggle with it.

My existing router runs OpenWRT but I've found the firewall and IPsec
setup is a little bit constrained in that environment and it is tempting
to move to a router running a full OS.

I've seen a lot of discussions about making DIY routers running a free
OS like Debian, FreeBSD or OpenBSD and I was tempted to go with
something like that running Shorewall, strongSwan, DHCP and DNS.  Maybe
it will also do wifi or maybe the existing router will be a bridge to wifi.

Can anybody share any comments or links about this topic?

- quiet (fanless), low-power and low cost hardware suitable for Gigabit
routing and maybe use as a NAS too.  It would also be useful to have
fibre support in the router and avoid using a media convertor.

- are there any live builds or other out-of-the-box solutions that
address this use case particularly well?

- any blogs or other articles that provide a good example of how other
people already did this?

One particular concern for me is minimizing the number of components.
I've got a media convertor and fibre transceiver already, but that has
its own plug-pack PSU and those are all extra things that can fail at
some random moment in the future.  Having a self-contained solution
without a bunch of plug-pack PSUs would hopefully be easier to support
and make less clutter.

Regards,

Daniel

KVM virtualization with VMM/virt-manager and mouse lag and stutter

[J Mo]

This is one of those I-fixed-it-myself posts where I'm just sharing my 
solution for others, should they google it in the future.


I recently started learning about KVM virtualization. Naturally I 
stumbled across the VMM/virt-manager GTK tool, since that's pretty much 
the only good tool available at the moment (aqemu is promising but not 
good), so I started loading up some Linux live ISO images.


Immediately I had the problem where my mouse was lagging all over the 
place and the experience was horrible!


When I started my VMs manually from the command line with qemu, I 
noticed the mouse lag problem completely went away. Also, later, I 
noticed that the Fedora live ISO images did not have this problem.


VMM forces you to use Spice, even if you are running on the hypervisor 
itself. You have to use either VNC or Spice. You can't start a native 
qemu window like you can do by starting a qemu command manually.


The reason the Fedora Live images worked was because they have the 
spice-vdagent package already installed. The spice-vdagent creates a 
communications channel between the client/viewer host and the 
guest/client host so that mouse movement is smooth, copy-paste/clipboard 
functionality works, and a few other things.


Unfortunately, other than Fedora, none of the other Linux live images I 
tested have this package installed by default: Not Ubuntu, not Mint, not 
Debian, not KDE Neon. OpenSUSE installs it by default, but it's not 
really a live CD. These distros should all fix this if they want people 
to have a good experience when testing under KVM.


And, because these are Live CD images, it's not like I can easily 
install the package and logout/restart, since I have not configured a 
hard drive/permanent storage.


Fortunately, I found a hacky solution in VMM:  Add Hardware --> Input 
--> EvTouch USB Graphics Tablet


Adding a tablet device fixes many of the problems which I experienced 
with VMM, without installing the spice-vdagent on the guest OS.


After finding this solution myself, I also googled and found this post, 
which gives a similar solution to a slightly different problem:


https://serverfault.com/questions/457603/any-way-to-release-focus-on-a-kvm-guest-in-virt-manager-without-having-to-click

So if you use virt-manager and your mouse movement is horribly laggy, 
stuttery, and otherwise intolerable, install spice-vdagent or configure 
VMM to add a non-existent tablet device to the guest.

Re: Recommendation: Backup system

[mo]

Am 02.10.2016 um 12:55 schrieb Dan Purgert:

mo wrote:

Am 02.10.2016 um 02:47 schrieb Dan Purgert:

mo wrote:

Maybe this is a little OT, but what kind of backup strategy would you
guys recommend? (Any advice Gene? :) )


If it *must* survive, 3-2-1 is the way to go.

3 copies (Original, Backup, and Backup of the Backup)
2 different media types (such as HDD(Orig) + HDD(Bk1) + Optical(Bk2))
1 stored offsite


Except for the offsite storage (Just for my private data) this sounds
perfect for my needs. Good thing is that i have two free HDD's here with
2TB each, so this would work ;)


Yeah, I don't have a spare copy offsite either -- but I don't
(currently) have any electronic data that would be absolutely
devastating if I lost it.  If / when I have kids or something, then baby
pics among other things will likely have that status.


But i guess i should consider it, loosing all the data is quite hard 
(Had that a while ago).



[snip]
One question Dan: What do u use to encrypt your files? also openssl?


I just use PGP.



I need to delve into PGP a little more ;) (Currently i use the openssl 
command to do my encrpytion on the backup archives)

Re: Recommendation: Backup system

[mo]

Am 02.10.2016 um 02:47 schrieb Dan Purgert:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

mo wrote:

Maybe this is a little OT, but what kind of backup strategy would you
guys recommend? (Any advice Gene? :) )


If it *must* survive, 3-2-1 is the way to go.

3 copies (Original, Backup, and Backup of the Backup)
2 different media types (such as HDD(Orig) + HDD(Bk1) + Optical(Bk2))
1 stored offsite


Except for the offsite storage (Just for my private data) this sounds 
perfect for my needs. Good thing is that i have two free HDD's here with 
2TB each, so this would work ;)



That being said, most of my stuff isn't of the "absolutely must survive"
nature, so I just have it on external HDDs.  If something is
particularly important, it's on HDDs and also somewhere like google
drive / dropbox (although, encrypted when at those places).


I currently use dropbox myself to store my conf files (gzipped and then 
encrypted with aes) in case something bad should ever happen to my NAS, 
so that i can at least restore my servers quickly ;)


One question Dan: What do u use to encrypt your files? also openssl?


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJX8FjGAAoJEI4R3fMSeaKBX9gH/i6qw2GOY/LSE5haz8uv6u/X
GNT6m44c6olrnzGtKFzEPae3ELTTAT/t47yet2noAR+AS9aJzhtR86l3JfQfu4ug
0XplxY/GkkrEpIeMFrqKy2hc3u++PoEHEBkQut46x6QAw/85ieKs2tsbmfeyUuF7
y5gFbGlowcy3NtSdGIMR6qzn67I+DaO2veTMV3Z+/aR+fAegZtvv/t3CCi1dsmRW
kEWIuPyGR//Foy/vkQsakpHJnl9AvJREB5/T+zRX3pkBXKkzQrIfe80eJYAm5Z8w
rhvZc9lLbO/bVcSvLwRKqYtDmWRY4AeVrqmCitiuXf54KjwZY5Lh16LVq+KfCiQ=
=YzZ4
-END PGP SIGNATURE-



Greets

mo

Re: Recommendation: Backup system

[mo]

Am 01.10.2016 um 23:06 schrieb Bob Weber:

Like I said backuppc uses incremental and full backups.  The web
interface lets you browse any backup (inc or full) and you see all the
files backed up.  I set the incremental for each day up to a week.  So I
have up to 7 of them.  The full can kept for for however long you want.
I currently keep 12 weekly, 8 bi-weekly and 4 monthly full backups so
that covers almost a year.


That would serve my needs well also :) (For the moment it is just my 
private data - But either way, data should always be backed up ;) )

Thanks for the info ;)


There is another solution you might like called rsnapshot.  I use it to
backup just my root directory on my desktop before I do updates.  That
way if something goes wrong I can boot into a rescue cd and restore the
system to the state before the update.  I just can't afford to have my
desktop to break.  rsnapshot uses rsync so it can backup any computer
that has rsync.  It uses hard links so duplicate files are only stored
once.  You specify how many backups you want to keep and rsnapshot
deletes older ones over that max before adding the new one.  That way
you always have backups (assuming you set the count greater that 1) that
will be there even if there is a transfer error.  This is similar to
your script but is very versatile.


I heard about it but never used it so far, i should give that a try for 
sure :)




*...Bob*
On 10/01/2016 04:42 PM, mo wrote:

Maybe this is a little OT, but what kind of backup strategy would you
guys recommend? (Any advice Gene? :) )






Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 02.10.2016 um 00:22 schrieb Brian:

On Sat 01 Oct 2016 at 22:47:27 +0200, mo wrote:


Am 01.10.2016 um 20:17 schrieb Brian:

On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:


On 2016-10-01, mo <mo...@gmx.net> wrote:

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,

>from the Server to my Main PC.

The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all
this is sitting locally at my home. The most important thing for me is
to send and receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(

Thanks again for all your help ;)

Greets

mo




I should have been a little clearer myself. You don't need to register a
domain name. Just invent your own domain name for local purposes. Let's
say you choose the domain name "monet", and that you have already given
the hostnames "desktop" and "server" to your two machines. Then you
would edit the file /etc/hosts on both machines to contain the following
lines:

192.168.23.11 desktop.monet desktop
192.168.23.200 server.monet server


I did that on gnome and desktop with appropriate changes:

   192.168.7.20 desktop.monet desktop
   192.168.7.67 gnome.monet gnome


Now you only need to tell exim4 on the server that it is the final
destination for emails to *.monet, again using the debconf wizard. You
will then be able to send emails to local addresses, while emails to all
other domains will go through your ISP's smarthost.


I did that on gnome and desktop.


Incidently, you can also tell exim4 on the desktop to use the server as
its smarthost.

I realise that you're getting lots of (sometimes contradictory)
information from various sources. The barebones configuration I have
described above has served me well for several years.


All commands are issued from gnome.

 brian@gnome:~# ping -c3 desktop
 PING desktop.monet (192.168.7.20) 56(84) bytes of data.
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms

 --- desktop.monet ping statistics ---
 3 packets transmitted, 3 received, 0% packet loss, time 2001ms
 rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms

 brian@gnome:~# ping -c3 desktop.monet
 PING desktop.monet (192.168.7.20) 56(84) bytes of data.
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms

 --- desktop.monet ping statistics ---
 3 packets transmitted, 3 received, 0% packet loss, time 2002ms
 rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms

We expect that result because ping uses files in /etc/nsswitch.

 root@gnome:~# exim -bt brian@desktop
 R: dnslookup for brian@desktop
 brian@desktop is undeliverable: Unrouteable address

 root@gnome:~# exim -bt brian@desktop.monet
 R: dnslookup for brian@desktop.monet
 brian@desktop.monet is undeliverable: Unrouteable address

Am I the only one who gets this? No capability to deliver mail to
desktop. What am I doing wrong?



I think this is the problem with exim calling DNS on the given hostname...
which is doomed to fail. To get it working you need to create the
hubbed_hosts file and set your aliases in there, for example:
192.168.7.20: desktop

Then it should work fine, at least for me it did.

Hope this helps :)


Not really, I'm afraid.

We all know a hubbed_hosts file works. Mark Fletcher has written
extensively about it and I have said a thing or too also. What I want to
know is why following the advice from Liam O'Toole doesn't work for me,
even though I have followed the instructions exactly.

BTW: It would be 'desktop: 192.168.7.20' and 'desktop.monet:192.168.7.20'
in hubbed_hosts.


Ah yeah, right, i mixed the syntax up, sorry about that.

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 20:17 schrieb Brian:

On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote:


On 2016-10-01, mo <mo...@gmx.net> wrote:

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all
this is sitting locally at my home. The most important thing for me is
to send and receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(

Thanks again for all your help ;)

Greets

mo




I should have been a little clearer myself. You don't need to register a
domain name. Just invent your own domain name for local purposes. Let's
say you choose the domain name "monet", and that you have already given
the hostnames "desktop" and "server" to your two machines. Then you
would edit the file /etc/hosts on both machines to contain the following
lines:

192.168.23.11 desktop.monet desktop
192.168.23.200 server.monet server


I did that on gnome and desktop with appropriate changes:

192.168.7.20 desktop.monet desktop
192.168.7.67 gnome.monet gnome


Now you only need to tell exim4 on the server that it is the final
destination for emails to *.monet, again using the debconf wizard. You
will then be able to send emails to local addresses, while emails to all
other domains will go through your ISP's smarthost.


I did that on gnome and desktop.


Incidently, you can also tell exim4 on the desktop to use the server as
its smarthost.

I realise that you're getting lots of (sometimes contradictory)
information from various sources. The barebones configuration I have
described above has served me well for several years.


All commands are issued from gnome.

  brian@gnome:~# ping -c3 desktop
  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms

  --- desktop.monet ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2001ms
  rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms

  brian@gnome:~# ping -c3 desktop.monet
  PING desktop.monet (192.168.7.20) 56(84) bytes of data.
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms
  64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms

  --- desktop.monet ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2002ms
  rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms

We expect that result because ping uses files in /etc/nsswitch.

  root@gnome:~# exim -bt brian@desktop
  R: dnslookup for brian@desktop
  brian@desktop is undeliverable: Unrouteable address

  root@gnome:~# exim -bt brian@desktop.monet
  R: dnslookup for brian@desktop.monet
  brian@desktop.monet is undeliverable: Unrouteable address

Am I the only one who gets this? No capability to deliver mail to
desktop. What am I doing wrong?



I think this is the problem with exim calling DNS on the given 
hostname... which is doomed to fail. To get it working you need to 
create the hubbed_hosts file and set your aliases in there, for example:

192.168.7.20: desktop

Then it should work fine, at least for me it did.

Hope this helps :)

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 18:25 schrieb Liam O'Toole:

On 2016-10-01, mo <mo...@gmx.net> wrote:

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all
this is sitting locally at my home. The most important thing for me is
to send and receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(

Thanks again for all your help ;)

Greets

mo




I should have been a little clearer myself. You don't need to register a
domain name. Just invent your own domain name for local purposes. Let's
say you choose the domain name "monet", and that you have already given
the hostnames "desktop" and "server" to your two machines. Then you
would edit the file /etc/hosts on both machines to contain the following
lines:

192.168.23.11 desktop.monet desktop
192.168.23.200 server.monet server

Now you only need to tell exim4 on the server that it is the final
destination for emails to *.monet, again using the debconf wizard. You
will then be able to send emails to local addresses, while emails to all
other domains will go through your ISP's smarthost.

Incidently, you can also tell exim4 on the desktop to use the server as
its smarthost.

I realise that you're getting lots of (sometimes contradictory)
information from various sources. The barebones configuration I have
described above has served me well for several years.


Thanks for the clarification Liam :)


If you add more machines to your network later on you should consider
setting up local DHCP and DNS instead of manually updating /etc/hosts
files. But we'll leave that for another day. :)


I think that day will soon come for me :) (I cant live without some 
playing and fuzzing around :^) )

Re: Recommendation: Backup system

[mo]

Am 01.10.2016 um 21:37 schrieb Glenn English:



On Oct 1, 2016, at 10:22 AM, Gene Heskett  wrote:

On Saturday 01 October 2016 08:40:35 Mark Fletcher wrote:


I know Gene is a fan of Amanda, I have it on my list to try it out
myself based on positive remarks he has made about it in the past.


Yeah. Amanda's a good solution. I use it with tape.

There are a couple advantages to this:

Amanda's been around for a very long time (in computer years). So, like Debian 
stable, the bugs tend to have been worked out.

Amanda does its backups using plain old standard *nix software, dump or tar. So 
if you have a really nasty data loss, you can restore from a backup without 
dealing with data in a format built by the backup program. It's not a trivial 
job, I'm told, but if you're really stuck...

The tapes aren't disks, and every backup is done to a different and simple 
storage device with few moving parts. (The reliability of a disk RAID1 reduces 
this advantage significantly.)

OK, there are disadvantages too: Amanda's not easy to configure, and tapes and 
tape drives are very expensive and very slow.

But I like the advantages more than the disadvantages. It does a really good 
and reliable job.



Amanda is beginning to be more and more interesting to me :)

Re: Recommendation: Backup system

[mo]

Maybe this is a little OT, but what kind of backup strategy would you 
guys recommend? (Any advice Gene? :) )

Re: Recommendation: Backup system

[mo]

Am 01.10.2016 um 14:20 schrieb Dan Purgert:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

mo wrote:

As the title say i'm in search for a backup application/system.
Currently i manage my backups with a little script that i wrote... but
it does not really serve my needs anymore.
I want to be able to make backups on my main PC and also on my server,
the backups i would then store on my NAS.


There's always rsync from the hosts to the NAS box.


rsync is quite handy for that, indeed ;)
(I actually do that atm - i transfer the data over via rsync to my NAS)


Only thing that I see "wrong" with your script is that:
 - you're deleting the backups (what happens when you delete something,
   and don't catch it til after the next backup run?)


I forgot to mention that i have a script which transfers the current 
backup over if the given backup is not yet saved, sorry, i kind left 
that out. :P



 - you're backing up everything, even if it hasn't changed.


That's indeed a problem atm... That's mainly why i'm on the search for a 
more professional approach so to speak. Honestly, i have not yet planned 
a specific strategy...





-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJX76m+AAoJEI4R3fMSeaKBwWQH/RiG+HH83WcyGT5wOhGM344j
UTOXN+VS7UC0jOsZG+MYrNJkAE8U9qwAYahi/63X+TFmSa2rFRmw6rv0pfvfBeiP
mItlVsjqyeR00tFc+zmAPWKnOZgela6kO6sdM7w2/GZTTThDL/CF/a+BP7YuOyid
QQEM5HLcSqbF1fiIStKkP2bTBZq0C8aSioy69Tg0nWES3vou7WxkXESUyP5ZEjp7
k9WQZj8JHZvJsJlfzRfJWSswkoR5Rj6OjsEjbbgFmoIHjndQ+ivhlKoJH+/6oGIM
txTwx8LzlucuKeYNr9bFQkV74ws8VGQBQPi1JBqvhXQEzW7qlbGg6ri3ADMrfq0=
=jx9W
-END PGP SIGNATURE-



Thanks Dan ;)

Greets

mo

Re: Recommendation: Backup system

[mo]

Am 01.10.2016 um 18:22 schrieb Gene Heskett:

On Saturday 01 October 2016 08:40:35 Mark Fletcher wrote:


On Sat, Oct 01, 2016 at 11:37:31AM +0200, mo wrote:

Hi Debian users :)

Information:
Distributor ID: Debian
Description:Debian GNU/Linux 8.6 (jessie)
Release:8.6
Codename:   jessie

As the title say i'm in search for a backup application/system.
Currently i manage my backups with a little script that i wrote...
but it does not really serve my needs anymore.
I want to be able to make backups on my main PC and also on my
server, the backups i would then store on my NAS.

Make a long story short:
Have you guys a recommendation for me?
Is there a specific application you use for your backups guys?


I know Gene is a fan of Amanda, I have it on my list to try it out
myself based on positive remarks he has made about it in the past.

Mark


Yeppers! It runs in the wee hours of the night here, for an hour or so.
Currently backing up this machine, and 3 more on my little home network
here, using its own unique, distribute the nightly load to equalize as
much a it can given its list of what to back up with nightly backups
totaling 11 to 14 Gb per night.

When I first started using it, I had a DDS2 changer, but it wasn't very
dependable, and at only 4Gb per tape, limited what I could do.  About
the time 500Gb Hd's came out, amanda had worked out a way to use virtual
tapes on a hard drive, so I converted. That has the advantage that
should I need to recover something, its random access instead of
sequential, so I can get back anything I need in just a few minutes,
most of which is spent studying the recovery docs because I've forgotten
how to do it. ;-)

With tapes, I could easily be a half a day recovering the same file
because each level of a backup has to be read from the start of the tape
until its found.  If I need something whose last good backup was a level
3, it would have to back up and find the level0, which is the last full
backup, then find the level 1 and merge any changes, wash, rinse, and
repeat.  A hard drive based system can do all that in seconds.


I guess i'm too young for tapes... or let's put it that way: I've never 
used them. (Why would you need tapes at home anyway :D )



And HD's have become much more dependable than tape, along with the
methods of warning the user that the drive is failing, and that alone
beats tape all the way into the trash bin.


True, the oldest HDD here (which is a 500GB drive) is running since 7 
years straight without a problem.



I was rather worried about the drive I use for amanda's v-tapes when I
saw almost 3 years ago that smartctl said it had 25 Reallocated sectors.
It still says 25 10 seconds ago.  That drive, now a 1Tb drive
as /dev/sdc, now has 58357 Power up hours on it. I don't care what you
may have paid for a tape library, it cannot survive that long, when this
HD has done that for a $100 bill at the time I bought it.  And I can put
this HD in a shirt pocket.  The tape library would need a refrigerator
rated 2 wheel dolly to move it, and a similar second dolly to move its
tapes.

Whats not to like?

I've had far more trouble dealing with tar changes as its been updated
over the years than I've had with amanda itself. All have been fixable
in a day or two once you can post the breakage on the tar list. amanda
uses tar to do the bare metal work.  A wrapper for tar in that sense,
and I then wrap amanda with a bash script that fixes the always a day
late record keeping that you can add to the v-tape image by making a
copy of amanda's database and writing it to the V-tape amanda just used,
so I can lose the main drive and have to start with a new install on a
fresh drive. With amanda I would install from the repo's on the new
drive. Its 2 or 3 steps, but in an hours time I can have this working
wheezy system with all its dross, put back on a new drive.

Cheers, Gene Heskett



Thanks for the info Gene ;)

Re: Recommendation: Backup system

[mo]

Has someone experience with Bacula?
I heard good things about it, although i never looked into it... maybe 
someone has and can give me his report on it :)

Re: Recommendation: Backup system

[mo]

Am 01.10.2016 um 16:46 schrieb Bob Weber:

I use backuppc.  It is web browser based setup and usage.  It takes
incremental and full backups that can remain as long as you want or have
space for.  It can browse files by name or in a version mode where you
can see the date where a file changed and restore an earlier version if
you want (or to a separate  download directory).  It compresses files
for space and only keeps one copy of a file's data if it is located in
different directories or servers (using hard links as needed).  It can
even backup user data for windows users (samba).  I use the rsync
transfer for Linux machines and even with windows running Cygwin.


I like the web interface part i have to say (Just browsed their website :) )
I will look into it ;)
(I have currently no windows machines here, but that might change in the 
future since i plan to deplay Windows Server 2012 R2)


Thanks for the hint ;)


I currently backup 8 computers going back almost 1 year.  I even backup
a vm at digital ocean.  Backuppc reports this:

144 full backups of total size 8951.56GB (prior to pooling and compression),
57 incr backups of total size 57.13GB (prior to pooling and compression).
Pool is 358.94GB comprising 1903010 files and 4369 directories (as of
10/1 01:09).

So 8951GB is compressed or pooled into just 358 GB!


The compression is quite nice, i might have at least 100GB to backup 
here. (Maybe a little more depending on what i want to save)



*...Bob*


Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 16:17 schrieb rhkra...@gmail.com:

On Saturday, October 01, 2016 08:23:10 AM mo wrote:

I use Icedove (Thunderbird) for all my personal mails and also to write
mail to the Debian users Mailing list ;)
I have never tried Kmail before, maybe i should, but Icedove fit's the
bill right :) (I'm normally a wm guy.. so i opt for lesser dependencies
when i install software... (Kmail pulls in a lot of KDE stuff that i
don't want) but atm i use Gnome.. well it works :D )
I will give Kmail a try on one of my vm's (Got Debian Jessie here in a
vm on which i have KDE installed)


AFAIK, Icedove is the same kind of email client as kmail, so there is no need
to try kmail.  (I happen to use (or, at least, used to use) a lot of other KDE
stuff, do using kmail was no burden for me.)  (I mean that Icedove uses (or at
least can use) pop3 to get emails and smtp to send emails--otoh, I have never
used Icedove, so I'm not absolutely sure.


Indeed, they are both MUA's with quite the same features (Of course the 
GUI is different - also another gui toolkit, qt - icedove uses gtk)

Yes, that is true, icedove can handle POP and IMAP


regards,
Randy Kramer



Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 15:57 schrieb Teemu Likonen:

mo [2016-10-01 12:36:10+02] wrote:


I'm not a friend of avahi to be honest, i much rather ignore it :D


Avahi is great. My ethernet-connected printer uses DHCP to get IP
address and network configuration. The printer announces itself to the
network with .local name so a print server can use that
name to connect to it. CUPS print server also announces its printers by
names. No static IP address configuration needed anywhere. I think the
underlying technique is called multicast DNS.



I guess i should be looking into avahi, never really did that, to be 
honest avahi so far did not really made much sense to me with my static 
network... But one can never learn enough ;)


Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 15:36 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 01:56:40PM +0100, Brian wrote:


The thing for Mo to grasp is that exim *always* does an MX lookup, often
using the ISP's DNS server. user@server will fail (as has been found
out) because the domain "server" is not in the DNS.

/etc/hosts is not consulted when the lookup is done. exim can be made to
look at /etc/hosts but for such a simple setup it is not worth the
effort and would likely lead to a world of pain.



With great respect I think that confuses the issue. A DNS lookup will
*not* explicitly get done by exim4 if the target domain is in
hubbed_hosts, or if exim4 has been told it is the local domain. The
point is one wishes to PREVENT a DNS lookup that is doomed to fail, and
one does so for machines that are not the machine-local domain by
putting them in hubbed_hosts, which will cause exim4 to throw out a
connection request for the local network infrastructure (starting with
the network infra on the local machine) to handle, without doing an
explicit DNS lookup. That is handled by /etc/hosts if it is populated,
and by Avahi if it is present and /etc/hosts is not populated, and no
doubt by a few other alternatives I am not familiar with as well. If
none of them succeed, the delivery will fail, because if I recall
correctly hubbed_hosts router config ends with no_more which prevents
other routers having a go.

However, for domains NOT listed in hubbed_hosts, if not in smarthost
mode, yes exim4's next move will be an explicit DNS lookup on the
domain. It is trying to find out what *machine* it should contact to
make the delivery to that domain. If it is in smarthost mode, it throws
its hands in the air and passes the problem to the smarthost to solve.


Oh yes, i see. Indeed i can understand your point!
Thanks for the explanation ;)
My picture of exim is getting better and better :)


Mark



Greets

mo

Re: Recommendation: Backup system

[mo]

Am 01.10.2016 um 14:40 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 11:37:31AM +0200, mo wrote:

Hi Debian users :)

Information:
Distributor ID: Debian
Description:Debian GNU/Linux 8.6 (jessie)
Release:8.6
Codename:   jessie

As the title say i'm in search for a backup application/system.
Currently i manage my backups with a little script that i wrote... but it
does not really serve my needs anymore.
I want to be able to make backups on my main PC and also on my server, the
backups i would then store on my NAS.

Make a long story short:
Have you guys a recommendation for me?
Is there a specific application you use for your backups guys?


I know Gene is a fan of Amanda, I have it on my list to try it out
myself based on positive remarks he has made about it in the past.


Sounds good to me :) - I'll set that on the todo list myself to (Just 
checked the webpage of Amanda and it does sound pretty good!).


Gene, can you elaborate on Amanda? :) (If Gene does read this mail)


Mark



Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:52 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 02:24:16PM +0200, mo wrote:



Am 01.10.2016 um 14:20 schrieb Brian:

On Sat 01 Oct 2016 at 14:09:19 +0200, mo wrote:


Am 01.10.2016 um 14:02 schrieb Mark Fletcher:


No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.


I have colones in the hubbed_hosts file... seems to work.
I just tested it: It works with or without the colon. Maybe this is
interesting to know ;)


Please see exim4-config_files(5).



Just looked into the man page, indeed a colon is required there. ;)



No, it isn't. I don't use colons in my hubbed_hosts file.


Both works actually. I Just tried it. But the man pages uses colons.. 
seems like it works fine with or without ;)



Mark



Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:56 schrieb Brian:

On Sat 01 Oct 2016 at 21:23:33 +0900, Mark Fletcher wrote:


On Sat, Oct 01, 2016 at 12:36:10PM +0200, mo wrote:


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


hubbed_host entries apply only to exim4. I also suspect, but am not
sure, that they are a Debian extension to exim4 in the sense that the
*DEBIAN* exim4 comes configured for them out of the box, while the
upstream exim4 does not. IIRC there is no reference to hubbed_hosts in
the upstream documentation, only in the Debian docs.


Correct. I'll add: the upstream documentation spec.txt.gz covers
hubbed_hosts in sections 20.3 to 20.7. It is not obligatory to read it.


They work because the debian config contains a router to handle hubbed
hosts. You can see what it is doing if you search
/var/lib/exim4/config.autogenerated for the text hubbed_hosts.


Fine.


If the file is not populated this router is skipped and then exim4
requires either that the address is the local machine, or that there is
a smarthost configured that it can delegate to, or that it can find an
official MX entry for the target domain by doing a DNS lookup. All of
which will fail for a local box that isn't registered to the world as a
mail server.


The thing for Mo to grasp is that exim *always* does an MX lookup, often
using the ISP's DNS server. user@server will fail (as has been found
out) because the domain "server" is not in the DNS.

/etc/hosts is not consulted when the lookup is done. exim can be made to
look at /etc/hosts but for such a simple setup it is not worth the
effort and would likely lead to a world of pain.


just out of curiosity:
What did i have to do to make exim honor the /etc/hosts file? :)
(I quite often find myself in the world of pain :D )

Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:51 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 02:33:27PM +0200, mo wrote:




I sure appreciate to know the inner workings of it all :)
Good to know how avahi is involved here, this paints me a clearer picture :)



I just want to correct one thing I said here, having read your other
posts. In one of them you mentioned you have static routing mappings set
up for your network machines in /etc/hosts. That is a perfectly valid
setup, albeit it is not the default "Debian way" (by which I mean only
that it is not how Debian comes configured out of the box, or more
accurately out of the .iso) and not how I do it. What a pain if you buy
a new computer to add to your network! But absolutely nothing invalid
about it.


Well i'm using the static network config since quite some time, but i 
had planned to change over to DHCP... But for now it works ;)
(The work is not so hard, adding a machine to the network is done 
quickly with Debian ;) - My other machines use different Operating 
Systems, got FreeBSD and OpenBSD here to on the LAN, works like a charm :) )



In this case, Avahi is probably *not* involved because exim4 gets an
answer to the question of what IP the host name maps to, without having
to consult it. But it *would be* involved if you did not have static
mappings set up in /etc/hosts.


Good to know ;)


Mark



Thanks Mark ;)

Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:23 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 12:36:10PM +0200, mo wrote:


Did you follow a specific book or guide?


Google "debian exim4 configuration". And look at the upstream
documentation in package exim4-doc-html.



I will do so ;)




Exim configuration has the concept of "routers" and "transports".
Routers basically decide what to do with a message, and transports do
it. One of the routers configured by default in the Debian exim
configuration is for "hubbed hosts". What this means, is machines
capable of sending and receiving email ("hosts" in exim speak) that are
on the same LAN as this machine (connected by a "hub"). Note that this
"hub" could be your local home network router, and for these purposes
machines on WiFi and machines on a wired LAN would be considered on the
same hub, even though that isn't strictly true. The point is that
network packets can be addressed directly between the machines, they
don't require a router in between.



As far as i do understand this is that only machines which are defined as
hubbed hosts can be send mail in the local LAN? Or am i misunderstanding
something here? :)



In essence yes you are right, because a local configuration of exim4
would determine that the addresses are not local and not in
hubbed_hosts, and tell you to eff off, while a smarthost configuration
would attempt to use the smarthost to send to the local machine, which
is doomed to failure, and the internet configuration would attempt to
use DNS to find the local machine, which is also doomed to failure.
Being in hubbed_hosts prevents exim4 for going looking for an MX record
for the receiving host, which is guaranteed to fail for a machine that
isn't registered to the world at large as an email server.



Alright, i finally go it ;) Thanks for the explanation Mark! :)


In Debian, this is achieved with Avahi. This is what allows you, if you
have MachineA and MachineB on your network, to do for example "ping
MachineA.local" from MachineB and expect MachineA.local to be resolved
into an IP address.



I'm not a friend of avahi to be honest, i much rather ignore it :D


All I can do here is echo Brian. But also, even if you aren't its
friend, ignoring it is fine, because it comes already configured and
will just do its job whether it gets any love from you or not. I just
assumed you'd like to know what is going on under the hood.


I sure appreciate to know the inner workings of it all :)
Good to know how avahi is involved here, this paints me a clearer picture :)




In /etc/exim4, create a file owned by root called hubbed_hosts. In the
file, each line maps a "domain" (the part after the @ sign in an email
address) to a "host" (the name of a machine on your network, as it can
be reached from this machine). Put the domain first, then a tab
character (spaces may also be OK) and then the host. So for example I
have a machine on my network called affinity, and so in the hubbed_hosts
file on the machine I am sitting in front of now, I have two lines, one
saying "affinity.localaffinity.local", and the other saying
"affinityaffinity.local" (no quotes in the file). This tells the
local exim installation that any email address with @affinity.local as
the domain should be forwarded on to a machine called affinity.local,
and any mail with @affinity as the domain should be forwarded on to a
machine called affinity.local. Exim4 will then say "Connect to
affinity.local!" with no attempt to translate that into an IP address,
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
affinity will wake up and co-operate to deliver the mail.


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


hubbed_host entries apply only to exim4. I also suspect, but am not
sure, that they are a Debian extension to exim4 in the sense that the
*DEBIAN* exim4 comes configured for them out of the box, while the
upstream exim4 does not. IIRC there is no reference to hubbed_hosts in
the upstream documentation, only in the Debian docs.

They work because the debian config contains a router to handle hubbed
hosts. You can see what it is doing if you search
/var/lib/exim4/config.autogenerated for the text hubbed_hosts.


I will consult the Debian docs, currently reading over the wiki page of 
exim :)



If the file is not populated this router is skipped and then exim4
requires either that the address is the local machine, or that there is
a smarthost configured that it can delegate to, or that it can find an
official MX entry fo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:20 schrieb Brian:

On Sat 01 Oct 2016 at 14:09:19 +0200, mo wrote:


Am 01.10.2016 um 14:02 schrieb Mark Fletcher:


No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.


I have colones in the hubbed_hosts file... seems to work.
I just tested it: It works with or without the colon. Maybe this is
interesting to know ;)


Please see exim4-config_files(5).



Just looked into the man page, indeed a colon is required there. ;)

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:02 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 11:01:17AM +0100, Brian wrote:

On Sat 01 Oct 2016 at 11:06:07 +0200, mo wrote:


First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all this is
sitting locally at my home. The most important thing for me is to send and
receive mail from both systems in my home network.
I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(


Assuming the server hostname is "server".

1. On Main PC use your editor to create /etc/exim4/hubbed_hosts. In it
   put

   server: 192.168.23.200

   in it and restart exim4.

2. Send mail to user@server.

3. You can replace 'server: 192.168.23.200' with 'server: server.local'
   if avahi-daemon is running on both machines.



No colons as separators in hubbed_hosts, to my knowledge. Use spaces or tabs.


I have colones in the hubbed_hosts file... seems to work.
I just tested it: It works with or without the colon. Maybe this is 
interesting to know ;)



Mark

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 14:00 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 01:39:47PM +0200, mo wrote:



Am 01.10.2016 um 13:22 schrieb Brian:

On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:



I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


I'd suggest you try it and look at the logs.


Watch out, you may piss off your ISP if you repeatedly send emails it
can't deliver. They'll make their displeasure felt by not delivering
_any_ mails for you for a while. My suggestion is get local delivery
working first, then turn attention to mails outside.



Thanks for the hint Mark :)
So far i only tried it twice, i think i'm save for the moment. :D haha


Mark

Re: Configuring Exim for mail delivery

[mo]

Hi Mo


Hi Clive :)


I tried to send this with a .pdf yesterday d'oh! Anyway, we've just
reinstalled our servers with mail and automated backup and updated our
notes. They're not finalised and hence not on the web yet but you can
access them here:
https://dl.dropboxusercontent.com/u/63603283/InstallationNotes2016.9.24.pdf

Bit's of it may help.


It sure does! I quickly scanned over the pdf and the mail part is quite 
interesting for me, thanks a lot! ;)


Btw: Nice setup you got there! :)



Regards

Clive



Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 13:36 schrieb Mark Fletcher:

On Sat, Oct 01, 2016 at 11:06:07AM +0200, mo wrote:


I think i should elaborate a little more on my setup.. i guess i did not
make that very clear in the first place, sorry about that.

My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around,
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to
other SMTP servers).
The second requirement is optional since i dont own a domain and all this is
sitting locally at my home. The most important thing for me is to send and
receive mail from both systems in my home network.
I hope this made my problem a little clearer :)



Right. So you get mail going back and forth between your two machines,
server and PC, by creating and populating the hubbed_hosts file I
talked about in my previous mail, on both machines, pointing at each
other of course.


I created the hubbed_hosts file under /etc/exim4 and it now works fine, 
i can send mail from my server to my pc and vice versa :)



If you want to ping the server from the client, you should be able to do
"ping server.local" from your PC (obviously replace the actual name of
your server, which you didn't include in your mail, where I put server).
What is happening if you do that is your PC is saying "get me the
address of server.local!" and the Avahi daemon on your PC either already
knows that, or sends out a broadcast message to your network saying "is
there a server.local in the house???". The Avahi daemon running on the
server responds to that saying "yes, I'm here, and my IP address is
192.168.23.200!". The Avahi daemon on your PC responds to whatever did
the asking (ping in this case) with the required IP. Ping then requests
that packets be sent to IP address quoted. By this mechanism computers
on the same LAN can communicate with each other peer to peer without
fannying around with full-blown DNS, which is what Avahi is for. That is
installed by the Jessie installer by default as far as I can tell, so
both your machines should have it. It doesn't require any configuration,
so if you haven't touched it, it should work as I have described.
Although obviously, you have to substitute the real names for your
server and PC (but you *do* require the .local unless you have configured
Avahi to use something else)


I'm currently not using avahi as a matter of fact, but it works all fine 
without it ;)
(I have static entries in the /etc/hosts file for my server and for the 
pc - on each system of course)
I have never really worked with avahi... i kinda ask myself why do i 
need it if i can just use DNS or static entries in /etc/hosts. 
/etc/nsswitch.conf is also configured to lookup the /etc/hosts file first.
I know this question is OT, but since you mentioned avahi maybe i can 
ask you what kind of benefits avahi can offer me? :)

(I'm having a statically configured network with 4 machines)


If you used the default config of exim4 the hubbed_hosts router is set
up and waiting to be used. All you need to do to enable it is to
populate the hubbed_hosts file as I described. The other thing you need
to do is follow Liam's advice, except importantly what needs to be set
there is the "domain" of the local PC (on the local PC) or the server
(on the server) only. So the PC will accept mail for pc.local (or
whatever your pc is called) and the server for server.local (or whatever
the server is called). Then, you will be able to email yourself at the
server from the PC by sending a mail to mo@server.local, where I am
assuming your user name on the server is mo and the server's machine
name is server. Obviously you would substitute real names. And to go the
other way, from the server, you could send a mail to yourself on the PC
by mailing mo@pc.local.


I have asked that before i believe, sorry if this question shows up 
twice But why do i even need to set up hubbed_hosts?
I don't really understand why... Should exim not consider the /etc/hosts 
file to resolve the ip of my pc or server (Which i have entered there)
Also i have seen (before it worked) in the log that i get a "destination 
unreachable"... I just don't understand why exim needs to rely on the 
hubbed_hosts being set up?
(I hope you can understand what i mean, if not i will try my best to 
make it clearer :D )



Let's take a moment to go through what happens if you send a mail from
PC to server with everything set up as it should be.

On the PC you create a mail and address it to mo@server.local. Let's
imagine you use mutt to create it. And let's assume mutt is using its
default configuration to send the mail, which is to call sendm

Re: Configuring Exim for mail delivery

[mo]

Am 01.10.2016 um 13:22 schrieb Brian:

On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:


I just figured out how to get this working myself a week or two back, so
it's fresh in my mind. The key trick is the use of "hubbed hosts".


Did you follow a specific book or guide?


The manual for exim4-config_files is the first place to look.



I will look into the manual.
I also found a book about exim from O'Reilly, it's quite old (2001) but 
i guess i can get some info out of it.



Exim configuration has the concept of "routers" and "transports".
Routers basically decide what to do with a message, and transports do
it. One of the routers configured by default in the Debian exim
configuration is for "hubbed hosts". What this means, is machines
capable of sending and receiving email ("hosts" in exim speak) that are
on the same LAN as this machine (connected by a "hub"). Note that this
"hub" could be your local home network router, and for these purposes
machines on WiFi and machines on a wired LAN would be considered on the
same hub, even though that isn't strictly true. The point is that
network packets can be addressed directly between the machines, they
don't require a router in between.



As far as i do understand this is that only machines which are defined as
hubbed hosts can be send mail in the local LAN? Or am i misunderstanding
something here? :)


hubbed_hosts can send mail wherever you want. For example:

  example.com: smtp.example.com

would send mail to someone at example.com through smtp.example.com
(which could be a smarthost).



Got it, thanks ;)


In Debian, this is achieved with Avahi. This is what allows you, if you
have MachineA and MachineB on your network, to do for example "ping
MachineA.local" from MachineB and expect MachineA.local to be resolved
into an IP address.



I'm not a friend of avahi to be honest, i much rather ignore it :D


Let's hope your IP addresses do not change.



No changes here, static network configuration, so that should not pose 
problems. (My network only has 4 machines, so DHCP is not needed, at 
least atm i don't need it :) )



In /etc/exim4, create a file owned by root called hubbed_hosts. In the
file, each line maps a "domain" (the part after the @ sign in an email
address) to a "host" (the name of a machine on your network, as it can
be reached from this machine). Put the domain first, then a tab
character (spaces may also be OK) and then the host. So for example I
have a machine on my network called affinity, and so in the hubbed_hosts
file on the machine I am sitting in front of now, I have two lines, one
saying "affinity.localaffinity.local", and the other saying
"affinityaffinity.local" (no quotes in the file). This tells the
local exim installation that any email address with @affinity.local as
the domain should be forwarded on to a machine called affinity.local,
and any mail with @affinity as the domain should be forwarded on to a
machine called affinity.local. Exim4 will then say "Connect to
affinity.local!" with no attempt to translate that into an IP address,
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
affinity will wake up and co-operate to deliver the mail.


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be fine
alone to make a entry in /etc/hosts for the machines i want to send mail to
(I do not operate a dedicated DNS server).
This is something i dont really understand...


I'd suggest you try it and look at the logs.



I will try that out, exim has a pretty nice logging format i think ;)

Greets

mo

Re: Configuring Exim for mail delivery

[mo]

I'll assume you have a home network and are trying to connect to send
mails between machines on that network, and additionally be able to send
email to domains outside your network.


That is right ;)


I'm also assuming that you don't have specific domains for your own
machines, so that when you send mail outside you want to use an email
provider such as gmail, or hover, etc.


Also true ;)



I just figured out how to get this working myself a week or two back, so
it's fresh in my mind. The key trick is the use of "hubbed hosts".


Did you follow a specific book or guide?


Exim configuration has the concept of "routers" and "transports".
Routers basically decide what to do with a message, and transports do
it. One of the routers configured by default in the Debian exim
configuration is for "hubbed hosts". What this means, is machines
capable of sending and receiving email ("hosts" in exim speak) that are
on the same LAN as this machine (connected by a "hub"). Note that this
"hub" could be your local home network router, and for these purposes
machines on WiFi and machines on a wired LAN would be considered on the
same hub, even though that isn't strictly true. The point is that
network packets can be addressed directly between the machines, they
don't require a router in between.



As far as i do understand this is that only machines which are defined 
as hubbed hosts can be send mail in the local LAN? Or am i 
misunderstanding something here? :)



In Debian, this is achieved with Avahi. This is what allows you, if you
have MachineA and MachineB on your network, to do for example "ping
MachineA.local" from MachineB and expect MachineA.local to be resolved
into an IP address.



I'm not a friend of avahi to be honest, i much rather ignore it :D


In /etc/exim4, create a file owned by root called hubbed_hosts. In the
file, each line maps a "domain" (the part after the @ sign in an email
address) to a "host" (the name of a machine on your network, as it can
be reached from this machine). Put the domain first, then a tab
character (spaces may also be OK) and then the host. So for example I
have a machine on my network called affinity, and so in the hubbed_hosts
file on the machine I am sitting in front of now, I have two lines, one
saying "affinity.localaffinity.local", and the other saying
"affinityaffinity.local" (no quotes in the file). This tells the
local exim installation that any email address with @affinity.local as
the domain should be forwarded on to a machine called affinity.local,
and any mail with @affinity as the domain should be forwarded on to a
machine called affinity.local. Exim4 will then say "Connect to
affinity.local!" with no attempt to translate that into an IP address,
and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to which
exim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on
affinity will wake up and co-operate to deliver the mail.


I just did that and now mailing works flawlessly :D
Just one questions: Why do i need hubbed_host entries? Should it not be 
fine alone to make a entry in /etc/hosts for the machines i want to send 
mail to (I do not operate a dedicated DNS server).

This is something i dont really understand...


If the target email domain is not present in hubbed_hosts, then a
default "smarthost" configuration will fall through the hubbed hosts
router and arrive at the smarthost router, which in my case then tries
to use my mail provider to send a mail to a local machine, which is
doomed to failure because the outside provider cannot see my individual
machines on my local network.

If you really should be using the "internet" configuration, you still
need hubbed_hosts for local mails because whereas the hubbed_hosts
option just leaves it to the local network to figure out what it is
talking about, an internet-configured exim will attempt to find and send
to the target machine. To do so, it will send out a DNS request to
resolve the ip address of the target host. Avahi won't catch this, and
unless you are running a DNS server locally on your network (most people
don't, and many home network routers don't include one) that request
will go out of your network to the DNS server provided by your ISP. That
DNS server, being outside your network, won't be able to resolve your
local machine names and so won't be able to give you back an IP address
to use, unless your target machines are publicly individually visible on
the Internet, which is unlikely if this is a home configuration we are
talking about here.

So the configuration you are after is local domains specified in
hubbed_hosts, and everything else falls through to either a smarthost or
a dns-based attempt to send outside your network.

Hope that helps, let us know if you need more help.


Your explanation helped a lot ;)


Mark




Greets

mo

Re: Configuring Exim for mail delivery

[mo]

Hi Brian :)



Assuming the server hostname is "server".

1. On Main PC use your editor to create /etc/exim4/hubbed_hosts. In it
   put

   server: 192.168.23.200

   in it and restart exim4.

2. Send mail to user@server.

3. You can replace 'server: 192.168.23.200' with 'server: server.local'
   if avahi-daemon is running on both machines.



It worked perfectly
...I just found out that "mail" does not support Maildir format, but 
mutt does fine
I can now send and receive mail from and to my server. Thank you very 
much for your help! (...And for the easy step by step guide )


Thanks again

Greets
mo

Recommendation: Backup system

[mo]

Hi Debian users :)

Information:
Distributor ID: Debian
Description:Debian GNU/Linux 8.6 (jessie)
Release:8.6
Codename:   jessie

As the title say i'm in search for a backup application/system.
Currently i manage my backups with a little script that i wrote... but 
it does not really serve my needs anymore.
I want to be able to make backups on my main PC and also on my server, 
the backups i would then store on my NAS.


Make a long story short:
Have you guys a recommendation for me?
Is there a specific application you use for your backups guys?

Btw: I dont mind configuring or playing around with new applications, 
every recommendation is welcome ;)



Here is my current backup script (Which is run by cron daily):
#!/bin/bash

TO_BACKUP="/home /etc /var/log"
BACKUP_DIR="/var/backup"
BACKUP_ARCHIVE="backup-`date +%d_%m_%Y-%H:%M`.tar"
TAR_OPTIONS='-cpf'

delete_old_backup() {
if [ -f ${BACKUP_DIR}/backup*.tar ]; then
rm -rf $BACKUP_DIR/backup*
fi
}

create_new_backup() {
tar $TAR_OPTIONS ${BACKUP_DIR}/$BACKUP_ARCHIVE $TO_BACKUP
}

main() {
delete_old_backup
create_new_backup
}

main

Greets
mo

Re: Configuring Exim for mail delivery

[mo]

First of all:
Thank you Liam for your help! :)
Thanks for the very nice and long explanation Mark! :)

I think i should elaborate a little more on my setup.. i guess i did not 
make that very clear in the first place, sorry about that.


My network is consisting of the following systems:

Main PC - 192.168.23.11  (Running Debian Jessie)
Server  - 192.168.23.200 (Running Debian Jessie)

The server is always online, the PC is only half of the day on.

What i want to do now is the following:

Sending mail from my Main PC to my Server and also the other way around, 
from the Server to my Main PC.
The Server should also be able to send mail to the "outside" (Meaning to 
other SMTP servers).
The second requirement is optional since i dont own a domain and all 
this is sitting locally at my home. The most important thing for me is 
to send and receive mail from both systems in my home network.

I hope this made my problem a little clearer :)

I'm a little ashamed to say that, but i could not totally follow your 
explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :(


Thanks again for all your help ;)

Greets

mo

Configuring Exim for mail delivery

[mo]

Hi fellow Debian users ;)

First off some information. (both, the pc and the server run Debian Jessie):

Distributor ID: Debian
Description:Debian GNU/Linux 8.6 (jessie)
Release:8.6
Codename:   jessie

Exim:
ii  exim44.84.2-2+deb8u1 
 all  metapackage to ease Exim MTA (v4) installation
ii  exim4-base   4.84.2-2+deb8u1 
 amd64support files for all Exim MTA (v4) packages
ii  exim4-config 4.84.2-2+deb8u1 
 all  configuration for the Exim MTA (v4)
ii  exim4-daemon-light   4.84.2-2+deb8u1 
 amd64lightweight Exim MTA (v4) daemon



I'm currently playing around with exim4... and to be honest i'm a little 
lost here.

I want to do the following configuration:
Send and deliver local mails between my systems. Currently exim is 
configured as a Internet Server (dpkg-reconfigure exim4-config).

In general i kinda ask myself how i would go about doing that?
I want to send mail from my server to my pc and vice versa, also i want 
to be able to send mail "out" to other smtp servers.


Is Exim here the right choice? (I do think so at least)

To be honest i never played with a smtp server before... so my knowledge 
is a bit foggy :P (Don't worry, i know what a MTA, MUA etc is)


Thank you all in advance for your help ;)

Btw: I will of course provide more information if needed ;)

Greets

mo

Systemd problem regarding resource control

[mo]

Hi Debian users :)

Well i'm back again with another problem i absolutely can't figure out. 
First of some information regarding my system and systemd:


mo@srv:~$ systemd --version
systemd 215
+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ 
-SECCOMP -APPARMOR


mo@srv:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 8.5 (jessie)
Release:8.5
Codename:   jessie

The problem is the following:
According to the systemd.resource-control man page it is possible to 
manage the resources of slices, scopes, sockets and mount points. 
However, always when i try to set a property on one of my virtual 
machine slices the changes have no effect at all.. no matter what i try.


The commands will be listed in order:

$ sudo systemctl set-property --runtime machine-qemu"\x2d"ts.scope 
CPUQuota=10%


No reply or error returned, so we should be good, then i type:

$ systemctl show machine-qemu\x2dts.scope | grep CPU
CPUAccounting=yes
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=(null)

As you can see CPUQutoa is _not_ listed here... which is quite strange 
to me. (Since systemctl did not return any error of any kind)


The vm runs under the user "libvirt-qemu" and is started by hand via virsh.

I honestly can't tell what seems to be wrong.
It would be great if any of you guys has a idea what the reason could be.

Thanks in advance :)

Greets

mo

[Solved] Re: A few questions about cgroups in Debian 8 (Jessie)

[mo]

Hello Debian users :)

I have googled a little bit and came to the conclusion that cgroups 
should be managed with systemd. (Thanks to Nicolas George for the 
systemd hint :^) )


For anyone who is interested here is a good guide from RedHat about 
resource management with cgroups and systemd:


PDF:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Resource_Management_Guide/Red_Hat_Enterprise_Linux-7-Resource_Management_Guide-en-US.pdf

Single page html:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Resource_Management_Guide/index.html

Have a nice day guys ;)

best regards

mo

Re: Installing a MINIMAL Mate Desktop How?

[mo]

Hi Richard

I for one always make a minimal install, which means i only install the 
base. (You can select that in tasksel during the installation)


From there on i build the system so to speak myself. Installing xorg 
and the needed video driver, the core package for my DE of choice (which 
currently is gnome) and then i install my display manager of choice (i 
use gdm atm).

After that you either start gdm yourself by doing:
# systemctl enable gdm && systemctl start gdm
or you simply do a reboot... then you should be presented with your 
display manager of choice and you can login to your DE.


About your problem with having to less applications installed with the 
core mate package:

Have a look at the mate-desktop-environment meta package:
https://packages.debian.org/jessie/mate-desktop-environment
There you can see which applications get pulled in, you can select them 
yourself and then you can install the mate-desktop-environment-core 
package and add the software you need.


I hope this helps you

Best regards

mo

Am 11.09.2016 um 13:47 schrieb Richard Owlett:

When Squeeze was the latest I was able to install without any desktop.
I would then do
   apt-get install gnome-session gdm3 gedit gnome-terminal gparted
The result was a nice uncluttered desktop to which I could add what *I*
needed rather than what the proverbial "everybody" should have ;)

According to http://wiki.mate-desktop.org/download#debian I should be
able to do
   apt-get install mate-desktop-environment-core

That is not enough, it leaves me with only a command line.
I have the full Mate desktop on one machine. Using Synaptic on that
machine and using apt-get install  on the other I was able too
identify some missing pieces.

"apt-get install mate-desktop-environment-core" does not install marco,
xorg, xterm, nor lightdm. My brute force diagnostic procedure was to
install each of them in the order listed with a reboot in between to see
if everything worked. It did not. After installing each of the 1st three
I was left at the command line. After installing lightdm I was presented
with a blank screen.

As I have minimal bandwidth available I am installing from purchased
DVD's - currently version 8.0.0 . After the point release later this
month I will obtain the latest.

Has anyone successfully done such a minimal install as I am attempting?
TIA

Re: A few questions about cgroups in Debian 8 (Jessie)

[mo]

I have found a Fedora guide to cgroups (I know this is Debian.. but i 
could really not find anything specific to Debian)
They mention that there is a cgconfig service for systemd.. My problem 
is that i could not find a equivalent service for my Debian system.
Listing all the units with "systemctl list-units" did not show anything 
regarding cgroups specifically... Maybe i'm blind but i don't seem to 
find any information. (Sorry if i totally overlooked something)


Any help would be greatly appreciated.

Thank you all ;)

Re: A few questions about cgroups in Debian 8 (Jessie)

[mo]

Le quintidi 25 fructidor, an CCXXIV, mo a écrit :

Should i even attempt to manage cgroups this way? (Sorry, this must sound
quite "noobish")


Have you checked whether systemd can do the kind of control over users that
you want to? I know it uses cgroups intensively, so perhaps it already has a
nice interface to do exactly what you need.



Hello George :)

I have not yet checked out the functionality systemd provides in that 
manner... I wanted to try to work with cgroups "directly" so to speak.
Thanks for your reply, i will check out the functionality provided by 
systemd!

A few questions about cgroups in Debian 8 (Jessie)

[mo]

Hello fellow Debian users :)

First off, some general information regarding my Debian install:
$ lsb_release -a
Distributor ID: Debian
Description:Debian GNU/Linux 8.5 (jessie)
Release:8.5
Codename:   jessie

Now to my problems:
I'm currently looking into cgroups. (Planning to use them on my server 
to limit resources for my users)
I'm a little confused though.. I have installed the following three 
packages:
ii  cgroup-bin   0.41-6 
 all  control and monitor control groups (transitional package)
ii  cgroup-tools 0.41-6 
 amd64control and monitor control groups (tools)
ii  libcgroup1:amd64 0.41-6 
 amd64control and monitor control groups (library)


..But i don't seem to find the cgconfig.conf file which should be 
located under /etc..

I did however find a example cgconfig.conf:

"/usr/share/doc/cgroup-tools/examples/cgconfig.conf"
(Found in the cgroup-tools package)

My question is if i can simply use the example file for my running 
system, or is there something that i need to tweak/configure to make it 
work?


I sadly also was unable to find much resources about cgroups in Debian. 
Is there maybe something i overlooked?

Can you guys give me a hint?

Should i even attempt to manage cgroups this way? (Sorry, this must 
sound quite "noobish")


Thank you all in advance :)

greets

mo

Re: Repository problem

[J Mo]

I was having some similar problems the other day. It cleared up after 
awhile.




On 05/21/2016 12:00 AM, Hans wrote:

Dear debian-team,

I suppose there is a problem with one of your repos. Please take a look:

  LANG=C aptitude update
.
..
Hit ftp://ftp.de.debian.org/debian stable Release
Get: 2 ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata [1657
kB]
Err ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata
   Hash Sum mismatch
Err ftp://ftp.de.debian.org/debian testing/main DEP-11 64x64 Icons
Fetched 1425 kB in 5s (239 kB/s)
W: Failed to fetch
ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/Components-amd64.yml.xz:
 Hash Sum mismatch
W: Failed to fetch
ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/icons-64x64.tar.gz:
E: Some index files failed to download. They have been ignored, or old ones
used instead.

.


Aptitude is telling me, that the indexfile of 64x64 Icons shall 20,2 TB(!!!)
big, which might cause other problems, too.

You might want to take a look at it.

Happy weekend

Hans

Re: Grub won't install

[J Mo]

That's pretty awesome. Thanks to everyone for the lilo comments.



On 05/19/2016 04:54 PM, Stephen Powell wrote:

On Wed, May 18, 2016, at 14:57, Marc Shapiro wrote:

Lilo definitely still works with current kernels.  I started out using
lilo 17 or 18 years ago and I am still using it now under Jessie and
kernel vmlinuz-3.16.0-4-amd64.


I maintain a LILO web page for the benefit of Debian users here:

http://www.stevesdebianstuff.org/lilo.htm

I use it myself on the latest kernels without difficulty.  Many people believe
that modern UEFI boards don't have a BIOS for forward compatibility anymore.
That may be true in some cases.  But in other cases, the use of the "connected
standby" feature in UEFI, which is a default setting in many cases, has disabled
the Compatibility Support Module (CSM) which provides the BIOS.

LILO is not for everyone, but it is still usable in a surprising number of
situations.  I have a 64-bit machine that is only a couple of years old that
uses it.

Re: Grub won't install

[J Mo]

lilo is ultra-ancient. I don't even know if it works with modern kernels.

Grub is definitely a huge pain in the ass. It gets an F on usability 
from me. I was struggling with it just yesterday while doing a bcache setup.


You didn't say what you were dual booting with. The other OS makes a 
difference.


GPT or MBR partition type?

Are you using a particular HOWTO/doc on your setup?

More info plz.



On 05/17/2016 06:41 PM, Ralph Sanchez wrote:


I'm setting up a dual boot, and installing deb Jessie first. I 
installed it before, no problem. Now, grub won't install :( it just 
tells me it's a fatal error and refuses to install. Will lilo work for 
a dual boot? I've got no idea why it wouldn't work this time

RANT: Virtual filesystems are getting out of control

[J Mo]

Pardon my rant. Feel free to disregard this thread.

The output from these commands are on a freshly installed system.



-->df
Filesystem   1K-blocks   Used  Available Use% Mounted on
udev  16441312  0   16441312   0% /dev
tmpfs  3290364   96683280696   1% /run
/dev/sda2114287812   44945248   63514008  42% /
tmpfs 16451804208   16451596   1% /dev/shm
tmpfs 5120  4   5116   1% /run/lock
tmpfs 16451804  0   16451804   0% /sys/fs/cgroup
tmpfs  3290364  03290364   0% /run/user/116
tmpfs  3290364 123290352   1% /run/user/1000

One out of eight lines are actually disk filesystems. That is 88% 
garbage I didn't want to see.




-->mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=16441312k,nr_inodes=4110328,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3290364k,mode=755)
/dev/sda2 on / type ext4 
(rw,noatime,quota,usrquota,grpquota,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)

tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)

pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)

hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/116 type tmpfs 
(rw,nosuid,nodev,relatime,size=3290364k,mode=700,uid=116,gid=120)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3290364k,mode=700,uid=1000,gid=1000)



1 line out out 27. That's 96% garbage I didn't want to see.

grub freezing on Gigabyte GA-H170N-WIFI (and probably Gigabyte GA-Z170N-WIFI) solved with BIOS update

[J Mo]

This is an FYI post in case anyone googles for it in the future. No need 
to reply.


I recently built a new PC for my Linux desktop and was having strange 
issues with grub2 not working right. Sometimes the keyboard would freeze 
up, and if I tried to edit a boot entry, the cursor and screen output 
would become out of sync with what was happening on the keyboard -- like 
a backlogged buffer.


My motherboard is a Gigabyte GA-H170N-WIFI. The BIOS was the original F3 
which came with the board, so I upgraded to F4C, which is currently the 
most recent BETA BIOS. This seems to have fixed the problems.


Also note that the F3 BIOS seems to crash/reboot if you use the End key 
at bootup to enter the BIOS/UEFI update tool. Use the Del key, enter 
BIOS, and then upgrade from there instead.


Everything else about this motherboard on Linux has been great.

Looking for cheap low-end VPS providers in the USA

[J Mo]

Hello everyone

I am looking for a new low-end VPS provider in the USA. Does anyone have 
any recommendations?


I am dumping one of my old providers soon. It took them 6+ months to 
support Debian 8 and they just don't seem to care about supporting 
Debian in general.


I don't have a preference regarding Xen, KVM, or OpenVZ.

These are tiny low-end VPSes like they advertise at lowendbox.com. 
Unfortunately, this type of hosting tends to attract scammers, carders, 
and lots of trouble for the VPS providers. The result is that the 
industry has a lot of churn and providers come and go pretty quick, 
sometimes taking your VPS down and going dark without any notice. It's 
hard to find a good cheap low-end provider who won't disappear overnight 
or overload their boxes excessively.


My primary concern is reliability, then cost.

Any recommendations from fellow Debian admins would be appreciated.

Thank you in advance

drive network

[ribas mo]

Caros amigos e batalhadores do Debian,

Gostaria de saber se alguem pode me fornecer ou dar uma dica sobre drive da 
intel 8255-base PCI Ethernet Adapter (10/100).
Estou utilizando SO Debian 3.0 r2 , kernel 2.4.18...
Obrigado,
Humberto MOraes


-- 
__
Check out the latest SMS services @ http://www.linuxmail.org 
This allows you to send and receive SMS through your mailbox.


Powered by Outblaze

Re: Erro ao imprimir

[MO Mez]

Olá Guilherme,

Não tenho certeza sobre o que está acontecendo.
Vou apenas dar algumas sugestões:
Por acaso você tem algum tipo de configuração
especial na BIOS para a sua porta paralela? Veja que
o sistema está acusando um IRQ 7 para uma porta 
paralela, o que não é normal. Portas paralelas não
são interrupt driven, trabalham por polling. No seu
caso, pode ser que você tenha ou alguma configuração
especial ou algum tipo de hardware especial. Neste
caso, procure por informações na documentação do seu
kernel como habilitar interrupções para portas 
paralelas. O meu kernel já é o 2.4 e não tenho os
fontes do 2.2 aqui para verificar.
Eventualmente, o que você vai precisar fazer é
executar um comando do tipo:
# echo 1  /proc/algum_arquivo_config_parport
Ou seja, habilitar a comunicação com a porta
utilizando interrupções. Procure algo que faça sentido
no /proc e veja se funciona.
Espero ter ajudado!



--- Guilherme Oliveira [EMAIL PROTECTED] wrote:
 Boas !
 
 Tenho mais uma dúvida :)) de iniciante de Debian que
 não consigo satisfazer nos docs'/faq's.
 
 Penso que me falta apenas colocar a minha HP670C a
 imprimir.
 
 É assim, instalei o magicfilter, configurei e até
 redireciono texto para o /dev/lp0 !
 
 Ao fazer lpr de qualquer ficheiro, dá-me sempre este
 erro na minha consola:
 
   parport0: detected irq 7; use procfs to enable
 interrupt-driven operation.
 
 Tentei pocurar no /proc alguma coisa sobre esta
 indicação e não encontro.
 
 Vou ver aos log's e diz tb isto:
 
   Oct  9 00:53:19 varpa login[181]: ROOT LOGIN on
 `tty2'
   Oct  9 00:53:31 varpa kernel: parport0: PC-style at
 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2]
   Oct  9 00:53:31 varpa kernel: parport0: detected
 irq 7; use procfs to enable interrupt-driven
 operation.
   Oct  9 00:53:32 varpa kernel: parport_probe:
 succeeded
   Oct  9 00:53:32 varpa kernel: parport0:
 Unspecified, Unknown vendor Unknown device
   Oct  9 00:53:32 varpa kernel: lp0: using parport0
 (polling).
   Oct  9 00:53:33 varpa lpd[192]: lp: filter 'f'
 terminated (termsig=13)
   Oct  9 00:53:33 varpa lpd[192]: lp: job could not
 be printed (cfA011varpa)
 
 Falha de permissões, penso não ser já que tava como
 root. Impressora não é pois funciona em windows
 e não é um winprinter 
 
 Ideias ?
 
 Ajudem-me, pois tenho quase o meu Debian 2.2 num
 brinquinho ;)
 
 Obrigado.
 -- 
 mailto:[EMAIL PROTECTED] ||
 http://www.nortenet.pt/~guilherme
 on the net no one knows your a dog #
 # Copyright (c) 1983 Regents of the University of
 California.
 # All rights reserved.
 #
 # Redistribution and use in source and binary forms
 are permitted
 # provided that this notice is preserved and that
 due credit is given
 # to the University of California at Berkeley. The
 name of the University
 # may not be used to endorse or promote products
 derived from this
 # software without specific prior written
 permission. This software
 # is provided ``as is'' without express or implied
 warranty.
 #
 # @(#)etc.printcap5.2 (Berkeley) 5/5/88
 #
 # This file was generated by
 /usr/sbin/magicfilterconfig.
 #
 lp|hp670c|HP Deskjet 670C:\
   :lp=/dev/lp0:sd=/var/spool/lpd/hp670c:\
   :sh:pw#80:pl#72:px#1440:mx#0:\
   :if=/etc/magicfilter/dj690c-low-filter:\
   :af=/var/log/lp-acct:lf=/var/log/lp-errs:
 


__
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

Re: Problemas com relay no Exim

[MO Mez]

Olá Gleydson,


--- Gleydson Mazioli da Silva
[EMAIL PROTECTED] wrote:
 Oi,
 
 Estou tendo problemas com a atualização do smail
 para o exim em 
 uma rede onde as máquinas possuem o endereço
 192.168.0.0/24 e o 
 exim está configurado na máquina 192.168.0.10. 
 
 O que acontece é que as máquinas da rede não estão
 conseguindo 
 usar o servidor SMTP do exim para a entrega de
 mensagens ao 
 destinatário (isso antes era feito sem problemas com
 o smail). 
 A máquina que possui o exim consegue fazer o relay
 de e-mails 
 normalmente. 
 
 A linha host_accept_relay está ajustada para todos
 os endereços (*) e 
 a host_reject para aceitar somente mensagens de
 Localhost e da 
 rede 192.168.0.0/24. 

se você fez o que está escrito na linha acima, está
exatamente o contrário do que deveria ser:

a linha host_accept_relay deve conter, no seu caso:

host_accept_relay = localhost:192.168.0.0/24


a linha host_reject seria onde você qualifica os 
domínios para os quais __não__ quer fazer relay de
emails.

ou seja, no seu caso, basta colocar a linha 
host_accept_relay, tomando o cuidado de usar : como
separador de campos!

verifique também se o hosts.deny e o hosts.allow estão
configurados para aceitar conexões das máquinas
locais.

Abraços e ETA,


Mário,

__
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

$9.95/ mo web hosting

[$9 . 95/mo web hosting]

Sir:

I noticed your website and am simply offering you what could be a much better 
deal on your web hosting...  If you think you might be interested, go to our 
site:

http://www.buoinet.net

see what we have to offer... Our hosting plans start at $9.95...   Thanks again 
for your time - you wont be getting any more email from us unless 
you email us requesting more information.   If you represent a web design firm, 
we offer bulk discounting as well.


Very Truly Yours
-Mike Carlson
www.buoinet.net



This message is sent in compliance of the new e-mail bill: SECTION 301. Per 
Section 
301, Paragraph (a)(2)(C) of S. 1618, 
http://www.senate.gov/~murkowski/commercialemail/S771index.html 
Further transmissions to you by the sender of this email may be stopped at no 
cost to you by sending a reply to this email address with the word remove in 
the subject line.

Re: Imposto de Renda no Wine

[MO Mez]

Ola Paulo,

A url da Receita Federal eh:

http://www.receita.fazenda.gov.br


Voce esta utilizando o potato ou slink?
Espero boas noticias!
Abracos,


=
[]s,
Mario O. de Menezes
http://www.geocities.com/modemene
http://www.revistalinux.com.br

__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

PnP soundcard overrides conventional card

[Mo Oishi]

I've just installed isapnptools.  It works great on my PnP soundblaster
clone. The one problem is that now I can't use my non-PnP midi card. The
midi card just happens to sit at the same irq as the soundcard (which has
really corny midi emulation). Is there some way to get my midi card to
live happily with my soundcard? 

Mo

On Tue, 6 May 1997, Tim Sailer wrote:

 In your email to me, Christopher Ray Martin, you wrote:
  
  
  Is there a debian package which will allow me to configure my PnP ISA
  2Mbps tape drive accelerator card?
 
 Take a look at the 'isapnptools' package from Bo
 
 Tim
 
 -- 
  (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - 
 http://www.buoy.com/~tps
They tell me my job is easy... anyone can do it.
 Why doesn't anyone else want it?
   -- me
 ** Disclaimer: My views/comments/beliefs, as strange as they are, are my 
 own.**
 
 
 --
 TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
 [EMAIL PROTECTED] . 
 Trouble?  e-mail to [EMAIL PROTECTED] .
 
 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: NEED info concerning US Robotics modem

[Mo Oishi]

I've got the internal version of that modem. It works fine under debian
linux.

Mo


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

bad superblock (fwd)

[Mo Oishi]

Hello, all,

I'm having unexplained problems booting my debian box. I shutdown linux
yesterday morning and booted win 95 from /dev/hda1. When I tried to reboot
linux (/dev/hda2) in the evening using lilo, I got nothing but the
starting linux statement. I used the base rsc1440.bin disk (my boot
floppy didn't work) to boot linux. I ran e2fsck /dev/hda2. I got:

...
e2fsck: Bad magic number in superblock while trying to open /dev/hda2. 

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem, then the superblock is corrupt and you might trying running
e2fsck with an alternative superblock: 
e2fsck -b 8193 device

This last suggestion gives:
Attempts to read block from filesystem resulted in short read while trying
to open /dev/hda2...

cfdisk tells me that this still is a legit filesystem/partition.

My box is a pentium 150 pci with pnp bios, 2 gig HD and 32 MB memory. 
/dev/hda1 = msdos
/dev/hda2 = ext2
/dev/hda3 = linux swap

Advice, kind people?

Mo




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]