Re: Nvida Legacy 304 Catastrophe

2016-10-10 Thread David Baron
On יום ראשון, 9 באוקטובר 2016 13:03:24 IDT Felix Miata wrote:
> David Baron composed on 2016-10-09 13:17 (UTC+0300):
> > These packages upgraded (though they seem no longer on Debian!). The
> > upgrades would not play with opengl2 so plasma would no longer run.
> > Downgrading to testing, due to partial removal from the repos, proved
> > impossible. No more means to file bugs, either!
> > 
> > So I uninstalled them, went back to Nouveaux (which I might even prefer).
> > Plasmashell is unstable, crashes and restarts, and multiple session will
> > not work. Could live the a single-session if that be stable.
> > 
> > There had been problems with firefox in nouveaux last year.
> > 
> > What to do about all this?
> 
> Show us output from 'lspci | grep VGA'
> 
> If output includes 6150SE, try adding nouveau.config=NvMSI=0 to
> kernel cmdline.

01:00.0 VGA compatible controller: NVIDIA Corporation NV44 [GeForce 6200 
TurboCache] (rev a1)

so no 6150SE.
Note that one of the "new problems" is that when I attempt to run a second KDE 
plasma  session, the system hangs with NMI watchdog warnings.

> 
> Show us output from 'inxi -Fz'
Do  not have an inxi
> 
> Show us /var/log/Xorg.0.log
attached.

> Ensure all traces of NVidia driver are purged, including
> /etc/X11/xorg.conf which for most people with most gfxchips using
> FOSS drivers has not been necessary for several Debian generations.

No xorg.conf, as said, no longer needed or relevant.

> With proprietary NVidia driver never having been installed, lsmod
> output should resemble the following with legacy geforce gfxcard:
> 
> button 12944  1 nouveau
> drm   249998  5 ttm,drm_kms_helper,nouveau
> drm_kms_helper 49210  1 nouveau
> i2c_algo_bit   12751  1 nouveau
> i2c_core   46012  5
No 'core' entry.
> drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau mxm_wmi   
> 12515  1 nouveau
> nouveau  1122508  2
> ttm77862  1 nouveau
> video  18096  1 nouveau
> wmi17339  2 mxm_wmi,nouveau
> 
> Ensure kernel cmdline does not include nomodeset.
> 
Nomodeset. Once used this for a boot=time which between nvidia and nouveau. I 
had to test that to swap in and  out xorg.conf versions but might  wish to now 
attempt such magic by swapping in and out the nouveau blacklist file. If I had 
working nvidia drivers.

> Ensure nothing to do with nouveau is blacklisted.
> 
Removed several copies of that file.

> If a thorough nvidia purge is insufficient, you might try purging
> xserver-xorg-video-nouveau. In Debian Testing and Unstable, this
> should cause use of Xorg's built-in modesetting driver. See:
> http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Int
> el-DDX

[19.794] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[19.794] X Protocol Version 11, Revision 0
[19.794] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[19.794] Current Operating System: Linux dovidhalevi 4.7.0-1-amd64 #1 SMP Debian 4.7.6-1 (2016-10-07) x86_64
[19.794] Kernel command line: BOOT_IMAGE=Linux-4.7.0-1 ro root=UUID=d14ae79d-fd96-43d5-83b0-0bbbdd831196 quiet
[19.795] Build Date: 06 September 2016  01:32:44PM
[19.795] xorg-server 2:1.18.4-2 (https://www.debian.org/support) 
[19.795] Current version of pixman: 0.34.0
[19.795] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[19.795] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[19.795] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 10 09:45:23 2016
[19.916] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[20.071] (==) No Layout section.  Using the first Screen section.
[20.071] (==) No screen section available. Using defaults.
[20.071] (**) |-->Screen "Default Screen Section" (0)
[20.071] (**) |   |-->Monitor ""
[20.094] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[20.094] (==) Automatically adding devices
[20.094] (==) Automatically enabling devices
[20.094] (==) Automatically adding GPU devices
[20.094] (==) Max clients allowed: 256, resource mask: 0x1f
[20.253] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[20.253] 	Entry deleted from font path.
[20.271] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[20.271] (==) ModulePath set to "/usr/lib/xorg/modules"
[20.271] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[20

Re: kernel 4.7.0 and nvidia

2016-10-10 Thread David Baron
On יום ראשון, 9 באוקטובר 2016 17:54:35 IDT Boyan Penkov wrote:
> Hey folks,
> 
> OK, here was the procedure (as a reminder, I’m on stretch, testing):
> 
> — boot into 4.6, verify everything works, purge both 4.7 kernel and 4.7
> headers, purge all nvidia-* (and nvidia-dkms was indeed installed)
> 
> — purge xserver-xorg-video-nvidia
> 
> — install xserver-xorg-xideo-nvidia and nvidia-driver (which pulls in
> nvidia-dmks as a dependency, among others)
> 
> — I’m still booted into 4.6, so watch the install script build nvidia-dmks
> package for 4.6 only.
> 
> — reboot (into the only kernel I have: 4.6), verify all is ok
> 
> — install 4.7 and 4.7 headers.  I observed that the install script and
> post-install hook did not rebuild nvidia-dkms for 4.7
> 
> — reboot into 4.7  and everything works.
> 
> So, to wrap up: I’m happy for now, but I clearly don’t understand something
> about how nvidia-dmks built for 4.6 also functions on 4.7  Did we get lucky
> here, or do we need a bug filed to get the post-install script to check
> what kernels are there and build the kms accordingly?
> 
> Thanks for your individual help off-list as well.
> 
> Cheers!
> --
> Boyan Penkov
> www.boyanpenkov.com
> 
> > On Oct 6, 2016, at 1:34 PM, Pascal Obry  wrote:
> > 
> > Le jeudi 06 octobre 2016 à 08:55 +0200, gianluca a écrit :
> >> Are the opensource nouveau drivers so bad, so you need closed-source
> >> blob??? If so, that's your choice. But do not ask why something is
> >> not working as execpted if you upgrade something on the kernel-side.
> > 
> > You may also say this without being harsh.
> > 
> > A possibility (and that's my case) is that I'm using NVIDIA proprietary
> > driver as I need OpenCL support and AFAIK there is no OpenCL support
> > with the Nouveau driver.
> > 
> > Anyway on my side I'm also on the 4.7 kernel (Debian/sid) and have no
> > problem with the dkms nvidia package.
> > 
> > Cheers,

With legacy-304xx, did not build for the 4.6 and what was built for 4.7 did 
not work! Impossible to go back to testing which did work :-(
These packages are off Debian, it seems.



Re: Unsubscribing in order to killfile one individual. Was: Re: WARNING! New Perl/Perl-base upgrade removes 141 Sid/Unstable packages

2016-10-10 Thread Joe
On Sun, 9 Oct 2016 21:11:07 -0400 (EDT)
Bob Bernstein  wrote:

> On Mon, 10 Oct 2016, Lisi Reisz wrote:
> 
> > Why not just killfile me and go on reading everyone else?  
> 
> Umm...cuz he doesn't know how to do that? Perhaps?
> 
> One thing's fer sure, he's giving the time-honored tradition of 
> killfiles a bad name!
> 

He's right though, isn't he? The wheel which squeaks, gets the oil.
Without complaints, things improve slowly, if at all.

A formal complaint about a piece of software is the bug report, but
much of the time, things go wrong and there is insufficient data or
reproducibility to waste developers' time with an incomplete report.
Just about the only thing to do then is to moan about it publicly.

If it's finger trouble, you find that out very quickly. If nobody
replies, you have something peculiar to your own system, or at least,
not widespread. Live with it. If there's a chorus of 'yes, I've got
that too, but I didn't like to moan', then enough collective data may
surface to make a bug report practical, or at least to come to the
notice of one of the developers, who may be able to shed further light.

The alternatives of putting up with a problem in silence, or going
[back] to Windows, are not optimal.

As for fixing the problem yourself, you are either:
a) a systems programmer, but you probably knew that already, or
b) a user, who could learn enough to contribute usefully in a year or
two, if you didn't have a living to earn.

Fixing a bug so it doesn't happen again, and fixing a bug in a way that
doesn't break *anything* else, are two very different things. I have
enough trouble going back to my own (non-system) programming of a year
or more ago, and finding out how it works well enough to change
something without breaking it. It doesn't matter how many comments I
left, I have to get back into the same mindset as when I wrote it,
and I haven't worked out how to achieve that with comments. Details are
easy to see, it's the overall architecture that needs to be understood
fully.

-- 
Joe



Re: Synaptic NMU upload in testing

2016-10-10 Thread Brad Rogers
On Sun, 9 Oct 2016 16:46:18 -0700
Jimmy Johnson  wrote:

Hello Jimmy,

>Brad just wanted to let you know your not the only one, I did a 

Yeah, there's always something.   :-(

WRT that, are you following the thread started by David Baron - "Nvida
Legacy 304 Catastrophe"?  It /may/ prove helpful.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Everything in life should be free, except the bits that belong to me
Selfish Rubbish - Public Image Ltd


pgplqXKuzmtBp.pgp
Description: OpenPGP digital signature


Re: Nvida Legacy 304 Catastrophe

2016-10-10 Thread Brad Rogers
On Mon, 10 Oct 2016 10:07:49 +0300
David Baron  wrote:

Hello David,

>01:00.0 VGA compatible controller: NVIDIA Corporation NV44 [GeForce
>6200 TurboCache] (rev a1)

If that's the card you're using, why are you using the 304 legacy
version of the nVidia drivers?  That card is supported by the latest
driver.  At least that's my understanding from the relevant read.me
in/usr/share/doc/nvidia-drivers.

I'm using that driver myself, albeit with a different card, hence my
having the read.me installed.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
People stare like they've seen a ghost
Titanic (My Over) Reaction - 999


pgpcIKjLedAem.pgp
Description: OpenPGP digital signature


Re: {Solved} Synaptic NMU upload in testing

2016-10-10 Thread Brad Rogers
On Sun, 9 Oct 2016 19:53:27 -0400
kamaraju kusumanchi  wrote:

Hello kamaraju,

>Thanks for the kind words. I also learned about

My pleasure.

>update-apt-xapian-index command. So it is mutually beneficial!

Indeed.   :-)

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
If Adolf Hitler flew in today, they'd send a limousine anyway
(White Man) In Hammersmith Palais - The Clash


pgpMf6EyBLxIS.pgp
Description: OpenPGP digital signature


Re: veeger is infected ...startx again

2016-10-10 Thread Ric Moore

On 10/01/2016 09:40 PM, Jimmy Johnson wrote:

On 10/01/2016 12:49 PM, Ric Moore wrote:

... humans are infecting Veeger. I figured I'd fix the display manager
problem with a clean install.  Here's the fun part that gives me the
giggles: I downloaded the testing DVD to install clean from, whilst
thinking it would be stretch or sid. Best laid plans of mice.

I rebooted upon completion and it went smoothly. I installed my Nvidia
drivers and that went smooth. It was all s stupidly smooth that I
suspected something was wrong. Surprise, my sources list reflected
Jessie, not Stretch or Sid. I  FIXED that. Figuring baby
steps I'd go for Stretch. Long story short. I'm back to the black screen
with itty bitty mouse cursor where I should be logging in.  Synaptic is
also acting up again  with the drop down menus refusing to drop down.


Add the Sid/unstable sources and 'aptitude update' and 'aptitude
safe-upgrade' and you'll be okay ;). Maybe when the Stretch freeze
starts that will be the time to remove Sid to get the next stable system.


