gmane.linux.suse.opensuse.user

Re: [12.3 64Bit KDE] - Transmageddon Converter Error?

Martti Laaksonen — 2013-04-03T19:07:59

Looks like a dependency problem in transmageddon package:
mlaakson< at >darkside:~> rpm -q transmageddon --requires
/bin/bash
/bin/sh
/bin/sh
gstreamer-plugins-base >= 0.11.0
python-gobject >= 2.21.4
python3
...

So it uses python 3 and should probably require python3-gobject.
python-gobject package is meant for python 2.

Install python3-gobject package and you should be good to go, unless there are 
some other dependency problems lurking in there.


--
Martti

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Carlos E. R. — 2013-04-03T18:50:38

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2013-04-03 at 17:53 +0200, Per Jessen wrote:

:-)

Didn't know there was a named pipe in there :-)


Ah, I did not know that, either.

- -- 
Cheers,
        Carlos E. R.
        (from 12.1 x86_64 "Asparagus" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAlFceggACgkQtTMYHG2NR9WcEQCfWbRnfgLO4vC8hI0bxaLoVWLq
xEIAnj97eZpTDVdSKsFVSs+LTMUQa2jq
=8r3v
-----END PGP SIGNATURE-----

Re: Install 12.3 0n Emachine

Patrick Shanahan — 2013-04-03T18:09:51

* A. den Oudsten <AdenOudsten-42P/b7yZOt0< at >public.gmane.org> [04-03-13 14:06]:

Don't understand not having a fail-safe option, perhaps a botched install!

But, you might try adding "nomodeset" sans parentheses on the kernel
command line at boot.

Install 12.3 0n Emachine

A. den Oudsten — 2013-04-03T18:03:37

My desktop is an Acer emachine
AMD Athlon (tm) II 160 u processor 800,00 MHz x86_64
nVidia Corporation GeForge nForge 430, 2D drive nouveau, 3D drive 
nouveau Gallium(7.11)
RAM 1.7 GiB, Free memory 998.6 MiB (+306,5 MiB Caches), Free swap 2.0 GiB

I installed 12.2 and when I started up I got green diagonal lines on the 
screen. When I started fail safe, no problems.
After installing 12.3 the same, but there was no fail safe mode. 
Re-installing and Resque gave no solution.
KDE Live disk resulted in the same diagonal lines, but with various 
colours!! and no fail safe!!

I was a little bit surprised. Any ideas how to solve this?
Thanks
André den Oudsten

Re: Unexpected dual IP-addresses on NIC

Hans Witvliet — 2013-04-03T17:56:03

-----Original Message-----
From: James Knott <james.knott-bJEeYj9oJeDQT0dZR+AlfA< at >public.gmane.org>
To: SLE <opensuse-stAJ6ESoqRxg9hUCZPvPmw< at >public.gmane.org>
Subject: Re: [opensuse] Unexpected dual IP-addresses on NIC
Date: Wed, 03 Apr 2013 12:15:37 -0400

Koenraad Lelong wrote:

I just checked on my notebook, running 12.3 and don't see anything like 
that.  I just get the one IPv4 address for my WiFi connection. I also 
have 127.0.0.1 for the loopback, as expected.

You might check the content of " /etc/sysconfig/network/ifcfg-eth0 "
for strange things.

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Andrey Borzenkov — 2013-04-03T16:19:24

В Wed, 03 Apr 2013 15:17:00 +0100
Dave Howorth <dhoworth-fDajt2Yx3S8pY9vWkoisglpr/1R2p/CL< at >public.gmane.org> пишет:


Oh. Never noticed it before. Thank you!

Re: 12.3 + ntfs + ext4 + USB3 + different copying speeds

Linda Walsh — 2013-04-03T16:18:26

---
yeah right...
You realize that if it wasn't, you couldn't have synchronized RAID disks.

Try using desktop drives sometime in an LSI controller --
let me know how many 'pass' it's internal validation.

If a disk has an extra few ms of latency compared to other members
of the same array, LSI will kick the disk out as bad.

Re: Unexpected dual IP-addresses on NIC

James Knott — 2013-04-03T16:15:37

I just checked on my notebook, running 12.3 and don't see anything like 
that.  I just get the one IPv4 address for my WiFi connection. I also 
have 127.0.0.1 for the loopback, as expected.

Re: 12.3 + ntfs + ext4 + USB3 + different copying speeds

Linda Walsh — 2013-04-03T16:09:54

---
Are you using the -mmap option?

Do you tell it to skip devices and binary files?
i.e. in your ENV, set :

export GREP_OPTIONS="-D skip --binary-files=without-match"

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Per Jessen — 2013-04-03T15:53:23


You told it to look in there. 

Whenever I grep for something or other, I virtually always use the "find
<specification> | xargs grep" combination.  The xargs can also be
parallelized, a big advantage if you've got multiple cores and many
files.

Re: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]

