jboy

Here are two links on how to create the grub bootloader floppy: http://www.mepislovers-wiki.org/index.php?...oot_floppy_disk http://www.linuxjournal.com/article/4622 If you had the boot floppy to begin with, all you'd have to do to boot would be to edit the /boot/grub/menu.lst file on the floppy to reference the sda5 partition rather than sda6. I would think your scheme would work. If it doesn't, you could always use a LiveCD to boot, mount /dev/sda5 as /mnt/sda5, use chroot to make /mnt/sda5 your new /, then cd to /boot/grub, and edit the menu.lst file, and then create the boot floppy using the procedures above. For reference, here's a section from my menu.lst: title MEPIS at sdb8, kernel 2.6.10 kernel (hd1,7)/boot/vmlinuz-2.6.10 root=/dev/sdb8 nomce quiet splash=verbose vga=791 initrd (hd1,7)/boot/initrd.splash Note that for sda5, the (hd1,7) references above would become (hd0,4). EDIT: Oh yeah, I forgot about /etc/fstab. That would need to be updated as well.

Hi Devries. Really nice, useful post. Thanks! What terrific community spirit you have! Just thought I'd mention the very different image viewing behavior I get depending on whether I'm viewing as a guest or logged in. I don't understand why the difference. As a guest, I get an image link, as such: (IMG:http://picserver.org/view_image.php/P87HRG0QVYVX/128/p.png) If I click it, I get the small image that I see embedded in the message if I am logged in. But there doesn't appear to be a way to get the full image, if I'm a guest (at least I haven't found one). If I'm logged in, I see the small image embedded in the message. If I click it, the full-sized image pops up. But I don't get the full-sized image if I'm a guest.

Sorry, I should have mentioned something about that. Assuming you're the only person who uses the machine that you want to do administrative tasks, you could ignore that administrative user thing and simply become the root user whenever you need to administer anything for the printer. It would typically apply for the situation where you have multiple users set up who log onto the machine locally or over a network and you only want certain ones to administer the printer. What they are saying is that users in group bin would have administrative rights. By default, when a user is setup they are not in group bin. Of course, the root user could do any administrative task as well. To change what groups users are in can be done through MCC -> System -> Add, remove or change users. But unless you have the multiple user scenario, I'd suggest you just become root when you need to.

