date:20171128

Re: (deb-cat) Sticky-enganxos pel propietari de directori

2017-11-28 Thread Narcis Garcia

El propi grup principal de l'usuari (->gid) també actua com a «grup per
defecte», doncs si un directori està marcat amb g+s ja preval el grup
del directori per a nous elements per sobre del grup que aplica l'usuari
de forma predeterminada.
Així doncs, el mateix comportament hauria de tenir u+s per davant de la
màscara (umask).




__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 28/11/17 a les 20:56, Robert Marsellés ha escrit:
> 
> 
> El 28/11/17 a les 20:19, Narcis Garcia ha escrit:
>> La meva proposta és per a què s'heretin només els permisos r,w,s
>>
>>
> 
> Per curiositat i per allò de pensar amb els pros i contres de les
> propostes. D'aquesta forma que proposes deixaria de tenir sentit
> mantenir a la vegada la màscara per defecte 0022 per usuari i per grups
> ¿Correcte? ¿Quina de les 2 versions de donar permisos és/sembla més útil
> a la majoria dels usuaris?
> 
> robert
>

Re: Upgrading from very-old Debian

2017-11-28 Thread Michael Fothergill

>
>
>>
>>>
>>>
>>
>>> As a friendly recommendation:
> If it was about me, I would encourage to backup the home directories as
> well as mail or similar, depending what other kind of services running
> under the particular system.
>
> Backup the data to an external usb drive or the whole source drive if you
> are keen on that, for example. Then do a "clean" install of a new system on
> the original drive. Otherwise you might run into issues, where you might
> miss out on an important package, if you snapshot upgrade one by one.
>

I agree here.  Forget about rummaging through the last 5 years of
Icelandic telephone directories; phooey to creating a cyclical re-run of
the monolith scene from 2001 space odyssey, let the romantic notion of
upgrading from the operating system of an ancient Egyptian abacus to a yet
to be constructed quantum computer wither and fade away

And back up your work files etc and

reinstall stretch "Jessieson"

and sing the title track song from the sound of music NOT the one about
climbing every mountain etc.

Why bother?

Cheers

MF

Re: Désinstallation et réinstallation

2017-11-28 Thread didier gaumet

