ShALLaX.com Forums

If anyone can post a compressed file of all the conf files that shouldn't be replaced, that would be awesome. If I'm correct, so long as you haven't made any customizations, these files should work for anyone.

I'm not working with a default installation, so my files won't work.

Actually, in this case, magic wouldn't work. It produces the following error:

Error in open(/dev/i2c/0): No such file or directory

Well, I know that when I did this, I couldn't actually boot into the system (SSH can't load up), so that I had to use Stardust to boot into the system. Once I'm in, I could mount the partition (which I am assuming that anyone can get to this point), but I tried magic out, and that didn't work. I'd l...

Is there any way to just replace these conf files with a standard set of files? Can we make these files available for anyone who has accidentally replaced the conf files to recover from such an error? I myself have run into this problem in the past, and it's very frustrating to have had to go throug...

I know the df command, but that will only give you the whole device disk space usage. I was trying to find out if there was a way to recurively find out the space used by a directory (and all the files and folders under it). This would help me find out where the most usage is. Thanks for the help.

Ok, I'm a little frustrated right now cause it looks like my / partition has run out of space. I'm using all 3Gb of disk space, and I'm not even sure how. I know that the general gentoox installation uses about 1.7, but I don't know where the rest has come from, and what I can do to clear up the spa...

Actually, my problem is with the software that uses these filenames. The filenames include underscores, periods, and parenthesis in the filenames, and it appears as though the OS can not write the filename to disk on a FATX system, but works perfectly fine in the reiserfs partition.

Well, I think the biggest problem is the compatability of the FATX and the Linux Kernel which doesn't allow long filenames. At least, this was my biggest problem. I'm still trying to find out if it's a general limitation of Fatx or if it's the kernel. I guess a quick way to find out is to FTP a file...

I just wanted to add that it would probably be wise to perform a magic update of the kernel and emerge any updates prior to mounting the G drive. In other words, right after you move the filesystem to whatever drive you want to keep it on, update everything, and THEN mount the G drive. I'm not sure ...

First, I'd like to thank Terra for all her help, as she gave me a starting point to figuring this all out. More information on running Gentoox from drive G: can be found on the following thread: http://forums.shallax.com/viewtopic.php?t=406 I noticed that there were a few questions in this forum, an...

Has anyone experienced such a problem with their hard drive?

Also, when trying to install Gentoox to the F drive right off the bat, it gives me an odd error: Preparing Xbox: * Formatting filesystems... [ ok ] * Mounting filesystems... [ ok ] * Testing filesystems...-sh: cannot create /mnt/f/test: Read-only file system An error occurred, halting [Error writing...

I broke down and decided to reformat the whole unit. What I don't get is when I boot off the Gentoox install CD, I get a funny message. It says that LBA48 is supported, however a few lines lower after it shows my hard drive information, it says that LBA28 Support Only or something in those lines. I ...

To tell you the truth, I changed the bios information, then I formatted the system using Slayer's latest release. This allowed me to view/use drive G. I then installed Gentoox, and I'm at the point where I'm at right now. I'd hate to reformat the box again if I'm going to run into the same problems....

Are these instructions for when you want to use the G partition within Gentoox, or just to resolve any issues with the F partition when using a hard drive >137gb? I have a 160Gb hard drive, and I am getting odd behavior when trying to save data to the F drive. I have my bios set to use 137GB partiti...