Re: sysvinit - call for testers of 2.88dsf-59.9

[Ian Jackson]

Ian Jackson writes ("sysvinit - call for testers of 2.88dsf-59.9"):
> If you are running testing (stretch) and using sysvinit, I'd
> appreciate it if you could install the new sysvinit packages from
> unstable (sid).

Thanks to those who replies already.  I have had favourable test
reports for usrmerge[1] and a normal install with / and /usr on the
same filesystem, including some new stretch installs.

[1] usrmerge means binaries and libraries have been moved to /usr and
  /{bin,lib,sbin} are symlinks to /usr/{bin,lib,sbin} respectively.

I'm still lacking a test report for a system where /usr is a separate
filesystem, if anyone has one running stretch that they are willing to
test this package on.  (See my previous email for the list of binary
packages and versions etc.)

Thanks,
Ian.

Re: No. ,,l

[Tony Baldwin]

Cat?
My cat once kept #tcl on freenode entertained while I was making a 
sandwich. The channel enjoyed him (Flaquito RIP) so much, when I got 
back on and explained the garbled gibberish, they suggested I go take a 
bath and let him have the computer for a while...


On 02/13/2017 07:27 PM, Imara Ramirez wrote:

Vggbbhb

Sent from my iPad



--
http://tonybaldwin.me
all tony, all the time

No. ,,l

[Imara Ramirez]

Vggbbhb

Sent from my iPad

Re: [FOLLOW-UP] Re: Having scanned set of installation DVDs...

[songbird]

Richard Owlett wrote:
> On 02/12/2017 09:26 AM, songbird wrote:
>> Richard Owlett wrote:
>>> songbird wrote:
>> ...
   years ago i copied from dvds to a subdirectory
 on an external USB drive.  it worked ok, but i did
 have to tell in the apt sources list that i was
 using a file and not a dvd.

   i am pretty sure i used a "cp -r" to do it too...

   fwiw,  :)
>>>
>>> I have that on my TO-DO list.
>>> There's an additional step - creating packages.gz so apt related tools look 
>>> at
>>> it as a large DVD.
>>
>>   the package list is in there, should be no need
>> to regenerate it.
>>
>>   if your apt sources list points to the right
>> directory (use file not cd or dvd in the list)
>> it should find it and use it.
>
> We have different goals/assumptions.
> You are creating a directory for each CD/DVD.
> I have a situation in mind that mounting more than one directory would be a 
> problem. Thus my solution for Jessie would take 13 DVDs and create one 
> humongous 
> pseudo-DVD.
> P.S. I've never been described as "normal", much less "typical" ;/

  but you do understand that i only had them copied
to one device, one mount point, one directory which
contained them all, but apt doesn't care, it scans
them all the one time when you update and then they
are available just like any other repository.

  really, i think you are doing more work than is
needed here for no real gain in anything that i
can determine.

  mounting the device as i did caused absolutely
no problems that i recall.

  each disk was an entry in the apt sources list,
but if i didn't need that device (it was an
external USB device so not always turned on for
use) i just commented out those lines in the apt
sources list.


  songbird

Re: An Odd File Name

[Patrick Bartek]

On Mon, 13 Feb 2017 11:06:24 -0600 "Martin McCormick"
 wrote:

>   I downloaded a file from a site using lynx and the file
> name is "InstallingGRFromSource#Using-the-build-gnuradio-script.gz"
> Actually, the double quotes are here for clarity but the name is
> as it appears including the # sign.  Ls sees it and rm -i would
> remove it if I let it but if I do:
> 
> gunzip InstallingGRFromSource#Using-the-build-gnuradio-script.gz
> 
> or
> 
> ls InstallingGRFromSource#Using-the-build-gnuradio-script.gz
> 
> bash can't find/see the file.
> 
> I am a bit embarrassed to ask this question because I have been
> using unix for about 28 years and am well aware that certain
> [snip]

Is the file in your username's PATH?  Or enter full path to file.  Or
just CD to where the file is, maybe, preceeding the filename with ./

B

Kernel Update on Stretch

[Daniel Bareiro]

Hi all!

Some time ago I read that Linux 4.x incorporates the feature to be
updated without requiring a restart of the operating system.

Since stretch incorporates a kernel of the 4.x series, this would imply
that we can update the kernel package and avoid reboots?


Thanks in advance.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: OT: Read-Only NFS-mounted Debian System for Library Kiosk PCs, using KACE K2000 as PXE?

[Kent West]

On 12/05/2016 09:44 AM, Kent West wrote:
I've been tasked with replacing a few library kiosks in a university 
library. They currently run Windows with a kiosk-product named 
SiteKiosk to restrict them to just a few apps (web-browser, printing, 
MS-Word) and prevent tampering. It works pretty well.