I'm fulla pain killers (legitimately prescribed!) so I figure a much
younger, and more agile, mind with figure this out. I'll even buy my
newly found favorite cube-monkey a pizza, as long as the order doesn't
require truffles.


Good luck!


No luck so far and I just updated sid. On initial boot, the video driver 
kicks in, as all the monitors come to life, the harddrive is checked and 
then I get the black screen and mouse cursor which is active and moves 
with movement of the mouse. Buggers. What package should I file a 
bugreport against?? If I log into a terminal and issue "startx", 
everything comes up normally into XFCE4 desktop. Synaptic menus still 
refuse to drop down. Thanks all, Ric

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html



Re: Nvida Legacy 304 Catastrophe

2016-10-10 Thread David Baron
On יום שני, 10 באוקטובר 2016 9:07:33 IDT Brad Rogers wrote:
> On Mon, 10 Oct 2016 10:07:49 +0300
> David Baron  wrote:
> 
> Hello David,
> 
> >01:00.0 VGA compatible controller: NVIDIA Corporation NV44 [GeForce
> >6200 TurboCache] (rev a1)
> 
> If that's the card you're using, why are you using the 304 legacy
> version of the nVidia drivers?  That card is supported by the latest
> driver.  At least that's my understanding from the relevant read.me
> in/usr/share/doc/nvidia-drivers.
> 
> I'm using that driver myself, albeit with a different card, hence my
> having the read.me installed.

~$ nvidia-detect 
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV44 [GeForce 
6200 TurboCache] [10de:0161] (rev a1)

Checking card:  NVIDIA Corporation NV44 [GeForce 6200 TurboCache] (rev a1)
Your card is only supported up to the 304 legacy drivers series.
It is recommended to install the
nvidia-legacy-304xx-driver
package

Along with other documentation I have seen. Would love to use the latest and 
greatest rather than legacy excuses.

Since I uninstalled the 304, maybe send me your documentation.



Re: Nvida Legacy 304 Catastrophe

2016-10-10 Thread Brad Rogers
On Mon, 10 Oct 2016 12:17:58 +0300
David Baron  wrote:

Hello David,

>Since I uninstalled the 304, maybe send me your documentation.

Embarrassing 'egg on face' moment coming up:  I *was* misreading the
documentation.  The file I mentioned has a section detailing what
supported by which drivers.  It's in the legacy 304 section that your
chipset is listed.  I didn't check carefully enough first time round.

My apologies if I got your hopes up.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Loaded like a freight train flyin' like an aeroplane
Nightrain - Guns 'N' Roses


pgpapLhd6y4gV.pgp
Description: OpenPGP digital signature


Re: Nvida Legacy 304 Catastrophe

2016-10-10 Thread deloptes
David Baron wrote:

> Along with other documentation I have seen. Would love to use the latest
> and greatest rather than legacy excuses.

>From my experience with nvidia you have to install the version that supports
your hardware be it legacy or not.

regards



Re: Unsubscribing in order to killfile one individual. Was: Re: WARNING! New Perl/Perl-base upgrade removes 141 Sid/Unstable packages

2016-10-10 Thread Lisi Reisz
On Monday 10 October 2016 09:07:14 Joe wrote:
> On Sun, 9 Oct 2016 21:11:07 -0400 (EDT)
>
> Bob Bernstein  wrote:
> > On Mon, 10 Oct 2016, Lisi Reisz wrote:
> > > Why not just killfile me and go on reading everyone else?
> >
> > Umm...cuz he doesn't know how to do that? Perhaps?
> >
> > One thing's fer sure, he's giving the time-honored tradition of
> > killfiles a bad name!
>
> He's right though, isn't he? The wheel which squeaks, gets the oil.
> Without complaints, things improve slowly, if at all.
>
> A formal complaint about a piece of software is the bug report, but
> much of the time, things go wrong and there is insufficient data or
> reproducibility to waste developers' time with an incomplete report.
> Just about the only thing to do then is to moan about it publicly.
>
> If it's finger trouble, you find that out very quickly. If nobody
> replies, you have something peculiar to your own system, or at least,
> not widespread. Live with it. If there's a chorus of 'yes, I've got
> that too, but I didn't like to moan', then enough collective data may
> surface to make a bug report practical, or at least to come to the
> notice of one of the developers, who may be able to shed further light.
>
> The alternatives of putting up with a problem in silence, or going
> [back] to Windows, are not optimal.
>
> As for fixing the problem yourself, you are either:
> a) a systems programmer, but you probably knew that already, or
> b) a user, who could learn enough to contribute usefully in a year or
> two, if you didn't have a living to earn.
>
> Fixing a bug so it doesn't happen again, and fixing a bug in a way that
> doesn't break *anything* else, are two very different things. I have
> enough trouble going back to my own (non-system) programming of a year
> or more ago, and finding out how it works well enough to change
> something without breaking it. It doesn't matter how many comments I
> left, I have to get back into the same mindset as when I wrote it,
> and I haven't worked out how to achieve that with comments. Details are
> easy to see, it's the overall architecture that needs to be understood
> fully.

