Jump to content

pindakoe

Members
  • Posts

    186
  • Joined

  • Last visited

Everything posted by pindakoe

  1. via-82xx is for the sound card (module snd-via82xx). I have this (on an ASUS A7V8X-X motherboard with VIA chipset) and have no issues. Your output however suggests that the problem lies later, with the startup of HAL (or the next one after that). Suggest you browse /var/log/messages to see what the last entries are and also follow ianw1974' sugegstion for an interactive boot.
  2. I have seen the mounting porblem when upgrading from XFce 4.3.99.2 (RC2) to 4.4.0 official from Mandriva -- apparently the packages for thunar were not compiled with HAL support. Obviously this does not apply if you are not using thunar & Xfce (as it seems). For the rest I think I cannot add to the otehr advcie & comments.
  3. pindakoe

    URL Block

    If you want true blocking than dansguardian is your man -- not only uses lists of blocked urls & domains (which you can get from a couple of sources), but can also block on content. Using squid as caching proxy will use your internet connection somewhat more conomoical (but do not expect miracles from it; I save ~10% of bytes by using a 256 Mb proxy).
  4. Thanks arctic that solved it (I think -- I was thinking in same direction and deleted half a dozen other files in .gnome2 and .gconfg that seemed to be gedit config files. Anyway all is well.
  5. Thanks scarecrow. This occurs with gedit 2.16.0-1mdv. I have just verified that the problem is user specific (should have done that before posting). It turns out that all users except me can normally work with Gedit. Obviously I am the only user who want to use it.... This proves that it is (likely) not related to the program 9or librariers, but to some setting which is wrong for me. Sugegstions where to look are very welcome
  6. Since some time Gedit refuses to start, either when opening a text file, or the prorgram as such. I get the following error when starting it from from the commandline: >> gedit Gtk-ERROR **: file ../../gtk/gtkrecentmanager.c: line 2248 (get_uri_shortname_for_display): assertion failed: (name != NULL) aborting... >> I have no clue what this is trying to tell me. All other programs seem to run well (epiphany, abiword, gnumeric, gaim to just mention those in the gnome/gtk camp).
  7. I just noved from xfce 4.3.99.2 (RC2) to 4.4.0 final. I did this not by upgrading but by removing xfce completely and then re-installing 4.4.0 with urpmi. I then found that I didn't get back into Xfce on logging in. When checking the sessions I had in GDM I found 3 (beyond the normal previous and default) all called 'foo'. It was possible to starts xfce from level 3 by means of startxfce4. I (somehow) resolved this problem (cannot recall how), but would like to understand better how this works. Question: what defines the sessions I get to see in GDM (or KDM for that matter) when clicking the sessions button? Are these the files in /etc/X11/dm/Sessions or in /etc/X11/wmsessions.d? Is there any relation between the files in both directories?
  8. Racoon seems to be part of the ipsectools, which you may (or may not) use. I am a great believer of not having anytmore sofwtare installed than I understand to use, so I always try to remove what I do not need (or do not understand). I rely on rpmdrake to inform me if something is needed to support other software; so I would use rpmdrake to look up which package racoon is in and remove that -- I do not have such a file on my functioning 2007.0 PC. kdeinit -- I cannot say, not using KDE, but I expect this will be started when KDE starts to support KDE. Others with KDE experience are better placed to comment. These two lines: ! root 3778 tty7 /etc/X11/X -br -deferglyphs 16 :0 vt7 -auth /var/run/xauth/A:0-r4xUYZ ! root 15974 tty8 /etc/X11/X -br -deferglyphs 16 :1 vt8 -auth /var/run/xauth/A:1-coefgF indicate that X-servers (!) are running on tty7 and tty8. By default your Xserver will be running on tty7; a second instance can be started on the next higher TTY, but I cannot see how you could accomplish this without knowing why. I do not understand the error message other than that Linux' accounting is not 100% which may indicate an intrusion. Commands like w and who show who is currently logged in; commands like last and lastlog (both opnly as root) show the whole history of logons and restarts. You can go to TTY8 with Ctrl-Alt-F8 and see what is there as well.
  9. Not using qmail myself (I use postfix) I cannot give specifics beyond "have you looked in the logs?" For postfix these end up in /var/log/mail; I would check (as root) what files exist in /var/log and lower directories with a (q)mail like name and read these. My experience is that postfix at least took some time to setup correctly (largely due to trying to implement too much functionality at the start). Also, I would verify that your mail system is workin at all, by sendin yourself an email locally, i.e. logged in as 'Urza9814' type: mail -s "Test email" Urza9814 Any number of loines you care for End with a Ctrl-D and see whether that arrives at all. You should get a message while at the command prompt, the next time you enter a command (provided this is not instantenously after sending the email). If not, back to the logs to see where it went wrong. I have seen references to testing your mailserver by to run, by telnetting to it (telnet localhost:25), but I cannot recall the specifics.
  10. Try 'pgrep'. With this you look up details of processes meeting certain criteria, say: pgrep -lf -u rama would list all processes started by user rama, including command line and other details how thee were started. See man pgrep for details. Both gnome (gnome-system-monitor) and KDE (don't know) have graphical version of this.
  11. You could also start (whilst being logged in as normal user) start a terminal (Gnome-terminal, Terminal, rxvt, etc -- no shortage of alternatives), then become root for that terminal via "su" and then use tail /var/log/messages to see the last 10 lines (or tail -20 for 20 etc). Another good trick is tail -f /var/log/messages which will 'follow' (hence the -f) the log-file -- will update the output if the file grows. Just some ideas. If you want to be fancy there is also multi-tail (which allows clever filtering, multiple windows in a terminal etc) or you could use logdrake, also known as the 'View and Search' program from the control center (it is uner system).
  12. First port of call would be Easy-Urpmi to setup on-line repositories for software. Then start up the Mandriva Control Center from menu (or commandline via the command drakconf), select software management and add programs. Then search or browse.
  13. Did you try logging in on the console (Control-Alt-F2 or 3,4,5,6) as root with the root password you defined during install? If this works you can then add users with the 'useradd' command, say: useradd hbsnam passwd hbsnam followed by the password of your choice for the hbsnam account. This will create a home directory for hbsnam following the default template for user setups. If you do not recall the root password, then you could try booting in failsafe mode (though that may prompt you for a root password). If that fails, boot again from the install CD and read the boot options -- I think there is an option to set a new rootpassword. Then do as above.
  14. Anotehr place: Daemons / services are usually started from /etc/init.d/ via the System V init system. You can define for which run levels this should be done, so level 3 and 5 in your case. Yet another place: .bash_profile (per user) or /etc/profile (all users) after their logon has been completed.
  15. You may want to add --all to also purge otehr objects than files, directories & symlinks (sockets etc). Secondly I have found that some programs access files (I suspect updatedb), meaning that files never get deleted as their access times (by which tmpwatch works) are continuously updated. I usethe --ctime option. See man tmpwatch for details.
  16. I am not so sure that transfer by ftp preserves file attributes. It also depends on the file-system that the NAS uses. If this is FAT32 then permissions cannot be stored as FAT32 only knows hidden, system, readonly and archive attributes. with NTFS there is more room, but I am not so sure that the NAS software will map the linux attributes (user & group-ID, permission) correctly. I would just copy some files to the NAS and then back and see how that goes.
  17. One book which I have used that explains concepts rather than clik here/select that is 'Linux System Administration' from Marcel Gagne. He has his own website which gives some background. Drawback of the book is that it was written in 2002 (kernel 2.4, gnome at 1.x level), but the basic concepts were still the same. I still use it for checking some stuff. I have also looked at his later book 'Moving to Linux' which has same refreshing style, but is more of the click here/how to use that program.
  18. Verify that the NAS only does Samba (or CIFS). Some do rsync or NFS, both of which are somewhat more linux oriented [i think -- am researching the same, but haven't got anuthing going at present other than a repurposed old PC running FreeNAS. Some other references if you are using rsync are rsnapshot and Dirvish. I use rsnapshot to backup to a local HD (not good enough for disaaster recover I know), and find it quite usefull.
  19. I have been going through your logs (and mine) as well as browsed through /etc/rc.sysinit (which contains the code to set the hostname). I had hoped to find a clue in the logs what happened after the setting of hostname that causes your system to hang. The call to set hostname is in line 471 of this file, but this file is 1424 lines long, so lots of other things happen (that possibly cause your system to freeze). The sections immediately following hostname are ACPI, USB/Firewire and a whole block to mount the various file systems. If you are comfortable editing shell scripts, then you may want to place calls to "logger" after every thing -- this allows you to write a debug message into the log (messages). (urpmi logger if not installed). This process allows you to pintpoint the area a bit more accurate and doesn't hurt you if the boot is normal.
  20. The graphical desktop (KDE< Gnome etc) is runlevel 5. The other runlevels that are common are 3 (no X) and 1 (single user, used for maintenance). A very short overview is here; This one is more verbose (for Red hat/fedora, so not 100% correct but pretty applicable to Mandriva).. Basically run-levels are different 'states' of the system in which different sets of services (programs /daemons) are run: for maintenance you would only have the bare minimum, for level 3 you need all, except the X-windows environment, etc. I would read the following man pages for info on manipulating: service, chkconfig, init, inittab. Examples of such services can be email (split over getting email, an email transfer agent such as postfix), samba, ftp, cron, at etc. A vanilla mandriva install has just over 30 of these services (quite a few of which only do something once during booting).
  21. I suggest to browse in the logs (/var/log/messages for starters) to see whether these provide any clues where exactly this fails. The (new) parallel starting of services in 2007 makes it less than obvious what follows what. There is lots of detail in 'messages'...
  22. If you have sound in other apps, I have the following questions: Does this apply to all trailers or only specific trailers? Have you installer mplayer from mandriva or from plf? The plf version has been patched to include on library (libfaad if I recall the naam correctly) which decodes sound for some encoding. Quicktime is a container format that can contain sound & images encoded in all kind of different ways. I run with mplayer from plf & mplayerplugin and can view most. The only thing which fails often are HD-trailers -- typically the player crashes when I start playing. I can however usually retrieve the downloaded file from my ~/tmp directory where it will be sitting with a name starting with mplay followed by some random characters.
  23. The following entry disables core dumps for all users. The PAM-security framework enforces this: * hard core 0 You could also replace * by a specific user or a group. I have been running with this for a at least a year without ill effect -- main reason is taht I wouldn't know what to do with a core dump (know the principles; but the last time I worked with debuggers was on a VAX under VMS when the company was still called DEC). I do agree to the statement that just deleting core-dumps (or not allowing them) is sort of a band-aid approach -- the underlying problems/causes are not addressed.
  24. pindakoe

    xfce and glib ..

    Are you compiling from source (possibly via the Os-cillation installer)? All (as far as I know) components of Xfce 4.3.90 (beta 2) are in the contrib repository so can be easily installed via urpmi. You can either (all as root): fire up rpmdrake and look for packages containing xfc, xfw and possibly xff in their name -- allows you to select manually urpmi xfce -- pulls in the rest of xfce as a dependancy; I don't use this so haven't checked what exactly it pulss in (and what not) Alternatively you can install Xfce 4.3.99.2 (Release Candidate 2) from "eslrahc" source (http://www.eslrahc.com/2007.0). This does not conflict with a standard Mandriva 2007.0 install (as far as I have been able to make out; now using it for a week). The main improvements I found are the newer version of Thunar (with trashcan / undelete) and a functioning DateTime panel applet (the package coming with mdv2007.0 is broken -- requires a wrong dependancy). There are obviously more differences, but you'll have to consult the ChangeLog.
×
×
  • Create New...