But I have a philosophical distaste of Windows; I'm not in favor of 
maintaining more third-party products (SiteKiosk) than is necessary; I 
like the idea of disk-less workstations; I like the idea of 
configure-in-one-place-for-all-machines; and I just like Debian; and I 
think it might serve as a foot-hold in the door to converting other 
Windows PCs across campus to Debian.


But I have no real experience in PXE booting, and only vaguely 
understand the depths of Debian booting, and know very little about 
setting up a KACE (now Quest) K2000 Systems Deployment Appliance for 
network-booting a computer, and much less for booting a Linux image, 
and much less for pointing those Linux boxes to remote read-only NFS 
mounted systems (and I know little NFS at all).


So, does anyone have enough experience with this combination of stuff, 
and willingness, to guide me in this process? Or even subsets of the 
process that might get me closer to the whole? I can't help but think 
there might be others in a similar situation that would benefit from 
finding this process detailed on-line.




I haven't gotten the process entirely figured out, but I'm getting 
pretty close, and in case some other Quest/KACE K2000 Debianista wants 
to do this, I thought I'd document it:


*Setting up a KACE Boot Environment (KBE) That Boots memtest86*
*(that will eventually boot a Debian read-only NFS-mounted kiosk)*

*Introductory Notes*
This document assumes you have a working K2000 ("K2") box, and you're an 
administrator thereof.


The version with which I'm working is Quest/Dell KACE K2000 version 4.0.695.

I normally prefer to access the K2's web interface from my Linux box, 
but for most of the following to work, I'm using a Windows 10 PC 
(actually, a VirtualBox setup on my Debian GNU/Linux box; if it matters, 
my Win10 Enterprise Edition has been updated to the Anniversary 
("Version 1607") version).


*Do This From a Windows Computer*
Because the Quest/KACE tools are Windows-centric, you have to have a 
Windows computer. So I used VirtualBox on my Debian computer, but I 
think almost any recent WIndows computer should work for you.


*Get the Windows Assessment and Deployment Kit (ADK)*
On your Windows computer, web-browse tomicrosoft.com 
, then Support, and search for “ADK 10”. (If you 
have Windows 7 or 8, etc, you’ll need the ADK 7 or 8, etc.) Since my 
Windows Enterprise virtual machine had been upgraded to the 1607 
“Anniversary Version”, I had to get the 1607 version of the ADK.


*Get Media Manager*
On your Windows computer, log into your K2, and browse to Library/Source 
Media/Choose Action/Download Media Manager


Download for Windows

Save the file and run it, to install the Quest / KACE Media Manager onto 
your Windows computer.


*Get KBE Manipulator (KBEM)*
Go toquest.com / Support. You'll likely have to log 
into their support site (which means creating an account if you haven't 
already done so. Why?!!)


In the Search field for the web site (I couldn't find it 
browsing/searching the Download Software section), search for "kbe 
manipulator". Find a link that looks promising for your setup. In my 
case, it's the link that says "KBE Manipulator 3.7.1.25".


Add to Downloads / Download Now. Run the installer. I was presented with 
four checkboxes; I only left "Launch KBE Manipulator" checked.


I was given the offer to download an upgrade. I downloaded the upgrade, 
and  then repeated the above step, to finish installing the KBE 
Manipulator (KBEM) onto my Windows computer.


*Get the memtest86.iso*
On your Windows computer, search for and download memtest86. Make sure 
to get it from the officialmemtest86.com site, so 
you don’t have to worry about malware/trojans/etc. Unzip the file if 
necessary so that it's just a .ISO file.


*Use the KBEM to Create a KBE That Boots memtest86 (or other)*
When you start the KBE Manipulator on your Windows computer, you'll be 
brought to a configuration panel, which configures the KBE you’re 
building. Normally it'll build either a 32-bit or a 64-bit Windows KBE, 
but when you select an .ISO from the File menu, you get that ISO's OS 
instead of a Windows OS. For a regular Windows KBE, the process might 
take an hour or so; for something small like memtest86, half a minute or so.


The IP address is the IP address of your K2000 box; the Samba password 
should be the password in your K2000's Samba share control panel 
setting; the name to call the KBE is whatever name you want to show up 
in your K2's Deployments/Boot Environments listing. I called my KBE 
"memtest86", and made sure to select File / Choose an 

MPEG-TS : édition de fichier vidéo TNT HD.

[Randy11]

Bonjour,

Je vous propose un sujet pour les personnes intéressées par les
formats vidéo et le montage vidéo.

J'enregistre les émissions de la télévision transmises en TNT HD,
comme celles d'ARTE, les fichiers sont au format MPEG-TS et
je souhaiterais pouvoir les éditer : couper les minutes avant et
après la partie intéressante, supprimer les publicités.

Pour les enregistrement, j'utilise une clef USB Sundtek
MediaPro III et TvHeadend. TvHeadend peut aussi
sauvegarder au format MKV, mais cela ne réglera pas la
question des enregistrements existants.