Note that on the same page where you would download that .rpm.gz, there is a separate link to download the UNIX Driver Guide (it's a nice user guide, ug.pdf). Complete instructions are in there. Use the instructions for a RedHat install (the Mandriva packaging system, which is based on rpm, derives from RedHat). Note that you first have to use the gunzip utility to uncompress the gzipped file. Then you can install it as a regular rpm, using the instructions given in the User Guide. Basically, your commands are: gunzip <a_filename>.rpm.gz rpm -ivh <a_filename>.rpm (do this as the root user) But read the manual for the full procedure, as well as other valuable information about using the printer.

Unless your ISP has assigned you an IP (unlikely), that needs to be left blank and definitely not the internal address of your nic. Having that 192.168.1.100 in there is enough by itself to keep you from connecting. When you dial-in, typically your IP is assigned at that time from a pool and automatically detected by the system. Usually the DNS would be auto assigned too, although you should check with your ISP to see if you need to specify the DNS addresses in your dialup configuration (but that wouldn't keep you from connecting, you just wouldn't get any name resolution). If you're using the shorewall firewall, is shorewall configured for interface ppp0? You can do this from MCC -> Security -> firewall or by directly editing /etc/shorewall/interfaces. It's possible it could be the authentication method. Have you verified that your ISP is expecting either PAP or CHAP? When you try to connect, as root in a terminal, issue the command: tail -f /var/log/messages That will show some messages about what is happening and may provide some clues. Post that here if you're getting clear error messages.

Dr Bill, I am struck by how clear and well-stated your post is. And I am hoping that someone here will have a satisfying answer for you. But as just a regular user, probably a lot like yourself, my comment is that I would love to see you post this message at an official, company-sponsored forum such as the Mandriva Club Forum at http://forum.mandrivaclub.com/viewforum.ph...16f8ab178cda312 By suggesting this, I certainly do not intend to put you off. I sympathize with you. But you must realize that this forum is a group of volunteers who out of linux spirit are donating their time to network with other linux enthusiasts and help one another out as best they can. This board has no official affiliation with Mandriva. When you say "your distro" and "if I buy one" you have to realize that you are not talking to offical Mandriva people here. These are all volunteers. Many of them are developers, I'm sure. Some of them may even be developers for Mandriva, I don't know, but they do not speak for Mandriva. They speak for themselves as volunteers. That is why I suggest that you take up your issue with Mandriva directly through their official Club forum. That said, I am optimistic that many of the highly experienced linux people here will try to help you as best they can, but please, you have to realize they are doing this out of linux community spirit and not as a paid employee for which you should expect commercial satisfaction.

Hello Arctic! Damn you're fast!!! That's twice now when I finished replying I saw that you answered the question first. Anyway, I'm glad to say hello to you as you are clearly one of the support rocks around here! <among many others> I see that you also post at the Ubuntu forum and perhaps some others as well. Anyway, I always value your posts, so thanks for all your contributions.

The 3CD/DVD set is freely available at many public mirrors; see http://www1.mandrivalinux.com/en/ftp.php3 Oh, also be sure to check out the community wiki: http://mandriva.vmlinuz.ca/bin/view/Main/WebHome and http://www.mandrake.tips.4.free.fr/

No. Go for LE2005.

Welcome! 1. Yes, your existing grub menu can be reused. See this: https://mandrivausers.org/index.php?showtop...ndpost&p=197557 Note the first 4 posts in that thread for various options (e.g., while trying out Mandriva you could also boot it with a bootloader floppy before commiting to adding it to your grub menu). 2. Of the 3 distros you've mentioned, I've installed Mandriva and Mepis. Mepis is very nice, but IMO I'd give the edge to LE2005 for being easier to learn/administer. The available tools like the Mandrake Configuration Center (MCC) are great. Prior to installing, familiarize yourself with the install process by reviewing these slides: http://shots.osdir.com/slideshows/slidesho...ion+screenshots 3. You've found the best support side for Mandriva right here! The folks around here are very helpful and knowledgeable. Really good documentation too. Be sure you install the following doc packages: mandrake-doc-Starter-en-10.2-2mdk mandrake-doc-Drakxtools-Guide-en-10.2-2mdk If you have any problems, post here and somebody will help you out. Good luck with it.

Rich, you do have other options. Rather than try an upgrade-in-place from 10.1 to LE2005, you could try a new install of LE2005 by either of a couple methods: 1. You could download the LE2005 .iso images from a public mirror, burn the CDs, and then use them to install. 2. You could do a network install directly from an LE2005 mirror. See the following: https://mandrivausers.org/index.php?showtop...ndpost&p=192165 Before actually doing the install, you could familiarize yourself with the installation procedures by reviewing this site, which shows you screen shots of the complete installation process: http://shots.osdir.com/slideshows/slidesho...ion+screenshots

Did you use CUPS? If so, this is a total guess as to whether it applies in your situation, but I remember I had something similar when I set up my HP laserjet printer drivers using CUPS. There was a choice of several drivers, e.g., GhostScript/hpijs, Ghostscript +hpijs, GhostScript + gimp-print-ijs, etc. There were 5 different choices. The initial one I chose (which was the recommended one) gave me behavior similar to your situation. I chose another one and then it worked fine. Just a thought, maybe it applies to your situation. EDIT: In a clearer state of mind after I posted the above, I realized that the driver issue I referred to happened on an Epson Stylus CX6600 printer, not an HP laserjet. Exact same details though - one driver gave incomplete or even no text output and a different driver worked perfectly. So the suggestion stands - does one of the other available drivers work ok?

There is no absolutely no lack of functionality in LE2005. It is an excellent, full capability distro. The Limited Edition just means something to the effect that it's an interim release before the next major release coming later this year (or early next year?). Lots of posts about all this on this board. Whether to upgrade or not? You'll get all sorts of opinions on that. My advice is to first learn and enjoy the 10.1 release you have already invested the time and energy into. It is an excellent distribution. Get your feet wet with it. Explore all it's many capabilities. Have fun with it!

The situation is that all of these failed dependencies are LE2005 (10.2) packages. Urpmi and rpm are working perfectly on your machine - they will not find these LE2005 packages in your 10.1 repositories. That's why urpmi is saying everything is installed and up-to-date. Everything IS update-to-date based on the 10.1 repositories. Pbone.net may call this a generic 10.X package, but it looks like it's really an LE2005 package. I bet if you downloaded the rpm from an LE2005 mirror and compared the md5sum with that from the rpm you downloaded from pbone.net, you would find they are identical. As polemicz stated, if you absolutely have to have this gnumeric package, your best bet is to upgrade to LE2005 or do a fresh install of it on another partition if you have the hard drive space to support it. To test if you really need it or not, you could always boot with some LiveCD that has the upgraded version so at least you can see it in action before deciding whether you really need to upgrade or not. Please do not be tempted to download the 10.2 dependencies and try to install them on your 10.1 version. You will almost assuredly wreck your system.

Take a look at /usr/share/pci.ids and compare that against the output of lspci -v and lspci -vn. For example, lspci -v shows that I have an ATI Radeon 7500 video card: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon7500] (prog-if 00 [VGA]) lspci -vn gives me the codes for lookup in /usr/share/pci.ids: 01:00.0 Class 0300: 1002:5157 Subsystem: 1002:103a Flags: bus master, stepping, 66Mhz, medium devsel, latency 32, IRQ 16 Memory at c0000000 (32-bit, prefetchable) I/O ports at a800 Memory at cfef0000 (32-bit, non-prefetchable) Expansion ROM at cfec0000 [disabled] Capabilities: <available only to root> Finding 1002 in the first column of /usr/share/pci.ids gives the start of an ATI Technologies Inc. section. Now searching for 5157 within the 1002 section, I find my video card: 1002 ATI Technologies Inc ... 5157 Radeon RV200 QW [Radeon 7500] You might also want to read up on the hotplug process. For example, lspci -v shows that I have various USB Controllers (USB 1.1, 2.0, etc) by a certain vendor. But when I plug in a USB flash drive, the hotplug process gets involved. See: http://linux-hotplug.sourceforge.net/ Also, see the scripts in /etc/hotplug.