Le 28/11/2017 à 17:54, stephane.le...@free.fr a écrit :
> Bonjour à tous,
> 
> J'ai besoin d'aide. On m'a installé Debian et je dois faire echap avant que 
> l'ordi cherche à réparer : "préparation de la réparation automatique" puis 
> "diagnostic de votre ordinateur" et cela en boucle (et je n'ai plus accès à 
> Windows : j'aurais aimé le garder).
> 
> Quelqu'un pourrait-il m'aider?

Bonjour,

Le plus simple serait probablement de demander à la personne qui t'a
installé Debian de se pencher sur ton cas.
Le problème que tu signales me semble être du fait de Windows et si tu
veux garder ce dernier, je pense qu'il faut le réparer (voire le
réinstaller si le "réparateur" Windows ne s'en sort pas...

Re: Désinstallation et réinstallation

2017-11-28 Thread Étienne Mollier

Stéphane Lebel, le 2017-11-28 :
> Bonjour à tous,

Bonjour Stéphane,


> J'ai besoin d'aide. On m'a installé Debian et je dois faire
> echap avant que l'ordi cherche à réparer : "préparation de la
> réparation automatique" puis "diagnostic de votre ordinateur"
> et cela en boucle (et je n'ai plus accès à Windows : j'aurais
> aimé le garder).
>
> Quelqu'un pourrait-il m'aider?

Les réparations de Windows ne sont pas le sujet principal de la
liste, mais on va tout de même voir ce qu'on peut faire ; la
question revient de temps en temps à la suite d'installations
malheureuses.  :(

Allons y méthodiquement...
Si une étape coince, ou si vous avez besoin de plus de détails,
n'hésitez pas à répondre à la liste de diffusion, en particulier
en indiquant le message d'erreur, s'il s'en présente.


1. Sauvegardes

La première chose à faire, si ce n'est déjà le cas et si vous
avez commencé à travailler avec votre Debian, est de sauvegarder
votre répertoire utilisateur sur un disque externe.

Si vous pouvez également accéder à vos partitions Windows depuis
votre Debian, en installant le paquet ntfs-3g par exemple, alors
une sauvegarde de vos données stockées sous Windows serait aussi
la bienvenue.

Si vous avez déjà fait des sauvegardes, ce qui devrait être le
cas normalement[1], alors vérifiez simplement qu'elles sont assez
récentes et toujours lisibles.


2. Réparations

À moins que vous n'ayez pas de données à sauvegarder, n'allez pas
plus loin tant que vos sauvegardes ne sont pas vérifiées.  Ces
« réparations » peuvent potentiellement nécessiter de détruire
les données présentes sur le disque de votre machine pour
remettre le système d'aplomb.

Saisissez vous de votre ISO/CD/DVD de Windows, et votre clé de
licence, il se peut que vous en ayez besoin.  Si vous n'avez pas
un tel disque, il me semble que Microsoft distribue les ISO
d'installation de son système quelque part sur son site web.
Prenez bien la version qui correspond à l'OS que vous avez acheté
dans ce cas.

Normalement, en démarrant sur cette ISO, vous devriez vous voir
proposer un utilitaire de réparation qui devrait remettre en état
(au pire, réinstaller) votre partition Windows (dans mes
souvenirs, le disque d'installation de Windows 7 proposait un tel
mode de réparation, je n'ai pas encore eu l'occasion de constater
ça sur des versions plus récentes, mais j'imagine que ça existe
toujours).  Si vous souhaitez toujours installer Debian, et que
l'utilitaire de partitionnement de Microsoft vous le permet,
n'allouez pas tout le disque pour Windows, mais laissez de
l'espace pour Debian.  Vous n'aurez ainsi pas besoin d'effectuer
de redimensionnement de partition, potentiellement source de
casse.

Si la réparation se passe bien et que votre Windows démarre,
alors désactivez le « Fast boot » puis redémarrez sur l'ISO
Debian en suivant le manuel d'installation[2].  Il est peut-être
possible que cette réinstallation ne soit pas nécessaire, mais ça
dépendra fortement du résultat de la « réparation ».

Étant donné les symptômes que vous décrivez, je soupçonne le
mécanisme de « Fast Boot » de vous avoir fait des misères[3].
Mais je peux me tromper, notamment si vous avez réussi à accéder
à la partition Windows depuis Debian lorsque vous avez effectué
vos sauvegardes avant opérations.


3. Restauration

Restaurez vos données depuis les sauvegardes, en particulier si
les partitions qui stockaient vos données on dû être supprimées
pendant la manipulation.


Évitez le bouton « Shutdown » de Windows à l'avenir, il en fait
moins que ce qu'il est censé faire, préférez un « Restart », vers
Debian.  ;)


En espérant que ça puisse vous aider,
Librement,
-- 
Étienne Mollier 

[1] https://www.debian.org/releases/stable/amd64/ch03s02.html.fr
[2] https://www.debian.org/releases/stable/amd64/index.html.fr
[3] 
https://www.debian.org/releases/stable/amd64/ch03s06.html.fr#disable-fast-boot

Re: Upgrading from very-old Debian

2017-11-28 Thread Umarzuki Mochlis

2017-11-29 14:45 GMT+08:00 Jan :
>
>
> On 28.11.2017 17:58, The Wanderer wrote:
>>
>> On 2017-11-28 at 11:53, Patrick Bartek wrote:
>>
>>> On Tue, 28 Nov 2017 10:28:57 -0500 The Wanderer
>>>  wrote:
>>>
 I've run across someone who says her machine is running Debian
 oldoldoldstable or maybe even oldoldoldoldstable, and who
 consequently can't upgrade to newer Debian.

 I seem to recall that there *is* a way to do step-wise upgrades of
 such old systems, i.e. upgrading from oldoldoldoldstable to
 oldoldoldstable, then to oldoldstable, then to oldstable, then to
 stable. However, I'm stumped as to how to actually get started on
 doing that.

 The last few steps of this are straightforward; oldoldstable is
 still available in the repos, as far as I'm aware. The first ones
 are more of a problem; if I understand matters correctly, anything
 prior to oldoldstable is removed from the live repos, although its
 .deb files are still maintained on e.g. snapshot.debian.org. (Which
 doesn't really suffice for the equivalent of a dist-upgrade,
 because you'd have to manually download all the correct .debs by
 hand and then install them with dpkg.)

 Is there in fact a way to manage the first steps of this stepwise
 upgrade, from one aged-out-of-the-repos release to another?

 If so, any pointers to information on how to go about it?
>>>
>>>
>>> Save yourself time and lots of problems, back up your data and do a
>>> clean install of the current Debian release.
>>
>>
>> A: This isn't me, this is someone I encountered.
>>
>> B: That's not always a viable option, depending on the circumstances.
>> It's probably the easier option when it is viable, but that doesn't mean
>> it should be the only option considered, for cases when something else
>> may be more viable.
>>
>>> To do what you want requires dist-upgrading each release, in order,
>>> one-at-a-time, then troubleshooting each dist-upgrade once done with
>>> no guarantees it will work.
>>
>>
>> Yes, of course. That's established procedure, and it's entirely
>> reasonable to expect people to follow it. (Is there any reason it
>> shouldn't work, when it worked for people at the time when those
>> releases were made?)
>>
>>> Be sure to read and explicitly follow the dist-upgrade instructions
>>> in the Release Notes for each release. Many times there are special
>>> things that must be done. Just dist-upgrading from your current old
>>> install to Stretch, skipping all those inbetween is "not
>>> recommended," meaning it won't work.
>>
>>
>> Of course. That's exactly why accessible repositories containing those
>> older releases are needed; my question was about how / where to manage
>> those, and that was answered in the first reply.
>>
>
> As a friendly recommendation:
> If it was about me, I would encourage to backup the home directories as well
> as mail or similar, depending what other kind of services running under the
> particular system.
>
> Backup the data to an external usb drive or the whole source drive if you
> are keen on that, for example. Then do a "clean" install of a new system on
> the original drive. Otherwise you might run into issues, where you might
> miss out on an important package, if you snapshot upgrade one by one.
>
> Running such a old and obsolete system is not only a security risk, but also
> in other areas where improvements has been made, you miss out on a lot. This
> was not the question of course, but it simply doesn't make much sense to
> keep such an old operating system around which is not even actively
> supported by documentation or people likewise anymore.
>
> And it might not simply be worth the hassle to upgrade step by step,
> possible breaking something in the process and troubleshoot why one package
> depends on another or crippling other services, having obsolete folders or
> even configuration files and settings laying around, which are not needed
> anymore. As stated by other people here, it might and perhaps will, take
> much longer time to troubleshoot everything or simply end up to be
> impossible to do correctly.
>
> Better clean and start from scratch install with a known supported
> installation.
> Ensure just to backup mail(dirs), mail, .ssh, .config or similar folders in
> "home" (or better the whole home folders" or "var" or other locations which
> might contain data you need. Or "etc" for configuration settings - but "etc"
> content, might and will most likely have changed dramatically depending on
> what was installed previously.
>
> To backup the software list of what was installed on the system, I would use
> something like an "apt list | grep installed" and pipe the output into a
> file. But for "apt-get" this does not seem to be an option, so perhaps
> theres another way to get a list of installed packages using dpkg or such,
> I'm just not aware of that.
> This way, you can

Re: Debian 8 and Debian 9 Dual Boot

2017-11-28 Thread Michael Fothergill

On 29 November 2017 at 03:15, Dan Norton  wrote:

>
> On 11/13/2017 01:55 PM, Joe wrote:
>
> On Mon, 13 Nov 2017 11:01:27 -0500
> Dan Norton   wrote:
>
>
>
> Although I didn't say so, each install would have its own set of
> directories. Please say more about how to mount the other
> installation and share data. How to mount things in another volume
> group?
>
>
> Good advice so far, but to add a bit: all LVM groups will be seen at
> boot, and /dev will know about them. See man lvm2 and also here:
> https://wiki.debian.org/LVM  for complete information about the
> commands you have available. There are also numerous tutorials on the
> Net which show basic usage of the simpler commands. It's worth having a
> look when you have some spare time, as one day you'll need to know some
> of this and won't have any spare time.
>
>
> Reading the wiki reveals "Grub and ? LiLo
> are not compatible with LVM, so /boot should be outside the storage disk
> managed by LVM." Here's what I have:
>
> Attempts to boot normally do not work. But using Super Grub2 on a bootable
> cd and selecting "Boot manually" and picking the hd1 entry brings up the
> jessie system that the installer reports as successfully installed on sda3.
> Using fdisk to take a look:
>
> dan@debian8:~$ sudo fdisk /dev/sda
> Command (m for help): p
> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: A615A904-0620-459F-BF44-5E53E54FDF24
>
> Device StartEndSectors   Size Type
> /dev/sda1   2048 411647 409600   200M BIOS boot
> /dev/sda2 411648   16783359   16371712   7.8G Linux swap
> /dev/sda3   16783360  151001087  13421772864G Linux LVM
> /dev/sda4  151001088  285218815  13421772864G Linux LVM
> /dev/sda5  285218816  419436543  13421772864G Linux LVM
> /dev/sda6  419436544  553654271  13421772864G Linux LVM
> /dev/sda7  553654272 1953525134 1399870863 667.5G Linux filesystem
>
> Is there a problem here?
>

I have been using Supergrub for ages now.   If you use Gentoo as I do you
appreciate the irritation of continuous babysitting of grub2 every time
you reconfigure the kernel (e.g. after setting up the long winded nonsense
required to make a firewall work properly) then grub tends to go awol
and requires TLC, massage therapy and soft music to start working
properly.

Meanwhile you will feel so frustrated that you want to chew on barbed wire
etc.

But supergrub is cool.  It is like a bloodhound.  You just can't fool it.  

The more you use it the dumber you feel using grub2 until you have finally
sorted the gripes and things have calmed down and stabilised - usually a
month later.

Remember the scene from 2001 space odyssey where the monkey throws the
bones up in the air.

Do the same with grub2, then use supergrub until things work and then
de-evolve again and vegetate in this area as I do.

Cheers

MF

>
> dan@debian8:~$ df -h
> FilesystemSize  Used Avail Use% Mounted on
> /dev/dm-0 9.1G  3.0G  5.7G  35% /
> udev   10M 0   10M   0% /dev
> tmpfs 775M  9.0M  766M   2% /run
> tmpfs 1.9G   68K  1.9G   1% /dev/shm
> tmpfs 5.0M  4.0K  5.0M   1% /run/lock
> tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
> /dev/sda1 992K  142K  851K  15% /boot/efi
> /dev/mapper/debian8--vg-var   8.2G  1.3G  6.4G  17% /var
> /dev/mapper/debian8--vg-home  9.1G  356M  8.3G   5% /home
> /dev/mapper/debian8--vg-tmp   268M  2.1M  247M   1% /tmp
> tmpfs 388M  4.0K  388M   1% /run/user/115
> tmpfs 388M   12K  388M   1% /run/user/1000
>
>
> Doesn't this satisfy the statement that "/boot should be outside the
> storage disk managed by LVM" since it is on sda1?
>
> Look in /etc/fstab for lines beginning /dev/mapper/[volume] which will
> be the volumes mounted in the running installation. The 'mapper' is
> turning LVM volumes into things which look like partitions for many
> purposes.
>
>
> Here is fstab:
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> #
> /dev/mapper/debian8--vg-root /  ext4errors=remount-ro
> 0   1
> # /boot/efi was on /dev/sda1 during installation
> UUID=B07E-1F0B  /boot/efi   vfatumask=0077  0   1
> /dev/mapper/debian8--vg-home /home  ext4defaults
> 0   2
> /dev/mapper/debian8--vg-tmp /tmp

Re: Upgrading from very-old Debian

2017-11-28 Thread Jan




On 28.11.2017 17:58, The Wanderer wrote:

On 2017-11-28 at 11:53, Patrick Bartek wrote:


On Tue, 28 Nov 2017 10:28:57 -0500 The Wanderer
 wrote:


I've run across someone who says her machine is running Debian
oldoldoldstable or maybe even oldoldoldoldstable, and who
consequently can't upgrade to newer Debian.

I seem to recall that there *is* a way to do step-wise upgrades of
such old systems, i.e. upgrading from oldoldoldoldstable to
oldoldoldstable, then to oldoldstable, then to oldstable, then to
stable. However, I'm stumped as to how to actually get started on
doing that.

The last few steps of this are straightforward; oldoldstable is
still available in the repos, as far as I'm aware. The first ones
are more of a problem; if I understand matters correctly, anything
prior to oldoldstable is removed from the live repos, although its
.deb files are still maintained on e.g. snapshot.debian.org. (Which
doesn't really suffice for the equivalent of a dist-upgrade,
because you'd have to manually download all the correct .debs by
hand and then install them with dpkg.)

Is there in fact a way to manage the first steps of this stepwise
upgrade, from one aged-out-of-the-repos release to another?

If so, any pointers to information on how to go about it?


Save yourself time and lots of problems, back up your data and do a
clean install of the current Debian release.


A: This isn't me, this is someone I encountered.

B: That's not always a viable option, depending on the circumstances.
It's probably the easier option when it is viable, but that doesn't mean
it should be the only option considered, for cases when something else
may be more viable.


To do what you want requires dist-upgrading each release, in order,
one-at-a-time, then troubleshooting each dist-upgrade once done with
no guarantees it will work.


Yes, of course. That's established procedure, and it's entirely
reasonable to expect people to follow it. (Is there any reason it
shouldn't work, when it worked for people at the time when those
releases were made?)


Be sure to read and explicitly follow the dist-upgrade instructions
in the Release Notes for each release. Many times there are special
things that must be done. Just dist-upgrading from your current old
install to Stretch, skipping all those inbetween is "not
recommended," meaning it won't work.


Of course. That's exactly why accessible repositories containing those
older releases are needed; my question was about how / where to manage
those, and that was answered in the first reply.



As a friendly recommendation:
If it was about me, I would encourage to backup the home directories as 
well as mail or similar, depending what other kind of services running 
under the particular system.


Backup the data to an external usb drive or the whole source drive if 
you are keen on that, for example. Then do a "clean" install of a new 
system on the original drive. Otherwise you might run into issues, where 
you might miss out on an important package, if you snapshot upgrade one 
by one.


Running such a old and obsolete system is not only a security risk, but 
also in other areas where improvements has been made, you miss out on a 
lot. This was not the question of course, but it simply doesn't make 
much sense to keep such an old operating system around which is not even 
actively supported by documentation or people likewise anymore.


And it might not simply be worth the hassle to upgrade step by step, 
possible breaking something in the process and troubleshoot why one 
package depends on another or crippling other services, having obsolete 
folders or even configuration files and settings laying around, which 
are not needed anymore. As stated by other people here, it might and 
perhaps will, take much longer time to troubleshoot everything or simply 
end up to be impossible to do correctly.


Better clean and start from scratch install with a known supported 
installation.
Ensure just to backup mail(dirs), mail, .ssh, .config or similar folders 
in "home" (or better the whole home folders" or "var" or other locations 
which might contain data you need. Or "etc" for configuration settings - 
but "etc" content, might and will most likely have changed dramatically 
depending on what was installed previously.


To backup the software list of what was installed on the system, I would 
use something like an "apt list | grep installed" and pipe the output 
into a file. But for "apt-get" this does not seem to be an option, so 
perhaps theres another way to get a list of installed packages using 
dpkg or such, I'm just not aware of that.
This way, you can then, after some cleanup in an editor for example, 
pipe the output of listed installed packages into the new system 
apt/apt-get and reinstall as available in the repository everything that 
was installed earlier, most likely.


Of course, after the home directories have been created accordingly 
using add user and copy

Re: software to do drawings of houses, gardens, etc.

2017-11-28 Thread Erik Christiansen

On 28.11.17 21:41, Emanuel Berg wrote:
> Erik Christiansen wrote:
> 
> > After trying to get various GUI drawing
> > packages to function at the most basic level,
> > and failing to produce anything, I'm just
> > finishing the 8 drawings for my new house
> > build (floor plan, elevations, sections, and
> > site plan), using raw postscript. That has
> > proven a better fit for a retired programmer.
> > [...]
> 
> Sounds *great* and my thinking/style is exactly
> the same!
> 
> Do you mind sharing the source and Makefile?

It's not necessary to build anything - I've just defined a few
postscript procedures at the start of the postscript document.
Job done.

On 28.11.17 21:45, Emanuel Berg wrote:
> Erik Christiansen wrote:
> 
> > Interesting ... I had not heard of it
> > previously. Looking at it on wikipedia, I see
> > "Most operations in Xfig are performed using
> > the mouse," For the first, I've had no luck
> > mouse-wrangling GUI drawing packages - it's
> > all so counter-intuitive, and nothing works
> > for me. For the second, after my 8 drawings
> > I cannot imagine how I'd mouse-wrangle
> > something as simple as a wall cross-section
> > with complete positional and dimensional
> > precision. In postscript, it's just:
> >
> > /wall_height 2700 def % X Y X Y 3600 0 moveto
> > 100 wall_height box % Let's put it at 3600 mm
> > from origin, % at floor level.
> 
> This is, again, exactly what I want. Is there
> a collection somewhere of the postscript syntax
> or how did you pick it up?

The Adobe book "Postscript Language Reference", third edition, is useful
for looking up commands, but the bulk of the text is prolix and obtusely
dense reading.

Better for readability and examples is the BLUEBOOK.PDF, which is the
first hit on a google for "postscript blue book".

Two methods of specifying paper size are required for both printers and
software packages to pick it up. I found a way that works, by googling.

What I've put together is only a beginning - enough to satisfactorily
complete one drafting job of 8 drawings. It's only one way to do it.
(And a couple of things would need generalising, e.g the WC and kitchen
sink are currently just drawn in situ, rather than being in a procedure.

One thing which makes editing 840 lines of postscript more manageable
has nothing to do with the language. Enabling Vim's text folding renders
the entire document as 26 lines of top level headings. That greatly
simplifies navigating. (Though I also use search on the comments.)

If there's a place to put an example and some very basic howto guff -
enough for someone to get started, then I could clean up what I have,
and put together a little bit of intro text. (There'd need to be some
explanation of the way I chain and abut walls of differing rotation to
build rooms and dividers.)

After that, the seed can be grown into anything you care to program.

Erik

Re: open on nfs server -> resource temporarily unavailable

2017-11-28 Thread Salvatore Bonaccorso

Hi Andrey

> Hello *,
>   creating a file in the directory exported by the NFS server
> sometimes returns an error - "resource temporarily unavailable",
> when a client on importing computer is keeping reading that file.
> 
> serv:~# cat /etc/exports
> /home/me/data-t   cli(ro,sync,no_subtree_check)
> 
> serv:~# systemctl restart nfs-kernel-server
> 
> cli:~# cat /etc/fstab
> ...
> mhfpklytsserv:/home/me/data-t /home/me/dt nfs noauto,ro,noac,user 0 0
> 
> me@cli:~$ mount dt
> me@cli:~$ mount
> ...
> serv:/home/me/data-t on /home/me/dt type nfs4 
> (ro,nosuid,nodev,noexec,relatime,sync,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,noac,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.209.174,local_lock=none,addr=192.168.238.113,user=me)
> 
> It could be provoked in a few minutes by running on the server serv:~$ while 
> : ; do date > data-t/now.txt; sleep 1; done
> 
> 
> while on the client computer
> me@cli:~$ while : ; do cat dt/now.txt; sleep 1; done
> 
> After a while (it's unpredictable might take up 10 minutes or a few seconds,
> but in average about 2 minutes)
> on the server I get:
> data-t/now.txt: Resource temporarily unavailable
> 
> Lesser 'sleep', of 0.2 for ex., doesn't necessarily make the error appear 
> quicker.
> Also it doesn't depend whether a directory is exported read-only or 
> read-write.
> But without reading client the error never appears.
> 
> To narrow down the case a bit I made a test on 'C' for the server
> which does the same thing as the script above - just writing down a date in 
> the same file
> - but checking an error on creating a file and writing to it.
> 
> Sometimes error appears just in a few seconds:
> serv:~$ date;./tnfs-open data-t/now.txt ;date
> Mon Aug  1 18:58:23 CEST 2016
> open fd=-1 errno=11 -> Resource temporarily unavailable
> Mon Aug  1 18:58:25 CEST 2016
> 
> serv:~$ errno 11
> EAGAIN 11 Resource temporarily unavailable
> 
> I am at a loss :(
> 
> my system on the server and the client computes is the same Debian 8.5

Were you ever able to narrow down the issue? I'm able to reproduce the issue
easily as well just on localhost doing the following on a Debian 8, running
3.16.43-2+deb8u5 or 3.16.48-1, but the issue seems disapeared (or at least
harder to reproduce in 4.9, when installed from jessie-backports):

Sort of "minimal" reproducing steps:

# apt-get install nfs-kernel-server
# mkdir -p /srv/test
# echo '/srv/test *' >> /etc/exports
# systemctl restart nfs-kernel-server.service
# mount localhost:/srv/test /mnt

1. terminal
# while : ; do date >/srv/test/foo ; sleep 1 ; done

2. terminal
# while : ; do cat /mnt/foo ; sleep 1 ; done

I'm currently trying to bisect the issue. But since in the good cases it's not
clear if it's always fixed I can only guess at the moment that the 4.9 claim is
true.

Were you sucessful on isolating the issue?

Regards,
Salvatore

[SOLUCIONADO] Configurar manualmente una red wifi.

2017-11-28 Thread divagante

Mensaje reenviado
Asunto: Re: Configurar manualmente una red wifi.
Fecha: Wed, 29 Nov 2017 02:28:35 -0300
De: divagante
A: debian-user-spanish@lists.debian.org

Bien, aplique los pasos de la guia de geekland, mas algo de howtouse wifi
en debian: https://wiki.debian.org/WiFi/HowToUse#connman

Los resultados no fueron del todo satisfactorios, debido a que hay cierto
problema con el DNS. Puedo conectarme al router, establecer una ip fija,
pero no tengo salida a internet.
Bueno, al menos en el navegador ya que si hago un ping 8.8.8.8 (DNS google)
los paquetes son enviados y recibidos.

Hice un nmap -sn y en efecto veo el router, se conecta, pero sale un aviso
o advertencia sobre los DNS. Lamentablemtne lo copie en el portapapeles y al
reiniciar se borro. :(

Primero utilice en el archivo /etc/network/interfaces el parametro
dns-nameservers pero no resulto!
Luego intente escribir el archivo /etc/resolv.conf y colocar alli un DNS
pero no me lo permite! no lo puedo crear o escribir ni como root!?!?

Ahora que vuelvo a ver el archivo y activar networkmanager este mismo pudo
escribir en el al menos 3 ips y otras en ipv6 tambien..

La configuracion de /etc/network/interfaces que utilize es esta:

(lo copio todo por la linea del "source", hace una referencia a donde aun no
coloque nada)

Se puede apreciar tambien que numere (#) dos parametros primero uno y luego
el otro a ver si la situacion cambiaba, pero no se conecto y el mensaje de
los DNS mostrado por nmap persistio. reiniciando cada vez el equipo para
refrescar la red ya que con systemd no se como dar de baja y alta la
interfaz de red (ppfff..). Los viejos comandos ya no sirven :(

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.2.123
netmask 255.255.255.0
# broadcast 192.168.0.255
gateway 192.168.2.1
# dns-nameservers 8.8.8.8
wpa-ssid TeleCentro-
wpa-psk 6909729dc24a6f84d4f217a1c09ab14c

¿Tu router asigna ips por dhcp? verifica que no tengas conflictos.

Si, aunque si coloco ips fijas mediante networkmanger o en el archivo
interfaces para ethernet nunca tuve problema.

Si usaste esa misma dirección de broadcast, esta fuera de tu red.

jeje.. habia editado para ocultar valores reales. No problem con esto.

En tu caso el que tiene los dns es el router intenta dar la dirección
del router para el dns.

Si! apenas vi esta respuesta sabia que la iva a aplicar! y pense que
con exito pero no!! :(
lo mismo que antes.. ping a 8.8.8.8 (DNS google) bien, pero no se
conecta a ningun sitio.

Tambien estuve leyendo la wiki de debian respecto a DNS, con lo cual
probare una solucion instalando resolvconf y definiendo a estos en el
interfaces.

Otro link (del 2012, no se si el sistema tiene o no systemd) asegura
que mientras se tenga networkmanager instalado este borra el contenido
de /etc/resolv.conf

http://www.forosdelweb.com/f92/reiniciar-vps-archivo-etc-resolv-conf-le-borran-dns-1020844/

Su solucion fue desinstalarlo de raiz. Tambien tengo esta opcion.
Bueno, luego me estare autorespondiendo espero que con la solucion.

Pude conectarme mediante wireless sin network-manager aplicando los
pasos entendidos hasta aqui e instalando resolvconf, una entre
soluciones que brinda la wiki de debian al respecto de resolv.conf y
seleccion de dns. Hay otras soluciones! enfatizo leer el articulo.

Saludos y gracias.

https://wiki.debian.org/resolv.conf

Re: Configurar manualmente una red wifi.