Re: [gentoo-user] Modular X
On Mon, Apr 03, 2006 at 08:23:41AM +0200, Alexander Skwar wrote: Toby 'qubit' Cubitt wrote: The only downside to freeNX was it was more complicated to get working. The big downside of NX for me is, that your session ends as soon as NX is stopped. Not so with VNC (no matter which VNC). I'm not sure that's true. I thought freeNX could have persistent sessions too. There's an ENABLE_PERSISTENT_SESSION option in the config file, at any rate. I even vaguely remember trying it once. Perhaps someone else knows more (or has access to a couple of boxes they could test it on - I don't at the moment). In any case, the freeNX client can connect to VNC sessions, amongst others. Not sure whether that gives better performance than VNC though. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Modular X
On Sun, Apr 02, 2006 at 04:26:00PM +0200, Rick van Hattem wrote: On Saturday 01 April 2006 23:47, Jim wrote: On Sat, 2006-04-01 at 22:29 +0200, Alexander Skwar wrote: [EMAIL PROTECTED] /var/db/pkg $ epm -qf `which xmkmf ` imake-1.0.1-r1 Please file a bug against tightvnc, as it's missing a dependency. Will do. BTW: Why use tightvnc at all? Realvnc 4 is as fast in my experience and there's still somebody workign on it - seeing that the last update to tightvnc is dated July 2005, I doubt that anybody maintains it anymore. I am testing out the different vnc versions along with freeNX to see what will give me the fastest remote desktop. Alexander Skwar Jim When you're done testing please report/publish the results, I'm also very interested in a fast remote desktop system. Tightvnc can hog the cpu with the compression sometimes so that's not always a good solution either. I've tried tightVNC and freeNX, both over a relatively slow DSL link and on an old pentium2 450, and whilst both were usable there's no competition: freeNX wins hands down. I also like the fact that freeNX also lets you run single remote applications, instead of always having to start up a complete remote desktop - much closer to normal X-forwarding. The only downside to freeNX was it was more complicated to get working. (But that may have been due to the complicated things I was trying to do: everything had to be tunnelled through a firewall using ssh port-forwarding, and I needed to get my X server to talk to a remote font server, also via ssh tunnelling, so that fonts on the application I was running over freeNX would work.) HTH, Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Have portage lost its memory?
On Thu, Mar 23, 2006 at 01:43:15PM +0100, Jules Colding wrote: On Thu, 2006-03-23 at 06:26 -0600, Teresa and Dale wrote: Jules Colding wrote: On Thu, 2006-03-23 at 10:40 +0100, Jules Colding wrote: So what exactly is going on here? Having an SSH session on another machine and forgetting ll about it. Please forgive my stupidity here. Sorry, jules I thought only I could do that. Funny ain't it? Not when you do it in public ;-) I used to give the shell prompts different colours on different machines to help avoid this. Or rather, the local one would always be the same colour, but shells under ssh sessions were colour-coded by machine. I've lost the script I wrote for this somewhere in the mists of time (if I remember right, it was copied and hacked from a bash prompt example that colour-coded according to the login type: ssh, telnet, local, etc.) Someday I might get round to recreating it... Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Have portage lost its memory?
On Thu, Mar 23, 2006 at 03:07:08PM +0100, Jules Colding wrote:
On Thu, 2006-03-23 at 14:36 +0100, Toby 'qubit' Cubitt wrote:
Having an SSH session on another machine and forgetting ll about it.
Please forgive my stupidity here.
Sorry,
jules
I thought only I could do that. Funny ain't it?
Not when you do it in public ;-)
I used to give the shell prompts different colours on different
machines to help avoid this. Or rather, the local one would always be
the same colour, but shells under ssh sessions were colour-coded by
machine.
I've lost the script I wrote for this somewhere in the mists of time
(if I remember right, it was copied and hacked from a bash prompt
example that colour-coded according to the login type: ssh, telnet,
local, etc.)
Someday I might get round to recreating it...
That would be helpful.
Here you go. It also checks if you're root. Save it as something
suitable somewhere in your $PATH, (e.g. ~/bin/bash_prompt), modify to
suit your setup, then do:
source ~/bin/bash_prompt
colour_code_prompt
unset colour_code_prompt
either from the shell or in your .bashrc to load it.
Use at your own risk, since I've only just written it, and haven't
tested it very heavily! (When I've used it a bit to check it works
properly, I might document it a bit and put it on my web site.)
Toby
--
bash_prompt:
--
#!/bin/bash
function colour_code_prompt
{
# set up some colour escape variables
BLUE=\[\033[1;34m\]
GREEN=\[\033[1;32m\]
CYAN=\[\033[1;36m\]
RED=\[\033[1;31m\]
MAGENTA=\[\033[1;35m\]
YELLOW=\[\033[1;33m\]
WHITE=\[\033[1;37m\]
GREY=\[\033[00m\]
# if logged in via ssh, choose colours according to host and user
if [ -n $SSH_CLIENT ]; then
if [ $EUID == 0 ]; then
case $(hostname -f) in
box1.some.domain)
COLOUR1=$RED
COLOUR2=$GREEN
;;
box2*)
COLOUR1=$RED
COLOUR2=$YELLOW
;;
*)
COLOUR1=$RED
COLOUR2=$MAGENTA
;;
esac
else
case $(hostname -f) in
box1.some.domain)
COLOUR1=$GREEN
COLOUR2=$CYAN
;;
box2*)
COLOUR1=$YELLOW
COLOUR2=$BLUE
;;
*.some.other.domain)
COLOUR1=$CYAN
COLOUR2=$RED
;;
*)
COLOUR1=$MAGENTA
COLOUR2=$BLUE
;;
esac
fi
# if logged in locally as root, use different colours
elif [ $EUID == 0 ]; then
COLOUR1=$RED
COLOUR2=$BLUE
# otherwise, use default colours
else
COLOUR1=$GREEN
COLOUR2=$BLUE
fi
# set the prompt
export PS1=[EMAIL PROTECTED] $COLOUR2\w \$ $GREY
}
--
PhD Student
Quantum Information Theory group
Max Planck Institute for Quantum Optics
Garching, Germany
email: [EMAIL PROTECTED]
web: www.dr-qubit.org
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Writing to a 256MB Rom
On Wed, Mar 01, 2006 at 04:16:33PM -0500, Ryan Holt wrote: Is there any difference between ROM and NVRam? Yes. ROM is a WORM medium (write once, ready many times). The data stored in a PROM (programmable read only memory) is literally burned in by applying high-voltage pulses to the chip. There's also EPROM (eraseable PROM) which can be erased by exposing the chip to ultraviolet light, and EEPROM (electrically eraseable PROM). If we're being pedantic, ROM is a misnomer for these, since they're not really write once. NVRAM (non-volatile random access memory) is similar to EEPROM in some ways: it can be written and erased many times, and maintains its data even when power is disconnected. MRAM, FRAM, etc. are forms of NVRAM. Flash memory is I believe a more modern form of EEPROM. They all differ in the physical technology used on the chip, and have different properties, such as how many times the memory can be erased and rewritten, how fast writing and reading is, etc. Also, Wikipedia says: ...there is a convention to reserve the term EEPROM [for] byte-wise writable memories compared to block-wise writable flash memories. I think I mis-spoke when I said ROM; because it's actually Non Volatile Ram. You *could* have meant PROM, but NVRAM sounds much more likely ;-) Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How many people use KDE?
On Sat, Jan 21, 2006 at 12:56:47AM +0100, Hemmann, Volker Armin wrote: On Saturday 21 January 2006 00:44, Alan E. Davis wrote: May I ask others' experiences with e17? I just wasted my holiday installing e17 on two of three machines. It is smaller than Kde, but background is 20% of cpu . Buggy. Beautiful. A PITA to configure, and menus suck. I don't think I'll be there long. I liked enlightenment .16 except I guess I really do need icons to remind me of what I've got on the system, and good menus. that was exactly how I felt. All the problems to get it installed, and than it was such a bad thing to configureuse, that I deinstalled it some days later. I used earlier enlightenment incarnations as my main desktop for some time, back, when KDE 2.X was dead slow, but when KDE 3 came out, enlightenment lost its appeal. That's a bit unfair on e17, given that it's still pre-release software. It is indeed buggy at the moment (though I should add I haven't had any problems with more recent CVS installations), but that's to be expected in a pre-release, and you're warned about it in big red letters when you emerge it. It is also a PITA to configure at the moment, but graphical menu managers, keybinding editors, icon creaters, desktop icons, etc. are planned before the release version, and every CVS checkout seems to add more graphical configuration options at the moment, and reduce the number of times I resort to the enlightenment-remote shell command. Finally, on my ancient Pentium2 450, it uses 2-3% of cpu. In fact, I find it more responsive than e16. So I'm not sure where the 20% comes from. Maybe you've enabled lots of the processor intensive eye-candy, like animated backgrounds or the snow or flames modules? Or you just need to update to a more recent CVS release. Without wishing to start a flame war, it's unfair to the developers to give the impression that their software doesn't work very well without at least mentioning it's pre-release (and therefore not expected to!). And really, criticising it at all for being buggy and lacking features is a little unfair. If you're not prepared to put up with some rough edges, wait for the official release version. Just to put in a good word for e17 to balance the discussion... Personally, I prefer enlightenment to KDE or gnome because I don't like the whole integrated desktop approach. I prefer my window manager to manage windows, and leave me free to run whichever apps I like. My ideal window manager has nothing at all on the desktop (except maybe a wallpaper to gaze at when nothing's running), no gizmos taking up desktop real-estate, an easy way to run my most frequently used apps and some way to get at any others I might need occasionally, some way to navigate between running apps, and as much as possible of this should be manageable from the keyboard (with completely configurable keybindings). If it does all this and looks beautiful at the same time, so much the better! I find that, of the traditional window managers, enlightenment comes closest to this ideal (though I admit I've never tried FLuxbox or IceWM - I stopped looking when I found I was happy with enlightenment). Since a lot of e17 features are written as modules, I can choose not to load (or often not to install) them, so only those features I want take up disc space and memory (it's the gentoo way!). For instance, I don't bother loading e17's start menu. (what's the point when I have ibar and keybindings to run the apps I use most, and the run dialogue for the rest?). But it's there for those who want it. E17 has completely configurable keybindings, even if they're a pain to configure at the moment, and the enlightenment-remote command line...err...command is fantastic for getting shell scripts to interact with the window manager. If you've read all that, you'll not be surprised I also like ratpoison ;-) But I haven't used it long enough to get used to it yet. And I've not got beyond installing ion yet. Window managers are very much a personal choice, and there is no right decision, except try out a few and decide for yourself. Which means it's worth at least being aware that there are plenty of other choices apart from KDE and gnome, if you're not happy with them (unlike a certain other OS, where there's not even a single alternative ;) Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] different video formats to mpeg2
On Thu, Jan 19, 2006 at 09:17:05PM +0100, Marco Calviani wrote: Hi list, i need to transform different video format, that is wmv, rm, xvid and divx to mpeg2. Is there a utility that deals with this? mencoder, which is part of mplayer, might help if you have a few days spare to read the many page ;-) HTH, Toby -- Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] how to upload files...?any tool?
On 00:22 Fri 11 Nov , El Nino wrote: Dear friends, i develop my own webpages now want to upload them to a remote server. so im new to do this... so can any body to point me a tool to do this? If you can find some way (e.g. shell access or a friendly sysadmin) to install it on the remote server, I highly recommend unison: * net-misc/unison Latest version available: 2.13.16 Latest version installed: 2.13.16 Size of downloaded files: 1,001 kB Homepage:http://www.cis.upenn.edu/~bcpierce/unison/ Description: Two-way cross-platform file synchronizer License: GPL-2 It uses the rsync protocol, so is much faster than copying the files if you've just made small changes. But unlike rsync it allows full two-way synchronisation, which is very useful if files can be changed on the server as well as on your local copy. HTH, Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