Greetings, AussieJohn. I'm pleased to personally say hello and thanks as I've benefitted from many of your posts and have logged them into my tips file. That's what I love about MUB - practically every day I pick up several tip gems. I've found that oftentimes the floppy bootloader option is not addressed in some distro's install/setup documentation, so I thought I'd mention that SuSE had it. I remember I got caught unprepared once (I loved Ixthusdan's quip that "preparation is the key") in installing SimplyMepis 3.3.1 assuming I would have that option, only to find out mid-way through the install they didn't include the option for it.

Here's a third boot option, besides the good suggestions from Ixthusdan and AussieJohn. In SuSE (at least version 9.3), during the install setup you can choose to create a bootloader floppy (just select the /dev/fd0 option rather than MBR or root partition). Advantage: This is the simplest, easiest way to make sure you can boot into SuSE without having to mess with the lilo/grub configuration for your existing Mandriva install just yet. Maybe you're experimenting and not sure you really want to keep SuSE, or don't want at this time to mess with the lilo or grub details of being able to boot both distros. Get your SuSE up and going and later on you could always go back and apply the lilo or grub details to be able to boot both distros from the same lilo or grub menu as your Mandriva install. I think it's always a good option to have a bootloader floppy available anyway, and what better time to create it than when you're doing the install and have enough to mess with without doing the boot integration just yet.

You were close. It's the /etc/sysconfig/network file. Example entries: HOSTNAME=MY.HOSTNAME NETWORKING=yes GATEWAY=192.168.1.1

I know, it's a whole new world and it takes a little time to get going efficiently. Here's a few tips and others will chime in. I'm going to try to answer some of your questions directly, but I mostly want to give you some resource tips that may be helpful to you as you continue to explore linux. If you're using the KDE Desktop Manager: there's a very good KDE tutiorial: Menu -> More Applications -> Documentation -> KDE Help Center -> Tutorials -> QuickStart Guide. Also, get familiar with Konqueror -> click on the icon that looks like a home on the application launcher panel. The F9 key in Konqueror toggles the Navigation Panel (left side of window). Various icons at the left edge provide many functions. This could be considered like My Computer in Windows, but it has many more features. There's very complete Mandrakelinux Start Guide documentation in html and pdf format. If it doesn't show on the Documentation menu, download the mandrake-doc-Starter package. You've already found this board, which is a terrifc resources. Get familiar with it, espeically searching cause others will have asked and had answered most of the questions you have. The home directory for your userid is probably the closest to My Documents. Create subdirs as needed and use Konqueror as a file manager. In firefox, Edit -> Preferences to select the fonts you want, as well as other configurable options. Lots of helpful firefox messages here in these forums. Lots of configuration options in Menu -> System -> Configuration -> Configure your Desktop. Windows to Linux Beginner's Guide: http://www.reallylinux.com/docs/windowstolinux.shtml Check out the Mandriva community wiki: http://mandriva.vmlinuz.ca/bin/view/Main/WebHome Mandrake Tips: http://www.mandrake.tips.4.free.fr/ Easy Urpmi: http://www.mandrivausers.org/easyurpmi/index.php Linux Documentation Project: http://www.tldp.org/

First: In your fstab entry, vfats is not a valid file system type - it's vfat. Second: Note that there is a recent update for the haldaemon. Apply it if you haven't already done so. For info about the update, see: http://www.mandriva.com/security/advisorie...e=MDKA-2005:036 For now, I would take out that fstab entry and see if it's auto-mounted by the system after the update is in place. For example, here is the auto-generated fstab entry I get when I plug in a usb flash device: /dev/sdc /mnt/removable vfat pamconsole,exec,noauto,noatime,sync,codepage=850,iocharset=iso8859-1,managed 0 0 Also, from a terminal, enter the dmesg command after plugging in the usb drive and see what messages you get. Here's what I get: usb 5-6: new high speed USB device using ehci_hcd and address 3 Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new driver usb-storage USB Mass Storage support registered. usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning Vendor: Model: USB DISK 20X Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdc: 253952 512-byte hdwr sectors (130 MB) sdc: Write Protect is off sdc: Mode Sense: 23 00 00 00 sdc: assuming drive cache: write through SCSI device sdc: 253952 512-byte hdwr sectors (130 MB) sdc: Write Protect is off sdc: Mode Sense: 23 00 00 00 sdc: assuming drive cache: write through /dev/scsi/host2/bus0/target0/lun0: unable to read partition table Attached scsi removable disk sdc at scsi2, channel 0, id 0, lun 0 usb-storage: device scan complete If it doesn't work, post your fstab entry and dmesg output and someone should be able to help you diagnose the problem.

Yves, thanks for that tip. I want to put that in my rescue folder for future reference, so I did a quick search and found the following: GPart: http://www.stud.uni-hannover.de/user/76201/gpart/ Partition Rescue HowTo: http://www.ibiblio.org/pub/Linux/docs/HOWT...ion-Rescue.html

I had a drive behave similarly recently. It would lock up WinXP on boot-up but could be mounted in linux, though it would hang when trying to access certain directories. Mine was a partition table corruption. Though you may not be able to recover the data from those directories where it's hanging, the drive itself may not be dead. After a low-level format, an fdisk, and a re-format, the drive might be usable again. It worked for me, and the drive has been trouble-free since. YMMV. Good luck with it. Edit: I had not saved the partition table on this drive, so I couldn't try restoring it, and qtparted and fdisk were not able to fix it (even though I had an fdisk -l printout). If you've saved yours and you suspect that a bad partition table could be part or all of the problem, you might try restoring it.

Here's what may have happened to you: if you changed Kwrite's defaults by Settings -> Configure Editor -> Open/Save -> End of line -> DOS/Windows, I believe that applies to newly created files only. Existing files will retain whatever end-of-line format they were originally created with. To change the format of an existing document to what you want (regardless of the default setting), in Kwrite do a Tools -> End of Line -> Windows/DOS and then save the file. You can check that it's the format you want by opening the text file with hexedit (urpmi hexedit if it's not installed). You should see the 0D OA end-of-line combination if it's in the Windows/Dos format.

