Dual booting with freeBSD

[sossego]

In the installation media choose #3 because you are behind a router firewall.
Choose the site closest to you.
Nadir, it will be ftp.de.freebsd.org and a few others for you.

Choose the realtek card.
No to IPv6.
Yes for dhcp.
Make up a domain name. Mine for this example is chicken.wing.

Let it work.


I'll be back later to continue the added howto.

[llivv]

.

[sossego]

I can't smash the whole shebang into the partition -> / ?
Would the BSD-bootloader recognize a Linux-installation? (for hard-disk, atm this is just training)

No for the first part.
At the least you want 512M dedicated to swap.
This example disk size is small.
You should also have a smaller /home partition.
Yes, it would but do it with FreeBSD installed first then Linux such that the disk is as such:

Code: Select all

sh-4.0# fdisk -l

Disk /dev/sda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa8a8a8a8

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        2423    19455880+  a5  FreeBSD
Partition 1 does not end on cylinder boundary.
/dev/sda2   *        2423        4801    19101696   83  Linux
/dev/sda3            4801        4864      512000   82  Linux swap / Solaris
sh-4.0# 

And that- yes, I am doing the install and howto from a Fedora install because the desktop is running OpenBSD but the rules are the same. Just be sure that your /boot/grub/menu.lst is similar.
Later I will add the grub menu.lst from my Desktop.- /boot/grub/menu.lst should be like this:

Code: Select all

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,1)
#          kernel /boot/vmlinuz-version ro root=/dev/sda2
#          initrd /boot/initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.32.9-67.fc12.i686)
	root (hd0,1)
	kernel /boot/vmlinuz-2.6.32.9-67.fc12.i686 ro root=UUID=cc2665d8-a195-4600-99b1-f112402f5509 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
	initrd /boot/initramfs-2.6.32.9-67.fc12.i686.img
title Fedora (2.6.31.5-127.fc12.i686)
	root (hd0,1)
	kernel /boot/vmlinuz-2.6.31.5-127.fc12.i686 ro root=UUID=cc2665d8-a195-4600-99b1-f112402f5509 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
	initrd /boot/initramfs-2.6.31.5-127.fc12.i686.img
title FreeBSD i386 8.0
	rootnoverify (hd0,0)
	chainloader +1

[sossego]

I have a few thing to do. This howto will be continued later.
Apologies to anyone doing a follow-it-live deal.

[nadir]

I can't install grub on the linux one ! (in that case, explanation is long, just believe me).
Is there a way to do it from/for BSD ? Bootloader on BSD, and it also boots the Linux install?.
Else: perhaps put Grub on a floppy or CD then.
-
Partitions: ok, i got it (i understood and i got it that way)

"I have a few things to do". Null problemo.

@llivv: i don't think i did understand you. Sorry. If you care just explain (pm or here, what you prefer). My fault: English is quite difficult.

[llivv]

.

[nadir]

Well: at least i can appreciate the people from Turkey a bit more (though i always did): Some speak better German than i do.

--------
OK, that said:
I must be doing it wrong. I tried to build gdm, which is a rather small package, and i am getting asked all kind of weird questions for three hours now. The last one:
"Options for libcdio" "Paranoia" -> "Support for accessing audio via CD Paranoia"
Not sure what "cdparanoia" has got to do with gdm. I simply did "cd /usr/ports/gdm" and "make install clean". Oh my...

Therefor i couldn't start with qemu, the VirtualBox build of gdm takes forever. Like said. I will start as soon its finished in VBox. Perhaps that will be tomorrow.

[nadir]

Sossego, for your info:
I installed in qemu, and after installing xorg i had the same problem like above: no mouse, no keyboard. Again i edited /etc/rc.conf and added hald_enable="YES" and dbus_enable="YES". Voila, the mouse is moving.

[sossego]

Continuing the qemu howto.

Answer no to gateway.
No to inetd.
No to sshd login.
No to anonymous ftp access.
No to nfs server.
Remember that you are doing a limited install on a small virtual disk.
No to console.
Set your timezone.
UTC time choose no.
Yes, configure mouse.
Choose enable.
Click on the screen so that qemu grabs the mouse.
Hit enter and choose yes.
Use left ctrl + left alt simultaneously to disable the mouse from qemu.
No, do not browse the collection yet. Ports will be taken care of later.
You want to add a user.
Choose user andf hit enter.
Type name.
Tab to password and add password. Confirm password. In the member groups type wheel. You won't be able to su without it.
Exit and anter the root password.

Set any last options? No.
Exit install.

Close qemu. It won't hurt it and reboot with:

Code: Select all

$ qemu -hda freebsd.img -soundhw sb16 -m 384 -boot c

[nadir]

You want to add a user.
Choose user andf hit enter.
Type name.
Tab to password and add password. Confirm password. In the member groups type wheel. You won't be able to su without it.

I also read the handbook. Well: the ncurses-like interface has got two entries, both mention the word: "group". Nowhere is it explained which one is for what.

site note:
Perhaps mention somewhere, at the beginning might be the best warning, the word: "time". Very lots of time. Very, very lots of time. Makes me love the debian-package-management. Its ok if installing gdm takes 3 hours. What is not so ok is if after 1.5h one is getting asked a question (that is: you need to sit there for all the three hours and nanny it). Once the three hours are over: "Sorry pal, broken pipe, run it again".
That was a) a joke and b) really makes me <edited for profanity by the rules> up.

[sossego]

I've forgotten how to do the tun tap networking.
I'm going to break the tutorial for now.
I have notes in one of my emails.


Nadir, it's a different OS but with similar components. You're not given root privileges nor are you automatically entered into a group.
That has to be done with the root account. After a while, you should be comfortable enough to create and use an account that isn't in wheel.