Avec la TNT en HD et des émissions multi-pistes audio comme
ARTE, les choses sont un peu compliquées, du moins pour moi.
J'ai déjà essayé tout ce qui était possible il y a plus d'un an, mais
soit le format HD n'était pas supporté soit le il y avait
désynchronisation entre le son et l'image.

Je ne veux pas nécessairement garder le format d'origine, mais
j'aimerais garder plusieurs canaux audio.

Un essai aujourd'hui avec VLC et la conversion du fichier en
H-264+MP4 fait apparaître des problèmes de décodage à des
passages de la vidéo.

En pièce jointe, si elles passent, le résultat de "mediainfo" sur deux
fichiers issus de la TNT HD et ci-dessous le résultat sur le fichier
MPEG-TS.

Quelqu'un a-t-il une ou plusieurs solutions à me proposer pour
l'édition de fichier MPEG-TS comme celui décortiqué par
"mediainfo" ?


Merci beaucoup.


À bientôt

Randy11.

> mediainfo Arte-Xenius.2016-07-04.08-30.ts
General
ID   : 4 (0x4)
Complete name: Arte-Xenius.2016-07-04.08-30.ts
Format   : MPEG-TS
File size: 1.35 GiB
Duration : 39mn 25s
Overall bit rate mode: Variable
Overall bit rate : 4 893 Kbps

Video
ID   : 320 (0x140)
Menu ID  : 1031 (0x407)
Format   : AVC
Format/Info  : Advanced Video Codec
Format profile   : High@L4.0
Format settings, CABAC   : Yes
Format settings, ReFrames: 4 frames
Format settings, GOP : M=8, N=24
Codec ID : 27
Duration : 39mn 24s
Bit rate : 4 199 Kbps
Width: 1 920 pixels
Height   : 1 080 pixels
Display aspect ratio : 16:9
Frame rate   : 25.000 fps
Standard : Component
Color space  : YUV
Chroma subsampling   : 4:2:0
Bit depth: 8 bits
Scan type: MBAFF
Bits/(Pixel*Frame)   : 0.081
Stream size  : 1.16 GiB (86%)
Color primaries  : BT.709
Transfer characteristics : BT.709
Matrix coefficients  : BT.709

Audio #1
ID   : 330 (0x14A)
Menu ID  : 1031 (0x407)
Format   : E-AC-3
Format/Info  : Audio Coding 3
Format settings, Endianness  : Big
Codec ID : 6
Duration : 39mn 25s
Bit rate mode: Constant
Bit rate : 128 Kbps
Channel(s)   : 2 channels
Channel positions: Front: L R
Sampling rate: 48.0 KHz
Compression mode : Lossy
Delay relative to video  : -657ms
Stream size  : 36.1 MiB (3%)
Language : French

Audio #2
ID   : 331 (0x14B)
Menu ID  : 1031 (0x407)
Format   : E-AC-3
Format/Info  : Audio Coding 3
Format settings, Endianness  : Big
Codec ID : 6
Duration : 39mn 25s
Bit rate mode: Constant
Bit rate : 96.0 Kbps
Channel(s)   : 2 channels
Channel positions: Front: L R
Sampling rate: 48.0 KHz
Compression mode : Lossy
Delay relative to video  : -625ms
Stream size  : 27.1 MiB (2%)
Language : qaa

Audio #3
ID   : 332 (0x14C)
Menu ID  : 1031 (0x407)
Format

Re: (deb-cat) Administracio visual amb Mate

[Blackhold]

Hola,
Jo m'hi he trobat també varis cops i ja sé que just instal.lar debian amb
mate toca instal·lar el mozo i el printer-config (o algo així).

Fa uns mesos vaig provar el mate en testing i petava més que una escopeta
de fira i tinc por del funcionament del mateix quan tinguem la nova debian
:s

He de tornar-ho a provar i notificar dels errors quam tingui un xic més de
temps, que vaig sempre amb un coet al cul!!!

El dia 13 febr. 2017 8:51 p. m., "Narcis Garcia"  va
escriure:

> Estic fent instal·lacions de Debian amb l'escriptori Mate i, a
> diferència d'Ubuntu-Mate, no es preinstal·len les eines d'administració
> (GUI) d'impressores, comptes d'usuari i alguna cosa més quan hom tria la
> tasca Mate durant la instal·lació del sistema operatiu.
> De moment estic posant aplicatiu de Gnome per suplir aquesta mancança,
> però no s'integra al 100%.
>
> Com és això? Faig alguna cosa malament?
>
> --
>
>
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
>
>

(deb-cat) Administracio visual amb Mate

[Narcis Garcia]

Estic fent instal·lacions de Debian amb l'escriptori Mate i, a
diferència d'Ubuntu-Mate, no es preinstal·len les eines d'administració
(GUI) d'impressores, comptes d'usuari i alguna cosa més quan hom tria la
tasca Mate durant la instal·lació del sistema operatiu.
De moment estic posant aplicatiu de Gnome per suplir aquesta mancança,
però no s'integra al 100%.