I quite agree with the idea that squeaks are needed.  But there is a limit to 
how OFTEN it is useful to say it in the one thread.

Lisi



Re: Unsubscribing in order to killfile one individual. Was: Re: WARNING! New Perl/Perl-base upgrade removes 141 Sid/Unstable packages

2016-10-10 Thread Lisi Reisz
On Monday 10 October 2016 09:07:14 Joe wrote:
> On Sun, 9 Oct 2016 21:11:07 -0400 (EDT)
>
> Bob Bernstein  wrote:
> > On Mon, 10 Oct 2016, Lisi Reisz wrote:
> > > Why not just killfile me and go on reading everyone else?
> >
> > Umm...cuz he doesn't know how to do that? Perhaps?
> >
> > One thing's fer sure, he's giving the time-honored tradition of
> > killfiles a bad name!
>
> He's right though, isn't he? The wheel which squeaks, gets the oil.
> Without complaints, things improve slowly, if at all.
>
> A formal complaint about a piece of software is the bug report, but
> much of the time, things go wrong and there is insufficient data or
> reproducibility to waste developers' time with an incomplete report.
> Just about the only thing to do then is to moan about it publicly.
>
> If it's finger trouble, you find that out very quickly. If nobody
> replies, you have something peculiar to your own system, or at least,
> not widespread. Live with it. If there's a chorus of 'yes, I've got
> that too, but I didn't like to moan', then enough collective data may
> surface to make a bug report practical, or at least to come to the
> notice of one of the developers, who may be able to shed further light.
>
> The alternatives of putting up with a problem in silence, or going
> [back] to Windows, are not optimal.
>
> As for fixing the problem yourself, you are either:
> a) a systems programmer, but you probably knew that already, or
> b) a user, who could learn enough to contribute usefully in a year or
> two, if you didn't have a living to earn.
>
> Fixing a bug so it doesn't happen again, and fixing a bug in a way that
> doesn't break *anything* else, are two very different things. I have
> enough trouble going back to my own (non-system) programming of a year
> or more ago, and finding out how it works well enough to change
> something without breaking it. It doesn't matter how many comments I
> left, I have to get back into the same mindset as when I wrote it,
> and I haven't worked out how to achieve that with comments. Details are
> easy to see, it's the overall architecture that needs to be understood
> fully.

I accepted that analogy too easily.  In this case, the wheel isn't squeaking.  
He dislikes the colour and design of the wheel.

Lisi



Re: veeger is infected ...startx again

2016-10-10 Thread Charlie Kravetz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 10 Oct 2016 05:08:44 -0400
Ric Moore  wrote:

>On 10/01/2016 09:40 PM, Jimmy Johnson wrote:
>> On 10/01/2016 12:49 PM, Ric Moore wrote:  
>>> ... humans are infecting Veeger. I figured I'd fix the display manager
>>> problem with a clean install.  Here's the fun part that gives me the
>>> giggles: I downloaded the testing DVD to install clean from, whilst
>>> thinking it would be stretch or sid. Best laid plans of mice.
>>>
>>> I rebooted upon completion and it went smoothly. I installed my Nvidia
>>> drivers and that went smooth. It was all s stupidly smooth that I
>>> suspected something was wrong. Surprise, my sources list reflected
>>> Jessie, not Stretch or Sid. I  FIXED that. Figuring baby
>>> steps I'd go for Stretch. Long story short. I'm back to the black screen
>>> with itty bitty mouse cursor where I should be logging in.  Synaptic is
>>> also acting up again  with the drop down menus refusing to drop down.  
>>
>> Add the Sid/unstable sources and 'aptitude update' and 'aptitude
>> safe-upgrade' and you'll be okay ;). Maybe when the Stretch freeze
>> starts that will be the time to remove Sid to get the next stable system.
>>  
>>> I'm fulla pain killers (legitimately prescribed!) so I figure a much
>>> younger, and more agile, mind with figure this out. I'll even buy my
>>> newly found favorite cube-monkey a pizza, as long as the order doesn't
>>> require truffles.  
>>
>> Good luck!  
>
>No luck so far and I just updated sid. On initial boot, the video driver 
>kicks in, as all the monitors come to life, the harddrive is checked and 
>then I get the black screen and mouse cursor which is active and moves 
>with movement of the mouse. Buggers. What package should I file a 
>bugreport against?? If I log into a terminal and issue "startx", 
>everything comes up normally into XFCE4 desktop. Synaptic menus still 
>refuse to drop down. Thanks all, Ric

It sounds like GTK3 themes is taking over. I had a similar situation,
by removing all GTK3 themes, I was able to get GTK2 theme installed. It
gave me back those menus and the proper spacing. I am now using
Orangine in Appearance and Kindaker in Window Manager. It works here.

