Pepse

IIRC, "rm -fr filename" removes the tars. At least that's what I have in my big notebook of things I should have learned since starting Linux. Yeah, I'll try a few things in Konq and verify those deletions in mc. Thanx. Later. Pepse.

Ixthusdan, if for removing you mean going to Konqueror and deleting the stuff I downloaded, that didn't work as I deleted the Sane-Plustek drivers from Konq and they still show up in mc. Pepse.

aru, recent Sane backend, Xsane, and Sane-Plustek drivers that I downloaded un-tarred and for whatever reasons just don't work. I did a version check for Sane and the reply is 1.0.08 and I downloaded and untarred 1.0.12. And for reasons I discovered after re reading the Sane-Plustek info it appears that I didn't untar the S-P drivers in the right spot. Plus, I've decided to take the Epson scanner, that I just bought, back and go down to the big city to see if I can get a Epson or Canon scanner that doesn't have the Plustek drivers. It fiigures (for me, it seems) that I get something for Linux that should be alomost plug and play and it ain't; Epson Perfection 1250/Photo. That's what I get for going to Wal-mart, I guess. Forgive me for venting my frustrations, sometimes I just gotta say things somewhere. Also, I want to remove everything pertaining to Xcdroast and cdrtools. The drivers that came with MDK 9.0 as well as the stuff I downloaded and installed 6 weeks ago, as that still ain't working right either. Later. Pepse.

I just want to check to see if it is OK to remove a bunch of files I recently downloaded and I think, screwed up. I figure if I can delete everything I can re-download everything and hopefully get it right. I would be using "mc". It seems to be similar to "regedit"; which I've been there before. Later. Pepse.

cannonfodder, that didn't work. I get the: Error: /home/pepsi/partdata.txt, bad backup file. So it doesn't look like I can do anything. So, I am wondering if I can just repair this error by using the "boot disk" I made awhile ago. Or is it possible to repair/save my "/home" by running the 3 cd's again?? Pepse.

Sorry for the delay in responding, had other issues to deal with. Now I know this is going to seem like I'm a bit unsure of my abilities but I gotta make sure I'm doing it right. If I'm saving a txt file I type the command "/home/pepse/partdata.txt" in diskdrake-more-save partition table?? Remember I am using the "boot up" screen. If I need to go to a "commandline console (I can't boot all the way into Linux) do I go thru "linuxfb" or boot CD1 or?????????????? As for "edit the file and copy/paste it here" that is one thing I've never been able to do including in whine-doze. How do I do it?? Pepse.

Well, qnr's commands didn't get me anywhere, but I am able to use diskdrake. This whole screwup is on hda6 /home, Journalised FS: ext3 . So, when I went to More - save partition table I typed /home and the reply is: Error: /home bad backup file. I also tried /usr with the same result. Just for the record, if it matters, all of this is being done using the screen for when booting up a Linux OS; in otherwords the blue boot screen with the light gray Mandrake box. Pepse.

My mistake. I do my best to interpret these commands and sometimes I miss. I'll use "o" instead of "0", and I'll post back later this morning. Pepse.

Well, I did what you wrote and actually I got nowhere, except for this reply (that is, I used your "code" mount -0 remount -0 rw -t ext3 /devices/discs/disc0/part3 / ) Details found in /etc/fstab may be omitted mount -a [-t | -0 ] ... :Mount all stuff from /etc/fstab mount device :Mount device at known place mount directory :Mount known device here mount -t type dev dir :ordinary mount command Note that one does not really mount a device, one mounts a filesystem (of the given type) found on the device. One can also mount an already visible directory tree elsewhere: mount --bind olddrir newdir or move a subtree mount --move --olddir newdir A device can be given by name, say /dev/hda1 or /dev/cdrom, or by label, using -L label or by uuid -U uuid. Other options: [-nfFrsvw] [-0 options] [-p num]. For many more details, say man 8 mount. Anyway I also used various parts of your "code" with no success. As for man 8 mount it gave me many many pages and I really didn't learn anything that I could apply because I wasn't sure how to put the stuff to my advantage. Pepse.