Com és això? Faig alguna cosa malament?

-- 


__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.

Re: Chromium: all apps gone, reinstalling fails

[Markus Grunwald]

Hello Sven,

> Quoting from News.Debian of chromium:
>
> chromium-browser (55.0.2883.75-4) unstable; urgency=medium
>
>   * External extensions are now disabled by default.

> My advise: please install apt-listchanges if you follow Testing/Unstable
> to get notifications of such important changes.

Many thanks, Svan! I'll do this right now.

--
Markus Grunwald
http://www.the-grue.de/~markus/markus_grunwald.gpg

Re: An Odd File Name

[David Wright]

On Mon 13 Feb 2017 at 11:06:24 (-0600), Martin McCormick wrote:
>   I downloaded a file from a site using lynx and the file
> name is "InstallingGRFromSource#Using-the-build-gnuradio-script.gz"
> Actually, the double quotes are here for clarity but the name is
> as it appears including the # sign.  Ls sees it and rm -i would
> remove it if I let it but if I do:
> 
> gunzip InstallingGRFromSource#Using-the-build-gnuradio-script.gz
> 
> or
> 
> ls InstallingGRFromSource#Using-the-build-gnuradio-script.gz
> 
> bash can't find/see the file.
> 
> I am a bit embarrassed to ask this question because I have been
> using unix for about 28 years and am well aware that certain
> characters in file names such as blank spaces cause problems but
> these are usually negated by either putting the whole file name
> in double quotes or by escaping the troublesome character with a \ or 
> backslash.
> 
>   While there is no whitespace character anywhere in the
> name, there are several dashes and a # sign which is probably the
> worst offender. I tried escaping the # symbol with a backslash
> with no change and then I tried escaping all the dashes with
> backslash characters as in \- and \# but commands referencing the
> file by name all come up short. I also did try the whole name in
> both single and double quotes.
> 
>   This is a teachable moment but I am not sure what else to
> do other than remove all the other files in the directory and
> then gunzip * which might work but that's sure going about things
> the weird way rather than systematically. I did list the file by
> using ls and piped that in to a file which I then removed all
> names but the problem one and then used od -tx1 on the file name,
> piping that to less so I could see if there were any 8-bit
> characters or some other oddity, but the name was composed
> only of the letters you see.
> 
>   By the way, gunzip does not have a -i flag like rm but
> that thought crossed my mind.
> 
>   Since the name is long, I did make a short file with the
> command such as ls or gunzip and the file name and then I typed
> 
> source thatfile
> 
> or sh thatfile so I did not type the command directly from the
> command prompt but normally the source command is as if you did
> type on the keyboard from the prompt.
> 
>   Any ideas for matching that name?

You could try partial wildcarding, like:

$ ls *tall*build*

and if you succeed, then do type:

$ echo *tall*build* | od --endian=big -t x1

and try to reveal what the filename actually is by hex dumping it.

If you fail to match it, then you need a blunderbuss:

$ ls -1 | od --endian=big -t x1 | less

