~x86 that are now missing that flag and try to downgrade them
to what portage flags with "x86".
--
Wade Brown
On 9/16/05, Drew Tomlinson <[EMAIL PROTECTED]> wrote:
> I set the ~x86 use flag for ffmpeg, getting the newest version in the
> tree. However now I'm having
I suppose to make this thread complete I'll be the first (maybe only?)
one to voice support for good old WindowMaker. I think the
biggest reason I still use it is that I'm just stuck in a rut, I have
been running it for ages and have never wanted anything better.
It's definitely light weight enou
Easiest way would be to try "mformat a:" (yes, that is the actual
command), I'm not sure if it's part of the basic utilities set or not,
but it's about as simple as you can get regarding FAT floppies.
--
Wade Brown
On 8/29/05, Michael Kintzios <[EMAIL PROTECTED]&
else (configurable of
course) and the last line would be relevant to your progress. As for
actual screen savers, I doubt you'll find one already built for
xscreensaverd, but I've been wrong in the past.
--
Wade Brown
On 8/23/05, Daevid Vincent <[EMAIL PROTECTED]> wrote:
> When I'
Add to the mouse section of your xorg.conf a few specific lines:
Option "Protocol" "ImPS/2"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
After that, you should be able to restart X and run...hopefully.
--
Wade Brown
On 8/20
's comment, I'm not sure it's standard
specification. I have a Biostar iDeq 220T, with on board SATA RAID,
and the access LED lights up fine for me in Gentoo with no cajoling to
speak of. It seems more chipset specific than a standard
specification.
--
Wade Brown
On 8/19/05, Mark
The environment variable $PS1 controls what your prompt is, assuming
you're using bash. This can be set in many many places, such as
~/.bashrc, /etc/profile (controlled by something along the lines of
/etc/env.d/##bash), or even as a simple export. Try searching through
your /etc on your differen
Using FEATURES="buildpkg" is always a great place to start on your
'big' system. For more detail than that (all one lines of it), check
the gentoo-wiki site, it's full of useful information, well,
sometimes.
http://gentoo-wiki.com/HOWTO_Create_A_Build_Host
On 7/27/05, Alexander Skwar <[EMAIL PRO
I thought linux wouldn't allow suid shell scripts to work as suid.
The reasoning is a shell script doesn't quite execute, it gets
interpeted by the command on the first line. Just as a test I made a
simple script modded root.root 4755 that consists of the /bin/bash
line, and cat /etc/shadow. Roo
That doesn't seem to address the issue as mounting by hand still spits
out errors relative to partition problems. What's the output of
"fdisk -l /dev/hda"?
On 7/13/05, Colin <[EMAIL PROTECTED]> wrote:
> aabb wrote:
>
> >Hi,
> >
> >Here's a strange one...
> >
> >I use 2 partitions for Windows 98,
One useful piece of information would be the output of dmesg, usually
module loading errors will appear in there.
On 7/8/05, dini mamma <[EMAIL PROTECTED]> wrote:
> HI folks
>
> I got the problem, that several modules couldnt be loaded at boot. some of
> them are filesystems (xfs,jfs,ntfs). and s
Whoops, you're right, I thought that equery was part of the other
etools just because of the naming convention. Pity what not having
access to a gentoo box at work anymore will do to a man.
On 7/8/05, Zac Medico <[EMAIL PROTECTED]> wrote:
> Catalin Grigoroscuta wrote:
>
> >> I've just rebuilt my
Equery, esearch, and einfo (I think) are from an index built by
running eupdatedb. I'd imagine you're using esync which is just a
very small script that does emerge sync && eupdatedb, so doing a fresh
esync would alleviate the problem you seem to be having, albeit with a
bit of overkill. Just run
Actually, you can replace your world file provided you use "emerge
--emptytree --deep --newuse world", and portage won't complain that
packages aren't installed as the emptytree tells portage to (rightly
in this case) assume nothing is installed yet, including portage
itself.
On 7/6/05, David Morg
In this specific case, "Broken" means "Binary Package". Binary
packages are distributed with all kinds of libraries linked to so that
they can minimize the amount of binary packages they need to maintain
(e.g. they don't need an eclipse-gnome and an eclipse-nognome
package). The program will idea
Liar! Well, we forgive you, I think =).
Actually the better (Gentoo suggested) way to squelch these packages
is to exclude /opt from the search path in the revdep-rebuild script.
Just do EDITOR `which revdep-rebuild` and take /opt out of the
SEARCH_DIRS, most anything that goes in there should b
JDK is more than likely the one you want, the difference is exactly as
you said, one is supposed to be just runtime environment (what most
Windows users get to view java on web pages) whereas JDK lets you
build java applications on your machine. You can probably ignore that
line with jre-bin seein
Java 1.5 is in the portage tree, though I'm not entirely sure on its
masked state. I do know that some programs have issues with 1.5, and
there are plenty of warnings all over the place that using a
system-wide configuration of java 1.5 is potentially hazardous when
building up some of the older p
It's likely that gnome-base/gdm isn't in your world file. An easy way
to check this is:
grep gnome-base/gdm /var/lib/portage/world
It's more than likely a dependancy of some other gnome project that
hasn't upgraded its requirements to gdm. A way to upgrade
dependancies is to add --deep or just
One simple fact, the ebuilds don't rely on the rpms, they use the
self-extracting binaries distributed by Sun. Check the ebuild for
1.5.0.03:
x86file="jdk-${MY_PVA}-linux-i586.bin"
Sun distributes their JDK and JRE in two formats, the broken RPM you
mentioned, and a generic self extracting/insta
In response to the second portion, it varies from shell to shell.
Assuming you're using bash, add the following line to your ~/.bashrc
alias ls='ls --color'
On 5/18/05, Colin <[EMAIL PROTECTED]> wrote:
> Is it possible to get a background image for the console like it is on
> the LiveCD? Also, h
If you don't want to bother compiling any sound on your system, then
add "-alsa -arts -esd" to your use flags. It's more than likely one
of your packages found in the update --deep had the alsa tagged on
itself by default, which requires an override described above either
in /etc/make.conf or just
Glad to see I'm not the only one having this problem, though I'm
having it on gnome-print with a very slightly different output,
(ltmain.sh version 1.3.5). Likewise I wouldn't mind finding the root
of this, I just haven't had the time to dive into it.
On 5/12/05, Charles Read <[EMAIL PROTECTED]>
23 matches
Mail list logo
