Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by pindakoe

  1. Not quite certain but recommend to have a look at sudo and sudoers (the file that defines what authority you delegate). My understanding is that (by means of /etc/sudoers file, only to be edited by command 'visudo') this allows fine granular control on who can do what (in addition to normal user/group permissions).
  2. Is this permanent, i.e. what happens if you disconnect the external harddisk and remount it later or after a reboot. Is /media/disk still owned by username:username or does it get re-created by udev (which I think is what is hapening)? I haven't really gotten my arms around udev rules, so any starting points appreciated.
  3. New files get group/owner of the user that is running the program that creates them, unless you change this with su or sudo. I have a similar seituation where I use "su" to start a script as another user by means of following command: su - photo -c "script.sh arg1 arg2 arg3" This will start script.sh as user photo with arguments arg1..3
  4. May be start somewhere else -- why protect inittab? Figure out what is changing it, kill it and be done with it. Tackle the problem at its root rather than deal with the side effects. AFAIK inittab is only changed when you indicate whether or not to start in level 5 (X) -- XFDrake and possibly boot section of MCC.
  5. The files vmlinuz, initd.img, System.map, config and kernel.h in /boot are usually shortcuts to the most recently installed kernel versions of those files. This means that, after installing a new kernel, starting the first entry is the same as starting the last one.
  6. And even from 2008.0 to 2008.1 was surprisingly hard as I started my upgarde when the mirrors were being sync'd... Clean install (but just keep that /home directory and keep a copy of /etc, /usr/local and /usr/share/themes with any customisations you may have added).
  7. Mandriva's default /etc/passwd and /etc/group list users and groups for various system users. The reason for some is obvious from their name (squid for the suid proxy; postfix to run the postfix mail-system, etc), but I wonder about the need for the following users: adm, sync, operator, uucp, news, games. None of them own files. Anybody who can explain these users and whether they can be deleted from the system? The same applies to groups news, games. Surprisingly the group uucp owns some ttys in /dev/tty (I always thought uucp was the uold unix-to-unix-copy mail transfer system).
  8. Similar background (though I never worked with CP/M, but have worked a lot with mainframe systems when punch-cards or DECWriters were the norm). I found this book very valuable because it approached mastering Linux not from click here, click there, but from CLI with GUI-programs as optional. The book is ~5 years old: Linux system administration, Gagne (of Linux Journal fame). It probably doesn't cover everything but touches on a lot -- have look at Amazon for the TOC to see whether your areas are covered. Its mainweakness (due to age) is the dated and lack of coverage on desktops such as KDE, Gnome etc. If on the other hand, if you only want to partition and format, use a lvedCD or something else to get gparted started. I use systemrecuecd.
  9. And if you want to live dangerously, you can do the resizing and moving around also without first deleting the home directory, but this is not without risk, so do make that backup. I have never used the MandrivaCD for this and I think diskdrake can only resize and not move partitions. I prefer gparted (do a search for systemrescue LiveCD). The procedure is: Delete anything from /home that can be deleted (~/tmp, ~/.cache, browser and java caches and any files you have lying around that you do not really want to keep. Objective is to get /home to the minimum size Reboot from the liveCD Shrink /home to minimum possible size You may want to reconsider size of your swap partition. General advise used to be 2 times RAM, but I do not think that holds anymore with current amounts of RAM. I have a swap of 512MB with same amt of RAM and no complaints (even though I run some servers and climateprediction). Resize to what makes sense. Move partitions for /home and swap to end of extended partition Shrink extended partition which contains /hdb5 and /hdb6 by moving the start towards the startd of /hdb5 Expand the primary partition /hdb1 to fill freed up spwace Some other ways to get your system bootable: Boot from liveCD and delete all files in /tmp, /var/tmp Also review files in /var/cache & /var/spool
  10. The error An error occurred. Undefined subroutine &MDK::Common::System::uniq:: called sounds like a known 2008.1 problem, though I had not read that a part of gnome was forgotten. The install fails in the last bits, and does not update grub's configuration to the presence of new kernel's. Editing is straightforward: just include following lines in /boot/grub/menu.lst to have your other two kernels show up inthe boot menu: title Spring kernel (hd0,0)/boot/vmlinuz-desktop586 BOOT_IMAGE=linux root=/dev/hda1 resume=/dev/hda5 splash=silent vga=788 initrd (hd0,0)/boot/initrd-desktop586.img It will be started by default, if you put it first (after the line default 0). You may want to remove some older kernels once this works. At present you have 4 kernels from 2008.0 still lying around. My advice is to keep only the current and previous version and remove all others. Start rpmdrake, search for kernel to do this.
  11. This brings back memories when RAM was expensive and computers were slow. Software I used was Kermit, which acted as terminal emulator and fiole-transfer protocol (not fast, but robust). This ran perfectly on PC's which I recall had ~640 Kb RAM and maybe somewhat less. CPU's weere 286, but also 8086. Kermit is probably overkill as it provides a lot more functionality than terminal emulator, but had good DEC VT100 emulation (maybe even VT220 and I have faint memories of Tektronix emulation) which was what I needed to connect to VAXen (mainly running VMS, although I think I have connected to Linux as well). This will confine you to command line, but is easy to set up.
  12. Standard Linux access control will prevent a user from accessing something he does not have access to. I think this applies here, i.e. another user than yourself (dude67 on your linuxbox) is owning the mountpoints. Because this user is different from yourself, you are barred access by your Linux system. 'root' bypasses all access control so can access it. Can you post output of following commands: mount ls -l /home/dude67/nas (I include the mount command on the offchance that it will show who is owning the mounts). Assuming that dude67 does not own /home/dude67/nas (and the subfolders), but that another users owns these, I suggest you add dude67 to the group of this other user and ensure that /home/dude67/nas 'rwx' access for the group owning it (mode 770, like drwxrwx---). You can add dude67 to this other user's group via MCC, System, Manage Users.
  13. We are getting there -- slowly but surely. Check on your NAS what share(s) have been created. If none, create a small test one using the webinterface. Let's call this test. Having established that you can see the drive and that it uses CIFS as file-system I think this should work (al as root): Add following line to /etc/hosts in order to define a name for your nas: NAS Obviously you can change the name to whatever you like (but I guess it is best to stay an alphanumerics and avoid the rest). Create a mountpoint for the NAS. mkdir /mnt/nas chmod 777 /mnt/nas Depending on usage you may want to have more restrictive permissions. Note that the software on the NAS will also define access, so I prefer to start with NAS accessible to all on the linux box. Next step is mounting the file-system of the NAS on your linux box. You can do this as root (and even automate this at boot by adding the appropriate line to /etc/fstab) or do it as a user: mount -t cifs //nas/test /mnt/nas -o user=username-on-nas,pass=password-on-nas If this works w/o errors, then you should be able to see what is on the nas by an ls /mnt/nas command (or via file-browser).
  14. A NAS is a (small) PC, so let's boot it up after connecting it to your router and the router is configured to hand-out IP adresses via DHCP (99% chance yours is). Next step is to find out what IP address it lives on. Usually your router (try can tell you what is connected to it. One of them is the PC you connect from, the other is the NAS. Open browser, type in (or whatever the router tells you) and your router will welcome you (probably after a prompt for a password -- manual shoudl tell you what the default is). Can you get to this stage? This should not require making modifications on client PC.
  15. The WD-drive is a NAS (network attached storage) meaning it is a stripped down PC that will define how it provides storage space. This means it will offer you one or more file-systems (FAT32, NTFS, if you are lucky ext3 or something Linux-friendly) and how to make that data accessible (FTP, RSYNC, NFS or Samba). Only the WD documentation can tell you how to set up the NAS in one or more storage areas. Typically you will need the NAS to have a fixed IP adress (so that other PC's know where to find it). Linux clients can interact with FTP via an ftp client (lftp from commandlien, GFTP in Gnome and no doubt lots of other possibilities). Rsync can be interacted with via rsync or some of front-ends like dirvish and rsnapshot which are good to automatically make regularly (hourly, daily, weekly snapshots). NFS and Samba file-systems have to be mounted by the Linux client either via /etc/exports (nfs, but also install nfs client) or mount -t cifs //server/share /mnt/mywdbackup (samba).
  16. The 'lo' network device is loopback and is for linux PC's to talk to themselves (w/o leaving the machine). Its IP address is always My guess (like ianw) is that both linux machines have the default firewall settings, meaning closed to smb (ports 137-139, 445). Check the logs (/var/los/messages and /var/log/samba/). You can open the firewall for samba by hand by editing /etc/shorewall/rules. You can do the same via the control center (security, setup personal firewall, select Windows file sharing). This will create /etc/shorewall/rules.drakx. Mine looks like follows for CUPS (631), Samba & SSH (22): ACCEPT net fw udp 137,138,139,445,1024:1100,631 - ACCEPT net fw tcp 22,137,138,139,445,1024:1100,631 - My experience with a windows client (98, 98SE & XP) and Mandriva server is that samba does not give appropriate error messages it if gets blocked by a firewall, be it on the server or on the client (windows or linux client should accept responses from the server). Another problem I have had with Samba is that of the workgroup name. Whatever you have put in /etc/samba/smb.conf behind workgroup = should match with what you have as workgroup on your windows PC (I forgot where you set it, but you can check in under control panel, system, computer name). If these do not match (I do not think case matters to windows), then (my conclusion was) clkient will not see server or vice versa.
  17. This is doable, but not easy due to fact that Windows wants a primary partition to itself (which will now be occupied by your root-filesytem). I don't think Mandriva's drakdisk can do enough. I have good experiences with gparted (I use the SystemRescueCD which includes this and much more). You will be moving lots of data around, so do make that full backup. The SystemrescueCD has software for imaging which may help (though not if you are re-sizing a lot). I recommend you review your current setup and clean both / and /home partitions of any files that are not essential (/tmp, /var/tmp, ~/tmp, do I really need logs 4 month old?). This reduces the amount of data that needs moving. My approach would be: Create some space by shrinking /home or /. Create a new partition and copy your / partition to it. This way you free up your primary partition for windows Re-format the old / as NTFS for your future Windows install Install Windows Re-install Grub and make sure /boot/grub/menu.lst points to the right drives as well +-
  18. Ensure that the workgroup name listed in smb.conf matches with what the workgroup name defined in networking oif the Windows box. If not, then they are not talking...
  19. And ensure that said file is world readable (gdm is running as user gdm): file should be mode 644 (-rw-r--r--). Furthermore it should have the righ dimensions. I do not know the exact limits, but my pictures are ~45x48 PNG-files.
  20. My 2c: I only once managed to change bootsplashes. Various upgrades and reinstalls plus a lack of documentation from my side how I accomplised this have taken care of that. At this time I am 'splashless', possibly because I boot in 1024x768 rather than standard 800x600 mode (or that is at least my closest guess; vga=791 instead of vga=788). The only gripes I had with bootsplash (apart from being somewhat hard to understand) were (1) -- the MCC-wizzard sort of never worked (though it did generate files in various places) and (2) the default mandriva ones are a bit boring after a while. Neither is areal issue and I probably do not care enough about it to really figure it out. If splashy is better documented and easier to change OK.
  21. Have a look at this on how to setup DG with squid in a transparent proxy setup. Have been using it since end 2004 and works like a charm without being overly resource heavy. If you want I can provide a script to automatically update blocklists from a trusted repository that is frequently updated (4-7 times a week) and uses same structure as DG for its blocklists. Having used it so long I am aware of a few shortcomings of this approach: * This is for one machine which is used for browsing. It doesn't address how to set up that machine as gateway with proxying & filtering * The phraselists are sometimes overly restrictive if your language is something else than english (but you do visit websites in languages as dutch, danish etc). It is surprising what innocent words may mean in other languages * You may want to have different filter rules for different users. DG can do this, but will need to know which user it is filtering for. My best understanding is that this is incompatible with transparent proxying. It is possible with non-transparent setups where users log on to the proxy or where client PCs can identify themselves via and ident server (available for Linux and Windows). I prefer the simplicity of transparent proxying for now. * DG can also filter ads by using list of ads-sites and URLs and replace this by a 1x1 empty GIF. I have never been able to get this to work so tend to see the block-page I have set instead.
  22. There isn't a lot to be gained by going beyond three partitions (/, swap and /home) for most domestic uses, with something like fat32 or ntfs added for legacy reasons. Thus, I would give say 10 Gb to / (I use 3.1 Gb and have a fair bit of apps installed), 2 Gb for swap (you ver y likekly can get it away with a lot less unless you run loads of services and apps; monitor swap usage for a while during usage by typing 'free' every so often) and splitting the rest between /home and fat32.
  23. I think it is included (not having the DVD version I cant be absolutely certain), but it is just not installed onto your hard disk. Fire up the control center, goto software, search for kernel and install the source-files. Note: the kernel-devel files only contain sufficient info to build other software against the kernel, but not the complete source (only header files). In order to rebuild the kernel, you will need kernel-source of your version..
  24. Try dkms-nvidia-current (you misspelled nvidia ;-)
  25. I have had these (or somewhat similar errors) as well, but this is one upgrade and a fresh install ago so don't know how I solved it then. I checked some of my old links (as I only ever tested CDRW which may not be identical to DVD-RAM) and cam across this in the Gentoo WIki, which mentions (1) not to use cdwrtool (only for CDRW), but mkudffs instead. If that gives trying to change type of multiple extents it suggests not using mkudffs but dvd+rw-format /dev/hdc instead. I guess you have not yet tried to do this (especially after doing up the pktsetup thing). Just an idea..
  • Create New...