Now search for 0a (by typing /0a at less's prompt)
and, in the company of short filenames, your long one
will be delimited by two widely spaced 0a strings.

Here is what you're checking for:

$ echo ' InstallingGRFromSource#Using-the-build-gnuradio-script.gz' | od 
--endian=big -t x1
000 20 49 6e 73 74 61 6c 6c 69 6e 67 47 52 46 72 6f
020 6d 53 6f 75 72 63 65 23 55 73 69 6e 67 2d 74 68
040 65 2d 62 75 69 6c 64 2d 67 6e 75 72 61 64 69 6f
060 2d 73 63 72 69 70 74 2e 67 7a 0a
073

Perhaps there's something embedded in the name that doesn't display.

Cheers,
David.

Re: An Odd File Name

[Jude DaShiell]

I only remember part of this unfortunately.  When a situation like this 
happens you got to get the file's inode number then reference it using 
that inode number and perhaps open it.  This topic was covered shortly 
in the Unix class I took back in 1990.  How to do the rest of it I think 
is done with find but don't quote me on that.


On Mon, 13 Feb 2017, Martin McCormick wrote:


Date: Mon, 13 Feb 2017 12:06:24
From: Martin McCormick 
To: debian-user@lists.debian.org
Subject: An Odd File Name
Resent-Date: Mon, 13 Feb 2017 17:06:46 + (UTC)
Resent-From: debian-user@lists.debian.org

I downloaded a file from a site using lynx and the file
name is "InstallingGRFromSource#Using-the-build-gnuradio-script.gz"
Actually, the double quotes are here for clarity but the name is
as it appears including the # sign.  Ls sees it and rm -i would
remove it if I let it but if I do:

gunzip InstallingGRFromSource#Using-the-build-gnuradio-script.gz

or

ls InstallingGRFromSource#Using-the-build-gnuradio-script.gz

bash can't find/see the file.

I am a bit embarrassed to ask this question because I have been
using unix for about 28 years and am well aware that certain
characters in file names such as blank spaces cause problems but
these are usually negated by either putting the whole file name
in double quotes or by escaping the troublesome character with a \ or backslash.

While there is no whitespace character anywhere in the
name, there are several dashes and a # sign which is probably the
worst offender. I tried escaping the # symbol with a backslash
with no change and then I tried escaping all the dashes with
backslash characters as in \- and \# but commands referencing the
file by name all come up short. I also did try the whole name in
both single and double quotes.

This is a teachable moment but I am not sure what else to
do other than remove all the other files in the directory and
then gunzip * which might work but that's sure going about things
the weird way rather than systematically. I did list the file by
using ls and piped that in to a file which I then removed all
names but the problem one and then used od -tx1 on the file name,
piping that to less so I could see if there were any 8-bit
characters or some other oddity, but the name was composed
only of the letters you see.

By the way, gunzip does not have a -i flag like rm but
that thought crossed my mind.

Since the name is long, I did make a short file with the
command such as ls or gunzip and the file name and then I typed

source thatfile

or sh thatfile so I did not type the command directly from the
command prompt but normally the source command is as if you did
type on the keyboard from the prompt.

Any ideas for matching that name?

Thank you.

Martin McCormick WB5AGZ




--

Re: An Odd File Name

[Martin McCormick]

First, thank you to both responders. Next, I really
goofed. I forgot that gunzip normally removes the .gz file when
it runs so what I had in place of the .gz file was

InstallingGRFromSource#Using-the-build-gnuradio-script

without the extension. I didn't even miss it when I did rm -i *
so I was thinking nothing had happened.

Some days, some of us are just absentminded. I always
feel really bad if that causes other people to waste their time.
The file name actually needed no specialtreatment at all and
gunzip just worked.

Again, thank you.

Martin

Re: An Odd File Name

[John Darrah]

On 2/13/2017 9:09 AM, Martin McCormick wrote:

gunzip InstallingGRFromSource#Using-the-build-gnuradio-script.gz


Just quote the filename like this:

gunzip 'InstallingGRFromSource#Using-the-build-gnuradio-script.gz'

-- john

Re: An Odd File Name

[Greg Wooledge]

On Mon, Feb 13, 2017 at 11:06:24AM -0600, Martin McCormick wrote:
>   I downloaded a file from a site using lynx and the file
> name is "InstallingGRFromSource#Using-the-build-gnuradio-script.gz"
> Actually, the double quotes are here for clarity but the name is
> as it appears including the # sign.  Ls sees it and rm -i would
> remove it if I let it but if I do:
> 
> gunzip InstallingGRFromSource#Using-the-build-gnuradio-script.gz
> 
> or
> 
> ls InstallingGRFromSource#Using-the-build-gnuradio-script.gz
> 
> bash can't find/see the file.

The # character is only a comment indicator in bash when it appears
at the start of a word, not in the middle.  That's why ls and rm have
no problem with it.  Therefore bash has no problem with it, because
clearly bash is passing the filename intact to ls and rm.

If gunzip has a problem with it, then I would suggest you simply rename
the file.

An Odd File Name

[Martin McCormick]

I downloaded a file from a site using lynx and the file
name is "InstallingGRFromSource#Using-the-build-gnuradio-script.gz"
Actually, the double quotes are here for clarity but the name is
as it appears including the # sign.  Ls sees it and rm -i would
remove it if I let it but if I do:

gunzip InstallingGRFromSource#Using-the-build-gnuradio-script.gz

or

ls InstallingGRFromSource#Using-the-build-gnuradio-script.gz

bash can't find/see the file.

I am a bit embarrassed to ask this question because I have been
using unix for about 28 years and am well aware that certain
characters in file names such as blank spaces cause problems but
these are usually negated by either putting the whole file name
in double quotes or by escaping the troublesome character with a \ or backslash.

While there is no whitespace character anywhere in the
name, there are several dashes and a # sign which is probably the
worst offender. I tried escaping the # symbol with a backslash
with no change and then I tried escaping all the dashes with
backslash characters as in \- and \# but commands referencing the
file by name all come up short. I also did try the whole name in
both single and double quotes.

This is a teachable moment but I am not sure what else to
do other than remove all the other files in the directory and
then gunzip * which might work but that's sure going about things
the weird way rather than systematically. I did list the file by
using ls and piped that in to a file which I then removed all
names but the problem one and then used od -tx1 on the file name,
piping that to less so I could see if there were any 8-bit
characters or some other oddity, but the name was composed
only of the letters you see.

By the way, gunzip does not have a -i flag like rm but
that thought crossed my mind.

Since the name is long, I did make a short file with the
command such as ls or gunzip and the file name and then I typed

source thatfile

or sh thatfile so I did not type the command directly from the
command prompt but normally the source command is as if you did
type on the keyboard from the prompt.

Any ideas for matching that name?

Thank you.

Martin McCormick WB5AGZ

instalar gnome shell en jessie (latest)

[Darthcoli - Alejandro Izquierdo]

hola, hay una manera "sencilla" de instalar una version superior a la 3.14
de gnome shell en Jessie. (ya no digo la ultima, si acaso una mas moderna)

He buscado en backports y no he encontrado nada.

-- 
-Alejandro Izquierdo-

Re: HELP! Re: How to fix I/O errors? (SOLVED)

[Mark Fletcher]

On Sun, Feb 12, 2017 at 09:36:16PM -0500, Bob Weber wrote:
> I use a program called ossec.  It watches logs of all my linux boxes so I get
> email messages about disk problems.  I also do periodic self tests on all my
> drives controlled by smartd from the  smartmontools package.  I also use a
> package called logwatch which summarizes my logs.   The messages from mdadm 
> and
> smartd are seen by ossec.  When I mess with an array to make it larger and 
> add a
> disk for backup I get the messages in my mailbox about a degraded array.  As 
> I'm
> reading them I am startled until I remember ...Oh I did that!  I have a daily
> cron job that emails the output of "smartctl -a /dev/sdx" for each drive on 
> each
> machine so I can keep a history of the parameters for each drive.
> 

$ apt-file search ossec

sagan-rules: /etc/sagan-rules/ossec.rules

Seems like the only reference to ossec in Jessie is this rules file in 
the Sagan package. Looking at the description for sagan-rules, it seems 
to be along the right lines. But the sagan package is not in Jessie it 
seems. It's in wheezy and in stretch/sid, but not in jessie. Any idea 
what's up with that?

And was ossec packaged, or did you build it from source?

Cheers

Mark

Re: (deb-cat) Gitlab CE

[Narcis Garcia]

__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 13/02/17 a les 13:17, Marcos ha escrit:
> Hola,
> 
> A 2017-02-13 11:26, Narcis Garcia escrigué:
> 
>> Ara veig que demanen 4GiB de memòria RAM i jo només li havia assignat
>> 512MiB.
>> Brutal per un CMS; no pot estar gaire optimitzada una eina que demana
>> això per treballar.
> 
> Bé, categoritzar Gitlab com un CMS, em sembla un pél agossarat.  La
> versió CE que tens instal·lada demana aquestes quantitats de RAM perquè
> no és només l'aplicació: també hi ve el PostgreSQL, el servidor web, ...
> 
> I en quant al què ofereix, doncs home, recursos en demanarà, perquè no
> és només un repositori Git i quatre pàgines per gestionar tickets.
> També té un servei de integració continuada, que compila, executa tests,
> etcètera sobre cada merge request (si es configura per fer-ho).
> 
> Si el que només necessites és un servei de Git amb una interfície web
> bonica, pots provar Gogs[0].
> 
>> Espero que, després d'assignar-li més memòria, em
>> renti la roba i em posi el plat a taula cada dia.
> 
> Potser això no, però compil·lar, executar les proves unitàries i si tot
> va bé, crear una imatge Docker i enviar-la a producció sí ;)
> 
> Salut,
> 
> [0] https://gogs.io/