- -- 
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM.   [http://keepingdreams.com]
-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJX+45XAAoJEIqui46mydCACfoH/2VfONKeF/TrTRcMzg3J2i5Z
shB9O2GE0/GXsXqDEqlC6LUXDrELsvmfre1g7mdhSG4xc+XGm1YYjV44EPri9Ant
dQaxOitFWLzELeeDj3Q13GGxRqIEvs+w0h1dGs+PLdf0rDA8RgmE05Z6roas/BJo
K02vDG5T053THNLMO8bp0ZeK8JQH0vawStyXa6YyDIMR93OScNUabIFs558pILNr
4gM2EpX2rpdJ9uLCaef+UFFrG4aaXJQF8UTKXBh4xoelXuQTmSxjOMnaxSVSgD4v
UmTm4ww38noqTOiINU7VNp0iRlmUjbmJex+ABqFIIj+bzhNKnDSNuhpIbCnG2nU=
=8vYi
-END PGP SIGNATURE-


My bash script is missing something - what?

2016-10-10 Thread Richard Owlett
I have a trivial bash script named test.sh which has been marked 
as executable.

Its contents are:

#!/bin/bash
cat /etc/debian_version
mount | grep 'on / '

In a terminal I type:

test.sh

The response is:
bash: test.sh: command not found

I'm using Squeeze with Gnome2 as DE.
What's wrong?
TIA







Re: My bash script is missing something - what?

2016-10-10 Thread Robert Parker
you need to do:
./test.sh
instead.


On Mon, Oct 10, 2016 at 7:54 PM, Richard Owlett  wrote:

> I have a trivial bash script named test.sh which has been marked as
> executable.
> Its contents are:
>
> #!/bin/bash
> cat /etc/debian_version
> mount | grep 'on / '
>
> In a terminal I type:
>
> test.sh
>
> The response is:
> bash: test.sh: command not found
>
> I'm using Squeeze with Gnome2 as DE.
> What's wrong?
> TIA
>
>
>
>
>
>


-- 
Courtier "Sire I have bad news!"
King "Yes, what is it?"
Courtier "The peasants are revolting."
King "Yes they always have been. Now what is the bad news?"


Re: My bash script is missing something - what?

2016-10-10 Thread Richard Owlett

On 10/10/2016 8:00 AM, Robert Parker wrote:

you need to do:
./test.sh
instead.



That just fails differently by responding:

: No such file or directory

I had seen that suggestion before while searching the web - don't 
recall a page reference. At the moment I using 
http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_02_01.html as 
my reference.





On Mon, Oct 10, 2016 at 7:54 PM, Richard Owlett
mailto:rowl...@cloud85.net>> wrote:

I have a trivial bash script named test.sh which has been
marked as executable.
Its contents are:

#!/bin/bash
cat /etc/debian_version
mount | grep 'on / '

In a terminal I type:

test.sh

The response is:
bash: test.sh: command not found

I'm using Squeeze with Gnome2 as DE.
What's wrong?
TIA








--
Courtier "Sire I have bad news!"
King "Yes, what is it?"
Courtier "The peasants are revolting."
King "Yes they always have been. Now what is the bad news?"




Re: My bash script is missing something - what?

2016-10-10 Thread Lars Noodén
On 10/10/2016 04:10 PM, Richard Owlett wrote:
> On 10/10/2016 8:00 AM, Robert Parker wrote:
>> you need to do:
>> ./test.sh
>> instead.
>>
> 
> That just fails differently by responding:
> 
> : No such file or directory

Where ever the script is, it does have to be in the $PATH or else you
must run it using including a relative or absolute path to its location.

About your error message "bash: test.sh: command not found", you might
try putting the full paths to mount and grep in your script.  Or else
explicitly set the $PATH variable to something useful at the beginning
of the script.

If that was not it, you can use the set -x option with bash to trace the
script's actions.

#!/bin/bash -x

That prints out each line as it will be run just before it is actually
run, to see what precisely is causing the failure.

Regards,
Lars



Re: My bash script is missing something - what?

2016-10-10 Thread Robert Parker
1. You have to be in the directory where the script resides.
2. Then:
chmod +x test.sh
3. Then:
./test.sh


On Mon, Oct 10, 2016 at 8:10 PM, Richard Owlett  wrote:

> On 10/10/2016 8:00 AM, Robert Parker wrote:
>
>> you need to do:
>> ./test.sh
>> instead.
>>
>>
> That just fails differently by responding:
>
> : No such file or directory
>
> I had seen that suggestion before while searching the web - don't recall a
> page reference. At the moment I using http://tldp.org/LDP/Bash-Begin
> ners-Guide/html/sect_02_01.html as my reference.
>
>
>
>> On Mon, Oct 10, 2016 at 7:54 PM, Richard Owlett
>> mailto:rowl...@cloud85.net>> wrote:
>>
>> I have a trivial bash script named test.sh which has been
>> marked as executable.
>> Its contents are:
>>
>> #!/bin/bash
>> cat /etc/debian_version
>> mount | grep 'on / '
>>
>> In a terminal I type:
>>
>> test.sh
>>
>> The response is:
>> bash: test.sh: command not found
>>
>> I'm using Squeeze with Gnome2 as DE.
>> What's wrong?
>> TIA
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Courtier "Sire I have bad news!"
>> King "Yes, what is it?"
>> Courtier "The peasants are revolting."
>> King "Yes they always have been. Now what is the bad news?"
>>
>
>


-- 
Courtier "Sire I have bad news!"
King "Yes, what is it?"
Courtier "The peasants are revolting."
King "Yes they always have been. Now what is the bad news?"


Re: My bash script is missing something - what?

2016-10-10 Thread Greg Wooledge
On Mon, Oct 10, 2016 at 08:10:33AM -0500, Richard Owlett wrote:
> On 10/10/2016 8:00 AM, Robert Parker wrote:
> >you need to do:
> >./test.sh
> >instead.
> >
> 
> That just fails differently by responding:
> 
> : No such file or directory

Carriage return.  Did you edit this script with a Microsoft Windows
program, perhaps?  The shebang line (#!/bin/bash) probably ends with
a carriage return + line feed, instead of just a line feed.



Re: My bash script is missing something - what?

2016-10-10 Thread Thomas Schmitt
Hi,

Richard Owlett wrote:
> > >  bash: test.sh: command not found

Robert Parker wrote:
> > you need to do:./test.sh

Richard Owlett wrote:
> That just fails differently by responding:
> : No such file or directory
> At the moment I using
>   http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_02_01.html

It states
  "If you did not put the scripts directory in your PATH, and . (the
   current directory) is not in the PATH either, you can activate the
   script like this:

 ./script_name.sh 
  "

So on the first hand it was about the environment variable named "PATH".
Do

  echo $PATH

to get a list of directories where programs will be found automatically.
The directory paths are separated by ':' characters. E.g.

  /usr/local/bin:/usr/bin:/usr/local/games:/usr/games:/home/thomas/bin

--

But what does now prevent proper execution ?

I tested the script as shown by you. It works and says

  8.X
  /dev/sdaY on / type ext4 (rw,noatime,discard,errors=remount-ro,data=ordered)

(with X and Y being private numbers. :))

So this must be some flaw hidden from the human eye and copy+paste.

Be so kind and let program "od" show the bytes of your script.

  od -c test.sh

For me it says

  000   #   !   /   b   i   n   /   b   a   s   h  \n   c   a   t
  020   /   e   t   c   /   d   e   b   i   a   n   _   v   e   r   s
  040   i   o   n  \n   m   o   u   n   t   |   g   r   e   p
  060   '   o   n   /   '  \n  \n
  072

This should show us any CarriageReturn characters, which Greg suspects
to be to blame.


Lars Norden wrote:
> #!/bin/bash -x

Good proposal, too.
(I would have proposed command

   set -x

as second line of the script.)


Have a nice day :)

Thomas



Re: My bash script is missing something - what?

