Hello list,
Sorry to bother you with another OT question.
I've been trying the /chromium/ browser and I've come to like it -
except for one thing: I can't see how to force pages to be shown in
sans-serif but without forcing a particular font or size etc.
Has anyone found a way to do it? I coul
This is a little of the beaten track for this forum but there doesn't
seem to be a regular Xming forum. Also since my problem is related
to running emacs thru xming, I tried on emacs.help more than once to
get this figured out.
Any emacs users here will know about emacslcient, and maybe some of
On 5 February 2011 16:15, Sergei Trofimovich wrote:
> On Sat, 5 Feb 2011 19:43:11 +0100
> Cedric Sodhi wrote:
>
>> There are several reasons why portage, neither the tree nor (especially
>> not) the distfiles should reside in /usr.
>
> Hi Cedric!
>
> Why gentoo-user@ ? Choosing (and changing) rea
On Sat, Feb 05, 2011 at 06:43:32PM -0500, Walter Dnes wrote:
> The current ebuild is screen-4.0.3, and up to screen-4.0.3-r4 (with
> ~everything) shows up after an "emerge --sync". I can
> "./configure --with-various-options && make && make install" with the
> best of them (not that I know what
On 02/05/2011 03:43 PM, Walter Dnes wrote:
the latest builds
of "screen" are in a git repository, which I'm not familiar with.
(I'm not the same Walter, as you know already :)
I urge everyone to get to know git.
I admit, I could be prejudiced in git's favor just because it was the
first vcs
On 02/06/2011 01:54 AM, Walter Dnes wrote:
On Sat, Feb 05, 2011 at 09:31:48PM +0200, Nikos Chantziaras wrote
On 02/05/2011 08:00 PM, Mick wrote:
Just try video=1024x768 (or whatever your desired resolution is)
on the kernel line and it should just work.
Unfortunately, it doesn't.
Actual
Cedric Sodhi wrote:
You know... I appreciate all your helpful "if you want to move portage
to /var you can do it by..." 'suggestions', but, can you imagine the
following situation:
You push a change to a repository, on your way to work you realize that
there was an error in the commit so as soon
Yesterday I caught up with portage and updated quite a few packages on
a remote workstation. The system hadn't been updated for about a
month. The updates included some xorg stuff and some xfce4 stuff.
Today when the workstation's user logged in via gdm, she clicked the
x
On Sat, 5 Feb 2011 19:43:11 +0100
Cedric Sodhi wrote:
> There are several reasons why portage, neither the tree nor (especially
> not) the distfiles should reside in /usr.
Hi Cedric!
Why gentoo-user@ ? Choosing (and changing) reasonable defaults is up to
developer. You could add gentoo-dev@ to
On Sat, Feb 5, 2011 at 2:39 PM, Alex Schuster wrote:
> Mark Knecht writes:
>
>> Can someone recommend a good IDE to write C code in?
>>
>> 1) Something that can display multiple files in a project.
>>
>> 2) Something that have some sort of version control built into it?
>>
>> 3) If possible, I can
On Sat, Feb 05, 2011 at 09:31:48PM +0200, Nikos Chantziaras wrote
> On 02/05/2011 08:00 PM, Mick wrote:
> >
> > Just try video=1024x768 (or whatever your desired resolution is)
> > on the kernel line and it should just work.
>
> Unfortunately, it doesn't.
Actually, it does, "video=640x480" in m
On Sat, Feb 05, 2011 at 12:10:15PM -0500, Walter Dnes wrote
> As they say in the infomercials "but wait, there's more". My monitor
> supports 1280x720 and 1280x1024 modes. Using "screen" I should be able
> to do splitscreen mode with 2 sessions side-by-each.
That is going to have to wait a
On Saturday 05 February 2011 23:52:20 Alan McKinnon wrote:
> Apparently, though unproven, at 22:45 on Saturday 05 February 2011, Volker
>
> Armin Hemmann did opine thusly:
> > again, you are starting from a mistaken premise.
> >
> > /usr/portage makes sense, when you consider its history. It may
Apparently, though unproven, at 00:23 on Sunday 06 February 2011, Mark Shields
did opine thusly:
> > It's just plain outright stupid to have a default location for something
> > (that
> > by definition is variable) in a place that by definition (or by de-facto
> > consent) must be mountable read-
Acme from plan9port.
On Feb 5, 2011 5:11 PM, "Mark Knecht" wrote:
> Can someone recommend a good IDE to write C code in?
>
> 1) Something that can display multiple files in a project.
>
> 2) Something that have some sort of version control built into it?
>
> 3) If possible, I can compile right in
On 02/05/2011 12:05 PM, Alan McKinnon wrote:
Apparently, though unproven, at 20:43 on Saturday 05 February 2011, Cedric
Sodhi did opine thusly:
There are several reasons why portage, neither the tree nor (especially
not) the distfiles should reside in /usr.
I've been saying this for years. I
Cedric Sodhi writes:
> Replying to the three before messages which basically made the point
> that one can change the location manyually.
[...]
> It does not conform with any accepted standard, it is wrong per se, it
> should be changed.
>
> THIS is the point, please, as I already said in my firs
Mark Knecht writes:
> Can someone recommend a good IDE to write C code in?
>
> 1) Something that can display multiple files in a project.
>
> 2) Something that have some sort of version control built into it?
>
> 3) If possible, I can compile right in the IDE.
Emacs. If you dare to go this way
On Sat, Feb 5, 2011 at 4:52 PM, Alan McKinnon wrote:
> Apparently, though unproven, at 22:45 on Saturday 05 February 2011, Volker
> Armin Hemmann did opine thusly:
>
> > again, you are starting from a mistaken premise.
> >
> > /usr/portage makes sense, when you consider its history. It may not be
On 02/04/2011 04:54 PM, Grant wrote:
Yesterday I caught up with portage and updated quite a few packages on
a remote workstation. The system hadn't been updated for about a
month. The updates included some xorg stuff and some xfce4 stuff.
Today when the workstation's user logged in via gdm, she
Can someone recommend a good IDE to write C code in?
1) Something that can display multiple files in a project.
2) Something that have some sort of version control built into it?
3) If possible, I can compile right in the IDE.
I've starting writing something. It's hundreds of lines long in 1 fi
On Sat, Feb 05, 2011 at 09:45:23PM +0100, Volker Armin Hemmann wrote:
> again, you are starting from a mistaken premise.
>
> /usr/portage makes sense, when you consider its history. It may not be the
> appropriate decision, but with its background it was logical back then.
It was consistent back
On 02/05/2011 05:09 AM, Peter Humphrey wrote:
I even had a lockup while running from the live CD
Have you tried memtest86 on that machine?
Apparently, though unproven, at 22:45 on Saturday 05 February 2011, Volker
Armin Hemmann did opine thusly:
> again, you are starting from a mistaken premise.
>
> /usr/portage makes sense, when you consider its history. It may not be the
> appropriate decision, but with its background it was logi
again, you are starting from a mistaken premise.
/usr/portage makes sense, when you consider its history. It may not be the
appropriate decision, but with its background it was logical back then.
And if something is not broken, don't change it. You do not know what old
tool/setting/whatever mig
You know... I appreciate all your helpful "if you want to move portage
to /var you can do it by..." 'suggestions', but, can you imagine the
following situation:
You push a change to a repository, on your way to work you realize that
there was an error in the commit so as soon as you get to work yo
Replying to the three before messages which basically made the point
that one can change the location manyually.
I'm aware of that and as I've pointed out I consider it irrelevant to
the point that I'm making (with which you appear to agree at least
principally), that is, that it should not be the
Cedric Sodhi wrote:
There are several reasons why portage, neither the tree nor (especially
not) the distfiles should reside in /usr.
/var is expected to be heavily written and read from, as it is the case
with the portage tree.
It's possibly subject to fragmentation and small file sizes and he
Apparently, though unproven, at 02:54 on Saturday 05 February 2011, Grant did
opine thusly:
> >> Yesterday I caught up with portage and updated quite a few packages on
> >> a remote workstation. The system hadn't been updated for about a
> >> month. The updates included some xorg stuff and some
Apparently, though unproven, at 20:43 on Saturday 05 February 2011, Cedric
Sodhi did opine thusly:
> There are several reasons why portage, neither the tree nor (especially
> not) the distfiles should reside in /usr.
I've been saying this for years. I always change PORTDIR everywhere to
/var/po
where do the bsds put their ports?
also: just set the PORTDIR variable wherever you want it to point. There is no
reason to annoy the rest of humanity with a mailing list point complaining
about a perceived problem that is none.
On 02/05/2011 08:43 PM, Cedric Sodhi wrote:
There are several reasons why portage, neither the tree nor (especially
not) the distfiles should reside in /usr.
[...]
If you can think of good counter arguement which *logically* supports
that portage should by default reside in /usr (including the di
On Sat, Feb 5, 2011 at 10:43 AM, Cedric Sodhi wrote:
> There are several reasons why portage, neither the tree nor (especially
> not) the distfiles should reside in /usr.
>
I have no opinion on the subject really, but can't you build a link
from /usr/portage to anywhere you want to put it? I put
On 02/05/2011 08:00 PM, Mick wrote:
Right, but a framebuffer (KMS driven or vesa, et al.) is not a bad thing.
Just try video=1024x768 (or whatever your desired resolution is) on the kernel
line and it should just work.
Unfortunately, it doesn't.
Cedric Sodhi writes:
> There are several reasons why portage, neither the tree nor (especially
> not) the distfiles should reside in /usr.
>
> /var is expected to be heavily written and read from, as it is the case
> with the portage tree.
That's why I have /var/portage, with subdirectories tree
On Saturday 05 February 2011 19:43:11, Cedric Sodhi wrote:
> There are several reasons why portage, neither the tree nor (especially
> not) the distfiles should reside in /usr.
>
> /var is expected to be heavily written and read from, as it is the case
> with the portage tree.
>
> It's possibly s
There are several reasons why portage, neither the tree nor (especially
not) the distfiles should reside in /usr.
/var is expected to be heavily written and read from, as it is the case
with the portage tree.
It's possibly subject to fragmentation and small file sizes and heavy
changes, which is
On Saturday 05 February 2011 17:10:15 Walter Dnes wrote:
> On Thu, Feb 03, 2011 at 09:40:41PM +, Mick wrote
>
> > Leave KMS enabled and add the parameter:
> > video=1024x768 (or whatever suits your screen and taste)
> >
> > to your kernel line. You shouldn't need vesafb, uvesa or any other
On Saturday 05 February 2011 18:00:10 Mick wrote:
> On Saturday 05 February 2011 15:27:27 Walter Dnes wrote:
> > In "make menuconfig", I do not have any drivers enabled under...
> >
> > Device Drivers --->
> >
> > Graphics support --->
> > -*- Support for frame buffer d
On Saturday 05 February 2011 15:27:27 Walter Dnes wrote:
> On Thu, Feb 03, 2011 at 04:05:01PM -0800, walt wrote
>
> > On 02/03/2011 02:11 PM, Nikos Chantziaras wrote:
> > > On 02/03/2011 08:07 AM, Walter Dnes wrote:
> > >> Is there a way to have a real text console? I know that I can
> > >> have 2
Am 05.02.2011 17:59, schrieb Grant:
>>> Yesterday I caught up with portage and updated quite a few packages on
>>> a remote workstation. The system hadn't been updated for about a
>>> month. The updates included some xorg stuff and some xfce4 stuff.
>>> Today when the workstation's user logged in
Am 05.02.2011 14:34, schrieb Enrico Weigelt:
>
> BTW: I'm currently designing an emode/microcode-base computer
> architecture built on an matrix of nanocores, they don't have a
> concept of main memory, instead a relatively large (linear
> addressable) register memory, part of the register space i
On Thu, Feb 03, 2011 at 09:40:41PM +, Mick wrote
> Leave KMS enabled and add the parameter:
>
> video=1024x768 (or whatever suits your screen and taste)
>
> to your kernel line. You shouldn't need vesafb, uvesa or any other
> drivers to achieve this.
Thanks very much. That works. I f
On Saturday 05 February 2011 15:28:22 Enrico Weigelt wrote:
> * Volker Armin Hemmann wrote:
> > and that is all the intel stuff. For AMD all you have to do is:
> > modprobe -r microcode && modprobe microcode
>
> Is the microcode permanently flashed or loaded into some
> internal RAM ?
loaded. mi
>> Yesterday I caught up with portage and updated quite a few packages on
>> a remote workstation. The system hadn't been updated for about a
>> month. The updates included some xorg stuff and some xfce4 stuff.
>> Today when the workstation's user logged in via gdm, she clicked the
>> xfce4 "Migr
>> Yesterday I caught up with portage and updated quite a few packages on
>> a remote workstation. The system hadn't been updated for about a
>> month. The updates included some xorg stuff and some xfce4 stuff.
>> Today when the workstation's user logged in via gdm, she clicked the
>> xfce4 "Migr
On Thu, Feb 03, 2011 at 04:05:01PM -0800, walt wrote
> On 02/03/2011 02:11 PM, Nikos Chantziaras wrote:
> > On 02/03/2011 08:07 AM, Walter Dnes wrote:
> >> Is there a way to have a real text console? I know that I can
> >> have 2 X sessions on tty10 and tty11 with different resolutions, and
> >> co
Enrico Weigelt [11-02-05 16:08]:
> * Volker Armin Hemmann wrote:
>
> > and that is all the intel stuff. For AMD all you have to do is:
> > modprobe -r microcode && modprobe microcode
>
> Is the microcode permanently flashed or loaded into some
> internal RAM ?
>
>
> cu
> --
> ---
I wrote:
In case someone else also wants to setup this, here's the final steps to
make relaying work.
> Relaying does not work yet, I get a "Relay access denied (in reply to
> RCPT TO command)" error. But my initial goal is reached, I can send mail
> to {root,wonko}@wonkology.org. That's all I wa
* Volker Armin Hemmann wrote:
> and that is all the intel stuff. For AMD all you have to do is:
> modprobe -r microcode && modprobe microcode
Is the microcode permanently flashed or loaded into some
internal RAM ?
cu
--
--
E
* Volker Armin Hemmann wrote:
> the CPU. All CPUs use microcode. For decades. Google, or go straight to
> wikipedia.
> http://en.wikipedia.org/wiki/Microcode
Borroughs' large systems (b6500+) were designed as microcode
machines from ground up, which essentially interpreted an algol
bytecode (th
On 21:21 Fri 04 Feb , Enrico Weigelt wrote:
> * Nils Holland wrote:
>
> > 1) So a package using the GNU build system determines or is passed
> > (via --host aka. CHOST) a target triplet specifying the system on
> > which the resulting compiled code is supposed to run. What does the
> > packa
On Friday 04 February 2011 18:12:50 Paul Hartman wrote:
> On Fri, Feb 4, 2011 at 10:36 AM, Peter Humphrey
> wrote:
> > At the risk of hijacking the thread, this reminds me of a problem
> > on my workstation. It runs Gentoo fine (well, sluggishly) but when
> > I installed Fedora 14 to try it, I fou
Am 04.02.2011 23:26, schrieb Grant:
> Yesterday I caught up with portage and updated quite a few packages on
> a remote workstation. The system hadn't been updated for about a
> month. The updates included some xorg stuff and some xfce4 stuff.
> Today when the workstation's user logged in via gdm
Paul Colquhoun [11-02-05 10:08]:
> On Sat, 5 Feb 2011 18:05:05 meino.cra...@gmx.de wrote:
> > Hi,
> >
> > I want to do the following as fast as possible and with less
> > system load as possible:
> >
> > There are two directories called 'source' and 'target'.
> >
> > 'source' gets updated v
Am 05.02.2011 10:06, schrieb Nikos Chantziaras:
> On 02/05/2011 09:05 AM, meino.cra...@gmx.de wrote:
>> There are two directories called 'source' and 'target'.
>>
>> 'source' gets updated via 'svn up', then it gets compiled.
>> Since there is no "make install" or similiar, installation
>> i
On Sat, 5 Feb 2011 08:05:05 +0100, meino.cra...@gmx.de wrote:
> Now I need a copy mechanism which does the following:
> * copy all files with newer date to 'target' -- this can be done via
>'cp -u'
> * copy all files which only exist in 'source' to 'target' --
>this can be done also wit
On 02/05/2011 09:05 AM, meino.cra...@gmx.de wrote:
There are two directories called 'source' and 'target'.
'source' gets updated via 'svn up', then it gets compiled.
Since there is no "make install" or similiar, installation
is done via copying 'source' to 'target'. A symlink from
/usr
On 02/04/2011 08:10 PM, Paul Hartman wrote:
On Thu, Feb 3, 2011 at 6:37 PM, Nikos Chantziaras wrote:
[...]
For the radeon driver at least, disabling KMS means that you won't get DRI2
in X11. That means slower performance and tearing. The non-KMS X driver is
pretty much considered deprecated.
On Sat, 5 Feb 2011 18:05:05 meino.cra...@gmx.de wrote:
> Hi,
>
> I want to do the following as fast as possible and with less
> system load as possible:
>
> There are two directories called 'source' and 'target'.
>
> 'source' gets updated via 'svn up', then it gets compiled.
> Since there i
60 matches
Mail list logo
