General :: Build Fedora Server - Wipe Clean At Initial Time - Root Directory?
Jan 25, 2010
I messed up the first installation of Fedora on my server. My setup is as follows: Fedora and Gnome - NFS system, No dual boot (Windows or anything) Fedora ISO DVD downloaded No kickstart or other tools. how to set this up, from the time I insert the disk and have it boot up (configged already to boot from it). I know how to wipe it clean at intall time. Is that the root directory? And, is /boot the actual boot directory? I'm just having a hard time uderstanding that. As I said, I just want a quick itemized list, step 1, step 2, etc, from partitioning, creating file system, mounting, etc. in the right order.
I need to wipe the slate clean on my computer and start from scratch. I have too many issues and school is just around the corner for me, I've got a huge workload and don't have time to find solutions to my problems right now. I recently upgraded to Lucid but that only escalated my woes. The simple fact is my machine is getting too old and it's time to upgrade everything, which won't happen until fall. So for now I simply want to downgrade to hardy because it will be supported until April next year and it is very stable, plus I think it is the release that my graphics card got a decent resolution on (ATI, need I say more?). I'm somewhat of a noob, but I've got my wits about me and have researched the forums for many hours to find solutions, but to no avail. I don't want to go into details about what issues I'm having, I just need to know how to remove ALL kernels off of Grub and start from scratch. Any links to comprehensive tutorials would be ideal, or if someone knows of anything else that will work,
P.S. I love Ubuntu and am a lifer. The philosophy behind it as well as the community are supreme and will someday rule the universe,
I'm attempting to install some software on my friend's computer. It keeps saying the packages I want aren't there but I know they are. I've been fooling around with this for a while. I may have broken something in the process. Repository names, perhaps?Is there some way to reinstall Synaptic/Aptitude and "wipe the slate clean?"
I have a user who just got a new laptop and when he connects to the FTP server, it verifies his username and password like it should, but when it goes to do the directory listing, it just kinda sits there. if i refresh the view, the folders show up. wonder if there's something in a log somewhere for vsftp i should be looking at. it could just be his ftp client or air card too, but i want to be thorough on the server too becuase it will help me learn.
Information on the net seems very sparse or outdated for how to go about booting to a RAM disk. I need to be be able to boot a PC without a hard drive in it. I want to be able to PXE boot a PC and supply it with a RAM disk image that also contains the contents of the root file system (obviously stripped down enough to keep the file size small and the boot up time fast).What I have gathered so far is that I need to extract the contents of the initrd.img file, add files as necessary, and repackage the initrd.img file. What I get confused on is how to configure the kernel line parameters to tell it to boot to RAM and not the hard drive and how to go about modifying the init script in the initrd.img to not switch to the hard drive for the root file system. I can't find anything on the net that describes concrete steps on how to go about accomplishing all of this. I'm aware of the existence of Live CD's, but I need to be able to boot the PC without relying on a hard drive, CD, or any other external media. It needs to get all of its contents from the PXE boot server and boot to RAM only. I have the PXE boot side configured successfully. Also, putting the root file system on a NFS share is also out of the question.
mc (Midnight Commander) in Kubuntu 9.10 (Karmic Koala) has a problem accessing .zip and other archives as a virtual file system. It has to do with a changed format of the output from unzip. Discussions offer a workaround, but that requires system (i.e. root) file access; my work box is locked down.
I have Ubuntu (without the K) 9.10 at home, and I downloaded the source package and made a code change that's a horrible hack (I would not dream of publishing) that would allow me to run my own correctly working copy of mc in a subdirectory of my $HOME. Alas, my "at home" box is configured differently, both in terms of processor(s) and KDE vs. Gnome; a transferred-over mc executable fails immediately with bus error.
I'm attempting to install Kubuntu on a new laptop but seem to be having some strange issues. It's a Dell Latitude E5410 with 160GB HDD, 2GB RAM and Intel Core i5-520M(2.4GHz). I'm trying to install Kubuntu 10.10. When I restart the machine and boot from the CD for an initial install it seems to hang for a VERY long time. It will eventually get to the boot options (after hours) but seems sluggish. Once the install gets going everything seems decent except for that I can't seem to get it to finish. I know the CD is good since I used it to get Kubuntu on 2 desktops and another laptop in the last 48 hours. I've also burned another CD just to make sure. The checksum was spot on. Does anyone know what I can do to get this remedied?
The filesytem is (or was ) 500Gb ext3. We had a small electrical power failure yesterday, the server do not stop but the disk array (SCSI Raid 5 disk system) restarted. This morning, the filesystem was not available (I/O error) so I reboot the front end. The fsck failed with the message: root inode is not a directory There are nearly 400Gb of data on this filesystem. Any idea to solve the problem ? Google always point to a commercial software or windows software...
I have problem with my printer HP Deskjet D1460. My printer is configured and works. When I send a file on the print, the printer clings a sheet of paper and starts to print, but a paper as was clean so clean and remains, after printing.
I've just discovered that crontab is creating a new file in the root directory every time it executes a cronjob, and it doesn't erase over the old file so there are thousands of files in the root directory, they have the same name as the script file (appended with a numeral) but are all blank.here is what one of the cronjob's looks like[URL]
I have been running a web server from my fedora box for ~ 2 years now, though I have done terrible things to it by way of configuration settings. It seemingly works fine now, but i suspect that I have done some things in an innapropriate way. I would like to remove all of my current settings and web accessable info, and start fresh. What is the cleanest way to set my server's configuration files back to basics (not conserned about system settings related to firewalls).
I installed an Apache web server on Fedora 13. My website is built on PHP. When I try to access the web servers particular directory it take too much time to load.I have added index.php in DirectoryIndex statement also in the httpd.conf file. The home page of my sites has 150 kb image file.
I am using fedora 12. I got "no space in root directory" warning from the system. When I went through it, I found many of the space has been occupied by /var/log/httpd/error-log file. So I just deleted the file but when I check the space with "df -h" command. It shows 0% availability. The same problem occurred before but it solved when I restarted the system. But how to regain the space without restarting the system?
I deleted a bunch of things with root (old home folders) but now I can't empty the trash....where is the directory that the root trash goes to? I'll do a terminal delete from there but I can't seem to find it.