Jump to content

iphitus

Global Moderator
  • Posts

    3831
  • Joined

  • Last visited

Posts posted by iphitus

  1. Thanks for the quick answer. My keyboard comes with no ps2/usb adapter, and I think it may not even work with one, considering it is a whireless thing and it controls keyboard and mouse too. Anyway, thanks.

     

    ouch that's a pity. seeing as the computer doesnt have usb support in bios, it can't be too new, so do you have the original PS/2 keyboard about anywhere?

  2. Ok, two questions then - is the resulting information then only available to KDE applications? Or only to Nepomuk-aware KDE applications?

     

    and on that, what are it's dependencies? A google shows its included in kdelibs, which is a real disappointment as it seems to be a step toward more intelligent file management.

     

    James

  3. As much as I am a wannabe geek, i'm no good when it comes to flicking through documents on screen.

     

    I can't stand documents on a screen either. What I would like though, is a tablet pc or one of those ebook readers, that'd make it much more bearable.

     

    For notes and todo: I use a small, A2 sized book split into categories with some tabs. The one i have atm is spiral bound, so i chuck a pen in the spiral.

    For dates: I try to use my uni diary, but usually I end up remembering them myself. Going to print out calendars and glue them into the aforementioned notebook instead.

    For email: I bought myself a dreamhost account on sunday, and download all my email accounts to the one place and read it via imap or the webmail ui.

     

    I wouldnt mind a pda, but I can't afford one, and the above setup works pretty well.

     

    James

  4. Are you sure about the multi-thread thing?

    Here at work, we run Sun's Java5 JDK on Redhat on a dual-processor dual-core (total: 4 cores). We have a thread pool hence lots of threads, yet one core shows at roughly 80% while other cores are idle.

    Same on another server with 4 CPUs (total 8 cores).

    Yet as far as I know, Java is running with native threads and in server mode...

    Guess that depends on how it's scheduled. There are ways to tie processes to a particular processor. In this case, it sounds like many of those threads are idle, and what is running, isnt overstressing the active core, so theres no need to schedule it to another.

     

    Under linux "threads" are practically seperate processes, except they share some memory with their parent process, thus they may be scheduled to run on any processor.

     

    On a different subject, is it possible to force both cores to combine power for a single application. I'd be interested in running mencoder at 90% of both cores instead of a single core.

     

    Yves.

    No. The program needs to be explicitly designed to via the use of threads or multiple processes.

     

    You could though, split the movie you want to encode into two pieces, and then have a mencoder process encoding each. Though then you need to find a way to join them.

     

    James

  5. Yeah, hopefully the triage is improving. It's hard to tell from the outside.

     

    I disagree though ianw1974, they do need a new one badly. The current one is *miserable*. Searches literally take minutes. I've written this post in the time it's taken it to load up the list of bug reports i've made. Given that to do any triage, they need to search for new bugs, and existing bugs, that'd really slow them down, and a new one should drastically improve the triage effort.

     

    The triage is just the first step, the important bit is having the bugs *fixed*. We'll see the results of this effort in the next Mandriva release.

     

    James

  6. Unless you specifically know what code in the kernel is causing the problem for grub, and it is not the naming convention, it is impossible to intelligently discuss whether the kernel changes causing the problem are worth the aggravation caused to other developers. As I previously stated, there may be very good reasons for those kernel changes and those changes may significantly improve the kernel.

    I can appreciate the aggravation you have with the moving target the 2.6 kernel has become. However, if you want to use the linux kernel, that's the development model you're stuck with. And if grub wants to claim it can boot linux, their devs should deal with it as well as I'm confident they are.

     

    Such major changes should be made in a 2.7 cycle. NOT a "stable" cycle of 2.6

     

    I understand that the development of the kernel is a different process than it used to be, and that 2.6 isnt really a "stable" cycle as it once was. But it's becoming clear that it isnt feasible. Since adopting this new style, stability has gone *way* downhill. This is acknowledged quite globally by developers such as Greg KH[1], Dave Jones[2], and others.

     

    To try and remedy this, the y (2.6.x.y) release was created, and is currently maintained by Greg KH. It's become a great way of distributing security fixes quickly, though it still fails to cover many bugs that exist upon each release and is more of a band-aid than a solution. Adrian Bunk is *still* distributing the 2.6.16 kernel, now up to 2.6.16.52 [3], including many bug fixes and security fixes. This is a pretty solid kernel, and worked well on my laptop, excepting a resume from sleep bug that was fixed in later kernels.

     

    Distributions now need to include ridiculous amounts of patches, far far more than they ever needed to. This has inherent faults (see [1][2] again), many patches arent as well tested, and induce problems for others. What do the distros do? they're damned if they do include them, damned if they dont. This LWN subscriber article[4] describes the situation for some distributors well

     

    Take a look at this subscriber article from LWN which explains the situation of many distros quite well. [4]

     

    A 2.7 cycle would make more sense. Such changes as, libata, tickless kernel and hrtimers, overdue new suspend system, new scheduler, sem2mutex, and other major changes could have been developed far more agressively and in a better environment. This doesnt prevent them from being merged back to 2.6, as backports have historically been common, with many things being backported to 2.4. Along with an accellerated 2.7 cycle compared to previous odd numbered cycles, this is one possible solution.

     

    Maybe it's not an ideal solution, but changes do need to be made, and I'd rather criticise constructively and offer some sort of alternative, then just badmouth.

     

    I could rant for ages on the kernel, there's a host of other issues with the current development style. It works, but I think the talent of the kernel developers could be used better, and the kernel could work far better.

     

    James

     

    [1] http://www.kroah.com/log/linux/enterprise_kernel_future.html

    [2] http://kernelslacker.livejournal.com/82610.html

    [3] http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.52

    [4] http://lwn.net/SubscriberLink/239036/76e19bbb9ff0acd8/ - Subscriber only article, though lwn allow and encourage subscribers to post links to non-subscribers. LWN is an awesome resource, it offers a great summary of the weeks news in Linux, as well as many good articles. It's not expensive, and is a worthwhile investment if you spend plenty of time reading up on RSS feeds, checking news sites, or are a developer of a project.

  7. I discovered that Grub sometimes gets mixed up in a mixed environment with both ide and sata/scsi devices. When I installed Fedora on my laptop, it would not boot because it wanted to call my hard drive boot partition sda2 instead of hda2. It did the same on my brother's machine, with Mandirva rather than Fedora, but an edit of Grub fixed the problem. (On my brothers, it tried to boot hdb1, where the drive was on sda1.) In both cases the fix was to check that the file named the correct devices. So it is a good policy to look at the file, whether lilo or grub, before completing the install.

     

    I have used both lilo and Grub with 4 or more operating systems. I have also experienced problems with both.

     

    That's not grub, it's the kernel. As of 2.6.21 or 20, i cant remember, the kernel moved to the new libATA subsystem, which has all devices, sata and IDE named sdXX. If the installer spat out a bad grub.conf, you can hardly blame grub anyway, that's an installer bug, not grub. One of the criticims of grub, and things fixed in grub2, is it's naming. it uses it's own naming, different to the kernel, and this tends to cause confusion.

  8. grub v lilo's also a bit of a religious flamewar. I've used both successfully for extended periods of time, and most errors or criticism for either that I see, were caused by the user, not the bootloader.

     

    in reality, both suck in different ways because of their design.

     

    Once GRUB2 is released, I think we'll see a lot of these issues solved. GRUB2 is a redesign, and shares nothing with it's previous version.

     

    http://www.gnu.org/software/grub/grub-2.en.html

  9. Of course, but that's not the point. The point is that when you have a separate /home partition, you can see what data belongs to what part, since he obviously doesn't know that now.

    And I suggest that it would be rather easy to fix - having "/home" separate makes it so much easier to handle in the long run that maybe it's worth the trouble.

    And, of course, you don't have to have 12 GB for the "/" partition; that's just if you allow yourself the luxury to copy the contents of the DVD to disk (which I usually do).

     

    oh but it is the point. it's too late to separate home now. so we need to identify where the space is used, using tools like du, and filelight.

  10. Your audio driver is snd-hda-intel. Try killing all sound apps (esd, xmms, arts, whatever) and removing it.

     

    The other thing it could be, is a noisy capacitor. I have a similar whine that is audible on my laptop when running a kernel that operating at a high hz. For that, the fix is to either run >=2.6.21 or build a kernel with a hz of 100.

     

    James

  11. The partitioning isnt going to fix anything, though it might have been nice if done at install time. If he had a seperate /home, he'd have less space everywhere, his remaining space would be split between the two. So now, there's no point moving home, it'll result in less space for / and /home.

     

    It's the same amount of data, in the same space, but now the remainder is split.

     

    James

  12. in a shell, do hdparm -y /dev/xdx where xdx is your hdd, be it hda, sda or whatever. Does the whine dissappear before it spins back up (you should be able to clearly hear it spin down and up). Additionally, if you can, try and identify where in the computer the hdd is located. It's often not too hard as they tend to be user servicable in most laptops. See if the sound is coming from there, or elsewhere.

     

    Could also be coming from your sound system. Unload your sound card's driver with rmmod (post the output of 'lsmod' if you don't know which it is and we'll point it out), and spin the hdd down to see if you can hear anything.

     

    James

  13. I was using feisty, don' t know if they have wine running at startup :s

    what do you mean, they are malware of course?

    But I really wonder what this explorer.exe process was doing, it was taking up *a lot* of cpu

     

    coulda been doing anything...

     

    sending spam, participating in a botnet, ddos attacks, infecting documents...

     

    maybe it might be good if you get one of those virus scanners for linux and make sure you've left no traces :)

     

    James

×
×
  • Create New...