hey guys
Just install DragonFly-2.6.3
and i'm having trouble with what to do next ?
being trying to connect my 3g usb-modem so that i can update sys and put some programs on but have no idea, have been search here and everywhere but with no success.
then found out that the kernel sources come with the cd version and tried to compile them but having problems doing that, i extracted the src-sys.tgz in /usr and cd to /usr/src and tried to make it but gets error message
" make:dont know how to make /usr/src/sys/boot/pc32/boot2///////////
and so on
am i doing something wrong
tried doing the way the handbook said about compiling the kernel but i get a error message "must make buildworld first" so tried that and get error message
"mtree: line 1 too long"
so now im lost could someone help me please
cheers dave

thanks klanger for your reply i check out your ideas
my problem was orginally trying to connect to the internet through my huawei usb-modem as this is the only way i can get online,i just wanted to build my new dfbsd as i use linux on my laptop and setup dfbsd on my pc.never used bsd before and find it interesting
tried searching for usb-modem etc. here and feebsd forum but most say about adding
things to your kern.conf but cant find where it is locate.
cheers dave

If this your 1st time with BSD and you want to use this system as main OS, I thing you should try FreeBSD first (if you don't like cli installer there is a faster&more GUI way via PC-BSD GUI installer).

The main reason is that the community is bigger (there fore more problems are either solved or you'll solve them quicker), there are more pkg and the ports are more up-to-date etc.

Don't get me wrong DragonFlyBSD is fantastic (HAMMER ect - I'm using it now on my eeepc) but I think it is better to start with something easier and after a while get your hands dirty in DFBSD. In fact, DFBSD is "based" on FBSD so if you get to work your hardware in FBSD it should (hmmm) in the end work with DFBSD.

Eg. wifi in eeepc under DFBSD is activated the same way as in FBSD 7.2.
With applications it seems that linux is nearly "bleeding", then there is FBSD and then other BSD (with DFBSD).

In fact, DFBSD is "based" on FBSD so if you get to work your hardware in FBSD it should (hmmm) in the end work with DFBSD.

DragonFlyBSD is based on FreeBSD 4, which is from 2000/2001.
I don't know which direction DragonFlyBSD has taken since then, but I do know there have been *significant* changes and additions in FreeBSD.

So if a device works on FreeBSD, it's no guarantee it will work on DragonFlyBSD, or vice versa.

__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things.

i,ve just put that line in /etc/rc.conf and reboot and still the same.
i have read on here about putting "device ucom + device usbd" in your kern.conf but i cannot find where kern.conf is .in linux it is all in your /usr/src but after i installed dfbsd there was no /usr/src until i found out that the livecd had the kernel source codes , so i cp them to /usr and unpacked it and now i have /usr/src .but now kern.conf for the current kernel,read that i can build kernel from there (dfbsd + freebsd handbook) so i tried that but it tells me that i have to buildworld first and my understanding is to build world you need internet access which brings me back to my orginally problem off how to get my usb-modem to work.Is my understanding correct or is therea way off downloading something from another computer so i can buildworld and build kernel
cheers dave

i came across this quick guide to seting it all up and yep heeeeeee it is all working
here is that guide :

Connecting to the Internet with UMTS on NetBSD

All you need is a laptop with cardbus slot (PCMCIA) and a datacard which is supported by NetBSD. The card will appear as an USB modem to the kernel. In my example I am using an Option N.V. MC3G (Vodafone Mobile Connect Card).

First of all you have to make sure the datacard is recognized by the kernel:

ucom0 means we have successfully attached a serial adapter. ugen0 would mean the card is not yet supported. The device can be accessed through /dev/ttyU0. For a test, we add the following line to /etc/remote to communicate with the modem:

When you can talk to the modem as shown above you are nearly done. The card is fully supported and only some configuration is standing between you and a wireless internet connection. While at it you may want to disable the PIN on your SIM card. Otherwise you have to enter it every time the card is inserted or the system is rebooted. This can be a problem, because you can set the PIN only once. Afterwards this will produce an error. Type the following line while connected with the modem and replace "1234" with your valid PIN:

at+clck="sc",0,"1234"

If you do not want to disable the PIN, you have to enter it with the command at+cpin="1234" now. In both cases it should take only a few seconds before the blinking of both LEDs changes into a blinking of either the green (GPRS) or the blue one (UMTS) alone. The signal quality can be checked with at+csq:

at+csq
+CSQ: 15,0

OK

15 is a quite good value for UMTS. Possible levels are between 0 and 31. Now you should choose if you prefer UMTS or GPRS connections:
AT_OPSYS=0,2 GPRS only
AT_OPSYS=1,2 UMTS only
AT_OPSYS=2,2 Prefer GPRS
AT_OPSYS=3,2 Prefer UMTS

The provider is set with AT+CGDCONT, but it should already be preconfigured when receiving your SIM card. When missing, the configuration for Vodafone would be:

AT+CGDCONT=1,"IP","web.vodafone.de"

All the settings done above will be stored onto the SIM card, so we never have to bother about it again. Next step is the configuration of the internet access via PPP (point to point protocol)!

For the pppd daemon to work we have to provide a configuration and a chat script for our provider (Vodafone in this case). After activating pppd in /etc/rc.conf

ppp_peers="vodafone"

the daemon will read its options from /etc/ppp/peers/vodafone. The directories /etc/ppp and /etc/ppp/peers probably have to be created first. Then I am using a config file like this:

noauth
The provider doesn't have to authenticate itself.
connect
Specifies the chat-script to use when connecting (see below).
/dev/ttyU0
The modem device to use.
460800
Usual bps rate for UMTS.
local
Don't use modem control lines. Not required for UMTS.
defaultroute
Set the default route to this PPP connection, after it has been successfully established.
noipdefault
The provider supplies us with a local IP address during IPCP negotiation.
usepeerdns
Query the provider for DNS addresses and create /etc/ppp/resolv.conf with it.
novj
Diable Van Jacobsen header compression (Vodafone doesn't support it?).
user "vodafone"
User name for authentication.
password "vodafone"
Password for authentication.
persist
Always try to reconnect, when the connection fails or is lost.
maxfail 0
Never give up after failed connection attempts.

The chat-script (/etc/ppp/peers/vodafone.chat) is not much more than a simple dialing of *99***1#:

As soon as a connection to the provider was established successfully, we have a valid default route and a recent resolv.conf in /etc/ppp/. Now you could either use /etc/ppp/ip-up to copy resolv.conf or just create a link:

# cd /etc
# ln -s /etc/ppp/resolv.conf resolv.conf

That's all. Every time the system is booted you will be connected to the internet via UMTS, provided it is available. Now some fine tuning could be done. For example to delay pppd until /dev/ttyU0 is ready, or to allow LAN connections via DHCP, when you returned to your office.
Frank Wille, September 2008

i came across this quick guide to seting it all up and yep heeeeeee it is all working
here is that guide :

Connecting to the Internet with UMTS on NetBSD

All you need is a laptop with cardbus slot (PCMCIA) and a datacard which is supported by NetBSD. The card will appear as an USB modem to the kernel. In my example I am using an Option N.V. MC3G (Vodafone Mobile Connect Card).

First of all you have to make sure the datacard is recognized by the kernel:

ucom0 means we have successfully attached a serial adapter. ugen0 would mean the card is not yet supported. The device can be accessed through /dev/ttyU0. For a test, we add the following line to /etc/remote to communicate with the modem:

When you can talk to the modem as shown above you are nearly done. The card is fully supported and only some configuration is standing between you and a wireless internet connection. While at it you may want to disable the PIN on your SIM card. Otherwise you have to enter it every time the card is inserted or the system is rebooted. This can be a problem, because you can set the PIN only once. Afterwards this will produce an error. Type the following line while connected with the modem and replace "1234" with your valid PIN:

at+clck="sc",0,"1234"

If you do not want to disable the PIN, you have to enter it with the command at+cpin="1234" now. In both cases it should take only a few seconds before the blinking of both LEDs changes into a blinking of either the green (GPRS) or the blue one (UMTS) alone. The signal quality can be checked with at+csq:

at+csq
+CSQ: 15,0

OK

15 is a quite good value for UMTS. Possible levels are between 0 and 31. Now you should choose if you prefer UMTS or GPRS connections:
AT_OPSYS=0,2 GPRS only
AT_OPSYS=1,2 UMTS only
AT_OPSYS=2,2 Prefer GPRS
AT_OPSYS=3,2 Prefer UMTS

The provider is set with AT+CGDCONT, but it should already be preconfigured when receiving your SIM card. When missing, the configuration for Vodafone would be:

AT+CGDCONT=1,"IP","web.vodafone.de"

All the settings done above will be stored onto the SIM card, so we never have to bother about it again. Next step is the configuration of the internet access via PPP (point to point protocol)!

For the pppd daemon to work we have to provide a configuration and a chat script for our provider (Vodafone in this case). After activating pppd in /etc/rc.conf

ppp_peers="vodafone"

the daemon will read its options from /etc/ppp/peers/vodafone. The directories /etc/ppp and /etc/ppp/peers probably have to be created first. Then I am using a config file like this:

noauth
The provider doesn't have to authenticate itself.
connect
Specifies the chat-script to use when connecting (see below).
/dev/ttyU0
The modem device to use.
460800
Usual bps rate for UMTS.
local
Don't use modem control lines. Not required for UMTS.
defaultroute
Set the default route to this PPP connection, after it has been successfully established.
noipdefault
The provider supplies us with a local IP address during IPCP negotiation.
usepeerdns
Query the provider for DNS addresses and create /etc/ppp/resolv.conf with it.
novj
Diable Van Jacobsen header compression (Vodafone doesn't support it?).
user "vodafone"
User name for authentication.
password "vodafone"
Password for authentication.
persist
Always try to reconnect, when the connection fails or is lost.
maxfail 0
Never give up after failed connection attempts.

The chat-script (/etc/ppp/peers/vodafone.chat) is not much more than a simple dialing of *99***1#:

As soon as a connection to the provider was established successfully, we have a valid default route and a recent resolv.conf in /etc/ppp/. Now you could either use /etc/ppp/ip-up to copy resolv.conf or just create a link:

# cd /etc
# ln -s /etc/ppp/resolv.conf resolv.conf

That's all. Every time the system is booted you will be connected to the internet via UMTS, provided it is available. Now some fine tuning could be done. For example to delay pppd until /dev/ttyU0 is ready, or to allow LAN connections via DHCP, when you returned to your office.
Frank Wille, September 2008