[gentoo-user] Re: wayland

2014-07-21 Thread James
Stefan G. Weichinger lists at xunil.at writes:


 Anyone playing with wayland already?

Not yet.
Closely related, is the QT5 approach to start experimenting.

 Maybe even using it as daily driver ?
 I did some steps to compile and use it on my systems ... so far I wasn't
 able to start up gnome 3.12 (~ gnome-shell) with gdm here.
 Is it possible already?

This might help [1] 

 Stefan


[1] http://qt-project.org/wiki/QtWayland

hth,
James




[gentoo-user] Re: Networkmanager on uclibc Gentoo system x86

2014-07-21 Thread James
João Jerónimo joao.jeronimo.89 at gmail.com writes:

 
 Hello.
 
 I installed the uclibc stage3 tarball no a x86 machine (I chose uclibc  
 because the PC has only 256 MB of RAM).

Did you use one of these to install your system?

http://mirror.as24220.net/pub/gentoo/experimental/x86/uclibc/

Also note:

 The i586 CPU (family 5) but it has almost everything that a i686 CPU
(family 6) has. The only CPU instruction that is missing is the NOPL or NOP
Long (means no operation). Now there is a patch available that simulate the
missing instruction in the kernel so that the user space don't know that the
instruction is missing. The program can use the instruction as if there is
nothing missing instead of crashing. The advantage is, the programs that are
compiled for i686 can run on the i586 CPU with this modified Kernel. In
Debian there is also a special optimized C Lib version for i686 CPU's (with
uses cmov instructions). This optimized version of the library works with
the modified Kernel too. For more info's go to 

http://notes.osuv.de/doku.php?id=geode.

hth,
James




[gentoo-user] capturing emerge output

2014-07-21 Thread James
Hello,

I have some very large emerge builds going on
with my /usr/local/portage experiments.

