Re: Filesystem layout with sperated /boot partition
Hi Eric, Thanks for the reply. I have now a better understanding whats possible with FreeBSD. One question (last one) which I could not find an answer to in the online manual is : How would you do a Dual or multi OS boot machine f.e. with Windows on the first disk, first slice, first partition and FreeBSD on another partition ? Would I need a boot floppy or perhaps its not possible at all ? Best regards Nils Valentin http://www.be-known-online.com Quoting Erik Trulsson [EMAIL PROTECTED]: On Mon, Apr 03, 2006 at 02:33:42AM +, [EMAIL PROTECTED] wrote: Hello FreeBSD Fans, I wanted to create a new system and was thinking about the following layout. Size | Mountpoint | Device name | File system 100M /boot /dev/ad2s1a UFS2+S 1024MB --- /dev/ad2s1b SWAP 15GB / /dev/ad2s1c UFS2 I want to put /boot on its own partition, but somehow I dont have a lot of luck. I can install the OS, but when I reboot the bootloader will not boot. Don't do that. You can not have /boot as a separate partition. It just contains the kernel and the loader. The other things that are needed for booting (like /bin/sh or /sbin/mount) reside elsewhere. (Having /boot as a separate partition is apparently some Linux-specific convention.) What is normally done under FreeBSD when you want a small boot partition is to create /usr and /var as separate partitions which will let you create a small (100M) '/' partition. (You will probably also want either a separate /home partition for user home directories, or let them reside under /usr/home. (I think the latter is the default, but I am not 100% sure.) No /boot/loader ... Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel ... 1) I wouldnt mind on which partition /boot or / sits or what its named, but I would like to separate /boot on a different partition and it seems like it wouldnt boot when I do this. Is this just a matter of updating the bootloader ? Wouldnt the installer do that automatically ? See above. You can't do that. 2) The part which I dont get is why is / always ad2s1a - even when I create /boot first ? (/boot will become f.e. ad2s1d) and SWAP will become ad2s1b. You need to boot from / and it should be partition 'a' on the slice. It is probably possible to change this, but it would be much more pain and trouble than it is worth. So what I end up with is something like Size | Mountpoint | Device name | File system 15GB / /dev/ad2s1a UFS2 1024MB --- /dev/ad2s1b SWAP 100M /boot /dev/ad2s1d UFS2+S Any replies much appreciated. A good place to start reading is the online handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ especially the chapter on installing FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html The FAQ at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ might also prove helpful. Best regards Nils Valentin http://www.be-known-online.com -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
On Apr 2, 2006, at 11:16 PM, [EMAIL PROTECTED] wrote: Hi Eric, Thanks for the reply. I have now a better understanding whats possible with FreeBSD. One question (last one) which I could not find an answer to in the online manual is : How would you do a Dual or multi OS boot machine f.e. with Windows on the first disk, first slice, first partition and FreeBSD on another partition ? Would I need a boot floppy or perhaps its not possible at all ? Hi Valentin, Dual booting FreeBSD along with other Operating Systems is definitely possible. And you're right, I couldn't find any reference to how this can be done in the Handbook either. :) Basically, it is my understanding that you will want to add a dedicated FreeBSD partition to your disk, and configure the slices within that partition as you have learned previously. In terms of how to boot, while you can use a floppy, there are many boot managers, that once configured, are more convenient to use than floppies. I did a quick google, and found a guide that seems to cover this topic in some depth: http://www.faqs.org/docs/win_bsd/index.htm Good luck, -Andy Reitz. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
On Mon, 03 Apr 2006 08:48:30 +0200, Andrew Reitz [EMAIL PROTECTED] wrote: Dual booting FreeBSD along with other Operating Systems is definitely possible. And you're right, I couldn't find any reference to how this can be done in the Handbook either. :) http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
On Mon, Apr 03, 2006 at 06:16:02AM +, [EMAIL PROTECTED] wrote: Hi Eric, Thanks for the reply. I have now a better understanding whats possible with FreeBSD. One question (last one) which I could not find an answer to in the online manual is : How would you do a Dual or multi OS boot machine f.e. with Windows on the first disk, first slice, first partition and FreeBSD on another partition ? Would I need a boot floppy or perhaps its not possible at all ? It is certainly possible. Basically you just put each OS on a separate slice (either on the same disk, or on separate disks) and use some boot-manager that can be used to choose boot-disk. An article that is getting a bit old, but still should be useful that discusses this can be found at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/multi-os/index.html (The issues mentioned in the artice about the 1024-cylinder limit can be mostly ignored on reasonably modern systems, and there are newer boot-managers available than those described in the article.) Best regards Nils Valentin http://www.be-known-online.com Quoting Erik Trulsson [EMAIL PROTECTED]: On Mon, Apr 03, 2006 at 02:33:42AM +, [EMAIL PROTECTED] wrote: Hello FreeBSD Fans, I wanted to create a new system and was thinking about the following layout. Size | Mountpoint | Device name | File system 100M /boot /dev/ad2s1a UFS2+S 1024MB --- /dev/ad2s1b SWAP 15GB / /dev/ad2s1c UFS2 I want to put /boot on its own partition, but somehow I dont have a lot of luck. I can install the OS, but when I reboot the bootloader will not boot. Don't do that. You can not have /boot as a separate partition. It just contains the kernel and the loader. The other things that are needed for booting (like /bin/sh or /sbin/mount) reside elsewhere. (Having /boot as a separate partition is apparently some Linux-specific convention.) What is normally done under FreeBSD when you want a small boot partition is to create /usr and /var as separate partitions which will let you create a small (100M) '/' partition. (You will probably also want either a separate /home partition for user home directories, or let them reside under /usr/home. (I think the latter is the default, but I am not 100% sure.) No /boot/loader ... Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel ... 1) I wouldnt mind on which partition /boot or / sits or what its named, but I would like to separate /boot on a different partition and it seems like it wouldnt boot when I do this. Is this just a matter of updating the bootloader ? Wouldnt the installer do that automatically ? See above. You can't do that. 2) The part which I dont get is why is / always ad2s1a - even when I create /boot first ? (/boot will become f.e. ad2s1d) and SWAP will become ad2s1b. You need to boot from / and it should be partition 'a' on the slice. It is probably possible to change this, but it would be much more pain and trouble than it is worth. So what I end up with is something like Size | Mountpoint | Device name | File system 15GB / /dev/ad2s1a UFS2 1024MB --- /dev/ad2s1b SWAP 100M /boot /dev/ad2s1d UFS2+S Any replies much appreciated. A good place to start reading is the online handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ especially the chapter on installing FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html The FAQ at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ might also prove helpful. Best regards Nils Valentin http://www.be-known-online.com -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
Hi Andrew, Andreas and Eric, Thanks for the replies. I am done for today ;-) (or so) I learned again that sometimes it is important to know how to search ;-). Oviously I followed the wrong hints in the first place. Thanks for the many links and tips. I am definitely save from now on. I will give it another couple of installation sessions which should bring me closer to my destination. ;-) Thanks anybody for the help. Best regards Nils Valentin http://www.be-known-online.com Quoting Andrew Reitz [EMAIL PROTECTED]: On Apr 2, 2006, at 11:16 PM, [EMAIL PROTECTED] wrote: Hi Eric, Thanks for the reply. I have now a better understanding whats possible with FreeBSD. One question (last one) which I could not find an answer to in the online manual is : How would you do a Dual or multi OS boot machine f.e. with Windows on the first disk, first slice, first partition and FreeBSD on another partition ? Would I need a boot floppy or perhaps its not possible at all ? Hi Valentin, Dual booting FreeBSD along with other Operating Systems is definitely possible. And you're right, I couldn't find any reference to how this can be done in the Handbook either. :) Basically, it is my understanding that you will want to add a dedicated FreeBSD partition to your disk, and configure the slices within that partition as you have learned previously. In terms of how to boot, while you can use a floppy, there are many boot managers, that once configured, are more convenient to use than floppies. I did a quick google, and found a guide that seems to cover this topic in some depth: http://www.faqs.org/docs/win_bsd/index.htm Good luck, -Andy Reitz. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
Hello FreeBSD Fans,
I wanted to create a new system and was thinking about the following layout.
Do you really mean that or to you mean put root which is '/' in its
own partition?
There is no reason to put just /boot in a separate partition. It's just
a directory to help keep some things nicely organized and has no real
stand-alone value. It is not very large nor does anything write to it
in ways that might make it change size in an uncontrolled manner. Those
things (size, stand-alone value, may grow in size unexpectedly) are the
usual reasons for making a separate partition plus isolating users and
projects.
Size | Mountpoint | Device name | File system
100M /boot /dev/ad2s1a UFS2+S
1024MB --- /dev/ad2s1b SWAP
15GB / /dev/ad2s1c UFS2
I want to put /boot on its own partition, but somehow I dont have a lot of
luck.
I can install the OS, but when I reboot the bootloader will not boot.
No /boot/loader
...
Default: 0:ad(0,a)/boot/kernel/kernel
boot:
No /boot/kernel/kernel
...
1) I wouldnt mind on which partition /boot or / sits or what its named,
but I would like to separate /boot on a different partition and it seems
like it wouldnt boot when I do this. Is this just a matter of updating the
bootloader ? Wouldnt the installer do that automatically ?
The reason it won't boot that way is that everything needed to boot must
be in the booting partition because nothing else is mounted at that time.
The boot partition must be 'a' and must be montable as '/' (usually called
root). During boot, the system does a special read-only mount of the
first ('a') partiton in the bootable slice. /boot is supposed to be part
of that partition. If you make /boot a separate partition, then it will
not be mounted and not be available for the boot process to read. Since
there is stuff in there that is needed for boot, then it won't work.
Anyway, when the system comes up to a full multi-user mode, it mounts
everything as in /etc/fstab. That first (a) partition then is remounted
according to what is given in /etc/fstab which must be '/' (eg root) for
things to work right and is normally mounted read/write (though there are
ways of arranging things to make it work read only).
I am guessing you don't understand the meaning of what is in /boot and
what it is used for. See first part of my comments.
Maybe /boot is an unfortunate name for that directory. Maybe it should
really be named kernel.stuff or kernel.loader or something like that. I am
guessing the name boot is deceiving you as to its function.
jerry
2) The part which I dont get is why is / always ad2s1a - even when I create
/boot first ? (/boot will become f.e. ad2s1d) and SWAP will become ad2s1b.
The first partition in a slice is considered the boot slice and '/' is
the boot partition.
So what I end up with is something like
Size | Mountpoint | Device name | File system
15GB / /dev/ad2s1a UFS2
1024MB --- /dev/ad2s1b SWAP
100M /boot /dev/ad2s1d UFS2+S
Any replies much appreciated.
Best regards
Nils Valentin
http://www.be-known-online.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Filesystem layout with sperated /boot partition
Hello FreeBSD Fans, I wanted to create a new system and was thinking about the following layout. Size | Mountpoint | Device name | File system 100M /boot /dev/ad2s1a UFS2+S 1024MB --- /dev/ad2s1b SWAP 15GB / /dev/ad2s1c UFS2 I want to put /boot on its own partition, but somehow I dont have a lot of luck. I can install the OS, but when I reboot the bootloader will not boot. No /boot/loader ... Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel ... 1) I wouldnt mind on which partition /boot or / sits or what its named, but I would like to separate /boot on a different partition and it seems like it wouldnt boot when I do this. Is this just a matter of updating the bootloader ? Wouldnt the installer do that automatically ? 2) The part which I dont get is why is / always ad2s1a - even when I create /boot first ? (/boot will become f.e. ad2s1d) and SWAP will become ad2s1b. So what I end up with is something like Size | Mountpoint | Device name | File system 15GB / /dev/ad2s1a UFS2 1024MB --- /dev/ad2s1b SWAP 100M /boot /dev/ad2s1d UFS2+S Any replies much appreciated. Best regards Nils Valentin http://www.be-known-online.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
On 4/2/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello FreeBSD Fans, I wanted to create a new system and was thinking about the following layout. Size | Mountpoint | Device name | File system 100M /boot /dev/ad2s1a UFS2+S 1024MB --- /dev/ad2s1b SWAP 15GB / /dev/ad2s1c UFS2 I want to put /boot on its own partition, but somehow I dont have a lot of luck. I can install the OS, but when I reboot the bootloader will not boot. No /boot/loader ... Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel Because it instinctively (without the MBR boot manager) looks for /boot/kernel/kernel in the first partition of the first active slice on the first drive. ... 1) I wouldnt mind on which partition /boot or / sits or what its named, but I would like to separate /boot on a different partition Why you would want to do this is a bit unclear. 2) The part which I dont get is why is / always ad2s1a - even when I create /boot first ? (/boot will become f.e. ad2s1d) and SWAP will become ad2s1b. So what I end up with is something like Size | Mountpoint | Device name | File system 15GB / /dev/ad2s1a UFS2 1024MB --- /dev/ad2s1b SWAP 100M /boot /dev/ad2s1d UFS2+S That's a sysinstall thing. If you were to muck about and install your base system without sysinstall you could place it wherever. And it probably still won't boot. Part of the reason linux wants to make /boot its own partition is their ugly habit of not seperating anything else from root. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
Hello, snip Because it instinctively (without the MBR boot manager) looks for /boot/kernel/kernel in the first partition of the first active slice on the first drive. But I have choosen to install the Boot loader. ;-o ... 1) I wouldnt mind on which partition /boot or / sits or what its named, but I would like to separate /boot on a different partition Why you would want to do this is a bit unclear. I would like to use different mount option later on each partitions - just for the fun of it ;-). That wouldnt be possible if all is on one partititon. Would that make any sense ? snip That's a sysinstall thing. If you were to muck about and install your base system without sysinstall you could place it wherever. And it probably still won't boot. So whats the solution to this ??? Not installing FreeBSD ? Develop my own Boot loader ? Part of the reason linux wants to make /boot its own partition is their ugly habit of not seperating anything else from root. I decide not to comment on this anymore. I didnt came here to start a flame war of the OS's. Let's not go down that road (most come back uglier than before), lets focus on the technical issue instead. Best regards Nils Valentin http://www.be-known-online.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem layout with sperated /boot partition
On Mon, Apr 03, 2006 at 02:33:42AM +, [EMAIL PROTECTED] wrote: Hello FreeBSD Fans, I wanted to create a new system and was thinking about the following layout. Size | Mountpoint | Device name | File system 100M /boot /dev/ad2s1a UFS2+S 1024MB --- /dev/ad2s1b SWAP 15GB / /dev/ad2s1c UFS2 I want to put /boot on its own partition, but somehow I dont have a lot of luck. I can install the OS, but when I reboot the bootloader will not boot. Don't do that. You can not have /boot as a separate partition. It just contains the kernel and the loader. The other things that are needed for booting (like /bin/sh or /sbin/mount) reside elsewhere. (Having /boot as a separate partition is apparently some Linux-specific convention.) What is normally done under FreeBSD when you want a small boot partition is to create /usr and /var as separate partitions which will let you create a small (100M) '/' partition. (You will probably also want either a separate /home partition for user home directories, or let them reside under /usr/home. (I think the latter is the default, but I am not 100% sure.) No /boot/loader ... Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel ... 1) I wouldnt mind on which partition /boot or / sits or what its named, but I would like to separate /boot on a different partition and it seems like it wouldnt boot when I do this. Is this just a matter of updating the bootloader ? Wouldnt the installer do that automatically ? See above. You can't do that. 2) The part which I dont get is why is / always ad2s1a - even when I create /boot first ? (/boot will become f.e. ad2s1d) and SWAP will become ad2s1b. You need to boot from / and it should be partition 'a' on the slice. It is probably possible to change this, but it would be much more pain and trouble than it is worth. So what I end up with is something like Size | Mountpoint | Device name | File system 15GB / /dev/ad2s1a UFS2 1024MB --- /dev/ad2s1b SWAP 100M /boot /dev/ad2s1d UFS2+S Any replies much appreciated. A good place to start reading is the online handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ especially the chapter on installing FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html The FAQ at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ might also prove helpful. Best regards Nils Valentin http://www.be-known-online.com -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