[nadir]

Yes , i know. I was kidding. For me its very frustrating being that lost.

Please wait a sec. I re-installed in qemu and in a short while i will be asked about the user again. As said: there are two group-entries, and i don't know which one is the right one.
PS: i created a thread at forums.freebsd, but they too seem to be in love with the rtfm (being called handbook over there).

During this week i will go for hard-disk. I sure will create thread about it (at the freebsd-forum). If you care give me a hand.

----------------
Here is how it looks like:
----------
LoginID UID Group Passwd
FullName MemberGroups
HomeDirectory LoginShell
OK Canci...erghh...Cancel
----
I have added group wheel to the entry Group between UID and Passwd

[sossego]

The thread/howto here is a good beginners introduction to FreeBSD. This way you have a system setup and can work with it..

Which thread?

I'll create a howto thread on one of the forums that I am part of and will link you to it.

Do you have spare equipment to install FreeBSD on?
If not, are you comfortable resizing your partitions?
Did you let Debian do automated installing or did you create two primary partitions?

Trust me, I'm not being difficult; it's just that you either need a primary partition or a dedicated disk.

[nadir]

http://forums.freebsd.org/showthread.php?t=13195

As said: during this week i will go for hard-disk (my second PC, first partition). Like you say this is a how-to with a special purpose. Thats why i will make threads over there ( forums.freebsd.org). I don't expect answers but: read the handbook.

Thanks for your help in this thread here (during the last days).
In VirtualBox your OP-how-to worked like a charme (besides the hald and dbus-problem). But the resulting resolution is a bit odd. Qemu seems to be a different beast.

[sossego]

The first thing is that you don't need to run Xorg -configure anymore. So, to test it out, run the following code in the FreeBSD qemu install- and by the way, if you're networking does not work like mine is doing in qemu, then Do install the ports and packages you need from the beginning part of this qemu howto. I screw up a lot.-

Code: Select all

$su
Password:
# ls /root
<output here. If xorg.conf.new is present run the following command>
#rm -rf xorg.conf.new
#startx

it should start.

[sossego]

I need to add that you must cd to root.

Code: Select all

cd /root
<Now run the previous command. My apologies.>

[sossego]

I see that nadir has a good beginner's understanding of FreeBSD.


For this howto change a few things.
Install the packages at the install.

If you are having trouble with networking, you may need to setup tun/tap.
On a FreeBSD system, this isn't necessary. Depending on your distribution and setup within your home/ workplace/ lab, there may be some trouble.

You can use any cd/dvd device by writing a "permanent" script such as

Code: Select all

qemu -hda <name>.img -m <value between 128 and 512m> -soundhw <option> -cdrom </path/to/real/device> -usbdevice tablet <to prevent grabbing> -other_options <other values> -boot c

and save it as freebsd_vm.sh

[sossego]

Other notes.
Gnome_mount and hald don't play with each other too well. Choose one or the other.
KDE3 and KDE4 may cause troubles with each other. Just pick one.
If a port breaks/stops during compiling, go back and see where the problem is. Correct that and then cd back to the original port you were building.

Once you are comfortable with this tutorial, you can try those out at daemonforums and forums.freebsd.

Please do not judge other members of the Linux and BSD communities by my actions and words. Believe me, they are much more stable than I am.

[nadir]

I see that nadir has a good beginner's understanding of FreeBSD.

Lol. Though i like compliments i disagree. The BSD-userland is giving me the business. Hell of a business. I am barely able to change my Prompt or enable syntax-highlighting in vim. To sum it up: No-brainer have become a problem.
I got it on hard-disk now, which worked with much less problems then in Qemu or VBox (but then: i already had a bit of training). X and that worked out of the box. With the extra-speed of a hard-disk-install its more fun.

Anyway:
a) Is the BSD-bootloader able to load Linux and/or Windows or not? The PC dosna seem to boot from floppy.
b) You got some examples about mounting Linux-partitions from BSD and the other way around ?
c) How would i change $SHELL from zsh (?) to bash. I already got it installed.
those were Linux/BSD dual-boot related, here comes:
d) You got a good link bout the compiling? I am not able to get e17 running, but wouldn't know about changing/troubleshooting it. (NO, i don't want the `pgk_add enlightenment-version`. It socks. )

Also, if you like, you might add a comparison between basic cli-commands and where files (like config-files or bin-files) are stored in linux and bsd. This are just some 'lousy ideas' from me, a nadir in the bsd-world, who might tell you what problems one might run into. You might do ti or do it not, but i think it might be useful ... ok?

[sossego]

Yes.
The way you want it is:
1) Windows installed first, then FreeBSD
2 )FreeBSD then Linux.

There will be a function key for each. You can also install grub.


The look for shells in /usr/ports or run

Code: Select all

make search name=<name of shell>

and cd to that directory.
I believe the command is chsh.



Those examples are here. Use the find in the iceweasel/firefox browser and type in "mount -t". That will bring you to the example.

You need to switch to ports and use make. Meta packages usually have a config file.
Cd to the port and run

Code: Select all

make config && make depends config && make install clean

and watch where the port breaks. It's those values you will need to change. KDE4 took a few days to build. Enlightenment may take a few hours.
Gives you time to enjoy a few beers and a nap.


The binary files are in the same basic places. System configuration is different. The most important are: /etc/rc.conf, /boot/defaults/loader.conf, and sysctl.

Go through this howto again and look where the links take you.
Look at the tutorials at forums.freebsd as another beginner's source of information.


I use straight out vi, no highlighting.
I suck at bash.

Somethings I won't be able to help you on. For those, visit the forums mentioned and linked to.