*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
does x work at all? i had a similar problem, but, it was only for my user. x worked fine for root. finally after a ton of reading, the simple solution was to overwrite the existing .xinitrc and .xsession then startx. it worked like a charm. if x isn't working at all, my apologies for posting 0 amount of help. i read the post and no one has mentioned if x works for root, so i thought i'd contribute just in case.
right now, I have serious computer problems .. I have 2 operating systems:
1) Windows XP
2) FreeBSD 4.8
last Sunday there was a storm here .. and when I got home the computer was shut (I had left if open) .. it was running windows when it got shut ..
anyway .. I turned the computer on ..
Checking NVRAM ...
(it pauses for about 30 seconds) ..
CMOS Battery low
^ what does that mean ?
(another 30 second pause)
anyway .. Windows works , nothing damaged, BSD works, nothing damaged .. so I thought anyway ..
(the 30 seconds pause still take place when I open the computer ..)
Tuesday .. when I open it ..
what follows is a BEEP!
I try again .. F1 .. BEEP!
again again again .. a continuous BEEP! ..
restart .. same thing ..
decide to see if FreeBSD works .. no problems there ..
so .. Windows doesn't want to boot .. now .. because of the events Sunday .. I can't quite diagnose the problem (which is *probably* not a freebsd problem .. but its solution will cirtantly involve freebsd) ..
-> could it be a windows problem (meaning I have to reinstall)
-> could it be a hardware problem ?
-> could it be a MBR problem ? and I should reinstall the freebsd boot loader ? (p.s.: how would I do that ?)
I have asked a question some time ago, tryed to fix it on my own .. couldn't .. how do you mount a floppy ? I have tryed /dev/afd0[a-c], /dev/fd0 .. no results .. really can't figure it out ..
You have to do a couple of things. First, create a file system on your hard drive that you mount the floppy to. /mnt/floppy is not uncommon.
Assuming that you have done this, you need to read through the output of dmesg to see what device bsd assigns to your floppy (my guess is /fd0, but read the output carefully). Make sure that the floppy is already formatted and readable on your windows boxes. Then one of the following should work:
mount -t vfat /dev/fd0 /mnt/floppy
mount -t msdos /fev/fd0 /mnt/floppy
I have also had to do this
mount -t msdos /dev/fd0.720 /mnt/floppy
You can save a little time by doing an "ls /dev | more" and looking for the approaiate entry, i.e., fd0, fd0.1440, fd0.720 and the like.
cnjohnson - thanks a lot for replying ! I will try what you have said soon enough ..
what a silly problem I have now .. (maybe all my problems have been "silly" ..)
some time ago .. I had these 2 problems
1) I wanted a smaller Console font
2) X didn't work
.. LQ was of great help and I managed to fix them both !
My problem now:
because of the smaller console font, when I start X .. it has a very high resolution .. if I open a shell .. I can barley even read the prompt .. and this happens to other programs as well ..
now .. of course I can make Konsole's font "huge" , and try do so with all the programs I use .. but .. I was wandering if there is some method .. to give X a lower resolution .. without damaging the console resolution
I still want a small font in text-mode but I want a lower resolution in X