2016-10-10 Thread Nicolas George
Le nonidi 19 vendémiaire, an CCXXV, Greg Wooledge a écrit :
> > That just fails differently by responding:
> > 
> > : No such file or directory
> 
> Carriage return.  Did you edit this script with a Microsoft Windows
> program, perhaps?  The shebang line (#!/bin/bash) probably ends with
> a carriage return + line feed, instead of just a line feed.

I had the same diagnosis. Note that modern shells print a more useful
diagnosis:

execve("/tmp/foo.sh", ["/tmp/foo.sh"], [/* 45 vars */]) = -1 ENOENT (No such 
file or directory)
open("/tmp/foo.sh", O_RDONLY|O_NOCTTY)  = 3
read(3, "#!/bin/sh\r\n", 64)= 11
close(3)= 0
ioctl(2, TCGETS, {B38400 opost isig icanon echo ...}) = 0
write(2, "zsh:1: /tmp/foo.sh: bad interpreter: /bin/sh^M: no such file or 
directory\n", 74) = 74
exit_group(127) = ?

-- 
  Nicolas George


signature.asc
Description: Digital signature


Re: My bash script is missing something - what?

2016-10-10 Thread Greg Wooledge
On Mon, Oct 10, 2016 at 04:10:22PM +0200, Nicolas George wrote:
> Le nonidi 19 vendémiaire, an CCXXV, Greg Wooledge a écrit :
> > > That just fails differently by responding:
> > > 
> > > : No such file or directory
> > 
> > Carriage return.  Did you edit this script with a Microsoft Windows
> > program, perhaps?  The shebang line (#!/bin/bash) probably ends with
> > a carriage return + line feed, instead of just a line feed.
> 
> I had the same diagnosis. Note that modern shells print a more useful
> diagnosis:
> 
> execve("/tmp/foo.sh", ["/tmp/foo.sh"], [/* 45 vars */]) = -1 ENOENT (No such 
> file or directory)
> open("/tmp/foo.sh", O_RDONLY|O_NOCTTY)  = 3
> read(3, "#!/bin/sh\r\n", 64)= 11
> close(3)= 0
> ioctl(2, TCGETS, {B38400 opost isig icanon echo ...}) = 0
> write(2, "zsh:1: /tmp/foo.sh: bad interpreter: /bin/sh^M: no such file or 
> directory\n", 74) = 74
> exit_group(127) = ?

Actually, I'm going to change my diagnosis slightly.  The shebang is fine,
but the "cat /etc/debian_version" line has a carriage return at the end.
The error message is coming from cat.

If the shebang is wrong, bash (as interactive shell) prints:

bash: ./foo: /bin/bash^M: bad interpreter: No such file or directory

which is very close to your zsh message.  But putting the carriage return
on the cat command gives:

wooledg@wooledg:~$ ./foo
: No such file or directory

which is really:

wooledg@wooledg:~$ ./foo 2>&1 | less
cat: /etc/debian_version^M: No such file or directory

How the original poster ended up with a script with an extra carriage
return on just *one* line, rather than every line, is a mystery to me.



Re: Nvida Legacy 304 Catastrophe

2016-10-10 Thread David Baron
On יום שני, 10 באוקטובר 2016 11:25:42 IDT Brad Rogers wrote:
> On Mon, 10 Oct 2016 12:17:58 +0300
> David Baron  wrote:
> 
> Hello David,
> 
> >Since I uninstalled the 304, maybe send me your documentation.
> 
> Embarrassing 'egg on face' moment coming up:  I *was* misreading the
> documentation.  The file I mentioned has a section detailing what
> supported by which drivers.  It's in the legacy 304 section that your
> chipset is listed.  I didn't check carefully enough first time round.
> 
> My apologies if I got your hopes up.

Tried it before getting this. Simply did not work
Going back to nouveau hung up very quickly
So reinstalled sid legacy-304xx. Compiled this time (not for -rt but this is 
known).
My kdm splash screen resolution bollixed up. Had to redo all my desktops. Big 
pain. Have to resize all my fonts as well.

Otherwise, after a day wasted, working again.



Neuinstallation Debian 8.6

2016-10-10 Thread Alfons Grunenberg
Sehre geehrte Damen und Herrn,
ich bin seit Jahren ein Nutzer von Linux. Ich bin 57 Jahre und habe wenig
Kenntnisse in der manuellen Einstellung und Anpassung.
Ich habe mich vor Wochen entschlossen Debian Neu und unter ausschließlicher
Nutzung einer 1TB Festplatte  zu nutzen. Verschieden Installationsversuche
erst mit Jessie 8.5 jetzt mit 8.6 haben keinen Erfolg gebracht. Alle
scheiterten an der Automatik. Wie so ich bisher meine,

an grub2, der alleinigen Installation,
an Spiegelserver, konnte keine Verbindung herstellen (damit die securitis
update und upgrade) nicht auflösen, da auch keine Netzwerkverbindung
hergestellt werden kann und
im wichtigsten an xinit bzw. startx keine Herstellung der grafischen
Oberfläche.

Ich habe es in mehren Variationen versucht. Meine derzeitige und letzte die
Installation von der live Debian 8.6. amd64

Da ich nicht gänzlich aufgeben möchte, wende ich mich vertrauensvoll an Sie
und erhoffe Hilfe zur Herstellung der Nutzungsfähigkeit.

Vielen Dank.
---
Welche Fragen haben Sie zu nächst.?


Re: Nvida Legacy 304 Catastrophe

2016-10-10 Thread Hans
> My kdm splash screen resolution bollixed up. Had to redo all my desktops.
> Big pain. Have to resize all my fonts as well.
> 
The Windowmanagers settings are changed, when using nouveau instead of the 
prprietrary nvidia driver. This is, what I found out. However, same, when you 
now reuse the nouveau driver.

In case, the debian driver fails, or will be sometimes removed from the repo 
(as this is done for my old GF5700Ultra Nvidia card), you could try the 
drivers from the nvidia site. Before using them, remove all debian-nvidia 
stuff!

However, it may be, that those drivers cannot be build any more, like it is 
with legacy drivers for my old 5700Ultra. Then you are lost! 

Good luck!

Hans




PROGRESS - was [Re: My bash script is missing something - what?]

2016-10-10 Thread Richard Owlett

On 10/10/2016 8:21 AM, Greg Wooledge wrote:

On Mon, Oct 10, 2016 at 08:10:33AM -0500, Richard Owlett wrote:

On 10/10/2016 8:00 AM, Robert Parker wrote:

you need to do:
./test.sh
instead.



That just fails differently by responding:

: No such file or directory


Carriage return.  Did you edit this script with a Microsoft Windows
program, perhaps?  The shebang line (#!/bin/bash) probably ends with
a carriage return + line feed, instead of just a line feed.


You were on the right track.
My editor was gedit under Squeeze.
*HOWEVER*, as my original was saved to a flash drive that I also 
use to transfer information to/from my Windows machines, I had 
saved with Windows' line endings ;/


It now, like the proverbial child, it does what I _told_ it to do 
but not quite what I _wanted_ it to do.


1. What Debian oriented Bash Tutorial should I be reading?
2. What is a clean/neat/??? way to double-click on the file name 
and have it:

 open a terminal window [currently it prompts rather than do]
 run the script
 have window remain open until explicitly dismissed
  [I approximate the last with a "read trashvariable" as 
last line.]
3. As written each line appears in the window followed by 
response on the next line.

  Inelegant ;<

Thanks for all the responses.





Re: Neuinstallation Debian 8.6

2016-10-10 Thread Hans
Am Montag, 10. Oktober 2016, 16:25:03 CEST schrieb Alfons Grunenberg:
> Sehre geehrte Damen und Herrn,
Lieber Alfons, 

bitte beachte, daß dies eine englischsprachige Liste ist. Ich empfehle Dir 
daher Deine Anfrage entweder auf Englisch zu wiederholen, oder in der 
deutschsprachigen Liste zu fragen (debian-user-ger...@debian.org)

Dear Alfons, 
please note, this is an English talking list. I suggest, to repeat your 
Question either in English, or asking in a German speaking list (debian-user-
ger...@debian.org)
> ich bin seit Jahren ein Nutzer von Linux. Ich bin 57 Jahre und habe wenig
> Kenntnisse in der manuellen Einstellung und Anpassung.
> Ich habe mich vor Wochen entschlossen Debian Neu und unter ausschließlicher
> Nutzung einer 1TB Festplatte  zu nutzen. Verschieden Installationsversuche
> erst mit Jessie 8.5 jetzt mit 8.6 haben keinen Erfolg gebracht. Alle
> scheiterten an der Automatik. Wie so ich bisher meine,
> 
Vielleicht kannst Du die Festplatte aufteilen, es ist immer eine gute Idee, 
freien Plattenplatz extra zu haben.

Maybe you can split the hard drive. It always a good idea, to have an extra 
free space.
> an grub2, der alleinigen Installation,
> an Spiegelserver, konnte keine Verbindung herstellen (damit die securitis
> update und upgrade) nicht auflösen, da auch keine Netzwerkverbindung
> hergestellt werden kann und

Versuch mit Netzwerkkabel, entweder mit fester IP oder DHCP. Prüfe, ob Deine 
Netzwerkkarte unterstützt wird. Möglicherweise nutze nur für die Installation 
eine externe Karte.  Vielleicht kannst Du auch Debian testing installieren 
(neuerer Kernel, bessere Hardwareunterstützung)

Try with a cable, either with a static IP or via DHCP. Check, if your 
Networkcard is supported. Possibly use an external card just for installation. 
Maybe you can  install debian testing (more newer kernel, better hardware 
support))
> im wichtigsten an xinit bzw. startx keine Herstellung der grafischen
> Oberfläche.
> 
Das kommt später! Poste bei der nächsten Anfrage Deine genaue Hardware. 

This comes later. Post your exact hardware at next request.

> Ich habe es in mehren Variationen versucht. Meine derzeitige und letzte die
> Installation von der live Debian 8.6. amd64
> 
> Da ich nicht gänzlich aufgeben möchte, wende ich mich vertrauensvoll an Sie
> und erhoffe Hilfe zur Herstellung der Nutzungsfähigkeit.

Siehe oben.

See above.


> 
> Vielen Dank.
> 
> --- Welche
> Fragen haben Sie zu nächst.?

Best regards

Hans



Re: PROGRESS - was [Re: My bash script is missing something - what?]

2016-10-10 Thread Greg Wooledge
On Mon, Oct 10, 2016 at 09:58:44AM -0500, Richard Owlett wrote:
> 1. What Debian oriented Bash Tutorial should I be reading?

http://mywiki.wooledge.org/BashGuide is decent.  However, I might be
slightly biased.



Re: PROGRESS - was [Re: My bash script is missing something - what?]

2016-10-10 Thread Nicolas George
Le nonidi 19 vendémiaire, an CCXXV, Richard Owlett a écrit :
> 1. What Debian oriented Bash Tutorial should I be reading?

My first tutorial advice: do not do bash. I advise to do either or both of:
learn standard sh for portable scripts and for more advanced scripting learn
a modern shell less encumbered by backward compatibility with Bourne shell
misfeatures than bash.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature


Re: Neuinstallation Debian 8.6 [Update]

2016-10-10 Thread Hans
Correction

NOT: debian-user-ger...@debian.org

correct is:

debian-user-ger...@lists.debian.org

Sorry for that!

Happy hacking

Hans 




Debian Jessie !

2016-10-10 Thread Kunal Gupta
Hi Team,


For Debian Jessie 8.4 on XenServer having 10 or more CPUS crash while under 
stress and VM’s will never boot having 4 interface combination of 10 CPUS or 
more.

I suspect crash thing has been fixed in 8.6 (which I am still testing) any 
workaround || cause

Thoughts for the same will appreciated.


Thanks,
Kunal


Re: PROGRESS - was [Re: My bash script is missing something - what?]

2016-10-10 Thread Richard Owlett

On 10/10/2016 10:01 AM, Greg Wooledge wrote:

On Mon, Oct 10, 2016 at 09:58:44AM -0500, Richard Owlett wrote:

1. What Debian oriented Bash Tutorial should I be reading?


http://mywiki.wooledge.org/BashGuide is decent.


Now bookmarked. Neglected to do so last time I was looking.


 However, I might be slightly biased.


Lack of bias can be overrated ;/
P.S. FAQ65 points in useful direction for one of my sub-questions.



Re: PROGRESS - was [Re: My bash script is missing something - what?]

2016-10-10 Thread Richard Owlett

On 10/10/2016 10:04 AM, Nicolas George wrote:

Le nonidi 19 vendémiaire, an CCXXV, Richard Owlett a écrit :

1. What Debian oriented Bash Tutorial should I be reading?


My first tutorial advice: do not do bash. I advise to do either or both of:
learn standard sh for portable scripts and for more advanced scripting learn
a modern shell less encumbered by backward compatibility with Bourne shell
misfeatures than bash.



As my first programming course preceded Mr. Torvalds' birth, old 
tools and I share some underlying assumptions. Besides one of my 
projects requires dash ;/






Re: My bash script is missing something - what?

2016-10-10 Thread songbird
Richard Owlett wrote:
> I have a trivial bash script named test.sh which has been marked 
> as executable.
> Its contents are:
>
> #!/bin/bash
> cat /etc/debian_version
> mount | grep 'on / '
>
> In a terminal I type:
>
> test.sh
>
> The response is:
> bash: test.sh: command not found
>
> I'm using Squeeze with Gnome2 as DE.
> What's wrong?
> TIA

  also remember that test itself is a builtin
or binary on some systems.

  you may be running on thing and thinking
you are running another.

  in this particular case with the .sh 
extension you are safe, but forget that
once and ...


  songbird



Re: My bash script is missing something - what?

2016-10-10 Thread Greg Wooledge
On Mon, Oct 10, 2016 at 11:51:37AM -0400, songbird wrote:
> Richard Owlett wrote:
> > I have a trivial bash script named test.sh which has been marked 
> > as executable.

>   also remember that test itself is a builtin
> or binary on some systems.

It's required by POSIX, so it will be a command on *every* system.
Whether it's a shell builtin is not specified, but every modern shell
makes it a builtin -- even dash.

>   you may be running on thing and thinking
> you are running another.
> 
>   in this particular case with the .sh 
> extension you are safe, but forget that
> once and ...

Yes, this is excellent advice.  After being bitten by this once or twice
in my early Unix years, I stopped making commands called "test" and made
commands called "foo", "bar", "foobar", etc.



Re: PROGRESS - was [Re: My bash script is missing something - what?]

2016-10-10 Thread Peter Hillier-Brook
On 10/10/16 16:46, Richard Owlett wrote:
> On 10/10/2016 10:04 AM, Nicolas George wrote:
>> Le nonidi 19 vendémiaire, an CCXXV, Richard Owlett a écrit :
>>> 1. What Debian oriented Bash Tutorial should I be reading?
>>
>> My first tutorial advice: do not do bash. I advise to do either or
>> both of:
>> learn standard sh for portable scripts and for more advanced scripting
>> learn
>> a modern shell less encumbered by backward compatibility with Bourne
>> shell
>> misfeatures than bash.
>>
> 
> As my first programming course preceded Mr. Torvalds' birth, old tools
> and I share some underlying assumptions. Besides one of my projects
> requires dash ;/

Ignoring your youth, you need to precede your script with a valid path
such as './' :-)



Re: PROGRESS - was [Re: My bash script is missing something - what?]

2016-10-10 Thread Greg Wooledge
On Mon, Oct 10, 2016 at 05:19:34PM +0100, Peter Hillier-Brook wrote:
> Ignoring your youth, you need to precede your script with a valid path
> such as './' :-)

He did.



ifconfig question (recovered from hijacked thread )

2016-10-10 Thread Anthony Baldwin



On 10/09/2016 04:23 PM, rhkra...@gmail.com wrote:

I'm not the OP, and I'm sort of piggybacking and going somewhat (or a lot?)
OT, but I am curious about how old inet4 (right term?) and the new inet6
addresses interact.

When I do ifconfig, I see that eth0 has both a 32 bit (e.g., 192.168.1.19) and
an inet6 address assigned.

Can anybody point me to a fairly short document that explains things like
which gets used under what circumstances, does one have precedence over the
other, do they both use DNS, and similar things which might let me make sense
of the situation?


Don't hijack another thread, send a new mail with an appropriate subject 
line like the one on this message. That way you're more likely to get 
the help you need, and it's just proper list edicate.


Good luck
tony (OP of the thread you tried to hijack)


--
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT



Re: Recommendation: Backup system

2016-10-10 Thread Celejar
On Mon, 3 Oct 2016 10:48:57 +0100
Jonathan Dowland  wrote:

> On Sat, Oct 01, 2016 at 11:37:31AM +0200, mo wrote:
> > Make a long story short:
> > Have you guys a recommendation for me?
> > Is there a specific application you use for your backups guys?
> 
> rdiff-backup[1]. I don't know what your NAS is, whether it's an off-the-shelf
> thing or a DIY system, but I tend to initiate the backups on my NAS (which is
> a Debian-powered mini itx PC). You can initiate from the clients instead if
> you prefer.
> 
> rdiff-backup is, conceptually, quite similar to the level of detail you are
> working at with your script, so it should be easy to get working. I'd also
> consider looking at Obnam[2], and I'd avoid rsnapshot if I were you (it
> falls over with large quantities of files, such as mailboxes, and rdiff-backup
> basically does the same job but better).

Interesting, thanks. I've been using rsnapshot for years, and am
basically satisfied with it, although the performance when run on my
T61 laptop (backing up to a (slow) USB external disk) is indeed painful
(I do have largeish Maildirs). [Interestingly, when run on my ARM
(Kirkland) NAS, pulling from the laptop over ethernet / wifi,
performance seems much better ...]

One thing I really like about rsnapshot is how the backups are all
stored just as the files themselves, without any special formats, and
can therefore be inspected / restored from using just the ordinary
filesystem tools.

A number of years ago I looked at rdiff-backup, but dropped it due to
suspicions of the code quality: the project seemed to be dead, and even
significant bugs were being ignored:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623336
https://lists.debian.org/debian-user/2012/10/msg00182.html

I see that you, too, have a report that's been ignored for more than 5
years ;)