Interessant el Gogs pel tema de la lleugeresa, però no donen bon exemple
allotjant el seu propi codi font en un servei Git diferent (Github).
Apart d'això, veig que utilitzen peces de tercers, com les «octicons»,
la qual cosa obre les portes al rastreig.

Ara que (potser) ja he fet la feina més feixuga, confio en què és
possible tenir una instància de Gitlab funcional, estable i sense
haver-hi de dedicar moltes atencions.

Re: (deb-cat) Gitlab CE

[Marcos]

Hola,

A 2017-02-13 11:26, Narcis Garcia escrigué:


Ara veig que demanen 4GiB de memòria RAM i jo només li havia assignat
512MiB.
Brutal per un CMS; no pot estar gaire optimitzada una eina que demana
això per treballar.


Bé, categoritzar Gitlab com un CMS, em sembla un pél agossarat.  La
versió CE que tens instal·lada demana aquestes quantitats de RAM perquè
no és només l'aplicació: també hi ve el PostgreSQL, el servidor web, ...

I en quant al què ofereix, doncs home, recursos en demanarà, perquè no
és només un repositori Git i quatre pàgines per gestionar tickets.
També té un servei de integració continuada, que compila, executa tests,
etcètera sobre cada merge request (si es configura per fer-ho).

Si el que només necessites és un servei de Git amb una interfície web
bonica, pots provar Gogs[0].


Espero que, després d'assignar-li més memòria, em
renti la roba i em posi el plat a taula cada dia.


