-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael George wrote:
|
| It was /etc/man-conf. A change in the NROFF definition caused the
| problem. Running dispatch-conf didn't prompt me for the config change,
| so I ran etc-update this time and found it.
|
| Hopefully this will be helpful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James wrote:
| Hello,
|
| On an amd64, If I want to add -fomit-frame-pointer to a system's
| CFLAGS setting, I can just add it and eventually all of the
| executables will be recompile (willing to wait)
| or do I have to rebuild system (all packages)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James wrote:
|
| But in order to avoid recompiling all of those packages (for now)
| I can just add it to my CFlags and wait a few months, as another option?
Yes, there shouldn't any problems appear.
|
| Or is there real peril with this approach to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| I searched for NROFF in /etc/man-conf and found a note saying to add
| -c if something had a specific version. I tried that and it works
| now. There may be otehr fixesm but that works for me. Just edit it
| and look for
[EMAIL PROTECTED] wrote:
In the middle of doing a major upgrade from very old pkgs to current
2008 and compiling lots and lots of stuff.
Seeing that line `checking for WHATEVER' go by 486,211 times so far
makes me wonder if there wouldn't be someway to cache all those
answers somewhere so
Brandon Mintern wrote:
ccache caches the compile step. I believe the OP was specifically
looking for something that would cache the answers to the checking
for lines (the configuration step).
Yes, you are right, but I thought that ccache cached parts of the
configuration too.
That's what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
since I gcc downgraded to version 4.1.2 I have in the top
column WCHAN only a -. This applies to all processes.
The System.map is available in /usr/src/linux.
It works after installation, that was late 2007, with gcc 4.1.2
and it works with gcc
Volker Armin Hemmann wrote:
extremly long. So long that you have to start ooo several times a day for a
year so that the saved startup time equalizes the time spent compiling it.
I have to disagree. On my laptop Dell Inspiron 6400, Dual Core Pentium
(T2130) 1.8 GHz,
2 GB RAM, 160 GB HD. The
Volker Armin Hemmann wrote:
On Montag, 5. Mai 2008, Wolf Canis wrote:
Volker Armin Hemmann wrote:
extremly long. So long that you have to start ooo several times a day for
a year so that the saved startup time equalizes the time spent compiling
it.
ccache in make.conf
Mick wrote:
You people don't know what pain means! :-))
--
[ebuild R ] app-office/openoffice-bin-2.4.0
Estimated update time: 5 minutes.
--
[ebuild N] app-office/openoffice-2.4.0
Estimated update time: 23 hours,
Volker Armin Hemmann wrote:
On Montag, 5. Mai 2008, Wolf Canis wrote:
Volker Armin Hemmann wrote:
On Montag, 5. Mai 2008, Wolf Canis wrote:
Volker Armin Hemmann wrote:
extremly long. So long that you have to start ooo several times a day
for a year so
Zdenek Travnicek wrote:
I don't know a machine with the name thunderbird :-[ . But I started
with Gentoo
on a Toshiba Tecra 8100, that's a PIII Copermine 800MHz and 512 MB RAM.
In this
respect, I can say: Yes, I did. :-) An emerge -e world lasted 11
hours, without OOO,
OOO alone
Sven Köhler wrote:
When you emerged grub-0.97-r5, this was displayed on your console:
WARN: postinst
*** IMPORTANT NOTE: you must run grub and install
the new version's stage1 to your MBR. Until you do,
stage1 and stage2 will still be the old version, but
later stages will be the new
Hello,
I just experienced the same problem. Could you solve your problem?
If so could you post the solution?
Some data of mine:
I'm in the groups:
groups=10(wheel),11(floppy),18(audio),19(cdrom),27(video),35(games),85(usb),100(users),250(portage),443(plugdev),1000(rh),1001(wireshark)
CD/DVD
Ian Hilt wrote:
On Fri, 9 May 2008 at 5:53pm +0200, Wolf Canis wrote:
Hello,
I just experienced the same problem. Could you solve your problem?
If so could you post the solution?
Some data of mine:
I'm in the groups:
groups=10(wheel),11(floppy),18(audio),19(cdrom),27(video),35(games),85
[EMAIL PROTECTED] wrote:
I've just started to use layman tools and wondered if setting such
things as /etc/portage/package.use would still be done in that same
place and same way?
I think yes.
I want to install an overlay of emacs-cvs but with different use flags
I would say there is no
Robin Atwood wrote:
grep -e ^\s+provide\s+\w /etc/init.d
but, as usual, nothing is matched. What am I doing wrong?
You have to use back slashed versions of metacharacters. Following
how would do that:
$ grep -e '^[[:space:]]\+provide[[:space:]]\+[a-z]\+' /etc/init.d/*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Atwood wrote:
grep -e ^\s+provide\s+\w /etc/init.d
but, as usual, nothing is matched. What am I doing wrong?
You have to use back slashed versions of meta characters. Following
how would do that:
$ grep -e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
it seems that sometimes mails of mine doesn't
go to the list. :-(
I had this problem just a couple of hours ago. I
send a reply to the thread Need help with a regex
but the mail doesn't reach the list. I looked in
the archive and it
.
and the second message:
Message was signed by Wolf Canis (Common) [EMAIL PROTECTED] (Key ID:
0xA174B705).
The signature is valid, but the key is untrusted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Norberto Bensa wrote:
Signed messages doesn't make any sense on a mailing list.
I may ask you for a explanation, please?
I think they make a lot of sense, because you or the
mailing system are able to verify the message or rather
the origin, if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mick wrote:
This is a nice list with helpful people.
No doubt about that. :-)
There are other lists however, when
it is not that rare for malicious (or unhinged) individuals to impersonate
someone else and hijack their email address to publish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
»Q« wrote:
Wolf Canis [EMAIL PROTECTED] wrote:
Would know a message reach the ML with my Name but no signature or a
different signature, could one relatively be sure about the fact that
this particular message is not from the original Wolf Canis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Iliev wrote:
[...]
Absolutely. I just wonder how many people will choose not to use such
kind of list in order not to sacrifice their anonymity.
Exactly.
[...]
It also might be the same person signing with different keys or
sometimes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Humphrey wrote:
I have no problem chrooting into a system on the hard disk if I've booted
from an installation CD, but every time I try it after booting from another
HD partition I get e.g. this:
# chroot /mnt/rescue /bin/bash
chroot:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Iliev wrote:
Come ooon! :)
The whole bet thing was of course a joke.
What I had in mind is that you'd have to hack Gmail which I believe
won't classify as relatively easy. Not to mention that even just
for proof of concept this would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Iliev wrote:
Unfortunately many times one cannot control the reverse records,
because the IP address pool belongs to the ISP. Nevertheless the SMTP
server logs the IP address which the message came from. It doesn't
matter if the message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Humphrey wrote:
[...]
# cd /mnt/rescue
# mount -tproc proc proc
# mount -obind /dev dev
I mean that the mount commands should be:
# mount -tproc proc /mnt/rescue/proc
# mount -obind /dev /mnt/rescue/dev
I just build a mini chroot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wolf Canis wrote:
Peter Humphrey wrote:
[...]
# cd /mnt/rescue
# mount -tproc proc proc
# mount -obind /dev dev
I mean that the mount commands should be:
# mount -tproc proc /mnt/rescue/proc
# mount -obind /dev /mnt/rescue/dev
Ooops, I
Ivan Alden wrote:
Hi,
My laptop ran out of battery and shut off while I was using it and it
seems to have done some damage to the bootloader. When I reboot I can't
see the grub splashscreen any more but if I press enter I does boot into
my kernel. As the computer is booting the output looks
Oh sorry,
_very_ _important_ :
Mount your boot partition _before_ you emerge grub.
W. Canis
signature.asc
Description: OpenPGP digital signature
Mick wrote:
On Sunday 20 July 2008, Wolf Canis wrote:
Oh sorry,
_very_ _important_ :
Mount your boot partition _before_ you emerge grub.
I believe that the grub ebuild mounts it for you, messes up your grub.conf
and
carries on with its business . . .
So far I that now, is that now
Mick wrote:
On Sunday 20 July 2008, Wolf Canis wrote:
Mick wrote:
On Sunday 20 July 2008, Wolf Canis wrote:
Oh sorry,
_very_ _important_ :
Mount your boot partition _before_ you emerge grub.
I believe that the grub ebuild mounts it for you, messes up your
grub.conf and carries
33 matches
Mail list logo