Am I being unreasonable? You are certainly more of an expert than I - I
suppose you find that it is quality software, and better than
rsnapshot, despite basically being dead?

Celejar



Re: My bash script is missing something - what?

2016-10-10 Thread gricketson
On 2016-10-10 10:57, Greg Wooledge wrote:
> On Mon, Oct 10, 2016 at 11:51:37AM -0400, songbird wrote:
>> Richard Owlett wrote:
>> > I have a trivial bash script named test.sh which has been marked
>> > as executable.
> 
>>   also remember that test itself is a builtin
>> or binary on some systems.
> 
> It's required by POSIX, so it will be a command on *every* system.
> Whether it's a shell builtin is not specified, but every modern shell
> makes it a builtin -- even dash.
> 
>>   you may be running on thing and thinking
>> you are running another.
>>
>>   in this particular case with the .sh
>> extension you are safe, but forget that
>> once and ...
> 
> Yes, this is excellent advice.  After being bitten by this once or twice
> in my early Unix years, I stopped making commands called "test" and made
> commands called "foo", "bar", "foobar", etc.
This is a very good point, and one example on Debian Wheezy:
Look at /usr/bin/test
and see 
'man test'
or 
'info coreutils 'test invocation''
---
http://elchanate.org/



Re: Unsubscribing in order to killfile one individual. Was: Re: WARNING! New Perl/Perl-base upgrade removes 141 Sid/Unstable packages