Potser això no, però compil·lar, executar les proves unitàries i si tot
va bé, crear una imatge Docker i enviar-la a producció sí ;)

Salut,

[0] https://gogs.io/
--
Marcos

Re: Instalación UEFI+GPT

[Dixan]

On 12/02/17 19:43, Santi Moreno wrote:

Hola gente,
no acabo de entender UEFI y no soy capaz de encontrar la forma de 
instalar Debian Stretch en UEFI+GPT como único SO en mi portatil. Dual 
con Win10 lo he podido hacer sin problemas pero quiero reinstalar 
Debian y aprovechar todo el disco sin Win10. Se que podría hacerlo 
Legacy+MBR pero no acabo de entender como hacerlo en UEFI+GPT. Alguien 
me puede echar una mano?


Gracias por adelantado.
@santimoreno


Si quieres instalar en modo UEFI debes de arrancar desde la usb en modo 
UEFI en la lista de dispositivos de arranque UEFI:KingstonX o si vas 
a instalar en modo legacy pues usa el nombre Normal de la usb 
KingstonX, Tampoco entiendo mucho del tema, pero siempre me ha 
funcionado así.


Saludos

Re: Instalación UEFI+GPT

[Gonzalo Rivero]

El dom, 12-02-2017 a las 20:43 +0100, Santi Moreno escribió:
> Hola gente,
> no acabo de entender UEFI y no soy capaz de encontrar la forma de
> instalar Debian Stretch en UEFI+GPT como único SO en mi portatil.
> Dual con Win10 lo he podido hacer sin problemas pero quiero
> reinstalar Debian y aprovechar todo el disco sin Win10. Se que podría
> hacerlo Legacy+MBR pero no acabo de entender como hacerlo en
> UEFI+GPT. Alguien me puede echar una mano?
> 
> Gracias por adelantado.
> @santimoreno

en su momento yo instalé la computadorita desde la que envío este mail,
que venía con win8. Todo lo que hice fue hacer un usb con la imagen
netinstall que encontré en el sitio de debian y después dar vueltas por
los menus de configuración de win hasta que logré encontrar como
decirle que arranque desde usb.
Lo único ¿malo? es que perdí la opción de arranque por usb en el
booteo, pero no importa porque ya tengo un SO como la gente, no creo
que necesite reinstalar de cero [*toca madera*]

Re: [hs] MySQL : utf8_general_ci ou utf8_unicode_ci ou utf8mb4_unicode_ci

[Dominique Asselineau]

Eric Degenetais wrote on Sun, Feb 12, 2017 at 09:55:11AM +
> >utf8mb4_general_ci est peut-être >suffisant pour le Français, mais dans
> le >doute,
> >le plus simple est d'utiliser >utf8mb4_unicode_ci
> Bonjour, en fait le français aussi utilise un caractère composé : œ comme
> dans œil ou œuf. Donc (je n'ai pas testé, mais il est probable que les
> approximations de général_ci soient visibles en français.

Justement, avec utf8mb4_general_ci, l'ordre alphabétique n'est pas
correct.  Le œ est rejeté à la fin de l'alphabet.  Le ß semble
toutefois être bien placé.

mb4_unicode_ci semble être plus précis sur l'ordre alphabétique.  Les
ligatures œ et ß sont normalement assimilés à oe et ss et placés en
conséquence.



-- 

Re: (deb-cat) Gitlab CE

[Narcis Garcia]

__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 12/02/17 a les 20:48, Àlex ha escrit:
> El 12/02/17 a las 15:54, Narcis Garcia escribió:
> 
>> He posat en marxa un lloc Git (git.actiu.net) amb l'esmentat programari
>> lliure, i és molt maco però no sembla que vagi molt fi. Per exemple, si
>> cerques projectes dóna algun error. I de vegades triga a respondre, com
>> quan deses alguna cosa via web.
>>
>> La instal·lació està feta amb els paquets de gitlab.com per Debian 8
>> (jessie).
>>
>> Algú té experiència amb aquesta eina i sap el què es pot afinar?
>>
>> Gràcies.
> 
> 
> Hola
> 
> No tinc experiència, però aquí hi ha un tutorial d'instal.lació que fa
> temps tenia pendents de llegir-me:
> 
>   https://www.howtoforge.com/tutorial/how-to-install-gitlab-on-debian-8/
> 
> Potser comparant la teva instal.lació amb la del tutorial trobes alguna
> pista.
> 
> Salutacions
> 
> 
>Àlex
> 

Igual com en Rolan també ho tenia instal·lat via repositori.
Ara veig que demanen 4GiB de memòria RAM i jo només li havia assignat
512MiB.
Brutal per un CMS; no pot estar gaire optimitzada una eina que demana
això per treballar. Espero que, després d'assignar-li més memòria, em
renti la roba i em posi el plat a taula cada dia.

Re: (deb-cat) Gitlab CE

[Narcis Garcia]

Gràcies per la suggerència; ara ho he repassat i estava tot bé (hosts i
DNS).



__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 12/02/17 a les 22:30, Josep Lladonosa ha escrit:
> Que no sigui algun tema de configuració de nom de màquina (/etc/hosts)
> no resoluble en local o dns, o de configuració de dns.
> Algun cop m'he trobat amb coses amb esperes per aquest motiu.
> 
> Josep 
> 
> On 12 Feb 2017 15:54, "Narcis Garcia"  > wrote:
> 
> He posat en marxa un lloc Git (git.actiu.net )
> amb l'esmentat programari
> lliure, i és molt maco però no sembla que vagi molt fi. Per exemple, si
> cerques projectes dóna algun error. I de vegades triga a respondre, com
> quan deses alguna cosa via web.
> 
> La instal·lació està feta amb els paquets de gitlab.com
>  per Debian 8
> (jessie).
> 
> Algú té experiència amb aquesta eina i sap el què es pot afinar?
> 
> Gràcies.
> 
> --
> 
> 
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
> 

RE: DNS hits

[Bonno Bloksma]

Hi Glenn,

>> Actually the current Bind in stable is just a blessing in this respect.
>> It - by default- just allows recursion for localnet, localhost.
>
> This server is still Wheezy. The virtual websites didn't work on Jessie 
> Apache (I have no idea why yet).
> 
>> So if you don't mess with it at all is does the right thing automagically.
> 
>> Most likely if you remove anything you tried to configure in the options it
>> will work just the way you want.
>
> I'd already done what Eduardo suggested in his post (config BIND to allow 
> recursion from only a specified list of IPs), and all was well -- as soon as 
> I tested it properly.
>
> FWIW, I ran dnstop for a while. I saw quite a bit of my own server at first, 
> but over few minutes, its output turned into a list of hits on my domains.
> Almost all from the 52, 54 area (AWS). I don't know, but I assume dnstop is 
> looking at packets before iptables processes them. If not, something is still 
> badly broken.

