[gentoo-user] linux-headers-2.6.38
While I'm about to do an `emerge -e @world` ... Should I `emerge -av =sys-kernel/linux-headers-2.6.38 ` ? Any benefits over the current sys-kernel/linux-headers-2.6.36.1 ? Rgds, -- Pandu E Poluan ~ IT Optimizer ~ • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
[gentoo-user] Re: linux-headers-2.6.38
Pandu Poluan pa...@poluan.info writes: While I'm about to do an `emerge -e @world` ... Should I `emerge -av =sys-kernel/linux-headers-2.6.38 ` ? Any benefits over the current sys-kernel/linux-headers-2.6.36.1 ? There is at least a theoretical benifit if you set NPTL_KERN_VER=2.6.38 in make.conf and recompile glibc. That way glibc could use things not present in older kernels. I haven't researched if there are any such things, perhaps someone else knows. Also, beware. If you recompile glibc withe NPTL_KERN_VER set, you can't boot with older kernels anymore. -- Christer
[gentoo-user] Re: Network Topology Diagrams
meino.cramer at gmx.de writes: lanmap2's github -- what it seems the only source for the source of it -- points to a 404 Error page. Is there any other, valid link to it? https://github.com/frac/lanmap2 https://github.com/frac/lanmap2/archives/master Let me know if you hack an ebuild for it James
Re: [gentoo-user] Re: linux-headers-2.6.38
On Wed, Aug 10, 2011 at 20:02, c...@chrekh.se wrote: Pandu Poluan pa...@poluan.info writes: While I'm about to do an `emerge -e @world` ... Should I `emerge -av =sys-kernel/linux-headers-2.6.38 ` ? Any benefits over the current sys-kernel/linux-headers-2.6.36.1 ? There is at least a theoretical benifit if you set NPTL_KERN_VER=2.6.38 in make.conf and recompile glibc. That way glibc could use things not present in older kernels. I haven't researched if there are any such things, perhaps someone else knows. Hmmm... without a reference, I'd rather not do something too drastic... Also, beware. If you recompile glibc withe NPTL_KERN_VER set, you can't boot with older kernels anymore. Can you explain what did you mean with older kernels? Kernels older than a certain version, or a previously-compiled kernel on my system? Anyways, this is a fresh install, so I don't think I'll have any trouble. But will still appreciate a reference and/or explanation re: NPTL_KERN_VER, though. Rgds -- FdS Pandu E Poluan ~ IT Optimizer ~ • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
[gentoo-user] Re: linux-headers-2.6.38
Pandu Poluan pa...@poluan.info writes: On Wed, Aug 10, 2011 at 20:02, c...@chrekh.se wrote: Also, beware. If you recompile glibc withe NPTL_KERN_VER set, you can't boot with older kernels anymore. Can you explain what did you mean with older kernels? Kernels older than a certain version, or a previously-compiled kernel on my system? Older then the kernel you specified, previously-compiled kernels not older than that is still fine. Any executable linked to glibc will fail unconditionally with FATAL: Kernel too old, including init. Anyways, this is a fresh install, so I don't think I'll have any trouble. But will still appreciate a reference and/or explanation re: NPTL_KERN_VER, though. glibc will be configured with --enable-kernel=2.6.38 The configure help says this; --enable-kernel=VERSION compile for compatibility with kernel not older than VERSION -- Christer
Re: [gentoo-user] Run command after root mounted ro?
Am 10.08.2011 03:04, schrieb Daniel Frey:
On 01/-10/37 11:59, Florian Philipp wrote:
Remounting root read-only is done by an init script called mount-ro
which is started in runlevel shutdown. Try to add a custom init script
to your /etc/init.d directory with the following content:
#!/sbin/runscript
depend()
{
after mount-ro
}
start()
{
ebegin 'Shutting down mdadm'
mdadm --wait-clean --scan
eend $?
}
Add it to the runlevel with `rc-update add your-script shutdown` and
don't forget to mark it executable.
Disclaimer: I've not tried this (obviously) and if the script eats your
dog and wreaks your system, it is entirely your fault ;)
Thanks, I tried this out, and while it does run after mounting ro, it
just hangs. I've noticed that it's supposed to be monitoring
/proc/mdstat but it was (presumably) unmounted long ago.
I guess I have to do some more experimenting.
Dan
Try remounting proc in your new init script. You have to advice mount to
not try adding it to /etc/mtab since that would obviously fail.
mount --no-mtab -t proc proc /proc
Hope this helps,
Florian Philipp
signature.asc
Description: OpenPGP digital signature
Re: [gentoo-user] IOMMU and other oddities...
Am Dienstag 09 August 2011, 07:32:34 schrieb meino.cra...@gmx.de: Hi, my PC consists -- beside other things -- of a AMD Phenom II X6 1090T, a ASUS Crossfire Formula IV and a NVidia GeForce GT 430 by MSI (PCIe). Furthermore I am using the vanilla Linux kernel 3.0.1. . I browsed through the output of dmesg and found these lines: Checking aperture... No AGP bridge found Node 0: aperture @ c400 size 32 MB Aperture pointing to e820 RAM. Ignoring. Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM Mapping aperture over 65536 KB of RAM @ c400 The kernel is not configured with any AGP-related (as far as I now) feature/config. Why does it look for an AGP-bridge??? The dmesg says I should switch on IOMMU, which I did. But that does not impress the kernel that much since it still recommends to switch on IOMMU. What did I wrong here ? I want to fix issues, which may be reported by dmesg, so: Where can I find explanations to the dmesg output? For your information I attached the compressed dmesg output to this mail. Thank you very much for your help in advance! Best regards mcc see also this: http://marc.info/?l=linux-kernelm=107764033904042w=2 -- #163933
[gentoo-user] vsftpd: how can I chroot both anon and auth users to the same dir?
Hi, I'm using vsftpd and I'm quite satisfied, except for one problem which I can not solve: Anonymous users are chrooted to base ftp-server directory /home/ftp but local users are chrooted to their own directories /home/ftp/$USER and they can not move higher. The only way for them to see directories of other local users is to log-off and log-in as anonymous. This is not very convenient. Why should authenticated user be allowed less (in this particular aspect) than anonymous? So I'd like to change it the way that both anonymous as well as local users are chrooted to base ftp directory /home/ftp but I do not know how to do it. Whe I remove chroot_local_users=YES from vsftpd.conf, local users are not chrooted at all, and can move around the whole system up to /. And when I let that chroot_local_users=YES activated, they are chrooted to home-dirs. So how can I solve this problem? Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] vsftpd: how can I chroot both anon and auth users to the same dir?
On 08/10/11 12:37, Jarry wrote: Hi, I'm using vsftpd and I'm quite satisfied, except for one problem which I can not solve: Anonymous users are chrooted to base ftp-server directory /home/ftp but local users are chrooted to their own directories /home/ftp/$USER and they can not move higher. The only way for them to see directories of other local users is to log-off and log-in as anonymous. This is not very convenient. Why should authenticated user be allowed less (in this particular aspect) than anonymous? So I'd like to change it the way that both anonymous as well as local users are chrooted to base ftp directory /home/ftp but I do not know how to do it. Whe I remove chroot_local_users=YES from vsftpd.conf, local users are not chrooted at all, and can move around the whole system up to /. And when I let that chroot_local_users=YES activated, they are chrooted to home-dirs. So how can I solve this problem? Why not just chroot anonymous users to /home/ftp/public?
Re: [gentoo-user] vsftpd: how can I chroot both anon and auth users to the same dir?
On 10-Aug-11 19:35, Michael Orlitzky wrote: Anonymous users are chrooted to base ftp-server directory /home/ftp but local users are chrooted to their own directories /home/ftp/$USER and they can not move higher. The only way for them to see directories of other local users is to log-off and log-in as anonymous. This is not very convenient. Why should authenticated user be allowed less (in this particular aspect) than anonymous? So I'd like to change it the way that both anonymous as well as local users are chrooted to base ftp directory /home/ftp but I do not know how to do it. Why not just chroot anonymous users to /home/ftp/public? If I wanted to have one more problem (anonymous users not able to access local users' files) I would do it... :-) I'll try to explain it one more time. I have local users user1, user2, userX and their home directories are: /home/ftp/user1 /home/ftp/user2 /home/ftp/userX Anonymous users are chrooted to /home/ftp, so they can access files stored in /home/ftp/user1 (user2, userX). That is OK, that is what I want. But local user1 is chrooted to /home/ftp/user1, so he can't access files in /home/ftp/user2 (or /home/ftp/userX). And *this* is what I want to solve: to give local users the same possibility to access other users' files (if file access permissions allow it, of course). So I want to chroot local users to the very same /home/ftp directory where anonymous users are chrooted, but I do not know how... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] Which gcc unstable?
Pandu Poluan wrote: On Wed, Aug 10, 2011 at 08:14, Dalerdalek1...@gmail.com wrote: Pandu Poluan wrote: I noticed Dale's email (hi Dale!) [1] asking about which gcc / glibc unstable to use. Is there any consensus yet as to which 'gcc'? I'm planning on doing an `emerge -e @system` on two fresh installs, one x86 and the other amd64. Should I go with 4.5.3? Or 4.5.2? Or play it safe and use 4.5.1-r1 (which, based on b.g.o search [2], seems to have less (serious) bugs compared to 4.5.2) Howdy, I'm using this: root@fireball / # equery list gcc glibc * Searching for gcc ... [IP-] [ ] sys-devel/gcc-4.4.5:4.4 [IP-] [ ] sys-devel/gcc-4.5.3:4.5 So, 4.5.3 is quite safe for day-to-day usage eh? Okay, keywording it. Thanks! * Searching for glibc ... [IP-] [ ] sys-libs/glibc-2.13-r4:2.2 root@fireball / # The higher gcc is the one in use. Everything compiles fine. One thing tho, I started a download and went to town. When I got back, I was sitting at my grub menu. Most likely not related but wanted to mention just in case. ;-) Yea, my reboot issues is happening again. :-@ Hmmm, just a hunch: Have you tried updating the motherboard's firmware? Rgds, I did upgrade it a while back. I'll check and see if there is a new one now. I hadn't thought of that before. We all know that a update fixes some bugs but introduces several new ones. lol Reminds me of Raid. Kill some but new babies come out a few days later. New bugs but still problems. :/ Thanks much. Great hunch. Dale :-) :-)
Re: [gentoo-user] Which gcc unstable?
Dale wrote: I did upgrade it a while back. I'll check and see if there is a new one now. I hadn't thought of that before. We all know that a update fixes some bugs but introduces several new ones. lol Reminds me of Raid. Kill some but new babies come out a few days later. New bugs but still problems. :/ Thanks much. Great hunch. Dale :-) :-) OK. Here is a linky: http://www.gigabyte.com/products/product-page.aspx?pid=3320dl=1#bios There is a update but I don't think it is something I should need. It has a brief description of what is changed. Does anyone think I should update this anyway? They always say not to upgrade unless it is going to fix something since it can break things. I'm on F4 now by the way. The F5A would be the new one. Thoughts? Yeps or nopes would be great. Alan, Neil and other gurus. Dale :-) :-)
Re: [gentoo-user] vsftpd: how can I chroot both anon and auth users to the same dir?
On 08/10/11 13:52, Jarry wrote: If I wanted to have one more problem (anonymous users not able to access local users' files) I would do it... :-) I'll try to explain it one more time. I have local users user1, user2, userX and their home directories are: /home/ftp/user1 /home/ftp/user2 /home/ftp/userX Anonymous users are chrooted to /home/ftp, so they can access files stored in /home/ftp/user1 (user2, userX). That is OK, that is what I want. But local user1 is chrooted to /home/ftp/user1, so he can't access files in /home/ftp/user2 (or /home/ftp/userX). Oh, ok. I didn't realize you wanted all users to be able to see the same hierarchy. I figured you were allowing anonymous users more access just to avoid the logical inconsistency =) And *this* is what I want to solve: to give local users the same possibility to access other users' files (if file access permissions allow it, of course). So I want to chroot local users to the very same /home/ftp directory where anonymous users are chrooted, but I do not know how... Are they local users? Change their home directories to /home/ftp.
Re: [gentoo-user] vsftpd: how can I chroot both anon and auth users to the same dir?
On Wed, Aug 10, 2011 at 11:37 AM, Jarry mr.ja...@gmail.com wrote: Hi, I'm using vsftpd and I'm quite satisfied, except for one problem which I can not solve: Anonymous users are chrooted to base ftp-server directory /home/ftp but local users are chrooted to their own directories /home/ftp/$USER and they can not move higher. The only way for them to see directories of other local users is to log-off and log-in as anonymous. This is not very convenient. Why should authenticated user be allowed less (in this particular aspect) than anonymous? So I'd like to change it the way that both anonymous as well as local users are chrooted to base ftp directory /home/ftp but I do not know how to do it. Whe I remove chroot_local_users=YES from vsftpd.conf, local users are not chrooted at all, and can move around the whole system up to /. And when I let that chroot_local_users=YES activated, they are chrooted to home-dirs. So how can I solve this problem? I haven't used vsftpd in a long time but I believe you can do something like this: Set user_config_dir to point to someplace such as /etc/vsftpd/users In that directory, create files for each username and within it put: local_root=/home/ftp I think that might set all of those users to login to that folder. I have not tried it. :) There was also an option to use alternative home directories rather than the one specified in /etc/passwd, but I can't remember exactly what that was and it may have still used the username as part of the path. man vsftpd.conf should explain it.
Re: [gentoo-user] Which gcc unstable?
On Wednesday, August 10, 2011 01:09:53 PM Dale wrote: Dale wrote: I did upgrade it a while back. I'll check and see if there is a new one now. I hadn't thought of that before. We all know that a update fixes some bugs but introduces several new ones. lol Reminds me of Raid. Kill some but new babies come out a few days later. New bugs but still problems. :/ Thanks much. Great hunch. Dale :-) :-) OK. Here is a linky: http://www.gigabyte.com/products/product-page.aspx?pid=3320dl=1#bios There is a update but I don't think it is something I should need. It has a brief description of what is changed. Does anyone think I should update this anyway? They always say not to upgrade unless it is going to fix something since it can break things. I'm on F4 now by the way. The F5A would be the new one. Thoughts? Yeps or nopes would be great. Alan, Neil and other gurus. Dale :-) :-) Comment 2 Update CPU AGESA code might help. You'd need to google for what AGESA means. (Not done this yet) Comment 1, however, Beta BIOS makes me think you might not want to try it. Beta is generally, testing, it might break things. Am surprised they put a Beta up though. -- Joost
Re: [gentoo-user] Which gcc unstable?
on 08/10/2011 09:48 PM Joost Roeleveld wrote the following: Comment 2 Update CPU AGESA code might help. You'd need to google for what AGESA means. http://en.wikipedia.org/wiki/AGESA
Re: [gentoo-user] Which gcc unstable?
Thanasis wrote: on 08/10/2011 09:48 PM Joost Roeleveld wrote the following: Comment 2 Update CPU AGESA code might help. You'd need to google for what AGESA means. http://en.wikipedia.org/wiki/AGESA Yea, I googled it too. Basically, it is to support newer CPUs. Since my CPU works, that shouldn't be the problem. I'll wait until it at least gets out of beta. ;-) We all know my record on breaking things. lol Dale :-) :-)
Re: [gentoo-user] Which gcc unstable?
On 2011-08-10 22:38, Dale wrote: Yea, I googled it too. Basically, it is to support newer CPUs. Since Hm... the way I interpret it it seems similar to Intels microcode updates; this could be updates to support new CPUs and/or updates to handle bugs in the CPUs... my CPU works, that shouldn't be the problem. I'll wait until it at least gets out of beta. ;-) We all know my record on breaking things. lol Yes, if you feel there's nothing wrong with your CPU perhaps it's prudent to not update to a beta... Best regards Peter K
[gentoo-user] Re: Plasma-runtime compilation problems
On 08/09/2011 08:34 PM, Jeff Cranmer wrote: Hi all, I'm trying to upgrade kde from 4.4 to 4.6, and I've run into a problem. Plasma-runtime-4.6.3 is failing. The error appears to be redefinition of 'struct QMetaTypeIDPlasma::Service*' I don't use kde so I can't be specific, but usually a redefinition is just a warning -- unless the package is compiled with the -Wall flag or equivalent. Do you see lots of other redefinition warnings before the build stops? If so, you may be overlooking the real error message which may appear dozens of lines earlier Often I find the real error message embedded in a long list of harmless warnings, especially if I'm compiling with -j2 or higher. (Waiting for unfinished jobs is a good clue that the error occurred much earlier in the build.)
[gentoo-user] Re: Which gcc unstable?
On 08/10/2011 10:57 AM, Dale wrote: Pandu Poluan wrote: Hmmm, just a hunch: Have you tried updating the motherboard's firmware? I did upgrade it a while back. Why did you upgrade it the first time? Were you trying to fix a different problem back then?
Re: [gentoo-user] Which gcc unstable?
pk wrote: On 2011-08-10 22:38, Dale wrote: my CPU works, that shouldn't be the problem. I'll wait until it at least gets out of beta. ;-) We all know my record on breaking things. lol Yes, if you feel there's nothing wrong with your CPU perhaps it's prudent to not update to a beta... Best regards Peter K If it wasn't beta, I'd update anyway. At least then I would know what it is not, well most likely anyway. It's the beta that bothers me. I'll try to remember to check back in a month or so to see if it is out of beta. Maybe it does have some sort of fix in it. I sure would like one. I had several days of uptime then it crashed. It has worked fine since too. Dale :-) :-)
Re: [gentoo-user] Re: Which gcc unstable?
walt wrote: On 08/10/2011 10:57 AM, Dale wrote: Pandu Poluan wrote: Hmmm, just a hunch: Have you tried updating the motherboard's firmware? I did upgrade it a while back. Why did you upgrade it the first time? Were you trying to fix a different problem back then? I think so. It was a while back when I first bought this thing. I think it had a update for the network card or something. I'm not 100% sure tho. I do know Gigabyte said to upgrade to F3 or higher. I actually sent them a message to see if it was mobo or what. When I did it tho I had my old rig sitting right here beside me so switching was easy. Now, my old rig is in another room and switching would be more difficult. I update the old rig once a month but it is over ssh. It doesn't even have a monitor now. Poor thing. Dale :-) :-)
Re: [gentoo-user] Re: Plasma-runtime compilation problems
Hi,
Am Mittwoch, 10. August 2011, 14:40:31 schrieb walt:
On 08/09/2011 08:34 PM, Jeff Cranmer wrote:
Hi all,
I'm trying to upgrade kde from 4.4 to 4.6, and I've run into a problem.
Plasma-runtime-4.6.3 is failing. The error appears to be
redefinition of 'struct QMetaTypeIDPlasma::Service*'
I don't use kde so I can't be specific, but usually a redefinition is
just a warning -- unless the package is compiled with the -Wall flag or
equivalent.
No, this is plain wrong. Redefinition of a struct is an error in C and C++
~$cat foo.c
struct foo {
int i;
};
struct foo {
char* v;
};
~$gcc foo.c -o foo
foo.c:5:8: error: redefinition of 'struct foo'
foo.c:1:8: note: originally defined here
-Wall enables some more warnings and has nothing to do with errors at all.
-Werror is the switch that turns warnings into errors.
Regards,
Michael
[gentoo-user] Re: Plasma-runtime compilation problems
On 08/10/2011 03:04 PM, Michael Schreckenbauer wrote:
Hi,
Am Mittwoch, 10. August 2011, 14:40:31 schrieb walt:
On 08/09/2011 08:34 PM, Jeff Cranmer wrote:
Hi all,
I'm trying to upgrade kde from 4.4 to 4.6, and I've run into a problem.
Plasma-runtime-4.6.3 is failing. The error appears to be
redefinition of 'struct QMetaTypeIDPlasma::Service*'
I don't use kde so I can't be specific, but usually a redefinition is
just a warning -- unless the package is compiled with the -Wall flag or
equivalent.
(Of course I meant -Werror, sorry.)
No, this is plain wrong. Redefinition of a struct is an error in C and C++
~$cat foo.c
struct foo {
int i;
};
struct foo {
char* v;
};
~$gcc foo.c -o foo
foo.c:5:8: error: redefinition of 'struct foo'
foo.c:1:8: note: originally defined here
Hm. I know I've seen compiler redefinition messages thousands of times
over the years. Is it really possible that all of those thousands were
errors instead of warnings? If that's true then I've wasted a lot more
time tracking them down than I care to think about :)
Re: [gentoo-user] Re: Plasma-runtime compilation problems
On Wed, 2011-08-10 at 16:16 -0700, walt wrote:
On 08/10/2011 03:04 PM, Michael Schreckenbauer wrote:
Hi,
Am Mittwoch, 10. August 2011, 14:40:31 schrieb walt:
On 08/09/2011 08:34 PM, Jeff Cranmer wrote:
Hi all,
I'm trying to upgrade kde from 4.4 to 4.6, and I've run into a problem.
Plasma-runtime-4.6.3 is failing. The error appears to be
redefinition of 'struct QMetaTypeIDPlasma::Service*'
I don't use kde so I can't be specific, but usually a redefinition is
just a warning -- unless the package is compiled with the -Wall flag or
equivalent.
(Of course I meant -Werror, sorry.)
No, this is plain wrong. Redefinition of a struct is an error in C and C++
~$cat foo.c
struct foo {
int i;
};
struct foo {
char* v;
};
~$gcc foo.c -o foo
foo.c:5:8: error: redefinition of 'struct foo'
foo.c:1:8: note: originally defined here
Hm. I know I've seen compiler redefinition messages thousands of times
over the years. Is it really possible that all of those thousands were
errors instead of warnings? If that's true then I've wasted a lot more
time tracking them down than I care to think about :)
I've seen lots of compiler warnings in the past. This one, however, was
flagged as an 'Error', not as a warning. It was the last message before
the compile failed, so I think it's reasonable to assume that therein
lies the problem?
I have emerged all system files, as well as a lot of the world files
that are currently out of date. This particular compilation failure
happened late in an emerge -NDuav kdebase-meta, as the first part of the
upgrade from kde4.4 to kde4.6
Running revdep-rebuild following the emerge didn't help. I still have
some world files that are out of date, but all of those are allegedly
not deep dependencies of kdebase-eta. Last time I tried to do a full
emerge -NDuav world, however, I was then unable to operate my HDPVR
unit, as it suffered a lot of usb failures. I had to recover my system
from an earlier clonezila backup, so now I'm trying to sneak up on the
problem by doing as little as possible each emerge, then checking
everything works and running another OS clone before continuing.
Unfortunately, kde is now broken, so I'm operating my mythtv interface
via gnome while I attempt to recover kde. It's probable that the fault
lies in one of the other packages within world that are still to be
upgraded, but it would be nice to get some clues as to which one is the
culprit, so I can continue to inch up on whatever is breaking my HDPVR
based mythtv.
Jeff
[gentoo-user] Re: linux-headers-2.6.38
On 08/10/2011 04:02 PM, c...@chrekh.se wrote: Pandu Poluanpa...@poluan.info writes: While I'm about to do an `emerge -e @world` ... Should I `emerge -av =sys-kernel/linux-headers-2.6.38 ` ? Any benefits over the current sys-kernel/linux-headers-2.6.36.1 ? There is at least a theoretical benifit if you set NPTL_KERN_VER=2.6.38 in make.conf and recompile glibc. That way glibc could use things not present in older kernels. I haven't researched if there are any such things, perhaps someone else knows. glibc will use things in newer kernels anyway. You don't need to use NPTL_KERN_VER=2.6.38 in order for glibc to use 2.6.38 features; it will do that by default. NPTL_KERN_VER only omits fallbacks for older kernels. It's there to reduce the size of glibc. The size difference is very small though.
Re: [gentoo-user] Re: Plasma-runtime compilation problems
Jeff Cranmer wrote: I've seen lots of compiler warnings in the past. This one, however, was flagged as an 'Error', not as a warning. It was the last message before the compile failed, so I think it's reasonable to assume that therein lies the problem? SNIP Jeff I can see where one would think that but it is often not the case. I had a compile to fail a few months ago, I had to go way back to find the original failure. It was far enough back that I had to copy the whole thing to a editor and use the find feature to find it. I use Konsole for most of this but I bet it was 7 or 8 screens further back than where it ended up failing. I am on a 4 core rig so that may have a bit to do with it but I have ran into the same on my older rig that is single core. It is amazing how far back the original problem is sometimes. May want to consider looking further back or just posting as a attachment or something. Dale :-) :-)
Re: [gentoo-user] Zynaddsubfx connected to Rosegarden WITHOUT Jack?
Hi Michael, thank you for your info ! :) What do I need for a midi connection (sorry, I am at the very beginning of exploring these kind of tools and jack is everywhere... ;) ) Best regards, mcc Michael Schreckenbauer grim...@gmx.de [11-08-11 02:45]: Hi Meino, Am Dienstag, 9. August 2011, 21:13:42 schrieb meino.cra...@gmx.de: Hi, may be this is a RDQ(tm) (real dumb question), but Is it possible to connect rosegarden and ZynAddSubFX without using jack ??? you could use a MIDI connection. But imho jack is the way to go :) Thank you very much for any help in advance! Best regards, mcc Hth, Michael
[gentoo-user] Re: wget killed -- wonder where I went wrong...
On Thu, Aug 11, 2011 at 12:24, Pandu Poluan pa...@poluan.info wrote: On Mon, Aug 8, 2011 at 20:11, Pandu Poluan pa...@poluan.info wrote: Hello folks! After installation and successful 1st reboot, all attempts at wget gets killed: [-- massive snippage --] Okay, now, where did I go wrong? So, apparently, I'm not alone. But #378449 [1] is full of people with similar experience. And hardened-sources-2.6.39-r9 has been removed from the tree [1] [2] [1] https://bugs.gentoo.org/378449?id=378449 [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-kernel/hardened-sources/ChangeLog?view=markup :%s/But/Bug/g Rgds, -- FdS Pandu E Poluan * ~ IT Optimizer ~** * • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
[gentoo-user] Re: wget killed -- wonder where I went wrong...
On Mon, Aug 8, 2011 at 20:11, Pandu Poluan pa...@poluan.info wrote: Hello folks! After installation and successful 1st reboot, all attempts at wget gets killed: [-- massive snippage --] Okay, now, where did I go wrong? So, apparently, I'm not alone. But #378449 [1] is full of people with similar experience. And hardened-sources-2.6.39-r9 has been removed from the tree [1] [2] [1] https://bugs.gentoo.org/378449?id=378449 [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-kernel/hardened-sources/ChangeLog?view=markup Rgds, -- FdS Pandu E Poluan * ~ IT Optimizer ~** * • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
Re: [gentoo-user] Which gcc unstable?
On Wednesday, August 10, 2011 11:11:48 PM pk wrote: Yea, I googled it too. Basically, it is to support newer CPUs. Since Hm... the way I interpret it it seems similar to Intels microcode updates; this could be updates to support new CPUs and/or updates to handle bugs in the CPUs... There was a thread on here started on January 17 about AMDs microcode and how to get that to work. If it's a bugfix for AMD cpus, you might be able to apply that using software during boot. -- Joost