2016-10-10 Thread Joe
On Mon, 10 Oct 2016 12:20:22 +0100
Lisi Reisz  wrote:


> 
> I accepted that analogy too easily.  In this case, the wheel isn't
> squeaking. He dislikes the colour and design of the wheel.
> 

Or perhaps it has been squeaking for so long that nobody hears it any
more. Aptitude does a great job of routine upgrades, but if I've left
an unstable for a month or more without upgrading, I wouldn't consider
using it, it doesn't deal gracefully with hundreds of upgrades.

-- 
Joe



Re: Partial Success [was: Re: Problems with upgrade from Wheezy to Jessie]

2016-10-10 Thread Hans Kraus

Hi,

Am 09.10.2016 um 23:46 schrieb Brian:

On Sat 08 Oct 2016 at 13:50:19 +0200, Hans Kraus wrote:


after following the propositions of Brian:


dpkg -l | grep fglrx

Lines with "ii" indicate installed packages. Purge and see what a reboot
does.

and Jörg-Volker Peetz:

Hi,

I also saw the other e-mail exchange with Brian where you concluded to

purge all

"fglrx"-related packages. Similarily, there seem to be "nvidia" packages

on your

system. Try

 dpkg -l | grep -i nvidia

Purge them also. Then have a look which xorg-video drivers are left:

 dpkg -l | grep xorg-video

Leave only xserver-xorg-video-radeon on the system.

And have a look if there's still an "glx-alternative" package left, like
glx-alternative-mesa. This could also be purged.


I issued:


[Account of package purging snipped]


Which partially solved my problems. The system is now booting into Gnome
again.


This is a fantastic step forwards. Before you had nothing, now you have
something. Why the original issue occured is a mystery. Why it was cured
is also a mystery.


A problem remains: the contents of the screen (I controlled only text
based ones like Thunderbird) are sometimes overwritten. This happens for
lines where the text is partially overwritten with other text (normally
or skewed) and line backgrounds. The contents are restored if I move the
mouse pointer to the distorted parts.

This looks like a driver issue to me. Is there a better mailing list to
cope with these problems as 'debian-user'?


But now the proposition is very different. We know you cannot have that
much of a driver problem because you can boot into GNOME. But you think
you have. Maybe its so. Let's eliminate GNOME.

Boot and do 'ps ax | grep xinit'. Kill xinit with 'kill process_number'.
Install fvwm and xterm (you can purge them later). Issue the command
'startx'. Check that nothing gnomish is running with 'ps ax | grep gnome.

Start an xterm (right or left click, I forget which). Any problems?
Start iceweasel (firefox) from an xterm. Any problems? Read a few man
pages. Any problems? Play with opening any program on your system. Any
problems? Which program? What are the symptoms?


Sorry, 'ps ax | grep xinit' didn't give any processes. The most similar
to X thing I found was:
=
 1350 tty7 Ssl+   4:14 /usr/bin/Xorg :0 -novtswitch -background 
none -noreset -verbose 3 -auth 
/var/run/gdm3/auth-for-Debian-gdm-ceY7sk/database -seat seat0 -nolisten 
tcp vt7

=
The whole output pf 'ps ax' is enclosed as ps.txt. Two parts of
screenshots with error regions in them are enclosed as err?.png.
I hope that's OK to include small graphics files, but to describe
display problems in text form is a bit awkward (at least to me).

I thought that my problems may be driver related because when I saw such
behaviour on Windows machines the culprit was always the graphics
driver.

Thanks & regards,
Hans

  PID TTY  STAT   TIME COMMAND
1 ?Ss 0:39 /sbin/init
2 ?S  0:00 [kthreadd]
3 ?S  0:24 [ksoftirqd/0]
5 ?S< 0:00 [kworker/0:0H]
7 ?S  4:38 [rcu_sched]
8 ?S  0:00 [rcu_bh]
9 ?S  0:00 [migration/0]
   10 ?S  0:01 [watchdog/0]
   11 ?S  0:01 [watchdog/1]
   12 ?S  0:00 [migration/1]
   13 ?S  0:21 [ksoftirqd/1]
   15 ?S< 0:00 [kworker/1:0H]
   16 ?S  0:01 [watchdog/2]
   17 ?S  0:00 [migration/2]
   18 ?S  0:20 [ksoftirqd/2]
   20 ?S< 0:00 [kworker/2:0H]
   21 ?S  0:01 [watchdog/3]
   22 ?S  0:00 [migration/3]
   23 ?S  0:20 [ksoftirqd/3]
   25 ?S< 0:00 [kworker/3:0H]
   26 ?S  0:01 [watchdog/4]
   27 ?S  0:00 [migration/4]
   28 ?S  0:24 [ksoftirqd/4]
   30 ?S< 0:00 [kworker/4:0H]
   31 ?S  0:01 [watchdog/5]
   32 ?S  0:00 [migration/5]
   33 ?S  0:21 [ksoftirqd/5]
   35 ?S< 0:00 [kworker/5:0H]
   36 ?S< 0:00 [khelper]
   37 ?S  0:00 [kdevtmpfs]
   38 ?S< 0:00 [netns]
   39 ?S  0:00 [khungtaskd]
   40 ?S< 0:00 [writeback]
   41 ?SN 0:00 [ksmd]
   42 ?SN 0:00 [khugepaged]
   43 ?S< 0:00 [crypto]
   44 ?S< 0:00 [kintegrityd]
   45 ?S< 0:00 [bioset]
   46 ?S< 0:00 [kblockd]
   50 ?S  0:00 [kswapd0]
   51 ?S< 0:00 [vmstat]
   52 ?S  0:03 [fsnotify_mark]
   58 ?S< 0:00 [kthrotld]
   60 ?S< 0:00 [ipv6_addrconf]
   62 ?S< 0:00 [deferwq]
  107 ?S  0:00 [scsi_eh_0]
  108 ?S< 0:00 [ata_sff]
  109 ?S  0:00 [khubd]
  110 ?S< 0:00 [scsi_tmf_0]

Re: Unsubscribing in order to killfile one individual. Was: Re: WARNING! New Perl/Perl-base upgrade removes 141 Sid/Unstable packages

2016-10-10 Thread Lisi Reisz
On Monday 10 October 2016 19:04:22 Joe wrote:
> On Mon, 10 Oct 2016 12:20:22 +0100
>
> Lisi Reisz  wrote:
> > I accepted that analogy too easily.  In this case, the wheel isn't
> > squeaking. He dislikes the colour and design of the wheel.
>
> Or perhaps it has been squeaking for so long that nobody hears it any
> more. Aptitude does a great job of routine upgrades, but if I've left
> an unstable for a month or more without upgrading, I wouldn't consider
> using it, it doesn't deal gracefully with hundreds of upgrades.

