Re: cannot rename with mv - SOLVED

[rlharris]

On Tue, January 17, 2017 12:39 am, Reco wrote:

> EBUSY  The  rename  fails  because  oldpath  or newpath is a directory
> that is in use by some process (perhaps as current working directory, or as
> root directory, or because it was open for reading) or is in use by the
> system (for example as mount point), while the system considers this an
> error.

/backup is a directory in / and "lsof | grep /backup" returns nothing.



> So, since nothing is using the directory in your case, this means
> either that /backup is a mounted filesystem, or your root filesystem
> suffers severe damage.

I do not suspect damage of the root filesystem, because the machine was
booted only a few hours ago.

But "cat /etc/mtab" prints the line:

/dev/sdb3 /backup ext4 rw,relativetime,data=ordered 0 0

so you have diagnosed the problem, and I thank you!

RH

Re: cannot rename with mv

[rlharris]

On Mon, January 16, 2017 11:08 pm, David Christensen wrote:
> It's probably a permissions issue.
>
> Please paste this command into a terminal (as any user) and then paste
> the command and output into a reply:
>
> $ ls -d -l / /backup
>
> Have you set ACL's, SELinux, or any such thing?

I am running Debian stable with xfce desktop.  P.S. I have been running
Debian since Potato.

I am not familiar with ACL or SELinux.

rlh@heidi:/$ ls -d -l / /backup
drwxr-xr-x 30 root root 4096 Jan 17 04:18 /
drwxr-xr-x  8 rh  rh  4096 Sep  8  2015 /backup

Again, could the problem possibly be that mv requires in the partition
sufficient free space to hold a copy of backup?

Re: cannot rename with mv

[Reco]

Hi.

On Mon, 16 Jan 2017 22:17:24 -0600
rlhar...@oplink.net wrote:

> I wish to rename the directory "/backup" to "/backup.new".
> 
> / is on a 452G partition with 54% in use.
> / is owned by root.
> /backup is owned by normal user "rh".
> 
> The command "$ mv /backup/ /newbackup/" fails with " cannot move ...
> Permission denied".
> 
> The command "# mv /backup/ /newbackup/" fails with "cannot move ... Device
> or resource busy".
> 
> No application and no terminal window is looking at / or at /backup .
> 
> What am I overlooking?

First case ('rh' user) is a canonical lack of filesystem permissions.
To rename a directory a user should be able to write into parent one
("/" in your case).

Second case ('root' user) is somewhat more interesting. 'mv' invokes
'rename' system call, and rename(2) has this pearl of wisdom to share:

EBUSY  The  rename  fails  because  oldpath  or newpath is a directory
that is in use by some process (perhaps as current working directory,
or as root directory, or because it was open for reading) or is in use
by the system (for example as mount point), while the system considers
this an error.

So, since nothing is using the directory in your case, this means
either that /backup is a mounted filesystem, or your root filesystem
suffers severe damage.

Reco

Re: cannot rename with mv

[David Christensen]

On 01/16/17 20:17, rlhar...@oplink.net wrote:

I wish to rename the directory "/backup" to "/backup.new".

/ is on a 452G partition with 54% in use.
/ is owned by root.
/backup is owned by normal user "rh".

The command "$ mv /backup/ /newbackup/" fails with " cannot move ...
Permission denied".

The command "# mv /backup/ /newbackup/" fails with "cannot move ... Device
or resource busy".

No application and no terminal window is looking at / or at /backup .

What am I overlooking?


It's probably a permissions issue.


Please paste this command into a terminal (as any user) and then paste 
the command and output into a reply:


$ ls -d -l / /backup


Have you set ACL's, SELinux, or any such thing?


David

Re: cannot rename with mv

[rlharris]

On Mon, January 16, 2017 11:23 pm, Doug wrote:

> if /backup is actually in the root directory, you need to su (or sudo) to
> root and then rename the file:
>
> [name@pcname]$ su
> Password:
> [root@pcname name]# mv /backup /newbackup

I did this; it did not work.


> if this doesn't work, try ./ instead of / in each case.

That does not work either.

Re: cannot rename with mv

[Doug]

On 01/16/2017 11:17 PM, rlhar...@oplink.net wrote:

I wish to rename the directory "/backup" to "/backup.new".

/ is on a 452G partition with 54% in use.
/ is owned by root.
/backup is owned by normal user "rh".

The command "$ mv /backup/ /newbackup/" fails with " cannot move ...
Permission denied".

The command "# mv /backup/ /newbackup/" fails with "cannot move ... Device
or resource busy".

No application and no terminal window is looking at / or at /backup .

What am I overlooking?

RH



if /backup is actually in the root directory, you need to su (or sudo) 
to root and then rename the file:


[name@pcname]$ su
Password:
[root@pcname name]# mv /backup /newbackup

if this doesn't work, try ./ instead of / in each case.

good luck


--
Blessed are the peacemakers...for they shall be shot at from both 
sides.--A.M,Greeley

Re: cannot rename with mv

[rlharris]

On Mon, January 16, 2017 11:06 pm, rlhar...@oplink.net wrote:
> On Mon, January 16, 2017 10:45 pm, Armando Cerna wrote:
>
>> You might want to be sure to double verify that fact nothing is
>> accessing that directory using lsof ex: lsof | grep backup
>
>
> lsof indicates no opened files for the directory


Could the problem be that the partition does not have sufficient space for
a copy of the directory to be renamed?  But does renaming a directory
involve copying any of the files or subdirectories?

Re: cannot rename with mv

[rlharris]

On Mon, January 16, 2017 10:45 pm, Armando Cerna wrote:
> You might want to be sure to double verify that fact nothing is
> accessing that directory using lsof ex: lsof | grep backup


lsof indicates no opened files for the directory

Re: cannot rename with mv

[Armando Cerna]

You might want to be sure to double verify that fact nothing is
accessing that directory using lsof ex:
lsof | grep backup



-- 
  Armando Cerna
  arma...@cerna.ca

On Mon, Jan 16, 2017, at 08:17 PM, rlhar...@oplink.net wrote:
> I wish to rename the directory "/backup" to "/backup.new".
> 
> / is on a 452G partition with 54% in use.
> / is owned by root.
> /backup is owned by normal user "rh".
> 
> The command "$ mv /backup/ /newbackup/" fails with " cannot move ...
> Permission denied".
> 
> The command "# mv /backup/ /newbackup/" fails with "cannot move ...
> Device
> or resource busy".
> 
> No application and no terminal window is looking at / or at /backup .
> 
> What am I overlooking?
> 
> RH
> 
> 

cannot rename with mv

[rlharris]

I wish to rename the directory "/backup" to "/backup.new".

/ is on a 452G partition with 54% in use.
/ is owned by root.
/backup is owned by normal user "rh".

The command "$ mv /backup/ /newbackup/" fails with " cannot move ...
Permission denied".

The command "# mv /backup/ /newbackup/" fails with "cannot move ... Device
or resource busy".

No application and no terminal window is looking at / or at /backup .

What am I overlooking?

RH

INFORMACION

[Alvin Abrahan Avila Sanchez]

CNA SEIRED CUBA

SERVICIOS QUE PRESTAMOS

 

 

Alojamiento en cuba

Servicios de comercialización de servicios de informática electrónica 

Servicios de transporte 

Servicios de internet 

 

 

Escribenos para viajar a cuba cm5...@frcuba.cu


Este mensaje le ha llegado mediante el servicio de correo electronico que 
ofrece la Federacion de Radioaficionados de Cuba. La persona que envia este 
correo asume el compromiso de usar el servicio y cumplir con las regulaciones 
establecidas. FRCUBA: https://www.frcuba.cu/

Re: Dell BIOS

[Felix Miata]

Mirko Parthey composed on 2017-01-17 00:36 (UTC+0100):


The BIOS clock could still have the correct time despite a dead battery
because the Linux system gets the time from an NTP server and writes it
to the BIOS clock on shutdown.  The clock then runs on ATX standby power
and will only lose its memory when the power cable is removed. The same
applies to the BIOS settings.


That's the logical expectation, but not the way it always works. Just hours ago 
on a Dell SFF Optiplex 745 I found a dead battery. After installing a new one I 
decided to remove it after first setting the BIOS clock and rebooting. Without 
having removed the power cable, only removing the battery and no other changes, 
on first subsequent boot it reported BIOS settings reset, and sure enough, clock 
was reset to its build date just short of 10 years ago.

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

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

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

Re: intel_pstate vs acpi-cpufreq freq scale

[Julian Brooks]

Dear Luis,

Many thanks for your input and guidance here.

'Have you tried to see if this happens with debian's official kernel?'
Doh! Of course.
Yes I have now, and intel_pstate is active - yay.

Complete newb with any kind of kernel config/tweaking/rebuilding - need to
do some reading-up.

Thanks again,

Julian

On 16 January 2017 at 15:03, Luis Felipe Tabera Alonso 
wrote:

> On lunes, 16 de enero de 2017 1:13:09 (CET) Julian Brooks wrote:
> > Hi all,
>
> Hi Julian,
>
> > Fresh install of Sid, with
> > liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work).
> > Have also installed linrunner's TLP.
>
> Have you tried to see if this happens with debian's official kernel?
>
> > My understanding is that the x230's Ivy Bridge processor should make use
> of
> > intel_pstate for frequency scaling but I can't seem to load the kernel
> > module at boot.
>
> Is it a module? At least on debian kernels, intel_pstate is inside the
> kernel,
> not as a separate module.
>
> $ grep -i pstate config-4.8.0-2-amd64
> CONFIG_X86_INTEL_PSTATE=y
>
> however, on liquorix
>
> $ grep -i pstate config-4.9.0-3.2-liquorix-amd64
> # CONFIG_X86_INTEL_PSTATE is not set
>
> So it seems that liquorix kernel has not compiled intel_pstate. So could
> try
> to recompile it as a module for your running kernel of rebuild liquorix
> kernel
> with intel_pstate support.
>
> Luis
>