Per Jessen — 2013-04-03T15:49:33


I don't think so, xargs will die right away.  


Yes, that should work:

find / -type f -print0 | xargs -0 file | \
awk '/Bourne-Again/{print $1}' | \
tr -d ':' | xargs -r grep <something>


Only if some of those shell scripts have quotes in their names, this
will break too.  (second xargs)

Re: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]

Per Jessen — 2013-04-03T15:44:51

`/data/storage_b/cer/cosas/antiguo_cosas_nimrodel__mirar/old_theother/etc/opt/gnome/gconf/gconf.xml.mandantory':

I guess you are finding a filename or a filetype with quotes in it.
Unless you have filenames with quotes in them, just use this tr
instead:

tr -d ':\'"'

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Carlos E. R. — 2013-04-03T14:49:32

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2013-04-03 at 10:26 -0400, Anton Aylward wrote:


:-)

Ah, Dave posted the trick a minute ago :-)


About grep and the Swiss army knife... I'm used to a special "grep" 
version made by Lucent Technologies (previous AT&T") that was named 
"cgrep". It is now available as free (well, actually "Lucent Public 
License"), sometime after the demise of Lucent and the disappearance of 
Bell Labs.

This switch is what made it of particular use to me:

    5ESS Project-Specific Options
        The  following  special-purpose  options  are provided for the convenience of those
        analyzing 5ESS International or Domestic ROP reports.

        -R    Sets window delimiters and other options for 5ESS International  or  Domestic
              ROP  reports.   The  -R option can also be used in conjunction with -nline or
              +nline to output preceding or subsequent ROP reports to the  matched  report,
              or both.  In either case, nline-1 a

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Anton Aylward — 2013-04-03T14:26:17

Carlos E. R. said the following on 04/03/2013 10:03 AM:


Ah, so you want a Swiss army knife?

It reminds me of Rob Pike's "considered harmful" view of what Berkeley
did to 'cat'

I agree with the 'each thing should do one things and only one thing'
approach to tool building.    Not only does it make combining tools
easier - the great power of UNIX is scripting, notable the shell -but
each thing can be proven to be 'correct'.


If you can make this case for grep then you can make it for cat and tr
and many other programs.


Perhaps you want to re-invent one of the mainframe OS's of the 50s and 60s?

http://harmful.cat-v.org/cat-v/unix_prog_design.pdf

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Carlos E. R. — 2013-04-03T14:27:00

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-ID: <alpine.LNX.2.00.1304031625101.21805-60RyU04tjfBYliKd9CYQ7VAUjnlXr6A1< at >public.gmane.org>


On Wednesday, 2013-04-03 at 15:17 +0100, Dave Howorth wrote:




Ha! Didn't see that one. Let's try - huh, no, I deleted that 3 year 
old named pipe. Ok, then:

cer< at >Telcontar:~> grep -D skip fdisk /dev/*
grep: /dev/core: Permission denied
cer< at >Telcontar:~>


I suppose that worked :-)

That's one to put in my book. Never stop learning! :-)


- -- 
Cheers,
        Carlos E. R.
        (from 12.1 x86_64 "Asparagus" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAlFcPDQACgkQtTMYHG2NR9VtowCeIBrh0ACyf+3go+FjzUmfvPn6
h/8AoJJDQxeLnmY9EnbCYdYGQlcm2T7k
=tjMD
-----END PGP SIGNATURE-----

Re: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]

Carlos E. R. — 2013-04-03T14:21:09

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2013-04-03 at 15:56 +0200, Carlos E. R. wrote:



It aborted after 5 minutes:

Telcontar:~ # time nice find /* -type f | xargs file | awk '/Bourne-Again/{print $1}'| tr -d ':' | tee listado_shells | xargs -r grep "mkfs.ext4 -L test_"
xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
find: `/home/cer/.gvfs': Permission denied
find: `standard output': Broken pipe
find: write error

real    5m2.171s
user    0m3.733s
sys     0m21.042s
Telcontar:~ #



I'll put another tee to see where.


Telcontar:~ # time nice find /* -type f | tee listado_total | xargs file | awk '/Bourne-Again/{print $1}'| tr -d ':' | tee listado_shells | xargs -r grep "mkfs.ext4 -L test_"
xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
tee: standard output: Broken pipe
find: `/home/cer/.gvfs': Permission denied
tee: write error

