Jump to content

RVDowning

Members
  • Posts

    505
  • Joined

  • Last visited

Posts posted by RVDowning

  1. I just got a netbook and was wondering if I should use the netbook kernel (2010.0). What is the benefit over the regular desktop kernel? -- just smaller or what? I am going to install virtualbox (PUEL) and it needs the kernel source so when looking through the downloads I noticed the netbook kernel. I hadn't known there was such a thing. So, should I change to the netbook one?

     

     

    [moved from Software by spinynorman]

  2. I've been using compiz-fusion on kde 4.x on Mandriva 2009.1 with 9 virtual double-wide (dual monitors) desktops with each having its own different background. I think there was supposed to be some kind of conflict with using icons on the desktop though, but I have never had any icons on my desktop so it was no bother.

     

    I don't use any of the kde 4 features though. The more it starts to look like 3.5 the better it seems to get.

  3. Has anyone gotten rdesktop to work outside of a lan? Neither I nor my buddy, who is not running Mandriva, have been able to use rdesktop to connect to our office location which runs Windows XP. However, I can bring up VirtualBox and then WinXP and connect from WinXP. It would be nice not to have to bring up Windows.

     

    Edited to note that we use tunneling. I believe it is this that is causing the problem. It is as though rdesktop is not using the tunneling ip, but is instead trying to go out over the network.

  4. Hmmmm. Ya know...... My web site is actually on a linux machine...... It is a web hosting service, but I actually have a virtual machine. I'll have to check that. It had never crossed my mind. May not get to it tonight. I have a road race in the morning (worlds largest 10k) and it about time for me to start preparing stuff and then get to bed. I'll post back after I get a chance to check it.

     

    Thanks for the insight.

     

    Rich

  5. # ls -la (in /etc/lograte.d)

    total 43

    drwxr-xr-x 2 root root 272 2009-07-03 16:46 ./

    drwxr-xr-x 104 root root 6800 2009-07-03 09:54 ../

    -rw------- 1 root root 96 2009-07-03 16:46 .directory

    -rw-r--r-- 1 root root 60 2009-06-15 11:33 kdm

    -rw-r--r-- 1 root root 448 2009-04-23 09:05 msec

    -rw-r--r-- 1 root root 136 2008-12-17 12:34 ppp

    -rw-r--r-- 1 root root 180 2009-02-06 06:23 preload

    -rw-r--r-- 1 root root 61 2009-06-18 04:55 rpm

    -rw-r--r-- 1 root root 61 2009-05-31 13:02 sudo

    -rw-r--r-- 1 root root 438 2009-02-05 12:34 syslog

    -rw-r--r-- 1 root root 71 2009-03-07 00:34 xdm

     

     

    There was a hidden file in /etc/logrotate.d called ".directory" with the following content:

     

    [Dolphin]

    AdditionalInfo=3

    Timestamp=2009,7,3,16,46,26

    ViewMode=1

     

    [settings]

    ShowDotFiles=true

     

    Ha, wouldn't you know that Dolphin has its dirty fingers in there somehow.

  6. Still puzzled:

     

    # logrotate -v /etc/logrotate.conf

    reading config file /etc/logrotate.conf

    including /etc/logrotate.d

    reading config file .directory

    error: .directory:1 lines must begin with a keyword or a filename (possibly in double quotes)

    error: .directory:2 unknown option 'AdditionalInfo' -- ignoring line

    error: .directory:2 unexpected text

    error: .directory:3 unknown option 'Timestamp' -- ignoring line

    error: .directory:3 unexpected text

    error: .directory:4 unknown option 'ViewMode' -- ignoring line

    error: .directory:4 unexpected text

    reading config file kdm

    reading config info for /var/log/kdm.log

    reading config file msec

    reading config info for /var/log/security.log

    reading config file ppp

    reading config info for /var/log/ppp/connect-errors

    reading config file preload

    reading config info for /var/log/preload.log

    reading config file rpm

    reading config info for /var/log/rpmpkgs

    reading config file sudo

    reading config info for /var/log/sudo.log

    reading config file syslog

    reading config info for /var/log/auth.log /var/log/messages /var/log/syslog /var/log/user.log /var/log/explanations /var/log/boot.log /var/log/mail/*.log /var/log/cron/*.log /var/log/kernel/*.log /var/log/daemons/*.log

    reading config file xdm

    reading config info for /var/log/xdm-error.log

    reading config info for /var/log/wtmp

    reading config info for /var/log/btmp

     

    Handling 10 logs

     

    rotating pattern: /var/log/kdm.log weekly (4 rotations)

    empty log files are not rotated, old logs are removed

    considering log /var/log/kdm.log

    log does not need rotating

     

    rotating pattern: /var/log/security.log monthly (4 rotations)

    empty log files are rotated, old logs are removed

    considering log /var/log/security.log

    log does not need rotating

     

    rotating pattern: /var/log/ppp/connect-errors after 1 days (5 rotations)

    empty log files are not rotated, old logs are removed

    considering log /var/log/ppp/connect-errors

    log does not need rotating

    not running postrotate script, since no logs were rotated

     

    rotating pattern: /var/log/preload.log 65536 bytes (4 rotations)

    empty log files are not rotated, old logs are removed

    considering log /var/log/preload.log

    log does not need rotating

    not running postrotate script, since no logs were rotated

     

    rotating pattern: /var/log/rpmpkgs weekly (4 rotations)

    empty log files are not rotated, old logs are removed

    considering log /var/log/rpmpkgs

    log does not need rotating

    not running postrotate script, since no logs were rotated

     

    rotating pattern: /var/log/sudo.log monthly (4 rotations)

    empty log files are rotated, old logs are removed

    considering log /var/log/sudo.log

    log does not need rotating

    not running postrotate script, since no logs were rotated

     

    rotating pattern: /var/log/auth.log /var/log/messages /var/log/syslog /var/log/user.log /var/log/explanations /var/log/boot.log /var/log/mail/*.log /var/log/cron/*.log /var/log/kernel/*.log /var/log/daemons/*.log weekly (4 rotations)

    empty log files are rotated, old logs are removed

    considering log /var/log/auth.log

    log does not need rotating

    considering log /var/log/messages

    log does not need rotating

    considering log /var/log/syslog

    log does not need rotating

    considering log /var/log/user.log

    log does not need rotating

    considering log /var/log/explanations

    log does not need rotating

    considering log /var/log/boot.log

    log does not need rotating

    considering log /var/log/mail/errors.log

    log does not need rotating

    considering log /var/log/mail/info.log

    log does not need rotating

    considering log /var/log/mail/warnings.log

    log does not need rotating

    considering log /var/log/cron/errors.log

    log does not need rotating

    considering log /var/log/cron/info.log

    log does not need rotating

    considering log /var/log/cron/warnings.log

    log does not need rotating

    considering log /var/log/kernel/errors.log

    log does not need rotating

    considering log /var/log/kernel/info.log

    log does not need rotating

    considering log /var/log/kernel/warnings.log

    log does not need rotating

    considering log /var/log/daemons/errors.log

    log does not need rotating

    considering log /var/log/daemons/info.log

    log does not need rotating

    considering log /var/log/daemons/warnings.log

    log does not need rotating

    not running postrotate script, since no logs were rotated

     

    rotating pattern: /var/log/xdm-error.log weekly (4 rotations)

    empty log files are not rotated, old logs are removed

    considering log /var/log/xdm-error.log

    log /var/log/xdm-error.log does not exist -- skipping

    not running postrotate script, since no logs were rotated

     

    rotating pattern: /var/log/wtmp monthly (1 rotations)

    empty log files are rotated, old logs are removed

    considering log /var/log/wtmp

    log does not need rotating

    not running postrotate script, since no logs were rotated

     

    rotating pattern: /var/log/btmp monthly (1 rotations)

    empty log files are rotated, old logs are removed

    considering log /var/log/btmp

    log does not need rotating

    not running postrotate script, since no logs were rotated

  7. Nothing in /etc/logrotate.conf and I did a scan of all the files under /etc/logrotate.d/ and everything is spelled correctly as "notifempty". I can find no occurrance of "notifyempty" but I keep getting this email every day. Puzzled.....

  8. I'm getting the following email:

     

    /etc/cron.daily/logrotate:

    error: sa-update:3 unknown option 'notifyempty' -- ignoring line

     

    By the way, I don't have a file named "sa-update"

     

    I understand the problem is a typo, namely 'notifyempty' should be 'notifempty' but I don't know where to make the change. I don't really want to have to scan every file in the system looking for the 'nofityempty' string.

  9. Still have issues with VirtualBox non-OSE latest and greatest on 2009.1(host) and WinXP client with kde 4.2.2. I also had this problem on 2009.0 with the previous versions of VirtualBox.

     

    Namely, for me to be able to access any usb device, the device needs to be plugged into the usb port when I first bring up Mandriva. Then when I bring up VirtualBox and WinXP I can see the devices listed and active. If I don't have the device plugged in at system startup, the entry is grayed out when I bring up VirtualBox/WinXP and is not available.

  10. Ok folks, what is the preferred way of assigning functionality to mouse buttons. I have a Logitech MX Revolution and have in the past used btnx which I had to compile. However, because of kernel changes it no longer works with some distributions and even if it does still work, it probably won't in the near future.

     

    So, I need some other way of assigning stuff to mouse buttons. Is there a "standard" or "preferred" way?

     

    Forgot to say: I'm on 2009.1 with KDE 4.2.2

  11. Ok, I'm up and running kinda. I only able to use one monitor of the two and am using the nvidia driver from Mandriva. I can't execute the nvidia-settings program because it doesn't exist on my system any more, and it seems I can't download it from Nvidia because it installs along with the driver. So, I will have to modify the xorg.conf by hand I guess. The other option is this nice PCLOS disk that my buddy just gave me. I'll look around a bit more about how to get this second monitor working, but I'm starting to get claustrophobic without it.

  12. Hi, I had a similar thing upon a kernel update. When I got the screen with the cursor in the upper left I used ctrl + alt + F1 and then logged into that terminal and used XFdrake in there I could then select the required driver.

    Hmmm. You could "select" a driver? They have drivers listed? I'll have to take a look at that. The problem may just be that xorg.com has an "nv" instead of an "nvidia" in it. I just don't know. I had gone into control center under the video section and it said that there was a more capable proprietary driver available and asked if I would like to use it. I said yes, so it did the install and then told me that I needed to log off and then back on for it to take effect. It didn't indicate that I needed to do anything else. Well I logged off and was then hosed and couldn't get back in.

  13. Ah, drakboot, ok. Thanks. That is what I was looking for. For editing I would usually use mc to get to the file and then use the embedded editor within mc.

     

    What other command line "drak" items are available? This would be useful to know. I didn't even know that drakboot existed.

     

    I tried 3.5.10 with 2009.0, but that was after having tried kde4 and there ended up being a mishmash of both on the system such that neither of them worked right.

     

    I was reading some posts on other forums that indicated that the nvidia driver from Mandriva was the reason my cam (Logitech QuickCam Pro 9000 with gqcam) was not working right. These other people had replaced that driver with the one from the nvidia site and it fixed their problem. That was how I got into this mess to begin with. I downloaded and installed the driver, logged off and was hosed.

×
×
  • Create New...