I have no Ubuntu experience, though I understand that it uses sudo instead of su, but the script is behaving like there really is a file named su <albeit non-functional> somewhere in the path. Are you sure there really isn't some non-functional su file out there (please forgive me if that's a stupid question, I just don't know enough about Ubuntu, but I know that the script works ok on some non-Ubuntu systems). If you try commands like the following in a terminal, what do you get? su which su whereis su locate su This is just a pure wild-ass guess but is there perhaps an executable su file that maybe just outputs a message saying that you must use sudo instead (or something like that?) Or may su is just a symbolic link to sudo? What I'm suggesting is, perhaps the script really is working as programmed, but there is some non-functional su file in your path somewhere that is tricking the script? At this point, that's all I can think of, because on non-Ubuntu systems that I've tried the script on - Mandrake 10.1, LE2005, Simply Mepis 3.3.1 and SuSE 9.3 - the script works and correctly identifies whether either, both, or neither of su/sudo is installed.

I don't have Ubuntu, but I did try it on Mandrake 10.1 (bash 2.0), and bash 3.0 in LE2005, Simply Mepis 3.3.1, and SuSE 9.3. It worked on all of them. But I still don't understand what the actual problem is. Are you getting error messages? Is the config.h file not getting created? Is it falsely detecting the presence of either su or sudo? One thought (assuming the config.h file is not being found where you expect it): you are creating the config.h with a >> config.h. Are you sure your current directory is the right one? Maybe you should use the full path in the redirect command, or make sure you have set the current working directory to what is needed, and that the user under which this is running has the proper write permissions. Are you sure you want to append to config.h with the >>, or do you just want to overwrite config.h with >, a single right caret?