OK, that will have to wait until late Wed. morning (CDT). I do remember that the "information" mentioned something about "Mass Storage" for the camera. Now as for going in to the hdd what option on the boot screen do I use?? nonfb or ??? Because this error screen shows up soon after it starts checking everything. Also, I am running MDK 9.0. Pepse.

OK, let me see if I can recall what I did. I went to MCC, hardware list, and clicked on /sda1 under "disk" and it showed my HP camera on the right side of the page under "information" and at the bottom I clicked on "run config tool" which takes me to "diskdrake" and I clicked on "FAT" and "expert mode" and then it gave me some options (( I am kinda using this hdd to get an idea of what I did, so I can't go too far for fear of screwing this one up, too)) and on the other hdd the "fat' was all blue and accessible (on this one it ain't). I remember there were 4 options and on this hdd I only get 3. Whatever the 4th one was had something to do with the filesystem. And as best I can remember I made a change so the my "fat" became, IIRC, ext3; I made a few changes to see if I could access it with the camera on, so the best I can say is that I changed it to "ext3". Then I noticed when I was still in diskdrake that when I clicked on "fat" nothing would happen, as in nothing would show up in the "choose action" box. I knew then that I screwed it up but waited until Monday to reboot. I hope this helps. Later. Pepse.

OK, hopefully this info will help. First to say is most of what I typed yesterday was from what I could see on the screen after trying a few things that didn't work. So here is what shows up on the initial boot: Checking Filesystems /devhda6: clean 9680/ 2932736 files, /dev/sda1 The Superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> fsck.ext3: No such file or diectory while trying to open /dev/sda1 Failed to check filesystem. Do you want to repair the errors? (Y/N) I then typed "Y" and the response is: *** An error occured during the filesystem check. ***Dropping you to a shell; the system will reboot ***when you leave the shell. Give root password for maintenance (or type Control -D for normal startup): (Repair filesystem)#1 "So I used your mke2fs -n /dev/sda1 and the reply is: Could not stat /dev/sda1 ---No such file or directory The device apparently does not exist; did you specify it correctly? The one thing I seem to remember is that in my "madness" I changed sda1 to ext3. Pepse.

I gotta be brief 'cause it's gettin' late. The sda1 was created when I first was trying to get my digi camera to do something (about 2 months ago) and I didn't get nowhere then but I didn't try as hard as I did Sun. night. I will copy your info and try it tomorrow (Tues.); because like I said I am on the other hdd and it's late. Later. Pepse.

Well, this will probably be a long one. To start I tried to get my HP Photosmart digi camera to work on MDK 9.0 (again) and I messed up my hdd/partitions. I (1) didn't want to bother anybody with my situation so (2) I tried to get it so my /dev/sda would somehow work so that I could transfer my pix to the hdd. Well after trying and trying for about a half hour I got mad and more or less tried to rename sda to (I think) ext3 or ext2; I dunno which or what. Anyway after a bit of thinking I realized I would not want to reboot the computer; and yet I would have to because the problem has to be fixed. So when I rebooted my computer I get this error: Checking filesystems /dev/hda6: clean, 9680/ 2932736 files, fsck. ext3/devsda1. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the Superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> : No such file or directory while trying to open /dev/sda1 Failed to check filesystem. do you want to repair the errors? (y/n) Well of course I typed "Y" and it repeated the last item of: No such file or directory blah,blah, blah, etc. I even tried "e2fsck -b" as well as a few other "- some other letters" that were provided and nothing works. So, what do I do now?? . Pepse. I thank the gods for my having enough brains to have an extra hdd with MDK 9.0 on it; anyways.

OK, I remember on either this board or one of the older boards some people would have the Linux Penguin sucking on a juicebox with the saying of "We suck More!" or somehin like that and also a saying about "Window for Dummies is not just a book it a M$ way of life". Where on the net can I find these things?? I know the M$ for dummies has more to it than what I just typed and I'm looking for the whole phrase. And IIRC somebody had a link to other Linux logos and such. Where?? Later. Pepse.

Well, that's why I posted this. To get a little feedback and see what other opinions are. It does sound good; but just because it sounds good doesn't mean it would be worth it. It does sound like it would be worth it :D . Considering the FUN I had when doing the initial compiling last winter, I could use a break on something for this system. I consider "X" being the biggest nightmare of the things to compile. You ain't got "X" right yer screwed. The other things I'm dealing with are not going to put me out of a Linux box; altho I do have a small hdd with 9.0 on it in case of emergency. Thanx for the opinions :D . Later. Pepse.

Right, but have you used it?? Or know of anybody that is?? I did look thru this site via searching for nVidia articles and didn't come across anything as far back as early Feb., but that doesn't mean something that was worded diff didn't get included in the search. Gotta research this a bit before I gamble on using/trying it. Sorta like I don't see any GOOD reason to upgrade to 9.1; I'm not a gamer and I presume that is most of the reasons for the newest distro. At present I only need upgrades for my digitsal camera thru Gphoto (whenever they include my camera). And Xcdroast ('tho that is getting the best of me :x ) So, basically I've decided to just upgrade what I need. To me it is safer that way. That's why I asked about this auto-update; to see if it's easy on the system. Later. Pepse.

I see on nVidia's site that they apparently have it so that the latest nVidia drivers can be updated automatically. Is that a good idea?? I mean with so many people having probs with installing nVidia drivers is it a good idea to have nVidia do it for us?? Or am I missing something here?? Later. Pepse. :?

Personally I'd blame the browser. I've had various crashes/freezes with Mozilla based browsers. Including when I used to use whine-doze. For the most part I primarily use Mozilla, but if I want to go to the sites that I have crashes/freezes on then I go to Opera. My opinion. I never considered the video driver as the fault. I have an nVidia card. Later. Pepse.

OK, I went to RPMdrake and did a search for cdrtool (s) and the result is nothing. So, I went to Kpackage and it states, when clicking un-install cdrecord "error: removing these packages would break dependencies " for the 4 cd burning packages that are in MDK 9.0. After it shows what it would break the dependencies of I get a line of: "result-1" . And of course if I click un-install again I get the same error screen. Later. Pepse.

Uh, no, but then I am never sure when some former versions of something has to be removed. Consider that I didn't have to remove the previous version of XCDroast. As for tar.gz verses RPM's?? To me on the 2 help sites I frequent that seems to be 6 of 1 and a half-dozen of the other as far as which is better, easier, blah, blah, blah. Altho in this case in particular I went with the tar.gz for practice. Up to this point in my Linux knowledge (1+ years) I feel that I need more work with tar.gz's. RPM's and SRC.RPM's are fairly simple and straight forward. I will do what is needed and post the reply later. I gotta deal with some pre-Bunny things before it's too late. Later. Pepse.

Well for starters this is the first reply of any sort to my problem. To let you know where I am at with the problem I first installed the latest ver of cdrtools (2.0) as tar.gz. Then I installed 'Roast Alpha13 (from tar.gz) . Then when going to 'Roast in root I get an error of " Invalid cdrecord version 1.11a32 found. Expecting at least 1.11a34. So, I re-installed cdrtools 2.0 and still get the same error. Now when doing the "cdrecord --scanbus " I get "Cdrecord 1.11a32 " and other things pertainging to the scsi bus and where my CDRW is. Before checking out Gentoo I will wait for your reply. Later. Pepse.

Besides this site and Justlinux does anybody have links to other similar boards?? I am having a problem with the latest version of CDRtools (2.0) not being recognized by the latest version of XCDroast (0.98 Alpha13) and have posted on this board and Justlinux and haven't received any replies. Just trying some other places to get help. Later. Pepse.

I did that and got an error pertaining to the wrong version of cdrecord (cdrtools??). I downloaded and compiled? cdrtools-2.0. Should I redo it?? Later. Pepse.

I have to go into preferences. Dumb question but how do I get there to make the additions?? Pepse.