What would folks suggest is the best way to capture the output
from the screen into a file (fancy formating?) as well as being
able see the local builds as they scroll the build out to
the terminal (screen) window (normal emerge results viewed fromt the
terminal session ?

Is there some tools (ebuilds) for such?


Then what tools exist for parsing via a gui.

(yea I still use command line parsing visually but I figure
I ask if there are some fancy tools for an old C hack to
experiment around with..


TIA,
James






Re: [gentoo-user] capturing emerge output

2014-07-21 Thread covici
James wirel...@tampabay.rr.com wrote:

 Hello,
 
 I have some very large emerge builds going on
 with my /usr/local/portage experiments.
 
 What would folks suggest is the best way to capture the output
 from the screen into a file (fancy formating?) as well as being
 able see the local builds as they scroll the build out to
 the terminal (screen) window (normal emerge results viewed fromt the
 terminal session ?
 
 Is there some tools (ebuilds) for such?
 
 
 Then what tools exist for parsing via a gui.
 
 (yea I still use command line parsing visually but I figure
 I ask if there are some fancy tools for an old C hack to
 experiment around with..
 


I use script all the time and just  say--nocolor and --nospinner (syntax
may be off a bit) as well.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com



Re: [gentoo-user] capturing emerge output

2014-07-21 Thread Douglas J Hunley
On Mon, Jul 21, 2014 at 9:54 AM, James wirel...@tampabay.rr.com wrote:

 What would folks suggest is the best way to capture the output
 from the screen into a file (fancy formating?) as well as being
 able see the local builds as they scroll the build out to
 the terminal (screen) window (normal emerge results viewed fromt the
 terminal session ?


sounds like a job for 'tee'


-- 
Douglas J Hunley (doug.hun...@gmail.com)
Twitter: @hunleyd   Web:
about.me/douglas_hunley
G+: http://google.com/+DouglasHunley


Re: [gentoo-user] Re: wayland

2014-07-21 Thread Stefan G. Weichinger
Am 21.07.2014 15:54, schrieb James:
 Stefan G. Weichinger lists at xunil.at writes:
 
 
 Anyone playing with wayland already?
 
 Not yet.
 Closely related, is the QT5 approach to start experimenting.
 
 Maybe even using it as daily driver ?
 I did some steps to compile and use it on my systems ... so far I wasn't
 able to start up gnome 3.12 (~ gnome-shell) with gdm here.
 Is it possible already?
 
 This might help [1] 
 
 Stefan
 
 
 [1] http://qt-project.org/wiki/QtWayland

hmm, thanks ... I am not sure how to apply this ;-)

You suggest that by running QtWayland I might be able to run gnome with
wayland?

S




Re: [gentoo-user] capturing emerge output

2014-07-21 Thread Neil Bothwick
On Mon, 21 Jul 2014 16:54:36 + (UTC), James wrote:

 What would folks suggest is the best way to capture the output
 from the screen into a file (fancy formating?) as well as being
 able see the local builds as they scroll the build out to
 the terminal (screen) window (normal emerge results viewed fromt the
 terminal session ?

Set PORT_LOGDIR in make.conf. This is not the same as the ELOG settings,
it logs the entire output from the ebuild.


-- 
Neil Bothwick

Approx. 1 in 36000 people will break a leg within 3 weeks of reading this
post


signature.asc
Description: PGP signature


[gentoo-user] Re: wayland

2014-07-21 Thread James
Stefan G. Weichinger lists at xunil.at writes:


  Anyone playing with wayland already?

  Not yet.
  Closely related, is the QT5 approach to start experimenting.

  This might help [1] 

  [1] http://qt-project.org/wiki/QtWayland

 hmm, thanks ... I am not sure how to apply this 

Most Desktops will be a while before interacting with Wayland,
let alone supporting it natively, imho. Bloatware like gnome
and KDE will be the last to get QT5, Wayland and a myriad
of new, super_fast, secure desktop toys, imho.

 You suggest that by running QtWayland I might be able to run gnome with
 wayland?

I don't 'gnome' or 'kde' anything anymore. Those bloated, security risks
will be the last ones to support Wayland, imho.

LXQT(5) is way ahead on Wayland, as they already have testing version
of lxqt running on qt5 (grep this list archives for discussions).

LXQt Got Full Support For Qt5. Wayland Support Will Be Soon Added


http://linuxg.net/lxqt-got-full-support-for-qt5-wayland-support-will-be-soon-added/


Best to the site for help, as I'm not on the razor's edge
with LXQT. I'm working on other stuff for a few more weeks..
Skinny (LXQT5) is the new PHAT. Join the revolution. LXQT is up to
13 devs now. Project is 'on fire', so pull up a seat, and get
roasted! 

hth,
James








Re: [gentoo-user] Re: wayland

2014-07-21 Thread Volker Armin Hemmann
Am 21.07.2014 23:40, schrieb James:
 Stefan G. Weichinger lists at xunil.at writes:


 Anyone playing with wayland already?
 Not yet.
 Closely related, is the QT5 approach to start experimenting.
 This might help [1] 
 [1] http://qt-project.org/wiki/QtWayland
 hmm, thanks ... I am not sure how to apply this 
 Most Desktops will be a while before interacting with Wayland,
 let alone supporting it natively, imho. Bloatware like gnome
 and KDE will be the last to get QT5, Wayland and a myriad
 of new, super_fast, secure desktop toys, imho.

 You suggest that by running QtWayland I might be able to run gnome with
 wayland?
 I don't 'gnome' or 'kde' anything anymore. Those bloated, security risks
 will be the last ones to support Wayland, imho.

 LXQT(5) is way ahead on Wayland, as they already have testing version
 of lxqt running on qt5 (grep this list archives for discussions).

 LXQt Got Full Support For Qt5. Wayland Support Will Be Soon Added


 http://linuxg.net/lxqt-got-full-support-for-qt5-wayland-support-will-be-soon-added/


 Best to the site for help, as I'm not on the razor's edge
 with LXQT. I'm working on other stuff for a few more weeks..
 Skinny (LXQT5) is the new PHAT. Join the revolution. LXQT is up to
 13 devs now. Project is 'on fire', so pull up a seat, and get
 roasted! 

 hth,
 James



who told you that 'bloated' buzz word? The same people who told you
about 'the cloud' or 'web 2.0'?





[gentoo-user] Re: capturing emerge output

2014-07-21 Thread James
Neil Bothwick neil at digimed.co.uk writes:


 
  What would folks suggest is the best way to capture the output
  from the screen into a file (fancy formating?) as well as being
  able see the local builds as they scroll the build out to
  the terminal (screen) window (normal emerge results viewed fromt the
  terminal session ?
 
 Set PORT_LOGDIR in make.conf. This is not the same as the ELOG settings,
 it logs the entire output from the ebuild.

This sound workable. If I don't want something logged, just comment 
out the PORT_LGDIR in make.conf, or is there a way on the Command line
to toggle this on and off, without manually editing the file?

I assume there is a unique log file for each separate ebuild.

Where do I read up on PORTDIR (documentation) referred to in
man make.conf ?

James




[gentoo-user] Re: wayland

2014-07-21 Thread James
Volker Armin Hemmann volkerarmin at googlemail.com writes:


 who told you that 'bloated' buzz word? The same people who told you
 about 'the cloud' or 'web 2.0'?


Nobody, common sense from practicle experience. Here's what you
*should* do to experince just how bloated  most desktops have become.

Build up a minimize workstation and compile some big codes under
gnome_bloat or KDE_lead_sinker and then compile the same code
on a light weight workstation of equal resources.  BLOAT is
ok if you got all day. Becoming aquaited with tons of ram
that is not being suck_dry by the desktop, is a mind altering
experince..  try it, you might like it...

Anyway, I'm moving to a 3 monitor setup (3 27 samsungs) as soon
as I fine a triple monitor mount for 27. Then I'll have 2
worksations under them, so I might put up a bloatware desktop,
just to remind me how sluggish they are
hahahahahahaha...


peace,
James








Re: [gentoo-user] Re: capturing emerge output

2014-07-21 Thread Neil Bothwick
On Mon, 21 Jul 2014 23:01:44 + (UTC), James wrote:

  Set PORT_LOGDIR in make.conf. This is not the same as the ELOG
  settings, it logs the entire output from the ebuild.  
 
 This sound workable. If I don't want something logged, just comment 
 out the PORT_LGDIR in make.conf, or is there a way on the Command line
 to toggle this on and off, without manually editing the file?

PORT_LOGDIR= emerge something?
 
 I assume there is a unique log file for each separate ebuild.

There is, the format is documented in man make.conf

 Where do I read up on PORTDIR (documentation) referred to in
 man make.conf ?

PORTDIR is *very* different from PORT_LOGDIR, but both are documented on
man make.conf.


-- 
Neil Bothwick

WinErr 013: Unexpected error - Huh ?


signature.asc
Description: PGP signature