Re: Dell BIOS

[Mirko Parthey]

On Mon, Jan 16, 2017 at 11:52:48AM -0600, Martin McCormick wrote:
> change the boot sequence order from floppy-C:-CDROM to
> CDROM-floppy-C: or CDROM-C:-floppy which prevents the hard drive
> from grabbing the boot sequence each time.

There may be a function key that brings up a BIOS boot menu.
For Dell machines, it should be F12. Other candidates are F8 and F11.
Choosing an entry in the menu takes effect exactly once,
then the previous boot order is restored.
This feature might be useful to you if the entries are the same each
time and appear in the same order.

>   I don't think the CMOS batteries are dead because the
> clock still seems to keep time

Changing the battery is certainly worth trying.

The BIOS clock could still have the correct time despite a dead battery
because the Linux system gets the time from an NTP server and writes it
to the BIOS clock on shutdown.  The clock then runs on ATX standby power
and will only lose its memory when the power cable is removed. The same
applies to the BIOS settings.

Regards,
Mirko

Re: Dell BIOS

[John Hasler]

Joe writes:
> The ones I saw were Japanese components in Japanese television
> cameras, many of them broadcast. This was from the mid-90s onwards.

Japanese companies can get suckered by something that looks like a good
deal just like anyone else.

> And silent leakage of copper-dissolving electrolyte can stop things
> working just as well.

Better.  Explosions lead to more lawsuits, though.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Your best source for personal finance knowledge

[SUPERMONEY]

 Your best source for personal finance knowledge 

Re: Dell BIOS

[Joe]

On Mon, 16 Jan 2017 15:54:05 -0600
John Hasler  wrote:

> Joe writes:
> > The electrolyte used in these [Japanese] capacitors  
> 
> They were Chinese knockoffs of a Japanese design.  However there was a
> proprietary trick that the Chinese missed and so they made and sold a
> vast number of caps that turned out to be defective.

The ones I saw were Japanese components in Japanese television cameras,
many of them broadcast. This was from the mid-90s onwards.

> 
> Electrolytics usually have burst membranes intended to prevent them
> from exploding when they evolve gas and they usually work on
> low-voltage ones.  They often work on high-voltage caps too, but
> other times you can get a nice bang.  Big motor starter capacitors
> can be fun that way.

And silent leakage of copper-dissolving electrolyte can stop things
working just as well.

-- 
Joe

Re: Dell BIOS

[John Hasler]

Joe writes:
> The electrolyte used in these [Japanese] capacitors

They were Chinese knockoffs of a Japanese design.  However there was a
proprietary trick that the Chinese missed and so they made and sold a
vast number of caps that turned out to be defective.

Electrolytics usually have burst membranes intended to prevent them from
exploding when they evolve gas and they usually work on low-voltage
ones.  They often work on high-voltage caps too, but other times you can
get a nice bang.  Big motor starter capacitors can be fun that way.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: OpenVPN - Dúvida ao compilar o instalador

[Leandro Henrique Stein]

Boa tarde,

Existe um criador de instaladores o InnoSetup[1] ele tem um Wizards para
criar os instaladores além do uso de uma linguagem específica para que você
possa customizar de acordo com a necessidade.

Acho que para sua necessidade ele vai suprir muito bem.

[1] http://www.jrsoftware.org/isinfo.php


-- 
Leandro Henrique Stein
Analista de Informática
Claro: (41) 9935-9960
Skype: leandro.h.stein
Twitter: @leandrohstein

"Desculpar-se é um sinal de fraqueza. Exceto entre amigos" - Leroy Jethro
Gibbs

Em 16 de jan de 2017 3:28 PM, "Henrique Fagundes" <
henri...@linuxadmin.com.br> escreveu:

Prezados Colegas,

Primeiramente saudações pinguianas a todos.
Estou com uma dúvida e gostaria de saber se alguém pode me ajudar.

Eu tenho um servidor Debian Jessie 8.7 x64 rodando o OpenVPN 2.3.4 em modo
server-clients.

Tudo funciona perfeitamente. Túnel, rotas, etc.

Eu gostaria de saber como posso comilar para os clients um instalador
personalizado para WINDOWS. De modo que, o usuário possa fazer a instalação
do tipo "NEXT, NEXT, FINSH", sem a necessidade de ter que colocar os
arquivos de configurações lá dentro de "C:\Arquivos de
Programas\OpenVPN\Config".

Eu sei que até pode estar parecendo que eu estou querendo, tipo, "enfeitar
o pavão", mas... Acreditem... A grande maioria dos consultores externos
desta empresa onde estou prestando serviços são "enrolados" (pra não dizer
outra coisa), ao ponto de não conseguirem fazer nem isso.

Então, um instalador que entregasse tudo pronto, ajudaria bastante.

Não sei se alguém já teve essa necessidade antes, mas...
Se alguém puder ajudar, ficarei muito grato!

Atenciosamente,

Henrique Fagundes
henri...@linuxadmin.com.br
Skype: magnata-br-rj
Linux User: 475399

http://www.aprendendolinux.com/
http://www.facebook.com/PortalAprendendoLinux
http://youtube.com/aprendendolinux/
http://twitter.com/aprendendolinux/
__
Participe do Grupo Aprendendo Linux
https://groups.google.com/forum/#!forum/portal-aprendendo-linux

Ou envie um e-mail para:
portal-aprendendo-linux+subscr...@googlegroups.com

Re: Dell BIOS

[Joe]

On Mon, 16 Jan 2017 14:53:33 -0600
"Martin McCormick"  wrote:

> Felix Miata  writes:
> > What models are they? If of approximately 2002 to 2007 vintage,
> > they could be victims of the bad capacitor plague:
> > 
> > http://en.wikipedia.org/wiki/Capacitor_plague  
> 
>   Interesting article. These dells could possibly be in
> that group as one has a BIOS date of August 1, 2001 and another
> is July 12, 2000. Both are Dell desktops so they could possibly
> be in that group. By the way, very few electronic malfunctions
> are quite as spectacular as an electrolytic capacitor that
> develops a sudden and catastrophic internal short.
> 
>   It sounds like the caps discussed in the article have a
> safety valve in the form of the vent but nothing short of high
> explosives equals an electrolytic filter cap popping.
> 
>   It sounds like a firecracker and throws more aluminum
> foil shrapnel than one could think would fit in the case.
> 
>   I had one about the size of a thumb blow up on me once
> and I could still find pieces of plastic and foil 6 months later.
> 
>   Thanks for the link to the article.
> 

It doesn't have the whole story. I've seen thousands (literally: some
television cameras I have repaired contained over 100 dodgy capacitors)
of surface-mount aluminium electrolytics leaking. The electrolyte used
in these [Japanese] capacitors was obviously very conductive, but it
also dissolved copper. There was literally no limit to the types of
fault caused by some tracks disappearing and some being bridged
together.

The mention of 'amine' rings a bell, when hot this electrolyte smelled
of fish, so the quick way to distinguish between harmless flux left on
a PCB after manufacture, and the brownish electrolyte, was to touch a
soldering iron to it. Evil stuff.

-- 
Joe

Re: How to find out the current display manager?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Jan 16, 2017 at 11:42:17AM -0500, kamaraju kusumanchi wrote:
> On Mon, Jan 16, 2017 at 4:42 AM,   wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote:
> >> How can I find out the display manager currently running on a machine
> >> from the command line?
> >
> > Hm. How do you know there aren't two running? Or fifteen?
> 
> Thanks for the detailed reply, Tomas.
> 
> For the first round, I am happy if I can get the display manager from
> which the current user's session is initiated from.
> 
> Background on why I need this:
> I am developing a script[1] that gathers relevant system information
> depending on what issue a debian-user is facing [...]

That sounds pretty exciting :-)

One building brick (assuming Debian context) might be to start from the
dependencies of the virtual package manger:

 | tomas@rasputin:~$ aptitude show x-display-manager
 | No current or candidate version found for x-display-manager
 | Package: x-display-manager
 | State: not a real package
 | Provided by: gdm3, kdm, lightdm, lxdm, nodm, sddm, slim, wdm, xdm

Next step would be to infer the name of the running binary (might well
be some of them install several binaries in /usr/bin) and search for
that in the process list.

I ask myself whether there's some giveaway in its /proc/ directory.

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

iEYEARECAAYFAlh9N1MACgkQBcgs9XrR2kazEwCeMd/JEw3UCkRYuKQkXg4VZbUm
FJkAnRxEtXRe/BFNIvAlvx540KiuOIAM
=I716
-END PGP SIGNATURE-

Re: Low Level Format of 1.4 Mb Floppy Isn't Happening Solved.

[David Niklas]