I accept that.  But I would also suggest that jacks of all trades are usually 
masters of none, and perhaps Aptitude is the wrong tool for you for that 
particular job.

Libre Office does word processing MUCH better than Kwrite.  Does this mean 
that Kwrite is a squeaky tool because it is bad at WP, or does it mean that I 
oughtn't to try to use it for that purpose?  (LO, conversely,is bad at script 
editing, for which I love Kwrite.)

Horses for courses.  If Aptitude is not the ideal tool for everything, that 
doesn't make it a squeaky wheel.  It just means that it shouldn't be used for 
everything.

Lisi



Re: Recommendation: Backup system

2016-10-10 Thread Jonathan Dowland
On Mon, Oct 10, 2016 at 09:32:02AM -0400, Celejar wrote:
> Interesting, thanks. I've been using rsnapshot for years, and am
> basically satisfied with it, although the performance when run on my
> T61 laptop (backing up to a (slow) USB external disk) is indeed painful
> (I do have largeish Maildirs). [Interestingly, when run on my ARM
> (Kirkland) NAS, pulling from the laptop over ethernet / wifi,
> performance seems much better ...]

The first machine where I really had performance problems
with rsnapshot was an ARM-powered Thecus N2100, but that was a pretty
weak CPU from what I recall.

> One thing I really like about rsnapshot is how the backups are all
> stored just as the files themselves, without any special formats, and
> can therefore be inspected / restored from using just the ordinary
> filesystem tools.

That is a nice property, yes. the rdiff-backup format is not quite this,
but is well specified outside of the code (from the last time I looked)
to give me confidence I could pull my files out by hand if I needed to.

I'm not sure if I mentioned it in this thread or not, but I actually began a
third party tool to parse rdiff-backup format backups[1], and there exists
another third party tool to do the same thing[2].

> A number of years ago I looked at rdiff-backup, but dropped it due to
> suspicions of the code quality: the project seemed to be dead, and even
> significant bugs were being ignored:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623336
> https://lists.debian.org/debian-user/2012/10/msg00182.html
> 
> I see that you, too, have a report that's been ignored for more than 5
> years ;)

Yes, that's true. The bug that I remember reporting (haven't looked it back up
to be sure) was that reverting a partial (failed) backup requires some disk
space and so fails if the backup device is full - this is a big problem in
theory, but in practice I'm running my backup jobs as non-root, so there's
always the 5% or so reserved space for root users. So in this situation I
can have the roll-back occur as root.

> Am I being unreasonable? You are certainly more of an expert than I - I
> suppose you find that it is quality software, and better than
> rsnapshot, despite basically being dead?
 
Lack of bug and development activity is certainly a worrying sign of a program
with problems. But development activity naturally dies off if a program does
what it is supposed to do, so it's not always a certainty that it is doomed.
It remains a concern for me, but regardless the tool has worked very well.

[1] https://jmtd.net/software/rdifffs/
[2] https://github.com/rbrito/rdiff-backup-fs

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature


Re: Bluetooh in Debian Jessie

2016-10-10 Thread juan hernandez
Hello, I just added a "non-free" component to /etc/apt/sources.list, the
APT "deb http://http.us.debian.org/debian/ testing main non-free" and then
installed the "firmware-atheros" package.
Thank you,

Best

2016-10-07 13:29 GMT-06:00 deloptes :

> juan hernandez wrote:
>
> > Hello:
> > I'm using Debian in a Lenovo but I'm unable to using with bluetooth. Any
> > advice?
> > Thank you in advance
> >
> > best.
>
> What does it mean you are unable of using bluetooth?
> What have you tried? do you have some logs?
> Have you tried bluetoothctl and rfkill?
> Is your bluetooth enabled?
>
> regards
>
>


Re: My bash script is missing something - what?

2016-10-10 Thread Tony Baldwin




 Forwarded Message 
Subject: Re: My bash script is missing something - what?
To: Richard Owlett 
References: <57fb8f79.9010...@cloud85.net>
From: Anthony Baldwin 
Message-ID: <3e26c189-eab5-d400-c3c7-5cc1d7321...@gmx.com>
Date: Mon, 10 Oct 2016 13:06:59 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 
Icedove/45.2.0

MIME-Version: 1.0
In-Reply-To: <57fb8f79.9010...@cloud85.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit



On 10/10/2016 08:54 AM, Richard Owlett wrote:

I have a trivial bash script named test.sh which has been marked as
executable.
Its contents are:

#!/bin/bash
cat /etc/debian_version
mount | grep 'on / '

In a terminal I type:

test.sh

The response is:
bash: test.sh: command not found

I'm using Squeeze with Gnome2 as DE.
What's wrong?
TIA



Is it in your $PATH? (i.e in ~/bin, if that is added to your path, or in 
/usr/local/bin, or /usr/bin, etc. I put all my bash (or tcl or python or 
ruby or perl)scripts  in /home/me/bin, which I have added to my $PATH
If the script is not in your path, you will have to cd to the directory 
it is in and do

$ ./test.sh
with that ./

I think you got that answer already,
but, as a side note (just a thought):
you could make this a one-liner, and even make an alias for it in your 
.bashrc,

like
# frp for find root partition
alias  frp = cat /etc/debian_version && mount | grep 'on / '
Then you could simply type frp and get the info you want.
close your terminal and start a new one to use the alias once it's added 
to the .bashrc file, of course)








--
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT



Mail Suspension Warning: Verification For (debian-user@lists.debian.org)

2016-10-10 Thread Email Adminitrator


debian-user@lists.debian.org,




?,?? ?

 




??,???

? 2016


The information contained in this e-mail, including any attachments, is 
intended only for the use of the intended recipient(s) named above and may 
contain confidential or proprietary information of the City of Lebanon's which 
is protected by law from disclosure. If you are not the intended recipient(s), 
please delete this message from your system and contact the sender immediately 
at (417) 532-2156. If you received this message and are not the intended 
recipient(s), you are notified that reading, copying or distributing this 
e-mail is prohibited. No confidentiality or privilege shall be waived or lost 
by any misdirected or unintended transmission.


Re: Recommendation: Backup system

2016-10-10 Thread Dave Thayer
On Mon, Oct 10, 2016 at 10:55:44PM +0100, Jonathan Dowland wrote:
> On Mon, Oct 10, 2016 at 09:32:02AM -0400, Celejar wrote:
> > Am I being unreasonable? You are certainly more of an expert than I - I
> > suppose you find that it is quality software, and better than
> > rsnapshot, despite basically being dead?
>  
> Lack of bug and development activity is certainly a worrying sign of a program
> with problems. But development activity naturally dies off if a program does
> what it is supposed to do, so it's not always a certainty that it is doomed.
> It remains a concern for me, but regardless the tool has worked very well.
> 

It looks like rdiff-backup has a new maintainer as of February 2016, sol1. See
. There may be some progress forthcoming
after all. 

dt

-- 
Dave Thayer / Denver, Colorado USA / d...@thayer-boyle.com 
 Whenever you read a good book, it's like the author is right there, in
 the room talking to you, which is why I don't like to read good books.
 - Jack Handey "Deep Thoughts"



Mail Suspension Warning: Verification For (debian-user@lists.debian.org)

2016-10-10 Thread Email Adminitrator


debian-user@lists.debian.org,




?,?? ?

 




??,???

? 2016


The information contained in this e-mail, including any attachments, is 
intended only for the use of the intended recipient(s) named above and may 
contain confidential or proprietary information of the City of Lebanon's which 
is protected by law from disclosure. If you are not the intended recipient(s), 
please delete this message from your system and contact the sender immediately 
at (417) 532-2156. If you received this message and are not the intended 
recipient(s), you are notified that reading, copying or distributing this 
e-mail is prohibited. No confidentiality or privilege shall be waived or lost 
by any misdirected or unintended transmission.