real    0m52.520s
user    0m3.404s
sys     0m10.551s

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Dave Howorth — 2013-04-03T14:17:00

-D ACTION, --devices=ACTION
    If an input file is a device, FIFO or socket, use ACTION to process
it. By default, ACTION is read, which means that devices are read just
as if they were ordinary files. If ACTION is skip, devices are silently
skipped.

What's that then?

Re: Grep crashing [Was: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]]

Carlos E. R. — 2013-04-03T14:03:09

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2013-04-03 at 09:24 -0400, Anton Aylward wrote:


Ok, but the man page does not say how to tell grep not to look inside not 
normal files :-)

Of course, it can be done with a "find" in the line, but not with grep on 
its own.

- -- 
Cheers,
        Carlos E. R.
        (from 12.1 x86_64 "Asparagus" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAlFcNp4ACgkQtTMYHG2NR9UlgwCggHhCzx4uHM8e4nRoURFl0BO3
anIAn2uCTmf1pxkNHQklP46Vxt3cLay9
=1keW
-----END PGP SIGNATURE-----

Re: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]

Carlos E. R. — 2013-04-03T13:56:33

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2013-04-03 at 15:47 +0200, Carlos E. R. wrote:


I have it running for real now. There is a little problem:

cer< at >Telcontar:~> find /* -type f | xargs file | awk '/Bourne-Again/{print $1}'| tr -d ':' | tee listado_shells | xargs -r grep "mkfs.ext4 -L test_"
find: `/boot/lost+found': Permission denied
find: `/data/cripta/root': Permission denied
xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
find: `/data/storage_b/cer/cosas/antiguo_cosas_nimrodel__mirar/old_theother/etc/opt/gnome/gconf/gconf.xml.mandantory': Permission denied


That about the quotes in xargs :-?

And I will have to run it as root to avoid the permission denied errors, 
too.

- -- 
Cheers,
        Carlos E. R.
        (from 12.1 x86_64 "Asparagus" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAlFcNREACgkQtTMYHG2NR9XEsgCeJ7ek9F9r294YbVTQg0vE3ovi
nhQAnjh4WaD9lb3uLSz3EBN2qAVaeOEt
=kz0u
--

Re: Searching for string in many files [Was: 12.3 + ntfs + ext4 + USB3 + different copying speeds]

Carlos E. R. — 2013-04-03T13:47:28

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2013-04-03 at 09:17 -0400, Anton Aylward wrote:


You are right, I googed in the copy-paste. :-o

It works:

cer< at >Telcontar:~> find bin/* -type f | xargs file | awk '/Bourne-Again/{print $1}' | tr -d ':' | xargs -r grep "for i in"
bin/CD-info:for i in  32768,7   32776,32 32808,32 32958,128 33086,128 33214,128 \
cer< at >Telcontar:~>


:-)))

- -- 
Cheers,
        Carlos E. R.
        (from 12.1 x86_64 "Asparagus" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAlFcMvkACgkQtTMYHG2NR9V8LACfT1zFHaK8gBRpJSmubwK+F3mt
EUEAoIJi7UP8G8Isk6bbS0eqy4D6vPW9
=m60H
-----END PGP SIGNATURE-----

Re: DLNA video problem

Bob Williams — 2013-04-03T13:25:21

etc, etc.

Many thanks for this Noel. I can't pretend to understand it yet, but
as I said, more homework needed. As an amateur, hobbyist computer
user, I really appreciate the help provided here by those who have
worked 'in the trade' all their lives.

I also like your point about NAT not providing security after a move
to ipv6 provision, in your reply to Togan.

Bob