On Sun, 15 Jan 2017 23:04:14 +
Brian  wrote:
> On Sun 15 Jan 2017 at 15:36:08 -0600, Martin McCormick wrote:
> 
> [A trip down Memory Lane snipped]
> 
> For those who may want to use Plop boot manager, it is far quicker and
> more reliable to do so from GRUB on the hard disc. The Plop website has
> details. Struggling with a pile of floppies is no fun and a floppy which
> works today ivery likely not to do so next month.
> 
Actually, I've had to transfer data from an old windowz to another
windowz system and I found that all the spare floppies I had lying around
contained correct file systems (and I'm assuming correct files too).
So, long term storage seems to work fine for floppies, but transfering
lots of data does not work so well (the floppies wear out).

Sincerely,
David

Re: Dell BIOS

[Martin McCormick]

Felix Miata  writes:
> What models are they? If of approximately 2002 to 2007 vintage, they could
> be victims of the bad capacitor plague:
> 
> http://en.wikipedia.org/wiki/Capacitor_plague

Interesting article. These dells could possibly be in
that group as one has a BIOS date of August 1, 2001 and another
is July 12, 2000. Both are Dell desktops so they could possibly
be in that group. By the way, very few electronic malfunctions
are quite as spectacular as an electrolytic capacitor that
develops a sudden and catastrophic internal short.

It sounds like the caps discussed in the article have a
safety valve in the form of the vent but nothing short of high
explosives equals an electrolytic filter cap popping.

It sounds like a firecracker and throws more aluminum
foil shrapnel than one could think would fit in the case.

I had one about the size of a thumb blow up on me once
and I could still find pieces of plastic and foil 6 months later.

Thanks for the link to the article.

Martin McCormick WB5AGZ

Re: Duvida Samba compartilhamento de arquivos

[Rodrigo Cunha]

srs. agora estou acessando via terminal, adicionei as configuraçõe abaixo:
interfaces = enp3s0 lo
bind interfaces only = yes


Em 16 de janeiro de 2017 09:34, Paulino Kenji Sato 
escreveu:

> 2017-01-16 1:33 GMT-02:00 Rodrigo Cunha :
> > Prezados,
> > tenho um samba configurado apenas como compartilhamento de arquivos da
> rede,
> > no entanto ao instalar uma outra rede embora eu tenha acesso tanto ao
> host
> > do samba quanto as portas 139 e 445, que meu daemon do samba estão
> > atendendo, meu compartilhamento de rede não funciona.
> > Existe alguma diretiva nos arquivos do samba para configurar o acesso a
> > redes diversas, fora da rede do host?
>
> Ola,
> As redes, tanto onde esta o servidor e onde esta o cliente estão se
> comunicando?
> São redes dentro da mesma infraestrutura (inclusive vpn)?
> Ou são redes distintas, ambas com conexão própria a Internet?
>  Nesse caso, pode ser que as portas 139 e 445 estejam sendo filtrados
> pelo provedor de Internet.
>
> Quando se tem redes roteadas, ou seja, com domínio de broadcast
> diferentes, se usa um servidores wins para centralizar e resolver os
> nomes netbios. Ou servidores DNS com os hosts com o mesmo nome
> netbios.
> Caso não use wins,  e necessário usar ip (que nem sempre da certo) ou
> usar arquivos lmhosts.
>
> O protocolo SMB/CIFS não e seguro para ser exposto na Internet, se
> necessita acessar remotamente, use um outro protocolo  ou use uma VPN.
>
> Nos de mais detalhes do que ocorre quando tenta acessar o servidor.
>
> --
> Paulino Kenji Sato
>
>


-- 
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

Re: Re: grub has stopped booting windows 10

[Charles E. Blair]

   Thank you very much!

   As you suggested, typing c at the grub menu,
followed by

  set root=(hdo,msdos1)
  chainloader +1
  boot

took me to Windows.  I suspect that there
must be a way to fix my grub menu, but don't
know how.

   The output from os-prober:

/dev/sda1:Windows Recovery Environment (loader):Windows:chain
/dev/sda2:Windows 7 (loader):Windows1:chain
/dev/sda3:Windows Recovery Environment (loader):Windows2:chain

Re: How to seperate grub devices?

[Pascal Hambourg]

Le 16/01/2017 à 11:56, Darac Marjal a écrit :


BIOS will typically only boot from one drive (That said, both BIOS and
UEFI often have mechanisms to choose what that drive is).


UEFI behaves differently. It mostly uses boot entries pointing at EFI 
executable files which can be located on any drive instead of boot drives.



When grub is
installed to a drive, it will use the grub.cfg from that drive (I'm not
sure if that's built in, or if it's an assumption that grub makes


GRUB comes in several parts (depending on the target/architecture), 
which can be installed on different drives.


GRUB BIOS comes in three parts :
- the boot image, installed in the MBR of a drive or the PBR of a partition
- the core image, which can be installed in different places but must be 
on the same drive as the boot image

- the other files (modules, config file...) installed in /boot/grub.

GRUB EFI only has a core image installed in the EFI system partition 
mounted on /boot/efi, and other files in /boot/grub.


The core image can contain an embedded configuration, but of course it 
is not updated by update-grub.



For that, run "dpkg-reconfigure -plow grub-pc" (or whichever build of
grub you're using: grub-efi-*, grub-coreboot etc. Note that you're
reconfiguring the application package itself, NOT an auxiliary package
such as 'grub2' or 'grub' or 'grub-common'). This *should* ask you to
which drives you want grub installed.


Only GRUB BIOS (grub-pc) asks for a boot device. GRUB EFI won't ask for 
a boot device, because it does not need to : it does not install a boot 
image, and it installs the core image in /boot/efi by default.



If, additionally, you want Debian's grub to ONLY boot Debian and Kali's
grub to ONLY boot Kali, then you should uninstall the "os-prober"
package and re-run update-grub.


Alternatively you could just add GRUB_DISABLE_OS_PROBER=true in 
/etc/default/grub instead of uninstalling os-prober.

instalar wireless-tools

[Juan sanchez]

Señores buenos días.
En una red prestada instalé jessie con un disco net.iso. 
Pero al tratar de utilizarla en wifi
no se cargaron los componentes wireless-tools.
ya no tengo acceso al la red cableada y si a wifi.
como puedo instalar wireless-tools? 
¿ lo puedo extraer del disco.iso e instalarlo con apt-get?...
o con dpkg?...
alguna idea? 
Muchas gracias.

Re: Dell BIOS

[Felix Miata]

Martin McCormick composed on 2017-01-16 11:52 (UTC-0600):


I don't know how common this is but the BIOS' of two Dell
Optiplexes plus the BIOS of another Dell Dimension don't stay set
the way one would like them to. As a computer user who happens to


What models are they? If of approximately 2002 to 2007 vintage, they could be 
victims of the bad capacitor plague:

http://en.wikipedia.org/wiki/Capacitor_plague

I've resurrected several, but also failed on several, by replacing bad caps.


be blind, the setup process is a royal pain in the backside
because since there is no OS booted, the only output device is
the VGA output. I have to hook it up to a monitor and have
someone like my kind and patient wife or, before I retired, a
coworker change the boot sequence order from floppy-C:-CDROM to
CDROM-floppy-C: or CDROM-C:-floppy which prevents the hard drive
from grabbing the boot sequence each time.


I sympathize. I have a bunch of different models Optiplexes. I've had three 
different ones waste an obscene amount of my time lately. Each of these is 
installed in locations that make opening them up for maintenance a significant 
inconvenience.


The first, a 780 with a Dell PCIe DVI port card and connected via DisplayPort, 
when shut down from Linux puts my new Dell 21:9 display to sleep in a fashion 
from which it cannot be awakened until after I remove and replace the 780's 
power cable. Even after a BIOS update it took quite some time to determine that 
the only way to acquire normal behavior was to remove the DVI port card.


The second, a 745, even with latest BIOS, has taken to reporting low battery 
voltage, after the previous battery voltage was reduced to nil. I replaced it 
with a brand new battery with measured voltage up to specification, but it still 
pauses at every power up to report low voltage even though clock is correct.


The third, a 270, has decided to randomly report failed RAM. Each time it has 
done so I've opened it, wiggled or removed and replaced the sticks, and then it 
would work normally. As I write this I'm running Memtest86+ on it after having 
replaced both sticks with matched pair of different brand but same 3-3-3-8 CL3 
specification.



I don't think the CMOS batteries are dead because the
clock still seems to keep time so I am guessing that something
happens that the BIOS code sees as an error maybe during bootup
so it decides to re-order the sequence. One doesn't discover this
until the next time the CDROM doesn't spin up when a bootable
disk is in it. By the way, the CDROM works fine when mounting a
CD or ripping one.


Clocks will keep time even with voltage quite low. Batteries are cheap enough, 
as little as $2US for a card of 5 or 6, that they should be replaced, or at 
least checked with a voltmeter, if ever there is any indication of a problem 
that might be CMOS related. It's also a good idea when a battery has needed to 
be changed, to clear CMOS, then restore any desired custom settings.

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

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

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

Dell BIOS ( was Low Level Format of 1.4 Mb Floppy Isn't Happening)

[Martin McCormick]

Brian  writes:
> Does the machine you are booting use GRUB as the boot manager?

Surprisingly enough, yes. I wasn't sure but it certainly does.

Here's an explanation with a hope for a workable
solution.

I don't know how common this is but the BIOS' of two Dell
Optiplexes plus the BIOS of another Dell Dimension don't stay set
the way one would like them to. As a computer user who happens to
be blind, the setup process is a royal pain in the backside
because since there is no OS booted, the only output device is
the VGA output. I have to hook it up to a monitor and have
someone like my kind and patient wife or, before I retired, a
coworker change the boot sequence order from floppy-C:-CDROM to
CDROM-floppy-C: or CDROM-C:-floppy which prevents the hard drive
from grabbing the boot sequence each time.

Of course you can make the hard drive unbootable and
maybe force it to CDROM but one should not kick Murphy in the
knee cap when things are already going South. In this particular
case, I want to try a ubuntu installation CD to see if the
"speakup" software synthesis system works on this box and if so,
I will install it. If not, the obsolete installation already on
the hard drive does work but it sure needs to be replaced if
possible.

What happens is that we set a desired boot order and save
the settings. Things go fine for several months and then I try to
boot from CDROM one day and it's all back wrong again.

A good solution would be what I call the yank-back. If
one could backup the settings when good and the box decides to
clobber them, force them back.

The true ideal solution is for it not to happen at all
but you fight the war with the weapons you have, not what you
wish they were.

I don't think the CMOS batteries are dead because the
clock still seems to keep time so I am guessing that something
happens that the BIOS code sees as an error maybe during bootup
so it decides to re-order the sequence. One doesn't discover this
until the next time the CDROM doesn't spin up when a bootable
disk is in it. By the way, the CDROM works fine when mounting a
CD or ripping one.

Martin WB5AGZ

OpenVPN - Dúvida ao compilar o instalador

[Henrique Fagundes]

Prezados Colegas,

Primeiramente saudações pinguianas a todos.
Estou com uma dúvida e gostaria de saber se alguém pode me ajudar.

Eu tenho um servidor Debian Jessie 8.7 x64 rodando o OpenVPN 2.3.4 em 
modo server-clients.


Tudo funciona perfeitamente. Túnel, rotas, etc.

Eu gostaria de saber como posso comilar para os clients um instalador 
personalizado para WINDOWS. De modo que, o usuário possa fazer a 
instalação do tipo "NEXT, NEXT, FINSH", sem a necessidade de ter que 
colocar os arquivos de configurações lá dentro de "C:\Arquivos de 
Programas\OpenVPN\Config".


Eu sei que até pode estar parecendo que eu estou querendo, tipo, 
"enfeitar o pavão", mas... Acreditem... A grande maioria dos consultores 
externos desta empresa onde estou prestando serviços são "enrolados" 
(pra não dizer outra coisa), ao ponto de não conseguirem fazer nem isso.


Então, um instalador que entregasse tudo pronto, ajudaria bastante.

Não sei se alguém já teve essa necessidade antes, mas...
Se alguém puder ajudar, ficarei muito grato!

Atenciosamente,

Henrique Fagundes
henri...@linuxadmin.com.br
Skype: magnata-br-rj
Linux User: 475399

http://www.aprendendolinux.com/
http://www.facebook.com/PortalAprendendoLinux
http://youtube.com/aprendendolinux/
http://twitter.com/aprendendolinux/
__
Participe do Grupo Aprendendo Linux
https://groups.google.com/forum/#!forum/portal-aprendendo-linux

Ou envie um e-mail para:
portal-aprendendo-linux+subscr...@googlegroups.com

Re: How to find out the current display manager?

[Greg Wooledge]

On Mon, Jan 16, 2017 at 11:42:17AM -0500, kamaraju kusumanchi wrote:
> Background on why I need this:
> I am developing a script[1] that gathers relevant system information
> depending on what issue a debian-user is facing.

That's pretty ambitious.  Good luck.

> Thanks. It looks like all I need is to find the parent process of
> Xorg. In my case, that would be lightdm.

There may not even be an "Xorg" process, if the user is doing something
unusual, like running a really old version of Debian (XFree86), or a
proprietary X server, or a really new version of Debian with Wayland(??),
or if the user is not currently able to get X to run at all.

Obviously, if X can't start up at all, you're going to have a very hard
time detecting a running display manager process.  So we'll get back
to that

For the absolutely normal course, where the user is logged into X through
a display manager and is running your script inside that X session,
what you should probably do is recurse up through the process tree
(following ps -o ppid,cmd "$pid" step by step) until you run into a
process that you recognize as being a display manager, or until you
hit PID 1.

If you don't find a display manager that way, then your second try can
be "look for a running X server, and then look for its parent, and see
if it looks like a display manager".  That will catch the cases where
a display manager is running, but the user isn't logged in through it
for whatever reason.  Or where the user isn't running your script inside
an X session.

Third try can be looking for *any* running process that appears to be a
display manager.  Maybe that'll catch something like "display manager
is running a Wayland session, but user is not logged into it" more often
than it generates false positives.  Who knows.

Fourth try can be parsing dpkg -l (or similar) output to look for any
installed package that looks like a display manager.  Of course in
that case you'll also have to parse the status flags ("hi" or "rc"
or whatever).  This may catch the cases where X can't run due to drivers
being wrong, or no mouse plugged in, or whatever.

Re: How to find out the current display manager?

[kamaraju kusumanchi]

On Mon, Jan 16, 2017 at 6:00 AM, Felipe Salvador
 wrote:
> 0;115;0cIn-Reply-To: 
> 
>
> On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote:
>> How can I find out the display manager currently running on a machine
>> from the command line?
>
> I'm not sure, did you mean something like:
>
> ~$ echo $DESKTOP_SESSION
> /usr/share/xsessions/plasma

No, that is not what I mean. I came across this while searching in
google. But this shows the desktop session and not the display
manager. For example, I am running lightdm display manager but the
DESKTOP_SESSION points to plasma.

% echo $DESKTOP_SESSION
plasma

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

Re: How to find out the current display manager?

[kamaraju kusumanchi]

On Mon, Jan 16, 2017 at 4:42 AM,   wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote:
>> How can I find out the display manager currently running on a machine
>> from the command line?
>
> Hm. How do you know there aren't two running? Or fifteen?

Thanks for the detailed reply, Tomas.

For the first round, I am happy if I can get the display manager from
which the current user's session is initiated from.

Background on why I need this:
I am developing a script[1] that gathers relevant system information
depending on what issue a debian-user is facing. For example, if the
user says "audio is not working", it will show sound card information.
If the user says "setting up wireless on debian", it will fetch
information on wireless card. If the user says "unable to install
package X", it will show how /etc/apt/sources.list is currently setup
etc., The idea is that before posting to debian-user mailing list, the
user will run this script and copy paste the output in the initial
email, so we do not see trivial replies such as "What is your video
card or what distribution are you running or are there any errors in
/var/log/Xorg.0.log" etc.,.

The idea is similar to reportbug which automates gathering dependency
information when reporting a bug against a package. But the focus here
is to help users ask smart questions.

The script is not yet ready. It only works for sound related tasks for
now. But my plan is to extend it for other categories such as video,
wireless, apt related problems.

[1] - 
https://gitlab.com/d3k2mk7/rutils/blob/master/debian_user/gather_system_info.py


> Have a look at this tree snippet from my machine, obtained by
> "ps wauxf" (I snipped most of the columns and shortened things
> a bit):

Thanks. It looks like all I need is to find the parent process of
Xorg. In my case, that would be lightdm.

root  2605  0.0  0.1 287812  5804 ?SLl  Jan15   0:00
/usr/sbin/lightdm
root  2705  9.7  2.6 46 106552 tty7Ssl+ Jan15  92:07  \_
/usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0
-nolisten tcp vt7 -novtswitch
root  3635  0.0  0.1 250596  6344 ?Sl   Jan15   0:00  \_
lightdm --session-child 12 21
rajuloc+  3645  0.0  0.0   4296  1524 ?Ss   Jan15   0:00
\_ /bin/sh /usr/bin/startkde
rajuloc+  3673  0.0  0.1 116044  6240 ?SJan15   0:13
   \_ /usr/bin/xbrlapi -q
rajuloc+  3722  0.0  0.0  11084   328 ?Ss   Jan15   0:00
   \_ /usr/bin/ssh-agent /usr/bin/im-launch /usr/bin/startkde
rajuloc+  3814  0.0  0.1  72172  4708 ?SJan15   0:00
   \_ kwrapper5 /usr/bin/ksmserver


> If you have control on your whole environment, you can make your life
> easier and set up your session to export a shell variable (the session
> above is this process with the funny name "-:0", which parents everything
> running under X in my box). There are admin-settable things in the session
> machinery (mainly in /etc/X11/xinit/, as shell script snippets which are
> dot-included (remember? they want to be able to set env vars) at start,
> and branch out, as needed, to per-user script snippets.

I do not see any "-:0" process in the output of ps wauxf. So may be it
is a system specific thing that can't be relied upon?


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

Re: apt-build

[TheFox]

Por lo que dices parece que falta algún paquete. Prueba con sudo apt-get
install -f.

Santiago.

El 16 ene. 2017 13:02, "Antonio Trujillo Carmona" <
antonio.trujillo.s...@juntadeandalucia.es> escribió:

> El 13/01/17 a las 15:42, TheFox escribió:
> > Para resolver ése problema tienes que abrir una terminal y ejecutar el
> > siguiente comando: dpkg --configure -a
> >
> > Con esto ya debería de estar listo, pero si sigues teniendo el
> > problema una vez que hayas ejecutado dicho comando debes de realizar
> > estos otros pasos:
> >
> > 1) Borra los archivos .portrm y .list:
> > sudo rm /var/lib/dpkg/info/*.postrm
> > sudo rm /var/lib/dpkg/info/*.list
> >
> > 2) Elimina la caché de paquetes y actualiza el sistema:
> > sudo apt-get clean all
> > sudo apt-get update
> > sudo apt-get upgrade
> > Santiago.
> >
> > El 13 ene. 2017 8:59, "Antonio Trujillo Carmona"
> >  > > escribió:
> >
> > Tengo que recompilar el paquete freerdp2-x11 que esta en sid.
> > Como me he encontrado problemas de compatibilidades de librerías he
> > creado una maquina virtual con streecht/sid solo para este proceso,
> al
> > intentar instalar apt-build me da :
> > # apt install apt-build
> > Leyendo lista de paquetes... Hecho
> > Creando árbol de dependencias
> > Leyendo la información de estado... Hecho
> > Se instalarán los siguientes paquetes NUEVOS:
> >   apt-build
> > 0 actualizados, 1 nuevos se instalarán, 0 para eliminar y 0 no
> > actualizados.
> > Se necesita descargar 0 B/42,1 kB de archivos.
> > Se utilizarán 180 kB de espacio de disco adicional después de esta
> > operación.
> > Preconfigurando paquetes ...
> > Seleccionando el paquete apt-build previamente no seleccionado.
> > (Leyendo la base de datos ... 92041 ficheros o directorios instalados
> > actualmente.)
> > Preparando para desempaquetar .../apt-build_0.12.45_amd64.deb ...
> > Desempaquetando apt-build (0.12.45) ...
> > Configurando apt-build (0.12.45) ...
> > sed: character class syntax is [[:space:]], not [:space:]
> > dpkg: error al procesar el paquete apt-build (--configure):
> >  el subproceso instalado el script post-installation devolvió el
> > código
> > de salida de error 4
> > Procesando disparadores para man-db (2.7.6.1-2) ...
> > Se encontraron errores al procesar:
> >  apt-build
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> >
> > --
> >
> > *Antonio Trujillo Carmona*
> >
> > *Técnico de redes y sistemas.*
> >
> > *Subdirección de Tecnologías de la Información y Comunicaciones*
> >
> > Servicio Andaluz de Salud. Consejería de Salud de la Junta de
> > Andalucía
> >
> > _antonio.trujillo.sspa@juntadeandalucia.es_
> >
> > Tel. +34 670947670 747670)
> >
> >
> >
> Después de eso sigo igual pero con muchos errores del tipo dpkg: falta
> el fuichero de lista del paquete ' xxx'
> Ademas de lo que me dijiste, en vista de que no funcionava hice un dpkg
> --purge apt-build y al hacer un
> 'apt install apt-build' me da:
>
> Preparando para desempaquetar .../apt-build_0.12.45_amd64.deb ...
> Desempaquetando apt-build (0.12.45) ...
> Configurando apt-build (0.12.45) ...
> sed: character class syntax is [[:space:]], not [:space:]
> dpkg: error al procesar el paquete apt-build (--configure):
>  el subproceso instalado el script post-installation devolvió el código
> de salida de error 4
> Procesando disparadores para man-db (2.7.6.1-2) ...
> Se encontraron errores al procesar:
>  apt-build
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> --
>
> *Antonio Trujillo Carmona*
>
> *Técnico de redes y sistemas.*
>
> *Subdirección de Tecnologías de la Información y Comunicaciones*
>
> Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía
>
> _antonio.trujillo.sspa@juntadeandalucia.es_
>
> Tel. +34 670947670 747670)
>
>
>
>

Re: intel_pstate vs acpi-cpufreq freq scale

[Luis Felipe Tabera Alonso]

On lunes, 16 de enero de 2017 1:13:09 (CET) Julian Brooks wrote:
> Hi all,

Hi Julian,

> Fresh install of Sid, with
> liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work).
> Have also installed linrunner's TLP.

Have you tried to see if this happens with debian's official kernel?

> My understanding is that the x230's Ivy Bridge processor should make use of
> intel_pstate for frequency scaling but I can't seem to load the kernel
> module at boot.

Is it a module? At least on debian kernels, intel_pstate is inside the kernel, 
not as a separate module.

$ grep -i pstate config-4.8.0-2-amd64
CONFIG_X86_INTEL_PSTATE=y

however, on liquorix

$ grep -i pstate config-4.9.0-3.2-liquorix-amd64
# CONFIG_X86_INTEL_PSTATE is not set

So it seems that liquorix kernel has not compiled intel_pstate. So could try 
to recompile it as a module for your running kernel of rebuild liquorix kernel 
with intel_pstate support.

Luis

Re: How to seperate grub devices?

[Thomas Schmitt]

Hi,

Hans wrote:
> > If you do not understand me yet, take this discussion as closed.

Mark Fletcher wrote:
> No, mate, we UNDERSTOOD you from the beginning, the problem is that 
> _what you are describing is impossible_.

To be exacting: It obviously goes beyond the imagination of the people
here, who have experience with running update-grub.

Hans, if you are sure that this happens and prepared to present the
experimental facts which make you sure, then consider to ask at
  help-g...@gnu.org
  https://lists.gnu.org/mailman/listinfo/help-grub
how this could be possible.

As one can see on
  http://lists.gnu.org/archive/html/help-grub/2017-01/threads.html
the main supporter is quite busy. So be friendly and concise when
you present your case.


Why your problem should be on topic there:

man 8 update-grup says its a "stub for grub-mkconfig". On my Debian 8
i see in file /usr/sbin/update-grub :
  #!/bin/sh
  set -e
  exec grub-mkconfig -o /boot/grub/grub.cfg "$@"
(Did you check what your "update-grub" command actually does ?
 In mine i see no indication that it would write two grub.cfg files.)

man 8 grub-mkconfig says you should report bugs to bug-g...@gnu.org.
This is the neighbor list of help-grub. Since your problem is not
yet identified as a bug in GRUB, i would start by asking at help-grub.

I'd skip "update-grub" and ask directly about

  grub-mkconfig -o /boot/grub/grub.cfg ...your.other.arguments.if.any...

(After having tested that it indeed shows the problematic behavior,
 of course.)


Have a nice day :)

Thomas

Re: apt-build

[Antonio Trujillo Carmona]

El 13/01/17 a las 15:42, TheFox escribió:
> Para resolver ése problema tienes que abrir una terminal y ejecutar el
> siguiente comando: dpkg --configure -a
>
> Con esto ya debería de estar listo, pero si sigues teniendo el
> problema una vez que hayas ejecutado dicho comando debes de realizar
> estos otros pasos:
>
> 1) Borra los archivos .portrm y .list: 
> sudo rm /var/lib/dpkg/info/*.postrm
> sudo rm /var/lib/dpkg/info/*.list
>
> 2) Elimina la caché de paquetes y actualiza el sistema:
> sudo apt-get clean all
> sudo apt-get update
> sudo apt-get upgrade
> Santiago.
>
> El 13 ene. 2017 8:59, "Antonio Trujillo Carmona"
>  > escribió:
>
> Tengo que recompilar el paquete freerdp2-x11 que esta en sid.
> Como me he encontrado problemas de compatibilidades de librerías he
> creado una maquina virtual con streecht/sid solo para este proceso, al
> intentar instalar apt-build me da :
> # apt install apt-build
> Leyendo lista de paquetes... Hecho
> Creando árbol de dependencias
> Leyendo la información de estado... Hecho
> Se instalarán los siguientes paquetes NUEVOS:
>   apt-build
> 0 actualizados, 1 nuevos se instalarán, 0 para eliminar y 0 no
> actualizados.
> Se necesita descargar 0 B/42,1 kB de archivos.
> Se utilizarán 180 kB de espacio de disco adicional después de esta
> operación.
> Preconfigurando paquetes ...
> Seleccionando el paquete apt-build previamente no seleccionado.
> (Leyendo la base de datos ... 92041 ficheros o directorios instalados
> actualmente.)
> Preparando para desempaquetar .../apt-build_0.12.45_amd64.deb ...
> Desempaquetando apt-build (0.12.45) ...
> Configurando apt-build (0.12.45) ...
> sed: character class syntax is [[:space:]], not [:space:]
> dpkg: error al procesar el paquete apt-build (--configure):
>  el subproceso instalado el script post-installation devolvió el
> código
> de salida de error 4
> Procesando disparadores para man-db (2.7.6.1-2) ...
> Se encontraron errores al procesar:
>  apt-build
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> --
>
> *Antonio Trujillo Carmona*
>
> *Técnico de redes y sistemas.*
>
> *Subdirección de Tecnologías de la Información y Comunicaciones*
>
> Servicio Andaluz de Salud. Consejería de Salud de la Junta de
> Andalucía
>
> _antonio.trujillo.sspa@juntadeandalucia.es_
>
> Tel. +34 670947670 747670)
>
>
>
Después de eso sigo igual pero con muchos errores del tipo dpkg: falta
el fuichero de lista del paquete ' xxx'
Ademas de lo que me dijiste, en vista de que no funcionava hice un dpkg
--purge apt-build y al hacer un
'apt install apt-build' me da:

Preparando para desempaquetar .../apt-build_0.12.45_amd64.deb ...
Desempaquetando apt-build (0.12.45) ...
Configurando apt-build (0.12.45) ...
sed: character class syntax is [[:space:]], not [:space:]
dpkg: error al procesar el paquete apt-build (--configure):
 el subproceso instalado el script post-installation devolvió el código
de salida de error 4
Procesando disparadores para man-db (2.7.6.1-2) ...
Se encontraron errores al procesar:
 apt-build
E: Sub-process /usr/bin/dpkg returned an error code (1)


-- 

*Antonio Trujillo Carmona*

*Técnico de redes y sistemas.*

*Subdirección de Tecnologías de la Información y Comunicaciones*

Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía

_antonio.trujillo.sspa@juntadeandalucia.es_

Tel. +34 670947670 747670)

Re: How to seperate grub devices?

[Mark Fletcher]

On Mon, Jan 16, 2017 at 12:45:51PM +0100, Hans wrote:
> It makes a grub.cfg on PHYSICAL harddrive ONE and
> a second one on PHYSICAL harddrive TWO and both are identical.
> 
> But as both shall be different, according to the drive I want start from.
> 
> If you do not understand me yet, take this discussion as closed.
> 
> 

No, mate, we UNDERSTOOD you from the beginning, the problem is that 
_what you are describing is impossible_.

So there is something you are not telling us, or something is going on 
on your machine that you either did not think relevant or did not know.

For example, could your setup when running Kali and when running Debian 
in FACT, contrary to what you think is going on, be sharing a /boot 
mount? That would be unusual, it would be strange, but it WOULD WORK, 
assuming both kernels were there -- and it is one way to explain the 
behaviour you are seeing.

Type "df" command in Kali and in Debian and post the output here, that 
will eliminate that question. Also the content of /etc/fstab

Mark

Re: How to seperate grub devices?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Jan 16, 2017 at 12:45:51PM +0100, Hans wrote:
> It makes a grub.cfg on PHYSICAL harddrive ONE and
> a second one on PHYSICAL harddrive TWO and both are identical.
> 
> But as both shall be different, according to the drive I want start from.
> 
> If you do not understand me yet, take this discussion as closed.

I was about to jump in, but if you get that grumpy at people who try
to help you, I better stay out. My days are exhausting as they are,
I don't need to take more abuse.

all the best, nevertheless
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlh8tM0ACgkQBcgs9XrR2kY+EwCZARd/tGETTfdXUD6DgnkwZyNX
dKQAoIHN83KfwQGzENWWqukcnrkCGGAX
=Ry0P
-END PGP SIGNATURE-

Re: How to seperate grub devices?

[Hans]

It makes a grub.cfg on PHYSICAL harddrive ONE and
a second one on PHYSICAL harddrive TWO and both are identical.

But as both shall be different, according to the drive I want start from.

If you do not understand me yet, take this discussion as closed.

Thanks for the try.

Best 

Hans
 

Re: Duvida Samba compartilhamento de arquivos

[Paulino Kenji Sato]

2017-01-16 1:33 GMT-02:00 Rodrigo Cunha :
> Prezados,
> tenho um samba configurado apenas como compartilhamento de arquivos da rede,
> no entanto ao instalar uma outra rede embora eu tenha acesso tanto ao host
> do samba quanto as portas 139 e 445, que meu daemon do samba estão
> atendendo, meu compartilhamento de rede não funciona.
> Existe alguma diretiva nos arquivos do samba para configurar o acesso a
> redes diversas, fora da rede do host?

Ola,
As redes, tanto onde esta o servidor e onde esta o cliente estão se comunicando?
São redes dentro da mesma infraestrutura (inclusive vpn)?
Ou são redes distintas, ambas com conexão própria a Internet?
 Nesse caso, pode ser que as portas 139 e 445 estejam sendo filtrados
pelo provedor de Internet.

Quando se tem redes roteadas, ou seja, com domínio de broadcast
diferentes, se usa um servidores wins para centralizar e resolver os
nomes netbios. Ou servidores DNS com os hosts com o mesmo nome
netbios.
Caso não use wins,  e necessário usar ip (que nem sempre da certo) ou
usar arquivos lmhosts.

O protocolo SMB/CIFS não e seguro para ser exposto na Internet, se
necessita acessar remotamente, use um outro protocolo  ou use uma VPN.

Nos de mais detalhes do que ocorre quando tenta acessar o servidor.

-- 
Paulino Kenji Sato

Re: How to find out the current display manager?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Jan 16, 2017 at 12:00:22PM +0100, Felipe Salvador wrote:
> 0;115;0cIn-Reply-To: 
> 
> 
> On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote:
> > How can I find out the display manager currently running on a machine
> > from the command line?
> 
> I'm not sure, did you mean something like:
> 
> ~$ echo $DESKTOP_SESSION
> /usr/share/xsessions/plasma

Thanks for that nice example.

That's why I went to such lengts. On my system, this variable is unset
(and this is OK). But this (setting a variable in the session init, as
your system is doing) was one of the things I proposed. Of course, if
your system is already doing it: the merrier.

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

iEYEARECAAYFAlh8r4MACgkQBcgs9XrR2kYVJwCcDRQfkByR77swzqtEfO5WBe/m
vegAnAs/nuPk8p8Ltnbmot+zgNvfLZEp
=+mmI
-END PGP SIGNATURE-

Re: Duvida Samba compartilhamento de arquivos

[Guimarães Faria Corcete DUTRA , Leandro]

2017-01-16 8:57 GMT-02:00 Chinabhz :
> Tente fazer ping de uma das máquinas da outra rede na porta 445 do
> servidor..

Se o ping funcionar, já emenda um telnet.  Pode ser raro, mas acontece
da porta responder mas o Samba, em si, não.


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

Re: How to seperate grub devices?

[Darac Marjal]

On Mon, Jan 16, 2017 at 12:05:06PM +0100, Hans wrote:

You all did not understand me, maybe caused by my bad English.

update-grub is ALWAYS changing grub.cfg on BOTH drives, same from which system
it is started. And I want it only have changed on THAT DRIVE, I am running AT
THE MOMENT. The other drive shall be then stayed untouched!


Then something is wrong with your system.

update-grub is a shell script which calls "grub-mkconfig -o 
/boot/grub/grub.cfg". (Evidence: 
https://sources.debian.net/src/grub2/2.02~beta2-22%2Bdeb8u1/debian/update-grub/)


grub-mkconfig generates a new configuration and outputs it either to 
stdout or to the file specified in the -o option. (Evidence: 
https://sources.debian.net/src/grub2/2.02~beta2-22%2Bdeb8u1/util/grub-mkconfig.in/)


There is no facility in either of these to output to TWO config files.

So, either you're using something like unionfs, or RAID mirroring or 
automatic file copying or something similar which is mirroring changes 
on one drive to another drive OR ELSE you actually only have one boot 
partition which both grubs point to.




Hope this makes it more clear.

Hans



--
For more information, please reread.

Re: grub has stopped booting windows 10

[Darac Marjal]

On Sun, Jan 15, 2017 at 06:36:36PM -0600, Charles E. Blair wrote:

  I have been running version 7.11 of Debian for several
years on a desktop with a dual boot of windows and linux
via grub.  I upgraded to windows 10 roughly 8 months ago,
and the system continued to work.

  On January 9, I noticed that the grub menu no longer
displayed a windows option, instead displaying linux
options twice.  This problem may have occurred earlier
without my noticing it.  The file /boot/grub/grub.cfg
was modified on January 4.  I do not know enough to
interpret it.

  I give below an abridged output from fdisk -l.  I
suspect the windows 10 system is supposed to be on
/dev/sda1 or /dev/sda2, but I don't understand what's
going on.

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors

  Device Boot  Start End  Blocks   Id  System
/dev/sda1   *2048 3074047 1536000   27  Hidden NTFS WinRE
/dev/sda2 3074048   491355297   2441406257  HPFS/NTFS/exFAT
/dev/sda3  1924173824  195352371114674944   17  Hidden HPFS/NTFS
/dev/sda4   491356158  1924173823   7164088335  Extended
Partition 4 does not start on physical sector boundary.
/dev/sda5   491356160  1890959359   699801600   83  Linux
/dev/sda6  1890961408  192417382316606208   82  Linux swap / Solaris

Partition table entries are not in disk order



I think that, with Windows 10, /dev/sda1 would be the boot partition and 
/dev/sda2 would be the system partition.


What is the output of (as root) "os-prober"?

Can you manually start Windows 10 by the following?

* At the grub menu, press 'c' for a command line.
* Enter: set root=(hd0,msdos1)
* Enter: chainloader +1


--
For more information, please reread.

Re: How to seperate grub devices?

[Hans]

You all did not understand me, maybe caused by my bad English.

update-grub is ALWAYS changing grub.cfg on BOTH drives, same from which system 
it is started. And I want it only have changed on THAT DRIVE, I am running AT 
THE MOMENT. The other drive shall be then stayed untouched!

Hope this makes it more clear.

Hans

Re: How to find out the current display manager?

[Felipe Salvador]

0;115;0cIn-Reply-To: 


On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote:
> How can I find out the display manager currently running on a machine
> from the command line?

I'm not sure, did you mean something like:

~$ echo $DESKTOP_SESSION
/usr/share/xsessions/plasma

?

> Google tells me that /etc/X11/default-display-manager will show the
> default display manager. But I want the display manager that is
> currently running (which can be different from the default). Is that
> possible?
> 
> thanks
> raju

-- 
Felipe Salvador

Re: Duvida Samba compartilhamento de arquivos

[Chinabhz]

Bom dia. Tente fazer ping de uma das máquinas da outra rede na porta 445 do 
servidor. Tá com jeito de falta de acesso. Se não for este o problema verifique 
se não tem nenhum agente, como configurações de segurança, se sobrepondo ao 
samba. Tenho uma rede nacional cada estado com sua própria rede que acessa um 
servidor samba sem problemas.

Em 16 de janeiro de 2017 01:41:59 BRST, Leandro  escreveu:
>Ola.
>tente as opçoes abaixo
>
>hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
>hosts deny = 0.0.0.0/0
>
>The above will only allow SMB connections from 'localhost
>
>
>Em 16/01/2017 01:34, "Rodrigo Cunha" 
>escreveu:
>
>Prezados,
>tenho um samba configurado apenas como compartilhamento de arquivos da
>rede, no entanto ao instalar uma outra rede embora eu tenha acesso
>tanto ao
>host do samba quanto as portas 139 e 445, que meu daemon do samba estão
>atendendo, meu compartilhamento de rede não funciona.
>Existe alguma diretiva nos arquivos do samba para configurar o acesso a
>redes diversas, fora da rede do host?
>Segue abaixo minha sessão global.
>
>[global]
>  # Substituir xx pelo nome do domínio desejado caso necessário
>  workgroup = oduvaldocozzi
>  # Substituir xx pelo nome do servidor caso necessário
>  netbios name = ocozzi
>  server string = desktopcasa
>  domain master = yes
>  preferred master = yes
>  local master = yes
>  domain logons = no
>  logon path = %systemroot%\%u
>#  #logon script = todos.bat
>#  security = user @root
>#  encrypt passwords = yes
>#  os level = 200
>#
># time server = yes
># unix charset = iso8859-1
># display charset = cp850
>#
># ##Arquivo de log
>  log file = /var/log/samba/%m.log
>  max log size = 5000
>  debug level = 2
>
>##Encrypta as senhas digitadas na rede, porém não funciona em
>estações##
>Windows 95 e Windows 3.11
>  smb passwd file = /etc/samba/smbpasswd
>  username map = /etc/samba/smbusers
>
>  ##Garantir melhor desempenho do servidor
>  socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>
>#  ##Permite a utilização de impressoras compartilhas em estações Linux
>#  load printers=yes
>#  printing=lprng
>#  printcap name = /etc/printcap
>
>
>
>-- 
>Atenciosamente,
>Rodrigo da Silva Cunha
>São Gonçalo, RJ - Brasil

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: How to seperate grub devices?

[Darac Marjal]

On Sat, Jan 14, 2017 at 10:50:47AM +0100, Hans wrote:

Hi list,
this is the situation:

I have debian installed on my first harddrive and kali-linux on my 
second

harddrive. When a new kernel version is installed, update-grub is always
editing both harddrives. Is there a way, to avoid this?

So, I do not want, that an upgrade of the kali-kernel touches the grub
installation of the first harddrive with debian and vice versa.

If this is not possible, I would also be happy to know.


As noted by Pascal, update-grub only recreates grub's config, but let's 
clarify some of the workings of grub to see where your problem lies.


BIOS will typically only boot from one drive (That said, both BIOS and 
UEFI often have mechanisms to choose what that drive is). When grub is 
installed to a drive, it will use the grub.cfg from that drive (I'm not 
sure if that's built in, or if it's an assumption that grub makes, but 
let's take it as read). That grub.cfg can then be used to start 
operating systems on any drive.


So, I think what you're wanting is A) Debian's grub pointing to Debian's 
grub.cfg, booting Debian and Kali AND B) Kali's grub pointing to Kali's 
grub.cfg, booting Kali and Debian.


For that, run "dpkg-reconfigure -plow grub-pc" (or whichever build of 
grub you're using: grub-efi-*, grub-coreboot etc. Note that you're 
reconfiguring the application package itself, NOT an auxiliary package 
such as 'grub2' or 'grub' or 'grub-common'). This *should* ask you to 
which drives you want grub installed. This will update the grub image 
embedded at the start of the drive(s) that you select. In theory, then, 
deselecting the Kali drive should mean that all data on the Kali drive 
is untouched (by grub).


If, additionally, you want Debian's grub to ONLY boot Debian and Kali's 
grub to ONLY boot Kali, then you should uninstall the "os-prober" 
package and re-run update-grub. Basically, the normal assumption is that 
ONE operating system is in charge of the bootloader, but you still want 
to be able to boot other operating systems, so update-grub calls 
os-prober which scans your system for other operating systems and adds 
them into the list. If you remove os-prober, grub will only know about 
itself.


Hope that helps.




Best

Hans



--
For more information, please reread.

Re: [OT] servidor irc en debian jessie

[Roberto Quiñones]

El 16 ene. 2017 3:55 AM, "divagante"  escribió:



On 15/01/17 22:02, Roberto Quiñones wrote:

>
>
> El 15 ene. 2017 8:52 PM, "divagante"  > escribió:
>
>
> Hola
>
>
> El OP debe dar más datos para saber que es lo que falla.
> - tipo de conexión
>
>
> Adsl o cablemoden de parte del servidor de internet. Inalambrica la
> mia..
>
> - versión del SO
>
>
> El sistema operativo que uso es el que esta anunciado en el asunto.
> Debian Jessie 8 sin repos ajenos ni cosas raras.
>
>
> - servicio a utilizar (no-ip, etc.)
>
>
> Use dos (creo que tambien lo dije), No-ip y nsupdate. Ambos
> funcionan correctamente enlazándose a mi ip publica dinámica del
> momento.
>
>  Esta info la brinda ddclient. Para cada uno poseo dos
> configuraciones diferentes obviamente. Ahora simplemente deje el de
> no-ip por un tema de elegancia en el nombre de dominio
>
> - pruebas realizadas.
>
>
>  Utilice Hexchat, añadi un canal con el nombre de dominio
> correspondiente mas su puerto, en este caso el 6667. El puerto esta
> abierto tanto en el router como en mi pc, y uso una ip fija.
>  El resultado es "conexion rehusada".
>
> Luego me avivaron de "usarlo" en la misma pc, asi que configure la
> conexion al servidor irc con 127.0.0.1/6667 
>
> y claro... funciono!
>  El servidor ngircd esta funcionando!
>
> Mas tarde, no sin trabajo previo, encontre una opcion en el router,
> un "firewall SPI", al desactivarlo pense que la solucion pero no!!
>  Ahora cuando me conecto a traves del exterior (ip publica bajo
> no-ip) hexchat me avierte algo diferente y un poco mas esperanzador
> a pesar de no conectarse:
>
>  (No se puede encontrar la ruta al host)
>
>
> - revisión de los logs.
>
>
> mm.. aqui estoy frito! no solo que no puedo entender el contenido de
> los logs (apenas ver alguna palabrita clave), si no que sospecho
> fuertemente, es un problema que se veria representado en ellos.
>
> - etc.
>
>
> ??. No se cuanto mas... un numero de tarjeta de credito tal vez? jeje
>
>
> Personalmente nunca he instalado un IRC bajo esa modalidad, pero
> generalmente los problemas al levantar un servicio mediante ip
> dinámica viene dado por parte del router ppal o modem del
> proveedor de
> la conexión, no sirve de nada abrir los puertos en el pc si no
> están
> abiertos en el router tanto interno como si te conectas al
> modem-router del proveedor.
>
>
>  Saludos y espero que estos datos den una mejor represetacion. Gracias.
>
>
>
> Localmente si intentas ingresar lograr conectar a tu servidor IRC ??
>

Asi es. Yo conmigo mismo funciono. 127.0.0.1/6667 (onanismo on)

Saludos.
>

 Otros para ti, disculpas por poder brindarte mi mano.

:)


Vale, pero yo me refería a si desde otro equipo desde tu red LAN logras
entrar al servidor que tienes de IRC.

PD: es ente doble que puedas entrar si te estás conectando desde la misma
máquina al 127.0.0.1.
Saludos.

apt-listbugs and apt.conf

[David Wright]

I'm still running apt-cacher-ng on wheezy (my "plumbed-in" server) and
have at various time switched to backports and backports-sloppy in
order to get error-free running. The main problem has been cache
expiration and at the moment it fails because of:
Problem with debrep/dists/jessie/main/binary-i386/Packages.xz
OK, I'll put up with that. The cache grows more than it ought.

The latest problem is that when I apt-get upgrade, apt-listbugs fails because:

Retrieving bug reports... 0%at depth 1 - 20: unable to get local issuer 
certificate
 Fail
Error retrieving bug reports from the server with the following error message:
 W: SSL_connect returned=1 errno=0 state=error: certificate verify failed
It could be because your network is down, or because of broken proxy servers,
or the BTS server itself is down. Check network configuration and try again
Retry downloading bug information? [Y/n] 

OK, I thought, I'll change the command line I type into:

# apt-get update && apt-get -d upgrade ; apt-get upgrade -o 
Acquire::http::Proxy=DIRECT

so that updating the Package files and downloading the packages both
take place through apt-cacher-ng, and then the actual upgrade can
run on a direct connection. The   -o Acquire::http::Proxy=DIRECT
counteracts the fact that /etc/apt/apt.conf contains:
Acquire::http::Proxy "http://192.168.1.19:3142/;;
APT::Default-Release "jessie";
(and nothing more).

The problem is that DIRECT doesn't trickle through to apt-listbugs,
which itself reads /etc/apt/apt.conf and so uses apt-cacher-ng
which fails, preventing any upgrade taking place. That's more
serious than just a cache growing too much.

Any ideas for an elegant solution? Some obscure configuration option?

Cheers,
David.

Re: [OT] servidor irc en debian jessie

[Ramses]

El 17 de enero de 2017 0:50:41 CET, divagante  
escribió:
>Hola
>
>> El OP debe dar más datos para saber que es lo que falla.
>> - tipo de conexión
>
>Adsl o cablemoden de parte del servidor de internet. Inalambrica la
>mia..
>
>> - versión del SO
>
>El sistema operativo que uso es el que esta anunciado en el asunto. 
>Debian Jessie 8 sin repos ajenos ni cosas raras.
>
>> - servicio a utilizar (no-ip, etc.)
>
>Use dos (creo que tambien lo dije), No-ip y nsupdate. Ambos funcionan 
>correctamente enlazándose a mi ip publica dinámica del momento.
>
> Esta info la brinda ddclient. Para cada uno poseo dos configuraciones 
>diferentes obviamente. Ahora simplemente deje el de no-ip por un tema
>de 
>elegancia en el nombre de dominio
>
>> - pruebas realizadas.
>
>  Utilice Hexchat, añadi un canal con el nombre de dominio 
>correspondiente mas su puerto, en este caso el 6667. El puerto esta 
>abierto tanto en el router como en mi pc, y uso una ip fija.
>  El resultado es "conexion rehusada".
>
>Luego me avivaron de "usarlo" en la misma pc, asi que configure la 
>conexion al servidor irc con 127.0.0.1/6667 y claro... funciono!
>  El servidor ngircd esta funcionando!
>
>Mas tarde, no sin trabajo previo, encontre una opcion en el router, un 
>"firewall SPI", al desactivarlo pense que la solucion pero no!!
> Ahora cuando me conecto a traves del exterior (ip publica bajo no-ip) 
>hexchat me avierte algo diferente y un poco mas esperanzador a pesar de
>
>no conectarse:
>
>  (No se puede encontrar la ruta al host)
>
>> - revisión de los logs.
>
>mm.. aqui estoy frito! no solo que no puedo entender el contenido de
>los 
>logs (apenas ver alguna palabrita clave), si no que sospecho 
>fuertemente, es un problema que se veria representado en ellos.
>
>> - etc.
>
>??. No se cuanto mas... un numero de tarjeta de credito tal vez? jeje
>
>> Personalmente nunca he instalado un IRC bajo esa modalidad, pero
>> generalmente los problemas al levantar un servicio mediante ip
>> dinámica viene dado por parte del router ppal o modem del proveedor
>de
>> la conexión, no sirve de nada abrir los puertos en el pc si no están
>> abiertos en el router tanto interno como si te conectas al
>> modem-router del proveedor.
>
> Saludos y espero que estos datos den una mejor represetacion. Gracias.

Lo que tienes que probar, a parte de si funciona en local (127.0.0.1:6667), que 
ya has probado que te funciona, es desde otro PC que esté en la misma LAN que 
el Servidor IRC, antes de buscar problemas de IP Pública, es decir, accediendo 
a :6667

Si esto último te funciona, entonces te centras en el firewall del PC y en el 
Router.


Saludos,

Ramses

Re: How to find out the current display manager?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote:
> How can I find out the display manager currently running on a machine
> from the command line?

Hm. How do you know there aren't two running? Or fifteen?

Yes, I know the question sounds at first a bit grumpy/wisecracky. Bear
with me :-)

- From some perspective (e.g. you are a shell script running in some
X terminal) still the notion of "the" display manager might make
sense: that would be the one which is y display manager *and* your
ancestor.

Have a look at this tree snippet from my machine, obtained by
"ps wauxf" (I snipped most of the columns and shortened things
a bit):

 | /usr/bin/xdm
 |  \_ /usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/lib[...]
 |  \_ -:0 
 |  \_ x-window-manager -s
 |  \_ /usr/bin/ssh-agent x-window-manager
 |  \_ xterm -fg rgb:// -bg rgb://5050
 |  |   \_ bash
 |  |   \_ emacs
 |  |   \_ mutt
 |  \_ /usr/lib/fvwm/2.6.5/FvwmCommandS 8 5 /home/tomas/.fvwm/config 0 8
 |  \_ /usr/lib/fvwm/2.6.5/FvwmButtons 9 4 none 0 8
 |  \_ /usr/lib/fvwm/2.6.5/FvwmIconMan 11 4 none 0 8
 |  \_ /usr/lib/fvwm/2.6.5/FvwmAnimate 13 4 none 0 8
 |  \_ /usr/lib/fvwm/2.6.5/FvwmPager 17 4 none 0 8 FvwmPager-Single * *
 |  \_ xbiff -geometry +5000+5000 -bg rgb:7070/8c8c/8c8c -fg 
rgb://
 |  \_ xclock -norender -geometry +5000+5000 -bg rgb:7070/8c8c/8c8c -fg 
rgb[...]
 |  \_ xterm -class bat -bg black -fg white -geometry +5000+5000 -fn 
xft:DejaVu [...]
 |  |   \_ watch -tn 10 bat
 |  \_ xload -geometry +5000+5000 -bg rgb:7070/8c8c/8c8c -fg 
rgb://[...]
 |  \_ xterm -fg rgb:// -bg rgb://5050
 |  |   \_ bash
 |  |   \_ xscreensaver
 |  |   \_ fetchmail -Nkd 30
 |  \_ xterm -fg rgb:// -bg rgb://5050
 |  |   \_ bash
 |  |   \_ /bin/bash /home/tomas/bin/tun
 |  |   \_ socat [...]
 |  |   \_ socat [...]
 |  \_ xterm -fg rgb:// -bg rgb://5050
 |  |   \_ bash
 |  \_ xterm -fg rgb:// -bg rgb://5050
 |  |   \_ bash
 |  |   \_ ssh to...@tuxteam.tun
 |  \_ xterm -fg rgb:// -bg rgb://5050
 |  \_ bash
 |  \_ ps wauxf
 |  \_ bash

The display manager(s) are thus the root(s) of those process trees which
contain an X session (unless there's no login at the moment). If you are
interested in "your" display manager, you only have to ascend your
process tree until you hit a program which "is" a display manager.

If you have control on your whole environment, you can make your life
easier and set up your session to export a shell variable (the session
above is this process with the funny name "-:0", which parents everything
running under X in my box). There are admin-settable things in the session
machinery (mainly in /etc/X11/xinit/, as shell script snippets which are
dot-included (remember? they want to be able to set env vars) at start,
and branch out, as needed, to per-user script snippets.

This is a pretty "classical" view. No idea how things work under
systemd or Wayland.

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

iEYEARECAAYFAlh8lW8ACgkQBcgs9XrR2kZ6bgCfSWliySpBB0zhlwj0eQnM7a7O
VnAAn1uUUjFebyJpnX/IpOm9HqSgGO+k
=R7MN
-END PGP SIGNATURE-

Re: Duvida Samba compartilhamento de arquivos

[Marcos Carraro]

Bom Dia,

Verificou os logs de erros?
Acesso por IP vai?
Resolve o nome corretamente?
As mascaras de rede estão corretas?
Tentou rodar um nmap -sS contra o ip do samba?


*--*
Att
Marcos Carraro 


Em 16 de janeiro de 2017 01:46, Rodrigo Cunha 
escreveu:

> nada, configurei e resetei o daemon e não funcionou.
> segue abaixo as novas configurações.
> [global]
>   # Substituir xx pelo nome do domínio desejado caso necessário
>   workgroup = oduvaldocozzi
>   # Substituir xx pelo nome do servidor caso necessário
>   netbios name = ocozzi
>   server string = desktopcasa
>   domain master = yes
>   preferred master = yes
>   local master = yes
>   domain logons = no
>   logon path = %systemroot%\%u
> #Redes de acesso
> hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
> hosts deny = 0.0.0.0/0
>
> #  #logon script = todos.bat
> #  security = user @root
> #  encrypt passwords = yes
> #  os level = 200
> #
> # time server = yes
> # unix charset = iso8859-1
> # display charset = cp850
> #
> # ##Arquivo de log
>   log file = /var/log/samba/%m.log
>   max log size = 5000
>   debug level = 2
>
>   ##Encrypta as senhas digitadas na rede, porém não funciona em estações##
> Windows 95 e Windows 3.11
>   smb passwd file = /etc/samba/smbpasswd
>   username map = /etc/samba/smbusers
>
>   ##Garantir melhor desempenho do servidor
>   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>
> #  ##Permite a utilização de impressoras compartilhas em estações Linux
> #  load printers=yes
> #  printing=lprng
> #  printcap name = /etc/printcap
>
>
>
>
>
> Em 16 de janeiro de 2017 01:41, Leandro  escreveu:
>
>> Ola.
>> tente as opçoes abaixo
>>
>> hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
>> hosts deny = 0.0.0.0/0
>>
>> The above will only allow SMB connections from 'localhost
>>
>>
>> Em 16/01/2017 01:34, "Rodrigo Cunha" 
>> escreveu:
>>
>> Prezados,
>> tenho um samba configurado apenas como compartilhamento de arquivos da
>> rede, no entanto ao instalar uma outra rede embora eu tenha acesso tanto ao
>> host do samba quanto as portas 139 e 445, que meu daemon do samba estão
>> atendendo, meu compartilhamento de rede não funciona.
>> Existe alguma diretiva nos arquivos do samba para configurar o acesso a
>> redes diversas, fora da rede do host?
>> Segue abaixo minha sessão global.
>>
>> [global]
>>   # Substituir xx pelo nome do domínio desejado caso necessário
>>   workgroup = oduvaldocozzi
>>   # Substituir xx pelo nome do servidor caso necessário
>>   netbios name = ocozzi
>>   server string = desktopcasa
>>   domain master = yes
>>   preferred master = yes
>>   local master = yes
>>   domain logons = no
>>   logon path = %systemroot%\%u
>> #  #logon script = todos.bat
>> #  security = user @root
>> #  encrypt passwords = yes
>> #  os level = 200
>> #
>> # time server = yes
>> # unix charset = iso8859-1
>> # display charset = cp850
>> #
>> # ##Arquivo de log
>>   log file = /var/log/samba/%m.log
>>   max log size = 5000
>>   debug level = 2
>>
>>   ##Encrypta as senhas digitadas na rede, porém não funciona em
>> estações## Windows 95 e Windows 3.11
>>   smb passwd file = /etc/samba/smbpasswd
>>   username map = /etc/samba/smbusers
>>
>>   ##Garantir melhor desempenho do servidor
>>   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>>
>> #  ##Permite a utilização de impressoras compartilhas em estações Linux
>> #  load printers=yes
>> #  printing=lprng
>> #  printcap name = /etc/printcap
>>
>>
>>
>> --
>> Atenciosamente,
>> Rodrigo da Silva Cunha
>> São Gonçalo, RJ - Brasil
>>
>>
>>
>
>
> --
> Atenciosamente,
> Rodrigo da Silva Cunha
> São Gonçalo, RJ - Brasil
>
>

Debian 8.7

[Luna Jernberg]

Dags att uppdatera lite idag:
https://www.debian.org/News/2017/20170114

COMUNICADO URGENTE / Email vinculado: debian-user-portuguese@lists.debian.org

[Banco Santander]

 
 Caso você não consiga visualizar as imagens abaixo clique em mostrar imagens 
ou Não é spam. Ou acesse a versão web. 
 
 
  

Prezado (a) Cliente,
 Em razão de fatores tecnológicos e legais, reiteramos que consta em nosso 
sistema o atraso de pagamento na anuidade de manutenção de conta junto ao nosso 
sistema. Devido ao ocorrido, estamos parcialmente realizando o bloqueio dos 
sequintes serviços  
  
  
Tabela de Segurança. 
Cheque especial. 
Cartões de débito/Crédito vinculados. 
 
 O prazo para desbloqueio imediato sem cobrança de taxas está disponivel a 
partir da abertura deste informativo,com prazo máximo de 24 horas,caso nao 
identificarmos o desbloqueio no prazo estimado,o mesmo só poderá ser realizado 
na agência de origem munido de toda documentação pessoal.