04-15-2008
Uh, tough one, I've never had issues installing BSD on any hardware that I had and still have. My suggestions :
try different machine - same disk
try latest bsd - 7.0 on the first machine.
try looking at BIOS options at boot time, something could have gone wrong.
Last question - is this going to be server ? Because if it's intended for GUI with KDE for example, you can try PCBSD -
PC-BSD - Home - it's a clone of FreeBSD 6.2
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i messed up while installing freebsd into a dual os wannabe system.
Now, how do i del it( so i wouldn't get prompted to choose freebsd during boot?)so that i could try installing a different flavour of linux?
cheers:eek: (1 Reply)
Discussion started by: coffeecoolers
1 Replies
2. UNIX for Advanced & Expert Users
Hi all,
I'm having a disturbing problem with getty i fbsd (fbsd 4.5 on a compaq laptop). One day, when the boot process was complete, my logs were spammed with messages from getty:
May 20 21:27:10 laptop getty: login_tty /dev/console: Operation not supported by device
May 20 21:27:10 laptop... (1 Reply)
Discussion started by: kuba
1 Replies
3. UNIX for Advanced & Expert Users
i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website.
in the documentation it says snort should be installed through the following:
-----
make -DWITH_MYSQL -DWITH_FLEXRESP ; make install
-----
later it says to do the... (13 Replies)
Discussion started by: xyyz
13 Replies
4. UNIX for Advanced & Expert Users
alright, this problem is a bit weird.
i rebuilt the kernel and included the parameters for the 2 AMD NIC's in
the system. now, ifconfig shows them to be pcn0 and pcn1. i assigned
them their ip addresses in rc.conf.
now, for some reason, i cannot ping the interface from another system and... (7 Replies)
Discussion started by: xyyz
7 Replies
5. BSD
I had just instal freebsd in my computer, wich is very nice,am very happy about it, am new to the unix os and i know unmost nothing and my problem is that i din't do i good configuration because i can get internet when i open the webbrowser, a have a yahoo dsl connection, i can't even play a cd in... (0 Replies)
Discussion started by: nobody
0 Replies
6. UNIX for Dummies Questions & Answers
hello,
i have a problem installing a d-link dwl-510 wireless network card on freebsd 4.8
first, i already successfully installed a dwl- 500 (which is a pcmcia card in a pci card) by adding just a few simple lines to my /etc/rc.conf
pccard_enable="YES"
pccard_mem="DEFAULT"... (0 Replies)
Discussion started by: termiEEE
0 Replies
7. BSD
Forgive the newbie question. I've been trying to install FreeBSD 5.4 on a new AMD64 based box at work today, and I started running into problems. Maybe some background is appropriate? Here goes...
I've finished the first stage of development of a model in C++ which simulates airflow through a... (1 Reply)
Discussion started by: ForestryJim
1 Replies
8. Linux
why is my new freeBSD hanging at setting up hostname each time I plug in the network cable i use host name like X.ng I intend to configure it as a gateway (2 Replies)
Discussion started by: AkinOkin
2 Replies
9. BSD
Hello
So i got my hands on some freebsd iso, installed it in a qcow2 image and installled git and bash.
So far, so good.
Git repositry retireved
install script executed
files got copied
files have exec flag
files are in $PATH / found by which / bash-completion works
But still,... (3 Replies)
Discussion started by: sea
3 Replies
10. UNIX for Advanced & Expert Users
This is a cross post as I haven't got any solution and I'm badly in need of one.
I've installed Slackware 14.2 in /dev/sda1 and x86Solaris 10 U6 in /dev/sda3 (sda2 is Linux swap)and boot menu was Solaris grub but, later deleted Solaris partition and installed FreeBSD12 (for i386) on the same... (3 Replies)
Discussion started by: vectrum
3 Replies
LEARN ABOUT FREEBSD
style.makefile
STYLE.MAKEFILE(5) BSD File Formats Manual STYLE.MAKEFILE(5)
NAME
style.Makefile -- FreeBSD Makefile file style guide
DESCRIPTION
This file specifies the preferred style for makefiles in the FreeBSD source tree.
o All makefiles should have an SCM ID at the start of the file, followed by a blank line.
# $FreeBSD$
o .PATH: comes next if needed, and is spelled ``.PATH: '', with a single ASCII space after a colon. Do not use the VPATH variable.
o Special variables (i.e., LIB, SRCS, MLINKS, etc.) are listed in order of ``product'', then building and installing a binary. Special
variables may also be listed in ``build'' order: i.e., ones for the primary program (or library) first. The general ``product'' order
is: PROG/[SH]LIB/SCRIPTS FILES LINKS [NO_]MAN MLINKS INCS SRCS WARNS CFLAGS DPADD LDADD. The general ``build'' order is:
PROG/[SH]LIB/SCRIPTS SRCS WARNS CFLAGS DPADD LDADD INCS FILES LINKS [NO_]MAN MLINKS.
o Omit SRCS when using <bsd.prog.mk> and there is a single source file named the same as the PROG.
o Omit MAN when using <bsd.prog.mk> and the manual page is named the same as the PROG, and is in section 1.
o All variable assignments are spelled ``VAR='', i.e., no space between the variable name and the =. Keep values sorted alphabetically, if
possible.
o Do not use += to set variables that are only set once (or to set variables for the first time).
o Do not use vertical whitespace in simple makefiles, but do use it to group locally related things in more complex/longer ones.
o WARNS comes before CFLAGS, as it is basically a CFLAGS modifier. It comes before CFLAGS rather than after CFLAGS so it does not get lost
in a sea of CFLAGS statements as WARNS is an important thing. The usage of WARNS is spelled ``WARNS?= '', so that it may be overridden
on the command line or in make.conf(5).
o ``NO_WERROR= yes'' should not be used, it defeats the purpose of WARNS. It should only be used on the command line and in special cir-
cumstances.
o CFLAGS is spelled ``CFLAGS+= ''.
o Listing -D's before -I's in CFLAGS is preferred for alphabetical ordering and to make -D's easier to see. The -D's often affect condi-
tional compilation, and -I's tend to be quite long. Split long CFLAGS settings between the -D's and -I's.
o Do not use GCCisms (such as -g and -Wall) in CFLAGS.
o Typically, there is one ASCII tab between VAR= and the value in order to start the value in column 9. An ASCII space is allowed for
variable names that extend beyond column 9. A lack of whitespace is also allowed for very long variable names.
o .include <bsd.*.mk> goes last.
o Do not use anachronisms like $< and $@. Instead use ${.IMPSRC} or ${.ALLSRC} and ${.TARGET}.
o To not build the ``foo'' part of the base system, use NO_FOO, not NOFOO.
o To optionally build something in the base system, spell the knob WITH_FOO not WANT_FOO or USE_FOO. The latter are reserved for the
FreeBSD Ports Collection.
o For variables that are only checked with defined(), do not provide any fake value.
The desire to express a logical grouping often means not obeying some of the above.
EXAMPLES
The simplest program Makefile is:
# $FreeBSD$
PROG= foo
.include <bsd.prog.mk>
The simplest library Makefile is:
# $FreeBSD$
LIB= foo
SHLIB_MAJOR= 1
MAN= libfoo.3
SRCS= foo.c
.include <bsd.lib.mk>
SEE ALSO
make(1), make.conf(5), style(9)
HISTORY
This manual page is inspired from the same source as style(9) manual page in FreeBSD.
BUGS
There are few hard and fast style rules here. The style of many things is too dependent on the context of the whole makefile, or the lines
surrounding it.
BSD
January 8, 2005 BSD