If you configure BIND to just respond to local requests then dnstop might still 
see the requests coming from other ip numbers, BIND just might not respond to a 
recurvice query.
AFAIK iptables has nothing to do with this. You cannot block dns requests at 
the iptables level as it cannot distinguish between a request for your own 
domain, to which BIND should respond, and a recursive request for another 
domain, which BIND should ignore.

Bonno Bloksma

Question on /proc/acpi/wakeup

[solitone]

Wakeup capable devices are listed in /proc/acpi/wakeup. For example, in my 
sytem I've got:

~
solitone@alan:~$ cat /proc/acpi/wakeup 
Device  S-state   Status   Sysfs node
PEG0  S3*disabled
ECS4*disabled  platform:PNP0C09:00
HDEF  S3*disabled  pci::00:1b.0
RP01  S3*disabled  pci::00:1c.0
RP02  S3*disabled  pci::00:1c.1
RP03  S3*disabled  pci::00:1c.2
ARPT  S4*enabled   pci::03:00.0
RP05  S3*disabled  pci::00:1c.4
RP06  S3*disabled  pci::00:1c.5
SPIT  S3*disabled
XHC1  S3*enabled  pci::00:14.0
ADP1  S4*disabled  platform:ACPI0003:00
LID0  S4*enabled  platform:PNP0C0D:00
~

It is possible to disable devices with e.g. 
solitone@alan:~$ sudo echo XHC1 > /proc/acpi/wakeup

However, when system reboots such settings are lost, and  /proc/acpi/wakeup is 
reset to its original content.

How does this work? What is the thing that resets /proc/acpi/wakeup to its 
standard content? What does this content depend on? What is that determines 
whether a device is enabled or disabled in the first place?

Re: Boot fails after stretch upgrade to linux 4.9.0

[francesco . montanari]

On 2017-02-04 19:26, Francesco Montanari wrote:

To sum up:
- using linux 4.8.0. I notice no problem.
- When I first booted linux 4.9.0, I got a TPM error message that I 
never

  had before. Disabling the security chip from BIOS solved it.
- The system does not boot as it gets stucked after loading some
  service (e.g., network manager).
- It boots in recovery mode, but freezes when passing the lspci
  command. It also freezes if I pass "systemctl reboot"
- Logs show error messages related to acpi, drivers, remount error of
  EXT4 partition (fsck did not find problems), and segfault related to
  gnome-session-f (https://is.gd/fMGaPr).



Comparing various logs of 4.8.0 vs 4.9.0 I didn't spot significant 
differences. As a test, I also tried to install the proprietary nvidia 
drivers and CPU microcode update packages, but things didn't change.


Thanks to an off-list exchange I managed to boot 4.9.0 in normal mode by 
deactivating the discrete graphic card (Nvidia Optimus) from BIOS. The 
integrated card is good enough for me anyway.


Best,
Francesco