Re: Multi-boot Linux + FreeBSD
Thank you Damien, Lucas and Juergen :) btw. the off topic on multimedia is my bad, I wasn't subscribed to FreeBSD questions. While reading howtos I missed http://www.freebsd.org/doc/faq/disks.html#grub-loader I'll add title FreeBSD 9.0 root (hd0,a) kernel /boot/loader to my menu.lst and then install FreeBSD. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Multi-boot Linux + FreeBSD
While no expert, I would advise against running the kernel directly.
The loader allows you to boot in single user which may come handy at times.
On 24 Nov 2012, at 18:08, "Lucas B. Cohen" wrote:
> Hi Ralf,
>
> On 2012.11.24 17:06, Ralf Mardorf wrote:
>> Perhaps later today I'll install 9.0 amd64. If possible I'll keep my
>> Linux GRUB legacy. Can I use my menu.lst [1] and add a chainloader or
>> something similar to boot FreeBSD from /dev/sda1?
> I don't know if GRUB v1 allows that, on a multiboot system I use GRUB 2
> to either load FreeBSD's loader(8) :
>
> menuentry "FreeBSD (Loader)" {
>insmod part_bsd
>set root='hd0,msdos2,bsd1'
>echo "Loading FreeBSD loader"
>kfreebsd /boot/loader
>echo "Starting FreeBSD loader"
> }
>
> or to run its kernel directly, after having passed it optional device hints:
>
> menuentry "FreeBSD (Direct Boot)" {
>insmod ufs2
>set root='hd0,msdos2,bsd1'
>echo "Loading FreeBSD kernel"
>kfreebsd /boot/kernel/kernel
>echo "Loading FreeBSD environment"
>kfreebsd_loadenv /boot/device.hints
>set kfreebsd.vfs.root.mountfrom=ufs:/dev/ada0s2
>echo "Booting FreeBSD"
> }
>
> I'm not saying it's impossible, but I'm unable to chainload to the
> loader code on my system with this:
> menuentry "FreeBSD (Chainload)" {
>insmod chain
>set root='hd0,msdos2'
>chainloader +1
> }
>
>
>
>> FWIW I made backups of my HDD's MBRs.
>> I wonder if the installer will overwrite the MBR?
> Always a good thing to have backups. From what I've experienced and
> read, 9.0-RELEASE's installer is not always predictable in that regard,
> it's probably safer to assume it'll won't do what you want, and just
> restore your MBR after the installation, to go back to using GRUB for
> dual-booting.
>
> Here's the pitfall, though: the MBR also holds the partition table. So
> make a fresh backup after you've created/reorganized the primary
> partitions (slices) on your disk using a tool you're familiar with.
> (Logical partitions and BSD partitions are stored differently, so they
> will survive an MBR restore, provided it doesn't modify the primary
> partition they're contained in.)
>
>> I also would like to know, if there's a way to recover the partition
>> table, including a primary FreeBSD partition/slice, if this ever should
>> get broken and there should be no backup of the partition table be
>> available.
> The partition table is held alongside the MBR, in the first logical
> sector of your disk. Restoring one will restore the other.
> For extra safety, you can save the output of partitioning tools like
> fdisk or GNU parted expressed in sectors.
>
> Hope this helps,
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Multi-boot Linux + FreeBSD
Hi Ralf,
On 2012.11.24 17:06, Ralf Mardorf wrote:
> Perhaps later today I'll install 9.0 amd64. If possible I'll keep my
> Linux GRUB legacy. Can I use my menu.lst [1] and add a chainloader or
> something similar to boot FreeBSD from /dev/sda1?
I don't know if GRUB v1 allows that, on a multiboot system I use GRUB 2
to either load FreeBSD's loader(8) :
menuentry "FreeBSD (Loader)" {
insmod part_bsd
set root='hd0,msdos2,bsd1'
echo "Loading FreeBSD loader"
kfreebsd /boot/loader
echo "Starting FreeBSD loader"
}
or to run its kernel directly, after having passed it optional device hints:
menuentry "FreeBSD (Direct Boot)" {
insmod ufs2
set root='hd0,msdos2,bsd1'
echo "Loading FreeBSD kernel"
kfreebsd /boot/kernel/kernel
echo "Loading FreeBSD environment"
kfreebsd_loadenv /boot/device.hints
set kfreebsd.vfs.root.mountfrom=ufs:/dev/ada0s2
echo "Booting FreeBSD"
}
I'm not saying it's impossible, but I'm unable to chainload to the
loader code on my system with this:
menuentry "FreeBSD (Chainload)" {
insmod chain
set root='hd0,msdos2'
chainloader +1
}
> FWIW I made backups of my HDD's MBRs.
> I wonder if the installer will overwrite the MBR?
Always a good thing to have backups. From what I've experienced and
read, 9.0-RELEASE's installer is not always predictable in that regard,
it's probably safer to assume it'll won't do what you want, and just
restore your MBR after the installation, to go back to using GRUB for
dual-booting.
Here's the pitfall, though: the MBR also holds the partition table. So
make a fresh backup after you've created/reorganized the primary
partitions (slices) on your disk using a tool you're familiar with.
(Logical partitions and BSD partitions are stored differently, so they
will survive an MBR restore, provided it doesn't modify the primary
partition they're contained in.)
> I also would like to know, if there's a way to recover the partition
> table, including a primary FreeBSD partition/slice, if this ever should
> get broken and there should be no backup of the partition table be
> available.
The partition table is held alongside the MBR, in the first logical
sector of your disk. Restoring one will restore the other.
For extra safety, you can save the output of partitioning tools like
fdisk or GNU parted expressed in sectors.
Hope this helps,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Multi-boot Linux + FreeBSD
Hi, as a long time Linux user I'll test FreeBSD, because I've got issues with my sound card on Linux. I'm already subscribed to FreeBSD multimedia. Perhaps later today I'll install 9.0 amd64. If possible I'll keep my Linux GRUB legacy. Can I use my menu.lst [1] and add a chainloader or something similar to boot FreeBSD from /dev/sda1? FWIW I made backups of my HDD's MBRs. I wonder if the installer will overwrite the MBR? I also would like to know, if there's a way to recover the partition table, including a primary FreeBSD partition/slice, if this ever should get broken and there should be no backup of the partition table be available. TIA, Ralf [1] $ cat /boot/grub/menu.lst timeout 8 default 0 color light-blue/black light-cyan/blue title Ubuntu Quantal,kernel 3.6.5-rt14 root (hd1,8) kernel /boot/vmlinuz-3.6.5-rt14 root=/dev/sdb9 ro quiet initrd /boot/initrd.img-3.6.5-rt14 title Ubuntu Quantal,kernel 3.5.0-18-lowlatency threadirqs root (hd1,8) kernel /boot/vmlinuz-3.5.0-18-lowlatency root=/dev/sdb9 ro quiet threadirqs initrd /boot/initrd.img-3.5.0-18-lowlatency title Ubuntu Quantal,kernel 3.5.0-18-lowlatency (recovery mode) root (hd1,8) kernel /boot/vmlinuz-3.5.0-18-lowlatency root=/dev/sdb9 ro single initrd /boot/initrd.img-3.5.0-18-lowlatency title Ubuntu Studio Quantal, Kernel 3.6.5-rt14 root=(hd1,12) kernel /boot/vmlinuz-3.6.5-rt14 root=/dev/sdb13 ro quiet initrd /boot/initrd.img-3.6.5-rt14 title Ubuntu Studio Quantal, Kernel 3.5.0-18-lowlatency threadirqs root=(hd1,12) kernel /boot/vmlinuz-3.5.0-18-lowlatency root=/dev/sdb13 ro quiet threadirqs initrd /boot/initrd.img-3.5.0-18-lowlatency title Ubuntu Studio Precise, Kernel 3.0.30 threadirqs root=(hd1,0) kernel /boot/vmlinuz-3.0.30 root=UUID=338316fb-364e-4a43-8deb-738127f878ce ro quiet threadirqs initrd /boot/initrd.img-3.0.30 title Ubuntu Studio Precise, Kernel 3.2.0-23-lowlatency threadirqs root=(hd1,0) kernel /boot/vmlinuz-3.2.0-23-lowlatency root=UUID=338316fb-364e-4a43-8deb-738127f878ce ro quiet threadirqs initrd /boot/initrd.img-3.2.0-23-lowlatency title AVlinux 5.0.3, Kernel 3.0.23-rt40 root=(hd1,10) kernel /boot/vmlinuz-3.0.23-rt40 root=/dev/sdb11 ro quiet initrd /boot/initrd.img-3.0.23-rt40 title AVlinux 5.0.3, Kernel 3.0.23-avl-7-pae threadirqs root=(hd1,10) kernel /boot/vmlinuz-3.0.23-avl-7-pae root=/dev/sdb11 ro threadirqs quiet initrd /boot/initrd.img-3.0.23-avl-7-pae title Edubuntu 10.10,Kernel 2.6.33.9-rt31 root=(hd1,7) kernel /boot/vmlinuz-2.6.33.9-rt31 root=UUID=ded93dfb-37ae-48cf-a3a3-b613aa5704fd ro initrd /boot/initrd.img-2.6.33.9-rt31 title Ubuntu Studio Oz, Kernel 3.0.0-17-generic root=(hd1,5) kernel /boot/vmlinuz-3.0.0-17-generic root=UUID=0241b2ac-a0ab-44de-8d73-0ed084e152e6 initrd /boot/initrd.img-3.0.0-17-generic title Ubuntu Studio Oz, Kernel 3.0.0-20-generic root=(hd1,5) kernel /boot/vmlinuz-3.0.0-20-generic root=UUID=0241b2ac-a0ab-44de-8d73-0ed084e152e6 initrd /boot/initrd.img-3.0.0-20-generic title Arch Linux Rt root (hd0,8) kernel /boot/vmlinuz-linux-rt root=/dev/sda9 ro initrd /boot/initramfs-linux-rt.img title Arch Linux root (hd0,8) kernel /boot/vmlinuz-linux root=/dev/sda9 ro initrd /boot/initramfs-linux.img title Arch Linux Fallback root (hd0,8) kernel /boot/vmlinuz-linux root=/dev/sda9 ro initrd /boot/initramfs-linux-fallback.img title openSUSE 11.2, Kernel 2.6.31.6-rt19 root (hd0,6) kernel /boot/vmlinuz-2.6.31.6-rt19 root=/dev/sda7 initrd /boot/initrd-2.6.31.6-rt19 title Ubuntu Quantal memtest86+ root (hd1,8) kernel /boot/memtest86+.bin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 8.2 Add second hard drive multi-boot
On Thu, 21 Jun 2012 09:59:19 -0700 (PDT), leeoliveshackelf...@surewest.net wrote: > Although the FreeBSD operating system seems to see the second > hard drive, it does not mount it upon startup. FreeBSD won't mount anything until explicitely told so. Check the output of dmesg (e. g. "dmesg | grep ^ad" or "dmesg | grep ^da") for the drive designation and issue the command yourself. If everything works, you can add an entry to /etc/fstab to make it mount on startup, e. g. # device target type options d p # -- - - - /dev/ad1s1 /xp/system ntfs ro,noauto 0 0 /dev/ad1s2 /xp/data ntfs ro,noauto 0 0 It might be worth applying other options like -M (mask) to have the missing attributes and "misinterpretation as executables" of NTFS file systems corrects. See the manual for details. > It does not appear in the fstab file. This file is not generated automatically. It's an entirely "user serviceable" part of the OS. > I attempted to mount it manually using the mount command, without > success, just to see if any of the data files could be read. Can you show the mount command? I think it will be something like # mount_ntfs -o ro /dev/ad1s1 /mnt If you need write access, ntfs3g / FUSE would be a good tool. Also see the port "ntfsprogs" which contains useful tools for dealing with NTFS. > I ran fsidk -B on the zeroeth sector of the second hard drive, but > that did not seem to help. You need to apply boot0cfg to install the initial boot blocks. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 8.2 Add second hard drive multi-boot
On Thu, Jun 21, 2012 at 09:59:19AM -0700, leeoliveshackelf...@surewest.net wrote: You need to put the FreeBSD boot manager on both disks. Use bootcfg. jerry > Good morning, FreeBSD enthusiasts. On my Hewlett-Packard xw4400 workstation, > I had one hard drive. I partitioned it with two slices, the first one for > FreeBSD 8.2 with its native file system, and the second one for a future > re-installation of Windows XP, to be formatted with NTFS file system. > FreeBSD 8.2 was then installed. The Windows XP re-installation has not yet > taken place. Recently, I installed a second hard drive on the machine that > was already formatted with two slices, both NTFS. Already installed on the > first of these slices is the Windows XP operating system with a special > application program. Already installed on the second slice is data. It is > my understanding that the FreeBSD loader is supposed to be able to load any > operating system. Upon power-up, the FreeBSD loader presents the following > screen: > > F1 Win > F2 FreeBSD > F5 Drive 1 > F6 PXE > > If I depress F1, I receive the response "BOOTMGR is missing. Press > Ctrl+Alt+Del to restart." If I depress F2, FreeBSD loads normally. If I > depress F5, I receive the response "Missing operatin system." How can I get > the FreeBSD loader to load the Windows XP operating system from the second > hard drive? The G.P.T. disklabel is not used by either of these operating > systems, so I do not believe that that is the problem. Although the FreeBSD > operating system seems to see the second hard drive, it does not mount it > upon startup. It does not appear in the fstab file. I attempted to mount it > manually using the mount command, without success, just to see if any of the > data files could be read. I ran fsidk -B on the zeroeth sector of the second > hard drive, but that did not seem to help. I know that this type of issue > comes up repeatedly in the mailing lists, some of which I have read, but I am > flummoxed. Any and all suggestions would be appreciated. Your truly, Lee > Shackelfo > r! > d > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD 8.2 Add second hard drive multi-boot
Good morning, FreeBSD enthusiasts. On my Hewlett-Packard xw4400 workstation, I had one hard drive. I partitioned it with two slices, the first one for FreeBSD 8.2 with its native file system, and the second one for a future re-installation of Windows XP, to be formatted with NTFS file system. FreeBSD 8.2 was then installed. The Windows XP re-installation has not yet taken place. Recently, I installed a second hard drive on the machine that was already formatted with two slices, both NTFS. Already installed on the first of these slices is the Windows XP operating system with a special application program. Already installed on the second slice is data. It is my understanding that the FreeBSD loader is supposed to be able to load any operating system. Upon power-up, the FreeBSD loader presents the following screen: F1 Win F2 FreeBSD F5 Drive 1 F6 PXE If I depress F1, I receive the response "BOOTMGR is missing. Press Ctrl+Alt+Del to restart." If I depress F2, FreeBSD loads normally. If I depress F5, I receive the response "Missing operatin system." How can I get the FreeBSD loader to load the Windows XP operating system from the second hard drive? The G.P.T. disklabel is not used by either of these operating systems, so I do not believe that that is the problem. Although the FreeBSD operating system seems to see the second hard drive, it does not mount it upon startup. It does not appear in the fstab file. I attempted to mount it manually using the mount command, without success, just to see if any of the data files could be read. I ran fsidk -B on the zeroeth sector of the second hard drive, but that did not seem to help. I know that this type of issue comes up repeatedly in the mailing lists, some of which I have read, but I am flummoxed. Any and all suggestions would be appreciated. Your truly, Lee Shackelfo r! d ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: multi-boot (fixed)
On Wed, 19 Oct 2011, Lowell Gilbert wrote: d...@safeport.com writes: On Wed, 19 Oct 2011, Lowell Gilbert wrote: d...@safeport.com writes: I have a system with two physical disks with a version of FreeBSD installed on each disk. With various 7.x systems I had: F1 disk1 on slices ads5x F5 disk2 on slices ads6x I installed 8.2 on disk2, incorrectly saying leave the mbr alone. So when I boot from the second disk I get F6 PXE Boot: F1 I can then hit F1 or wait and all goes okay. I tried using sysinstall to rewrite the FBSD boot manager but that not effect any change. Must I rewrite the mbr on disk 1 also? That's what I would expect to have to do... Pre 8.2 the behavior the selected system just boot without the extra message. I had a 7.0 and a 7.4 system installed. I replaced the 7.4 system with 8,2 With the boot setup I understand the FreeBSD boot manager would be on sector 0 track 0 of disk 1. The boot record for disk 1 is in the first logical sector for the drive. The boot record for disk 2 should be similarly placed on disk 2. What I think is missing is putting the boot manager on disk 2. If that is the case, is there a way to do that without reinstalling? boot0cfg(8) from the system that does boot. Or boot in "rescue" mode from a CD (or other removable media) and use sysinstall. thanks This is a classic cast (I think) of RTFM. Thanks for hanging in with me. The correct answer is install the standard boot record on disk 2. I think I can interpert the handbook that way. I did this with sysinstall as my second attempt at boot0cfg seriously broke the system on disk 2. boot0cfg is left to me as homework. This is a case where I may be able to get from the code what I could not from the man page. I do not know if part of the different is the BIOS has raid0 build in which almost works. I just turned this off giving me two test systems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: multi-boot
On Wed, 19 Oct 2011, Lowell Gilbert wrote: d...@safeport.com writes: On Wed, 19 Oct 2011, Lowell Gilbert wrote: d...@safeport.com writes: I have a system with two physical disks with a version of FreeBSD installed on each disk. With various 7.x systems I had: F1 disk1 on slices ads5x F5 disk2 on slices ads6x I installed 8.2 on disk2, incorrectly saying leave the mbr alone. So when I boot from the second disk I get F6 PXE Boot: F1 I can then hit F1 or wait and all goes okay. I tried using sysinstall to rewrite the FBSD boot manager but that not effect any change. Must I rewrite the mbr on disk 1 also? That's what I would expect to have to do... Pre 8.2 the behavior the selected system just boot without the extra message. I had a 7.0 and a 7.4 system installed. I replaced the 7.4 system with 8,2 With the boot setup I understand the FreeBSD boot manager would be on sector 0 track 0 of disk 1. The boot record for disk 1 is in the first logical sector for the drive. The boot record for disk 2 should be similarly placed on disk 2. What I think is missing is putting the boot manager on disk 2. If that is the case, is there a way to do that without reinstalling? boot0cfg(8) from the system that does boot. Or boot in "rescue" mode from a CD (or other removable media) and use sysinstall. thanks _ Douglas Denault http://www.safeport.com d...@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: multi-boot
d...@safeport.com writes: > On Wed, 19 Oct 2011, Lowell Gilbert wrote: > >> d...@safeport.com writes: >> >>> I have a system with two physical disks with a version of FreeBSD >>> installed on each disk. With various 7.x systems I had: >>> >>> F1 disk1 on slices ads5x >>> F5 disk2 on slices ads6x >>> >>> I installed 8.2 on disk2, incorrectly saying leave the mbr alone. So >>> when I boot from the second disk I get >>> >>> F6 PXE >>> Boot: F1 >>> >>> I can then hit F1 or wait and all goes okay. I tried using sysinstall >>> to rewrite the FBSD boot manager but that not effect any change. Must >>> I rewrite the mbr on disk 1 also? >> >> That's what I would expect to have to do... > > Pre 8.2 the behavior the selected system just boot without the extra > message. I had a 7.0 and a 7.4 system installed. I replaced the 7.4 > system with 8,2 With the boot setup I understand the FreeBSD boot > manager would be on sector 0 track 0 of disk 1. The boot record for > disk 1 is in the first logical sector for the drive. The boot record > for disk 2 should be similarly placed on disk 2. > > What I think is missing is putting the boot manager on disk 2. If that > is the case, is there a way to do that without reinstalling? boot0cfg(8) from the system that does boot. Or boot in "rescue" mode from a CD (or other removable media) and use sysinstall. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: multi-boot
d...@safeport.com writes: > I have a system with two physical disks with a version of FreeBSD > installed on each disk. With various 7.x systems I had: > > F1 disk1 on slices ads5x > F5 disk2 on slices ads6x > > I installed 8.2 on disk2, incorrectly saying leave the mbr alone. So > when I boot from the second disk I get > > F6 PXE > Boot: F1 > > I can then hit F1 or wait and all goes okay. I tried using sysinstall > to rewrite the FBSD boot manager but that not effect any change. Must > I rewrite the mbr on disk 1 also? That's what I would expect to have to do... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
multi-boot
I have a system with two physical disks with a version of FreeBSD installed on each disk. With various 7.x systems I had: F1 disk1 on slices ads5x F5 disk2 on slices ads6x I installed 8.2 on disk2, incorrectly saying leave the mbr alone. So when I boot from the second disk I get F6 PXE Boot: F1 I can then hit F1 or wait and all goes okay. I tried using sysinstall to rewrite the FBSD boot manager but that not effect any change. Must I rewrite the mbr on disk 1 also? _ Douglas Denault http://www.safeport.com d...@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Question. Multi Boot
On Sun, 2010-04-18 at 11:10 -0500, Jorge Biquez wrote: > Hello all. > I hope this question does not sound so stupid. I have read archives > and do gogled searches but would like , if possible, to hear comments > based on experience. > > I have a machine, pentium D 2.4mhz 2gb RAM, 160DD HD XP Pro. As I > mentuioned in other post I installed FreeBSD 7.3 under a virtual > machine using vmware. It works fine but seems it is too much for the > machine since when I am running it the machine is very slow. I have > that FB installation running without graphical interface since that's > why I need then. > > Now I would like to have a graphical interface running to learn to > use eclipse and continue with my PHP/Mysql development learning. I > know that if I continue under VMware the windows machine will be even > more slow so I decided that I would have this machine running with a > multi boot schema and choose when to boot under FreeBSd, Windows and > later with Linux (looking for a job and in some companies asked me to > have the basics of any distribution). The most important is that I > need to be able to continue having that actual windows partition > without loosing anything or changing anything. > > What do you think, based on experince, is the safest way to accomplish this? Not quite the exact answer you may be looking for, but why don't you flip the tables a bit and run Window$ as the virtual machine on the FreeBSD as a host? >From my experience it actually works much faster, and Window$ doesn't see any penalties at all. I haven't done it in quite some time, but that did work a treat at the time- no reason it should have changed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Question. Multi Boot
Actually you can find now some cheap HDDs so the safest way is to install BSD/Linux on a second one, but if you can't buy another HDD then backup all the important date and install BSD with bsd loader on your HDD, after making some free, unformatted space on it. From: "Kruppa, Peter Ulrich" To: Jorge Biquez Cc: freebsd-questions@freebsd.org Sent: Sun, April 18, 2010 6:50:04 PM Subject: Re: Question. Multi Boot Am 18.04.2010 18:10, schrieb Jorge Biquez: > Hello all. > I hope this question does not sound so stupid. I have read archives and do > gogled searches but would like , if possible, to hear comments based on > experience. > > I have a machine, pentium D 2.4mhz 2gb RAM, 160DD HD XP Pro. As I mentuioned > in other post I installed FreeBSD 7.3 under a virtual machine using vmware. > It works fine but seems it is too much for the machine since when I am > running it the machine is very slow. I have that FB installation running > without graphical interface since that's why I need then. > > Now I would like to have a graphical interface running to learn to use > eclipse and continue with my PHP/Mysql development learning. I know that if I > continue under VMware the windows machine will be even more slow so I decided > that I would have this machine running with a multi boot schema and choose > when to boot under FreeBSd, Windows and later with Linux (looking for a job > and in some companies asked me to have the basics of any distribution). The > most important is that I need to be able to continue having that actual > windows partition without loosing anything or changing anything. > > What do you think, based on experince, is the safest way to accomplish this? Since Windows isn't very cooperative with other operating systems, leave it where it is, buy a second hard disk and install FreeBSD (and Linux) on it. The FreeBSD bootmanager will be able to boot Windows but Windows will not boot any FreeBSD or Linux. Good Luck Uli. > Thanks in advance > > Jorge Biquez > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Question. Multi Boot
At 05:04 p.m. 18/04/2010, you wrote: On 4/18/10 12:50 PM, Kruppa, Peter Ulrich wrote: Since Windows isn't very cooperative with other operating systems, leave it where it is, buy a second hard disk and install FreeBSD (and Linux) on it. The FreeBSD bootmanager will be able to boot Windows but Windows will not boot any FreeBSD or Linux. I would agree that is the safest way to proceed, although the repartitioning of the hard disk as outlined by somebody else would certainly work. However, even here I would urge you to have a complete backup that you have verified is usable before you start. Makes that sinking feeling in your stomach when you realize you've just partitioned the wrong drive much less ugly. :-) --Jon Radel ___ Hello all. Thanks for your comments. The disk I have, actually has around 90GB of free space (more I guess). I will do repartition with Norton and will leave 2 partitions of 40GB for each extra OS. I then will install FB on the first one to have the boot manager there and later Linux on the other partition. I guess that could work. I hope so. Thanks for your time. JB ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Question. Multi Boot
On 4/18/10 12:50 PM, Kruppa, Peter Ulrich wrote: Since Windows isn't very cooperative with other operating systems, leave it where it is, buy a second hard disk and install FreeBSD (and Linux) on it. The FreeBSD bootmanager will be able to boot Windows but Windows will not boot any FreeBSD or Linux. I would agree that is the safest way to proceed, although the repartitioning of the hard disk as outlined by somebody else would certainly work. However, even here I would urge you to have a complete backup that you have verified is usable before you start. Makes that sinking feeling in your stomach when you realize you've just partitioned the wrong drive much less ugly. :-) --Jon Radel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Question. Multi Boot
On Sun, 18 Apr 2010, Jorge Biquez wrote: Hello all. I hope this question does not sound so stupid. I have read archives and do gogled searches but would like , if possible, to hear comments based on experience. I have a machine, pentium D 2.4mhz 2gb RAM, 160DD HD XP Pro. As I mentuioned in other post I installed FreeBSD 7.3 under a virtual machine using vmware. It works fine but seems it is too much for the machine since when I am running it the machine is very slow. I have that FB installation running without graphical interface since that's why I need then. I've tried VMWare player with FreeBSD 7, albeit on a faster machine. Text mode was fine, never tried xorg. A P4 should be adequate, but there may be other things going on in the background like Windows antivirus scanning. VirtualBox seems to work very well on Windows, and it's certainly worth a try before reorganizing your disk for multibooting. Now I would like to have a graphical interface running to learn to use eclipse and continue with my PHP/Mysql development learning. I know that if I continue under VMware the windows machine will be even more slow so I decided that I would have this machine running with a multi boot schema and choose when to boot under FreeBSd, Windows and later with Linux (looking for a job and in some companies asked me to have the basics of any distribution). The most important is that I need to be able to continue having that actual windows partition without loosing anything or changing anything. What do you think, based on experince, is the safest way to accomplish this? Safest would be still be the VM; little chance of damaging the host disk data when the VM has no direct access to it. For multiboot: back up entire Windows hard drive including a separate dd copy of the MBR, resize Windows partition to make room using partition software of your choice, test to make sure Windows still works. Back up again. Install FreeBSD, creating new partition/slice, leaving room for a Linux partition, and installing the FreeBSD boot manager. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Question. Multi Boot
Am 18.04.2010 18:10, schrieb Jorge Biquez: Hello all. I hope this question does not sound so stupid. I have read archives and do gogled searches but would like , if possible, to hear comments based on experience. I have a machine, pentium D 2.4mhz 2gb RAM, 160DD HD XP Pro. As I mentuioned in other post I installed FreeBSD 7.3 under a virtual machine using vmware. It works fine but seems it is too much for the machine since when I am running it the machine is very slow. I have that FB installation running without graphical interface since that's why I need then. Now I would like to have a graphical interface running to learn to use eclipse and continue with my PHP/Mysql development learning. I know that if I continue under VMware the windows machine will be even more slow so I decided that I would have this machine running with a multi boot schema and choose when to boot under FreeBSd, Windows and later with Linux (looking for a job and in some companies asked me to have the basics of any distribution). The most important is that I need to be able to continue having that actual windows partition without loosing anything or changing anything. What do you think, based on experince, is the safest way to accomplish this? Since Windows isn't very cooperative with other operating systems, leave it where it is, buy a second hard disk and install FreeBSD (and Linux) on it. The FreeBSD bootmanager will be able to boot Windows but Windows will not boot any FreeBSD or Linux. Good Luck Uli. Thanks in advance Jorge Biquez ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Question. Multi Boot
Hello all. I hope this question does not sound so stupid. I have read archives and do gogled searches but would like , if possible, to hear comments based on experience. I have a machine, pentium D 2.4mhz 2gb RAM, 160DD HD XP Pro. As I mentuioned in other post I installed FreeBSD 7.3 under a virtual machine using vmware. It works fine but seems it is too much for the machine since when I am running it the machine is very slow. I have that FB installation running without graphical interface since that's why I need then. Now I would like to have a graphical interface running to learn to use eclipse and continue with my PHP/Mysql development learning. I know that if I continue under VMware the windows machine will be even more slow so I decided that I would have this machine running with a multi boot schema and choose when to boot under FreeBSd, Windows and later with Linux (looking for a job and in some companies asked me to have the basics of any distribution). The most important is that I need to be able to continue having that actual windows partition without loosing anything or changing anything. What do you think, based on experince, is the safest way to accomplish this? Thanks in advance Jorge Biquez ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Question. Multi Boot
Hello all. I hope this question does not sound so stupid. I have read archives and do gogled searches but would like , if possible, to hear comments based on experience. I have a machine, pentium D 2.4mhz 2gb RAM, 160DD HD XP Pro. As I mentuioned in other post I installed FreeBSD 7.3 under a virtual machine using vmware. It works fine but seems it is too much for the machine since when I am running it the machine is very slow. I have that FB installation running without graphical interface since that's why I need then. Now I would like to have a graphical interface running to learn to use eclipse and continue with my PHP/Mysql development learning. I know that if I continue under VMware the windows machine will be even more slow so I decided that I would have this machine running with a multi boot schema and choose when to boot under FreeBSd, Windows and later with Linux (looking for a job and in some companies asked me to have the basics of any distribution). The most important is that I need to be able to continue having that actual windows partition without loosing anything or changing anything. What do you think, based on experince, is the safest way to accomplish this? Thanks in advance Jorge Biquez ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: 7.2 Sysinstall choices -- existing multi-boot (based on Win7 RC's boot mgr) system
<200910022231.28732.m.odonn...@shaw.ca> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 >> Currently=2C I have Win/XP in slice 1=2C no slice 2=2C Win 7 RC in slice= 3 and >> Acronis' hidden part in slice 4. I have unallocated space after slice 1 >> (about 45gb) I wanted to use for FreeBSD. >> >> I told sysinstall to create a slice (in the unallocated space)=2C then c= reate >> FreeBSD partitions in it for /=2C paging=2C /usr=2C /var=2C /tmp & /home= . I'm not >> sure what I'm supposed to tell it about boot managers though? Right now >> the MBR points to Acronis' recovery slice=2C which boots to Win 7's boot >> manager=2C it defaults to Win/XP. When I said do nothing sysinstall mark= ed >> the new slice bootable=2C and FreeBSD does boot to a text menu with Beas= tie >> on it. But=2C that doesn't give access to the OS's in slice 1 and 3? > > The default Windows MBR will simply just boot the active slice. When you > created your FreeBSD slice it was automatically marked active. > >> if I tell it to use the default boot manager=2C (booteasy?)=2C will it o= ffer at >> least access to what's currently in the master boot record & slice 2 >> (FreeBSD)? Or do I need a way to tell Win7's boot manager about FreeBSD = in >> slice 2? >> > > boot0 (aka BootEasy) will ask you what slice to boot from. If you've alre= ady > installed FreeBSD you can replace your current MBR with: > > boot0cfg -B ad0 > > Just make sure to replace ad0 with your actual hdd device name. > =20 Does boot0 use / save the existing MBR (there already is code in there to l= ook for an f11 key press then boot to Acronis's standalone restorer (It=20 looks like a tailored Linux :))=2C if not boot to 'active slice')? =20 Does FreeBSD's slice / partition boot block have enough info to boot FreeBS= D =20 if another boot manager selects it? Thinking I could possibly add FreeBSD's slice to Win 7's list of target OS's? =20 =20 =20 slice 1 is Win XP slice 2 is FreeBSD (/=2C page=2C /usr=2C /var=2C /tmp & /home BSD partition= s) slice 3 is Win 7 RC slice 4 is Acronis's hidden recovery setup =20 =20 =20 It appears that the Acronis' MBR looks for an f11 key press=20 (if found boot Acronis=2C if not boot the 'active partition').=20 Active partition was Win 7's boot manager which had Win 7 and=20 Win XP as targets with Win XP as it's default). =20 Acronis's standalone boot menu knows itself and Win 7's boot manager. I'm guessing whatever wrote the MBR saved the old boot code=2C so it could use it as an alternate target=2C (if one hit the the trigger key by mistake). =20 =20 = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.2 Sysinstall choices -- existing multi-boot (based on Win7 RC's boot mgr) system
> Currently, I have Win/XP in slice 1, no slice 2, Win 7 RC in slice 3 and > Acronis' hidden part in slice 4. I have unallocated space after slice 1 > (about 45gb) I wanted to use for FreeBSD. > > I told sysinstall to create a slice (in the unallocated space), then create > FreeBSD partitions in it for /, paging, /usr, /var, /tmp & /home. I'm not > sure what I'm supposed to tell it about boot managers though? Right now > the MBR points to Acronis' recovery slice, which boots to Win 7's boot > manager, it defaults to Win/XP. When I said do nothing sysinstall marked > the new slice bootable, and FreeBSD does boot to a text menu with Beastie > on it. But, that doesn't give access to the OS's in slice 1 and 3? The default Windows MBR will simply just boot the active slice. When you created your FreeBSD slice it was automatically marked active. > if I tell it to use the default boot manager, (booteasy?), will it offer at > least access to what's currently in the master boot record & slice 2 > (FreeBSD)? Or do I need a way to tell Win7's boot manager about FreeBSD in > slice 2? > boot0 (aka BootEasy) will ask you what slice to boot from. If you've already installed FreeBSD you can replace your current MBR with: boot0cfg -B ad0 Just make sure to replace ad0 with your actual hdd device name. > > Thanks > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
7.2 Sysinstall choices -- existing multi-boot (based on Win7 RC's boot mgr) system
Currently, I have Win/XP in slice 1, no slice 2, Win 7 RC in slice 3 and Acronis' hidden part in slice 4. I have unallocated space after slice 1 (about 45gb) I wanted to use for FreeBSD. I told sysinstall to create a slice (in the unallocated space), then create FreeBSD partitions in it for /, paging, /usr, /var, /tmp & /home. I'm not sure what I'm supposed to tell it about boot managers though? Right now the MBR points to Acronis' recovery slice, which boots to Win 7's boot manager, it defaults to Win/XP. When I said do nothing sysinstall marked the new slice bootable, and FreeBSD does boot to a text menu with Beastie on it. But, that doesn't give access to the OS's in slice 1 and 3? if I tell it to use the default boot manager, (booteasy?), will it offer at least access to what's currently in the master boot record & slice 2 (FreeBSD)? Or do I need a way to tell Win7's boot manager about FreeBSD in slice 2? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: installing linux after freebsd (multi-boot)
> "अनुज" == अनुज Anuj Singh <[EMAIL PROTECTED]> writes: अनुज> hi, अनुज> Today I removed partitions from Fedora 7 installation , (kept /home अनुज> partition from FC7). Again went threw installation I faced no problem अनुज> this time. Fedora 7 was installed without using LVM. on free space I अनुज> installed Ubntu7. server for test purpose. No error. अनुज> Sequence was Freebsd6.2 , Fedora Core 7 then RHEL4. अनुज> When I tried installation with deselecting many packages (minimal अनुज> installation) for RHEL5 अनुज> without using LVM , I faced no problem, rebooted in mid to use अनुज> LVM+minimal RHEL5 again same error. Repetation with minimal What is LVM+minimal RHEL5, you installed RHEL5 (without using LVM), right... or you tried activating existing LVM partitions in your RHEL5 installation (on non-LVM partitions), and got into some error, hmm...? If thats you get, I think is some kind of bug, better post it to some RHEL list or check out (and post it to) Red Hat Bugzilla, and see if someone has already similar oblem. अनुज> installation+ no LVM could not continued (found same error again). अनुज> Most likely it was due to partition table. Your partition table looks fine to me. HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- pgpgRvItbDGFS.pgp Description: PGP signature
Re: installing linux after freebsd (multi-boot)
hi, Today I removed partitions from Fedora 7 installation , (kept /home partition from FC7). Again went threw installation I faced no problem this time. Fedora 7 was installed without using LVM. on free space I installed Ubntu7. server for test purpose. No error. Sequence was Freebsd6.2 , Fedora Core 7 then RHEL4. When I tried installation with deselecting many packages (minimal installation) for RHEL5 without using LVM , I faced no problem, rebooted in mid to use LVM+minimal RHEL5 again same error. Repetation with minimal installation+ no LVM could not continued (found same error again). Most likely it was due to partition table. Now current partition table I have is. Disk /dev/hdc: 82.3 GB, 82348277760 bytes 255 heads, 63 sectors/track, 10011 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1127410233373+ a5 FreeBSDwrote: > > "अनुज" == अनुज Anuj Singh <[EMAIL PROTECTED]> writes: > अनुज> On Dec 31, 2007 1:29 PM, आशीष शुक्ल Ashish Shukla <[EMAIL > PROTECTED]> wrote: > >> ,--[ On Mon, Dec 31, 2007 at 09:03:08AM +0530, अनुज Anuj Singh wrote: > >> > >> [snipped] > >> > >> | > >> On 30/12/2007, <[EMAIL PROTECTED]> wrote: > >> | > >> > >> | > >>> Hello , > >> | > >>> I have freebsd6.2 installed with Fedora core 7 and rhe4. > >> | > >>> I am installing rhel5 , when linux installation process starts > I get an > >> | > >>> error of /dev/hdc1 busy , can not report to kernel about > partition > >> | > >>> layout. In the past I installed linux then FreeBSD. > >> | > >>> Is there some method that rhel5 installation can skip /dev/hdc1 > >> | > >>> (freebsd slice) ? saving my freebsd installation > >> > >> You get /dev/hdc1 busy error. At which step in installation, you get > >> /dev/hdc1 busy error, hmm...? Are you trying to remove '/dev/hdc1' > >> (FreeBSD slice), if yes, then you'll get error, and you probably need > to > >> remove FreeBSD partitions (present in slice) first. > > अनुज> No I am not removing/mounting/using FreeBSD slice. > > अनुज> This is the log... > > अनुज> 03:29:50 INFO: moving (1) to step confirminstall > अनुज> 03:30:13 INFO: moving (1) to step install > अनुज> 03:30:13 INFO: moving (1) to step enablefilesystems > अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol00, size of 1472 > अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol01, size of 2496 > अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol02, size of 672 > अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol03, size of 1024 > अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol04, size of 9984 > अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol05, size of 9344 > अनुज> 03:30:17 INFO: removing lv LogVol03 > अनुज> 03:30:18 INFO: removing lv LogVol00 > अनुज> 03:30:18 INFO: removing lv LogVol04 > अनुज> 03:30:19 INFO: removing lv LogVol05 > अनुज> 03:30:19 INFO: removing lv LogVol02 > अनुज> 03:30:20 INFO: removing lv LogVol01 > अनुज> 03:30:21 INFO: pv is /dev/hdc11 in vg VolGroup00, size is 29996 > अनुज> 03:30:21 INFO: vgremove VolGroup00 > अनुज> 03:30:22 INFO: pvremove -ff -y /dev/hdc11 > अनुज> 03:30:22 INFO: pvcreate -ff -y -v /dev/hdc11 > अनुज> 03:30:23 CRITICAL: parted exception: Error: Error informing the > kernel > अनुज> about modifications to partition /dev/hdc1 -- Device or resource > busy. > अनुज> This means Linux won't know about any changes you made to /dev/hdc1 > अनुज> until you reboot -- so you shouldn't mount it or use it in any way > अनुज> before rebooting. > अनुज> 03:31:08 CRITICAL: Traceback (most recent call first): > अनुज> File "/usr/lib/anaconda/partedUtils.py", line 876, in savePartitions > अनुज> disk.commit() > अनुज> File "/usr/lib/anaconda/packages.py", line 145, in turnOnFilesystems > अनुज> anaconda.id.diskset.savePartitions () > अनुज> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep > अनुज> rc = stepFunc(self.anaconda) > अनुज> File "/usr/lib/anacon
Re: installing linux after freebsd (multi-boot)
> "अनुज" == अनुज Anuj Singh <[EMAIL PROTECTED]> writes: अनुज> On Dec 31, 2007 1:29 PM, आशीष शुक्ल Ashish Shukla <[EMAIL PROTECTED]> wrote: >> ,--[ On Mon, Dec 31, 2007 at 09:03:08AM +0530, अनुज Anuj Singh wrote: >> >> [snipped] >> >> | > >> On 30/12/2007, <[EMAIL PROTECTED]> wrote: >> | > >> >> | > >>> Hello , >> | > >>> I have freebsd6.2 installed with Fedora core 7 and rhe4. >> | > >>> I am installing rhel5 , when linux installation process starts I get an >> | > >>> error of /dev/hdc1 busy , can not report to kernel about partition >> | > >>> layout. In the past I installed linux then FreeBSD. >> | > >>> Is there some method that rhel5 installation can skip /dev/hdc1 >> | > >>> (freebsd slice) ? saving my freebsd installation >> >> You get /dev/hdc1 busy error. At which step in installation, you get >> /dev/hdc1 busy error, hmm...? Are you trying to remove '/dev/hdc1' >> (FreeBSD slice), if yes, then you'll get error, and you probably need to >> remove FreeBSD partitions (present in slice) first. अनुज> No I am not removing/mounting/using FreeBSD slice. अनुज> This is the log... अनुज> 03:29:50 INFO: moving (1) to step confirminstall अनुज> 03:30:13 INFO: moving (1) to step install अनुज> 03:30:13 INFO: moving (1) to step enablefilesystems अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol00, size of 1472 अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol01, size of 2496 अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol02, size of 672 अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol03, size of 1024 अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol04, size of 9984 अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol05, size of 9344 अनुज> 03:30:17 INFO: removing lv LogVol03 अनुज> 03:30:18 INFO: removing lv LogVol00 अनुज> 03:30:18 INFO: removing lv LogVol04 अनुज> 03:30:19 INFO: removing lv LogVol05 अनुज> 03:30:19 INFO: removing lv LogVol02 अनुज> 03:30:20 INFO: removing lv LogVol01 अनुज> 03:30:21 INFO: pv is /dev/hdc11 in vg VolGroup00, size is 29996 अनुज> 03:30:21 INFO: vgremove VolGroup00 अनुज> 03:30:22 INFO: pvremove -ff -y /dev/hdc11 अनुज> 03:30:22 INFO: pvcreate -ff -y -v /dev/hdc11 अनुज> 03:30:23 CRITICAL: parted exception: Error: Error informing the kernel अनुज> about modifications to partition /dev/hdc1 -- Device or resource busy. अनुज> This means Linux won't know about any changes you made to /dev/hdc1 अनुज> until you reboot -- so you shouldn't mount it or use it in any way अनुज> before rebooting. अनुज> 03:31:08 CRITICAL: Traceback (most recent call first): अनुज> File "/usr/lib/anaconda/partedUtils.py", line 876, in savePartitions अनुज> disk.commit() अनुज> File "/usr/lib/anaconda/packages.py", line 145, in turnOnFilesystems अनुज> anaconda.id.diskset.savePartitions () अनुज> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep अनुज> rc = stepFunc(self.anaconda) अनुज> File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext अनुज> self.moveStep() अनुज> File "/usr/lib/anaconda/gui.py", line 1007, in nextClicked अनुज> self.anaconda.dispatch.gotoNext() अनुज> File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback अनुज> self.intf.icw.nextClicked() अनुज> File "/usr/lib/anaconda/gui.py", line 1034, in handleRenderCallback अनुज> self.currentWindow.renderCallback() अनुज> error: Error: Error informing the kernel about modifications to अनुज> partition /dev/hdc1 -- Device or resource busy. This means Linux अनुज> won't know about any changes you made to /dev/hdc1 until you reboot -- अनुज> so you shouldn't mount it or use it in any way before rebooting. अनुज> From anacdump.txt अनुज> Traceback (most recent call first): अनुज> File "/usr/lib/anaconda/partedUtils.py", line 876, in savePartitions अनुज> disk.commit() अनुज> File "/usr/lib/anaconda/packages.py", line 145, in turnOnFilesystems अनुज> anaconda.id.diskset.savePartitions () अनुज> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep अनुज> rc = stepFunc(self.anaconda) अनुज> File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext अनुज> self.moveStep() अनुज> File "/usr/lib/anaconda/gui.py", line 1007, in nextClicked अनुज> self.anaconda.dispatch.gotoNext() अनुज> File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback अनुज> self.intf.icw.nextClicked() अनुज> File "/usr/lib/anaconda/gui.py", line 1034, in handleRenderCallback अनुज> self.currentWindow.renderCallback() अनुज> error: Error: Error informing the kernel about modifications to अनुज> partition /dev/hdc1 -- Device or resource busy. This means Linux अनुज> won't know about any changes you made to /dev/hdc1 until you reboot -- अनुज> so you shouldn't mount it or use it in
Re: installing linux after freebsd (multi-boot)
On Dec 31, 2007 1:29 PM, आशीष शुक्ल Ashish Shukla <[EMAIL PROTECTED]> wrote: > ,--[ On Mon, Dec 31, 2007 at 09:03:08AM +0530, अनुज Anuj Singh wrote: > > [snipped] > > | > >> On 30/12/2007, <[EMAIL PROTECTED]> wrote: > | > >> > | > >>> Hello , > | > >>> I have freebsd6.2 installed with Fedora core 7 and rhe4. > | > >>> I am installing rhel5 , when linux installation process starts I get > an > | > >>> error of /dev/hdc1 busy , can not report to kernel about partition > | > >>> layout. In the past I installed linux then FreeBSD. > | > >>> Is there some method that rhel5 installation can skip /dev/hdc1 > | > >>> (freebsd slice) ? saving my freebsd installation > > You get /dev/hdc1 busy error. At which step in installation, you get > /dev/hdc1 busy error, hmm...? Are you trying to remove '/dev/hdc1' > (FreeBSD slice), if yes, then you'll get error, and you probably need to > remove FreeBSD partitions (present in slice) first. No I am not removing/mounting/using FreeBSD slice. This is the log... 03:29:50 INFO: moving (1) to step confirminstall 03:30:13 INFO: moving (1) to step install 03:30:13 INFO: moving (1) to step enablefilesystems 03:30:17 INFO: lv is VolGroup00/LogVol00, size of 1472 03:30:17 INFO: lv is VolGroup00/LogVol01, size of 2496 03:30:17 INFO: lv is VolGroup00/LogVol02, size of 672 03:30:17 INFO: lv is VolGroup00/LogVol03, size of 1024 03:30:17 INFO: lv is VolGroup00/LogVol04, size of 9984 03:30:17 INFO: lv is VolGroup00/LogVol05, size of 9344 03:30:17 INFO: removing lv LogVol03 03:30:18 INFO: removing lv LogVol00 03:30:18 INFO: removing lv LogVol04 03:30:19 INFO: removing lv LogVol05 03:30:19 INFO: removing lv LogVol02 03:30:20 INFO: removing lv LogVol01 03:30:21 INFO: pv is /dev/hdc11 in vg VolGroup00, size is 29996 03:30:21 INFO: vgremove VolGroup00 03:30:22 INFO: pvremove -ff -y /dev/hdc11 03:30:22 INFO: pvcreate -ff -y -v /dev/hdc11 03:30:23 CRITICAL: parted exception: Error: Error informing the kernel about modifications to partition /dev/hdc1 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/hdc1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. 03:31:08 CRITICAL: Traceback (most recent call first): File "/usr/lib/anaconda/partedUtils.py", line 876, in savePartitions disk.commit() File "/usr/lib/anaconda/packages.py", line 145, in turnOnFilesystems anaconda.id.diskset.savePartitions () File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1007, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1034, in handleRenderCallback self.currentWindow.renderCallback() error: Error: Error informing the kernel about modifications to partition /dev/hdc1 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/hdc1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. From anacdump.txt Traceback (most recent call first): File "/usr/lib/anaconda/partedUtils.py", line 876, in savePartitions disk.commit() File "/usr/lib/anaconda/packages.py", line 145, in turnOnFilesystems anaconda.id.diskset.savePartitions () File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1007, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1034, in handleRenderCallback self.currentWindow.renderCallback() error: Error: Error informing the kernel about modifications to partition /dev/hdc1 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/hdc1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. Local variables in innermost frame: self: disk: > > [snipped] > > | Hi, > | 1. I am trying to fresh install over single disk. > | 2. I have FreeBSD6.2 slice on first primary partition of the disk. > > There should be absolutely no problem in installing RHEL5, even > GNU/Linux can read FreeBSD disklabels (and partitions) without any > problem :) . > > | can I have a look at your partition table ? > > Here is mine, I'm running Ubuntu Linux, which is installed after FreeBSD. > > Disk /dev/sdb: 160.0 GB, 160041885696 bytes > 255 heads, 63 sectors/track, 19457 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x00083e09 > >Device Boot Start End Blocks Id Sy
Re: installing linux after freebsd (multi-boot)
,--[ On Mon, Dec 31, 2007 at 09:03:08AM +0530, अनुज Anuj Singh wrote: [snipped] | > >> On 30/12/2007, <[EMAIL PROTECTED]> wrote: | > >> | > >>> Hello , | > >>> I have freebsd6.2 installed with Fedora core 7 and rhe4. | > >>> I am installing rhel5 , when linux installation process starts I get an | > >>> error of /dev/hdc1 busy , can not report to kernel about partition | > >>> layout. In the past I installed linux then FreeBSD. | > >>> Is there some method that rhel5 installation can skip /dev/hdc1 | > >>> (freebsd slice) ? saving my freebsd installation You get /dev/hdc1 busy error. At which step in installation, you get /dev/hdc1 busy error, hmm...? Are you trying to remove '/dev/hdc1' (FreeBSD slice), if yes, then you'll get error, and you probably need to remove FreeBSD partitions (present in slice) first. [snipped] | Hi, | 1. I am trying to fresh install over single disk. | 2. I have FreeBSD6.2 slice on first primary partition of the disk. There should be absolutely no problem in installing RHEL5, even GNU/Linux can read FreeBSD disklabels (and partitions) without any problem :) . | can I have a look at your partition table ? Here is mine, I'm running Ubuntu Linux, which is installed after FreeBSD. Disk /dev/sdb: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00083e09 Device Boot Start End Blocks Id System /dev/sdb1 * 1261120972826 a5 FreeBSD /dev/sdb22612922953159085 83 Linux /dev/sdb392309254 200812 83 Linux Partition 3 does not end on cylinder boundary. /dev/sdb49255 1945781955597+ f W95 Ext'd (LBA) /dev/sdb59255 1537349150836 83 Linux /dev/sdb6 15374 1932931776538+ 83 Linux /dev/sdb7 19330 19457 1028128+ 82 Linux swap / Solaris | I have IDE hard disk. Mine is SATA disk, but that should make no difference :) | Regards. | Anuj singh "anugunj" HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- signature.asc Description: Digital signature
Re: installing linux after freebsd (multi-boot)
On Dec 31, 2007 11:28 AM, jery <[EMAIL PROTECTED]> wrote: > wrote: > > I want to install rhel5 on same hard disk. Freebsd6.2 slice is on > > primary partition , second OS is Fedora 7, 3rd is rhel4 (want to fresh > > install rhel5 over rhel4) . > > I can see freebsd mentioned in my rhel partitioning section, most > > likely linux does not have support for freebsd slice. > > Last time too I had do format my FreeBSD just for RHEL4/Fedora, and I > > dont want to format FreeBSD just to install linux. Is there some > > method to avoid formatting FreeBSD every time I fresh install linux? I > > have two disks , second disk I use for saving data. > > > > > > Thanks and Regards > > Anuj Singh "anugunj". > > > > > > > > On Dec 30, 2007 10:19 PM, Christian Walther <[EMAIL PROTECTED]> wrote: > > > >> Hi there, > >> > >> > >> On 30/12/2007, <[EMAIL PROTECTED]> wrote: > >> > >>> Hello , > >>> I have freebsd6.2 installed with Fedora core 7 and rhe4. > >>> I am installing rhel5 , when linux installation process starts I get an > >>> error of /dev/hdc1 busy , can not report to kernel about partition > >>> layout. In the past I installed linux then FreeBSD. > >>> Is there some method that rhel5 installation can skip /dev/hdc1 > >>> (freebsd slice) ? saving my freebsd installation > >>> > >> Do you want to install rhel5 on a different disk than your FreeBSD > >> installation is located on? In this case I would just remove the disk > >> (unplug the cable) during the installation. > >> > >> HTH > >> Christian > >> > >> > >> > >> > >> ___ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to "[EMAIL PROTECTED]" > hello, > > Install/upgrade rhel5 on the rhel4 partition. i have done that and i > never had to format FreeBsd partition for a > fresh linux installation. i am running Debian Gnu/Linux,rhel5,and > FreeBSD on the same hard disk,i have installed rhel5 many time's without > formatting Freebsd partition. > Hi, 1. I am trying to fresh install over single disk. 2. I have FreeBSD6.2 slice on first primary partition of the disk. can I have a look at your partition table ? I have IDE hard disk. Regards. Anuj singh "anugunj" > > jery > > > ___ > 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]"
Re: installing linux after freebsd (multi-boot)
wrote: I want to install rhel5 on same hard disk. Freebsd6.2 slice is on primary partition , second OS is Fedora 7, 3rd is rhel4 (want to fresh install rhel5 over rhel4) . I can see freebsd mentioned in my rhel partitioning section, most likely linux does not have support for freebsd slice. Last time too I had do format my FreeBSD just for RHEL4/Fedora, and I dont want to format FreeBSD just to install linux. Is there some method to avoid formatting FreeBSD every time I fresh install linux? I have two disks , second disk I use for saving data. Thanks and Regards Anuj Singh "anugunj". On Dec 30, 2007 10:19 PM, Christian Walther <[EMAIL PROTECTED]> wrote: Hi there, On 30/12/2007, <[EMAIL PROTECTED]> wrote: Hello , I have freebsd6.2 installed with Fedora core 7 and rhe4. I am installing rhel5 , when linux installation process starts I get an error of /dev/hdc1 busy , can not report to kernel about partition layout. In the past I installed linux then FreeBSD. Is there some method that rhel5 installation can skip /dev/hdc1 (freebsd slice) ? saving my freebsd installation Do you want to install rhel5 on a different disk than your FreeBSD installation is located on? In this case I would just remove the disk (unplug the cable) during the installation. HTH Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" hello, Install/upgrade rhel5 on the rhel4 partition. i have done that and i never had to format FreeBsd partition for a fresh linux installation. i am running Debian Gnu/Linux,rhel5,and FreeBSD on the same hard disk,i have installed rhel5 many time's without formatting Freebsd partition. jery ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installing linux after freebsd (multi-boot)
अनुज wrote: I want to install rhel5 on same hard disk. Freebsd6.2 slice is on primary partition , second OS is Fedora 7, 3rd is rhel4 (want to fresh install rhel5 over rhel4) . I can see freebsd mentioned in my rhel partitioning section, most likely linux does not have support for freebsd slice. Last time too I had do format my FreeBSD just for RHEL4/Fedora, and I dont want to format FreeBSD just to install linux. Is there some method to avoid formatting FreeBSD every time I fresh install linux? I have two disks , second disk I use for saving data. Thanks and Regards Anuj Singh "anugunj". On Dec 30, 2007 10:19 PM, Christian Walther <[EMAIL PROTECTED]> wrote: Hi there, On 30/12/2007, अनुज <[EMAIL PROTECTED]> wrote: Hello , I have freebsd6.2 installed with Fedora core 7 and rhe4. I am installing rhel5 , when linux installation process starts I get an error of /dev/hdc1 busy , can not report to kernel about partition layout. In the past I installed linux then FreeBSD. Is there some method that rhel5 installation can skip /dev/hdc1 (freebsd slice) ? saving my freebsd installation Do you want to install rhel5 on a different disk than your FreeBSD installation is located on? In this case I would just remove the disk (unplug the cable) during the installation. HTH Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" hello, i have installed rhel5,Debian Gnu/Linux,FreeBsd6.2, on the same hard disk. Try installing rhel5 on the current rhel4 partition. i have done that and i never had to format FreeBSD every time i install Gnu/Linux. jery ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installing linux after freebsd (multi-boot)
I want to install rhel5 on same hard disk. Freebsd6.2 slice is on primary partition , second OS is Fedora 7, 3rd is rhel4 (want to fresh install rhel5 over rhel4) . I can see freebsd mentioned in my rhel partitioning section, most likely linux does not have support for freebsd slice. Last time too I had do format my FreeBSD just for RHEL4/Fedora, and I dont want to format FreeBSD just to install linux. Is there some method to avoid formatting FreeBSD every time I fresh install linux? I have two disks , second disk I use for saving data. Thanks and Regards Anuj Singh "anugunj". On Dec 30, 2007 10:19 PM, Christian Walther <[EMAIL PROTECTED]> wrote: > Hi there, > > > On 30/12/2007, अनुज <[EMAIL PROTECTED]> wrote: > > Hello , > > I have freebsd6.2 installed with Fedora core 7 and rhe4. > > I am installing rhel5 , when linux installation process starts I get an > > error of /dev/hdc1 busy , can not report to kernel about partition > > layout. In the past I installed linux then FreeBSD. > > Is there some method that rhel5 installation can skip /dev/hdc1 > > (freebsd slice) ? saving my freebsd installation > > Do you want to install rhel5 on a different disk than your FreeBSD > installation is located on? In this case I would just remove the disk > (unplug the cable) during the installation. > > HTH > Christian > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installing linux after freebsd (multi-boot)
Hi there, On 30/12/2007, अनुज <[EMAIL PROTECTED]> wrote: > Hello , > I have freebsd6.2 installed with Fedora core 7 and rhe4. > I am installing rhel5 , when linux installation process starts I get an > error of /dev/hdc1 busy , can not report to kernel about partition > layout. In the past I installed linux then FreeBSD. > Is there some method that rhel5 installation can skip /dev/hdc1 > (freebsd slice) ? saving my freebsd installation Do you want to install rhel5 on a different disk than your FreeBSD installation is located on? In this case I would just remove the disk (unplug the cable) during the installation. HTH Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
installing linux after freebsd (multi-boot)
Hello , I have freebsd6.2 installed with Fedora core 7 and rhe4. I am installing rhel5 , when linux installation process starts I get an error of /dev/hdc1 busy , can not report to kernel about partition layout. In the past I installed linux then FreeBSD. Is there some method that rhel5 installation can skip /dev/hdc1 (freebsd slice) ? saving my freebsd installation regards Anuj Singh. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multi Boot Installtion FreeBSd+Fedora+Debian
Hello, I am sorry, actually it was working but taking too much time, and at that time I was unable to go to any tty, to avoid mishap I used knoppix qtparted and formated that partition (incomplete installation of BSD) back to fat32 file system. Now started my beastie installation , in fdisk utility I used "T" option giving it 165 and partitioned, I have one confusion according to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html says Table 2-2. Partition Layout for First Disk Partition Filesystem Size Description a / 100 MB This is the root filesystem. Every other filesystem will be mounted somewhere under this one. 100 MB is a reasonable size for this filesystem. You will not be storing too much data on it, as a regular FreeBSD install will put about 40 MB of data here. The remaining space is for temporary data, and also leaves expansion space if future versions of FreeBSD need more space in /. b N/A 2-3 x RAM The system's swap space is kept on this partition. Choosing the right amount of swap space can be a bit of an art. A good rule of thumb is that your swap space should be two or three times as much as the available physical memory (RAM). You should also have at least 64 MB of swap, so if you have less than 32 MB of RAM in your computer then set the swap amount to 64 MB. If you have more than one disk then you can put swap space on each disk. FreeBSD will then use each disk for swap, which effectively speeds up the act of swapping. In this case, calculate the total amount of swap you need (e.g., 128 MB), and then divide this by the number of disks you have (e.g., two disks) to give the amount of swap you should put on each disk, in this example, 64 MB of swap per disk. e /var 50 MB The /var directory contains files that are constantly varying; log files, and other administrative files. Many of these files are read-from or written-to extensively during FreeBSD's day-to-day running. Putting these files on another filesystem allows FreeBSD to optimize the access of these files without affecting other files in other directories that do not have the same access pattern. f /usr Rest of disk All your other files will typically be stored in /usr and its subdirectories. when I followed 100 MB for my root "/" it said 118MB is minimum requirement. So I gave 120MB for / 1024MB 2x Physical Ram 300MB /var 200MB /tmp and rest is for /usr. ^target is to use X over Freebsd. Problem I facing now is: 1:My debian is showing error dropping me to fsck, running e2fsck on hdc gives can not read superblock, ^I did some mistake with partitions. Fedora is working fine, At the boot manager time I installed Freebsd boot manager I had only 1 option to boot (I will read manual if it recognizes Linux installation same as grub do). again reinstalled grub with fedora core4 (rescue mode) #chroot /mnt/sysimage #grub-install /dev/hdc added following lines in /etc/grub.conf title FreeBSD 6.1 rootnoverify (hd0,a) chainloader +1 I can boot into FreeBSD with this entry. Problem 1:it is taking some extra time same as it was taking at the installation period. (most probably due to many partitions). === New fdisk -l shows Disk /dev/hdc: 40.0 GB, 40060403712 bytes 16 heads, 63 sectors/track, 77622 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hdc16089 7760036041827+ f W95 Ext'd (LBA) Partition 1 does not end on cylinder boundary. /dev/hdc3 * 295436 2725632 a5 FreeBSD Partition 3 does not end on cylinder boundary. /dev/hdc5 *60896296 104359+ 83 Linux /dev/hdc66296 12384 3068383+ 83 Linux /dev/hdc7 12384 22536 5116671 83 Linux /dev/hdc8 22536 24560 1020096 83 Linux /dev/hdc9 24560 25580 514048+ 83 Linux /dev/hdc10 25580 31668 3068383+ 83 Linux /dev/hdc11 31668 33724 1036161 82 Linux swap / Solaris /dev/hdc12 33724 33931 104391 83 Linux /dev/hdc13 33932 36975 1534176 83 Linux /dev/hdc14 36976 37995 514048+ 83 Linux /dev/hdc15 37996 52212 7164958+ 83 Linux Partition table entries are not in disk order and grub shell output is: GNU GRUB version 0.95 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0, Possible partitions are: Partition num: 2, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type is ufs2, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partit
Re: Multi Boot Installtion FreeBSd+Fedora+Debian
On Fri, 19 Jan 2007 03:52:22 +0530
Anuj Singh <[EMAIL PROTECTED]> wrote:
> Now with the FreeBSD 6.1 installation cd , Installations stops after
> detecting my hard disk. I unplugged my 2nd IDE (with data) as it
> sometimes it shows me data read error thinking it may causing problem.
> Still the problem is same, i can not proceed beyond the detection of my
> first IDE detection.
Hi Anuj,
what does exactly happen? what part of the installation process ? If you are
already in the ncurses interface, you can switch to another VT (Alt-F2 throught
to F4 at least should work ), where far more detailed information about the
installation process is shown. I think Alt-F2 should give you a console where
you can issue some commands to see what's going on.
Best,
_
{Beto|Norberto|Numard} Meijome
"I've dirtied my hands writing poetry, for the sake of seduction; that is, for
the sake of a useful cause." Dostoevsky
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Multi Boot Installtion FreeBSd+Fedora+Debian
Hello, I had 3 OS installed on 40 GB IDE hard disk, Windows nt+ Debian + Fedora recently I decided to completely remove windows from my pc and install FreeBSD 6.1, 2nd IDE I use for data backup only. I deleted windows partition installed on the primary partition, with the fdisk utility of FreeBSD installation. After saving changes, I rebooted machine to reconfirm, and read manual again, to avoid data loss. Now with the FreeBSD 6.1 installation cd , Installations stops after detecting my hard disk. I unplugged my 2nd IDE (with data) as it sometimes it shows me data read error thinking it may causing problem. Still the problem is same, i can not proceed beyond the detection of my first IDE detection. my partitions: [EMAIL PROTECTED] ~]# fdisk -l Disk /dev/hdc: 40.0 GB, 40060403712 bytes 255 heads, 63 sectors/track, 4870 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 383486936041827+ f W95 Ext'd (LBA) /dev/hdc3 2 342 2725632 82 Linux swap / Solaris /dev/hdc5 * 383 395 104359+ 83 Linux /dev/hdc6 396 777 3068383+ 83 Linux /dev/hdc7 7781414 5116671 83 Linux /dev/hdc814151541 1020096 83 Linux /dev/hdc915421605 514048+ 83 Linux /dev/hdc10 16061987 3068383+ 83 Linux /dev/hdc11 19882116 1036161 82 Linux swap / Solaris /dev/hdc12 21172129 104391 83 Linux /dev/hdc13 21302320 1534176 83 Linux /dev/hdc14 23212384 514048+ 83 Linux /dev/hdc15 23853276 7164958+ 83 Linux Partition table entries are not in disk order and [EMAIL PROTECTED] ~]# cat /proc/partitions major minor #blocks name 22 0 39121488 hdc 22 1 1 hdc1 22 32725632 hdc3 22 5 104359 hdc5 22 63068383 hdc6 22 75116671 hdc7 22 81020096 hdc8 22 9 514048 hdc9 22103068383 hdc10 22111036161 hdc11 2212 104391 hdc12 22131534176 hdc13 2214 514048 hdc14 22157164958 hdc15 22162723616 hdc16 I reinstalled the grub 2 times,, still the problem is same. Thanks and regards anugunj "anuj" signature.asc Description: This is a digitally signed message part
Re: FreeBSD-multi-boot
Vlad GURDIGA wrote: > Hello all, > > I have these slices on my HDD: > - /dev/ad0s1 - Windows XP > - /dev/ad0s2 - FreeBSD/i386 > - /dev/ad0s3 - FreeBSD/amd64 > > and I want them all in my boot.ini. > > Till now I succeeded with FreeBSD/i386 (first did "dd if=/dev/ad0s2 > of=boot.bsd bs=512 count=1" from FreeBSD/i386, then copied the > resulted "boot.bsd" file to Windows C:\) > > I did the same trick with FreeBSD/amd64 (first did "dd if=/dev/ad0s3 > of=boot64.bsd bs=512 count=1" from FreeBSD/amd64, then copied the > resulted "boot64.bsd" file to Windows C:\) so, my boot.ini looks like > this: > > ---cut here-- > [boot loader] > timeout=3 > default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS > [operating systems] > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP > Professional" /noexecute=optin /fastdetect > C:\boot.bsd="UNIX FreeBSD/i386" > C:\boot64.bsd="UNIX FreeBSD/amd64" > ---cut here-- > > > Now, the problem is that when I choose "UNIX FreeBSD/amd64" from the > boot menu, it boots "UNIX FreeBSD/i386"!!! > > What did I missed? this page may help:- http://www.ubergeek.co.uk/howtos/grub-freebsd-windowsxp.html Cheers Danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD-multi-boot
Hello all, I have these slices on my HDD: - /dev/ad0s1 - Windows XP - /dev/ad0s2 - FreeBSD/i386 - /dev/ad0s3 - FreeBSD/amd64 and I want them all in my boot.ini. Till now I succeeded with FreeBSD/i386 (first did "dd if=/dev/ad0s2 of=boot.bsd bs=512 count=1" from FreeBSD/i386, then copied the resulted "boot.bsd" file to Windows C:\) I did the same trick with FreeBSD/amd64 (first did "dd if=/dev/ad0s3 of=boot64.bsd bs=512 count=1" from FreeBSD/amd64, then copied the resulted "boot64.bsd" file to Windows C:\) so, my boot.ini looks like this: ---cut here-- [boot loader] timeout=3 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect C:\boot.bsd="UNIX FreeBSD/i386" C:\boot64.bsd="UNIX FreeBSD/amd64" ---cut here-- Now, the problem is that when I choose "UNIX FreeBSD/amd64" from the boot menu, it boots "UNIX FreeBSD/i386"!!! What did I missed? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Multi-boot DVD
I have ISO's for FreeBSD 5.3R, FreeSBIE, Knoppix, etc... and I want to dump them all onto a DVD-R and have the ability to choose which OS to boot off the DVD - like a boot menu. Is this possible? Thank you, ...D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-RELEASE: disklabel/bsdlabel for multi-boot system
Matthew, Thanks for the prompt reply. I have now solved the issues that were preventing me from installing (though I still had to do it manually due to some limitations in sysinstall) and, once installed, I'm impressed with the package management and automatic configuration in FreeBSD. So, to answer my own questions, in case others have the same questions: 1) The 'unit' size in bsdlabel/disklabel is the size of the individual slice. You can only create BSD-partitions within that slice, and you can't extend beyond that. However, you shouldn't need to, as: 2) FreeBSD supports DOS-style extended partitions. I guess I missed that reading the manual the first time around, and I wasn't expecting it because OpenBSD doesn't support these. 3) Although FreeBSD supports DOS-style extended partitions, you can't create (or at least can't access) BSD partitions within them - for example, you there is no such thing as /dev/ad0s5e. bsdlabel supports writing a label table, but it isn't read when devfs is detecting devices. 4) Although FreeBSD supports DOS-style extended partitions, sysinstall's fdisk and label management does not, and so the only way to have a small primary slice containing / and /var, and moving the bulk (/usr) into ad0s5 is to install a minimal environment, then chroot to it, mount the extra filesystem, and run sysinstall in upgrade mode. 5) /etc/fstab accepts TAB as the only white-space. Any spaces result in an "Inappropriate file type or format" error. I guess most of these problems revolve around your point that extended partitions aren't very popular. Unfortunately, I've already got tons of data in those partitions and was unable/ unwilling to shift them around just for the convenience of the BSD install process. What I was trying to do before (which worked with OpenBSD, but then OpenBSD doesn't support DOS-style extended partitions at all) was to use slice 2 as the BSD slice, but have it claim ownership of the entire disk, so that all slices and DOS-extended slices were able to be accessed as though they were a part of slice 2. This doesn't work with FreeBSD, as bsdlabel expects the slice's label table to stay within the space allocated to it. Anyway, thanks again for the help! __ Find People and Businesses at http://www.SearchBug.com Innovative Messaging Solutions by GMSI, http://www.gmsi1.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-RELEASE: disklabel/bsdlabel for multi-boot system
On Wed, Sep 03, 2003 at 07:54:12PM -0500, Meow Cat wrote: > Hi, > Before starting, I should say that I've RTFM'd, looked > in > the FAQ and the mailing lists, etc. I've seen lots of > people > complaining about similar problems but no answers. > I have an existing partition table, and I'd like > FreeBSD > to fit into it with as little damage to the existing OSs > as > possible. The setup I have (as reported by OpenBSD > disklabel) > is: > > a: 262144 2570404.2BSD 1024 819216 > b:16384 519184 swap > c: 498015 257040unused0 0 > d: 219487 5355684.2BSD 1024 819216 > e: 4000122 67473634.2BSD 1024 819216 > i: 256977 63ext2fs > l: 5992245 755055 MSDOS > m: 45351432 10747548 MSDOS > n: 32001417 56099043 MSDOS > o: 32001417 88100523 MSDOS > > It took me ages to figure out how to achieve this under > OpenBSD, and then after install I couldn't get X to work. > So I'm trying FreeBSD - of course bsdlabel only supports > slices a-h for some reason that is never explained, so I > have to delete half of the slices. Fine, I do that. > So with a heavily edited label file I try: > bsdlabel -R /dev/ad2s0 bsdlabel_file Unfortunately I don't think you can use an OpenBSD disk label on a FreeBSD system, or vice-versa. Seems that the OpenBSD folks have revamped the way the label data is arranged on the disk, incidentally giving themselves 16 possible partitions rather than the 8 available under FreeBSD. > Every slice starts "after end of unit" and "extends beyond > end of unit." The c slice "doesn't cover entire unit!" > > Okay, I can deal with that, I think - just extend the c > slice to cover the entire disk, use "bsdlabel -A" (after a > "bsdlabel -w") to read the disk configuration and edit it > to ensure that it's not broken, and try again. If you're trying to support multiple OSes on this one disk, then under FreeBSD you'ld tend to give FreeBSD a slice of it's own, using fdisk(8) -- there's a terminology problem here that confuses a lot of people. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html particularly 'Example 2.4. Conceptual Model of a Disk' about what FreeBSD means by 'partitions' and 'slices'. Under /dev, you'll see a heirarchy of devices for each drive: /dev/ad0The whole primary master drive /dev/ad0s1 The first slice on that drive Anyhow, within the FreeBSD slice you then create the FreeBSD partitions using disklabel(8), or as it seems to have mutated into on 5.x-RELEASE, bsdlabel(8). This gives you devices: /dev/ad0s1a The root partition /dev/ad0s1b The swap area /dev/ad0s1c The whole slice /dev/ad0s1d Another partition... so /dev/ad0s1c and /dev/ad0s1 effectively mean the same thing, which is a bit redundant. Unfortunately the concept that "the c partition is the whole [disk|slice]" is so deeply embedded in the psyche (not to mention the source code) of the BSD's it isn't going to be changed any time soon. > I get the same errors. How can the first slice possibly > begin "after end of unit" and what do I do to fix this? > How are these "unit"-related numbers calculated? Does > "unit"===entire-hard-disk? Why does this fail even when > I make the c slice cover the entire hard disk? This seems to be a confusion between the (DOS compatible) "Partition table" as established by fdisk(8) and the (BSD specific) disk label. If bsdlabel(8) is talking about slices, then something is definitely wrong with the universe. > Also, I'd like to have the a slice to be a small one > from the main partition table, and /usr mounted on a > larger slice within the extended partition table. I > managed this under OpenBSD with the table above - is > there a problem (other than the one I mentioned) with > using this type of table in FreeBSD? 'Extended partitions' are a windows sort of thing, not hugely popular in FreeBSD. sysinstall(8) doesn't cope with them very well, but if you have a pre-existing disk with them on, you can access them from within FreeBSD as: /dev/ad0s5 or above. They tend, however to be used for foreign filesystems rather than native UFS ones. > Finally, before you tell me to try sysinstall - I tried > it. I'm sure it has its uses, but the interactive fdisk > part is unable to understand extended partitions, and > the interactive disklabel does not allow you to specify > your own begin/end for slices, either in sectors, or in > cyl/trk/head. So it's useless for my purposes. The only > possible use I can see for it is for people who want to > devote their entire machine to FreeBSD. That's something > I noticed in OpenBSD also - both OSs seem about 10 years > behind when it comes to supporting mutli-boot systems :( Ah, but this whole PC disk layout thing has
5.1-RELEASE: disklabel/bsdlabel for multi-boot system
Hi, Before starting, I should say that I've RTFM'd, looked in the FAQ and the mailing lists, etc. I've seen lots of people complaining about similar problems but no answers. I have an existing partition table, and I'd like FreeBSD to fit into it with as little damage to the existing OSs as possible. The setup I have (as reported by OpenBSD disklabel) is: a: 262144 2570404.2BSD 1024 819216 b:16384 519184 swap c: 498015 257040unused0 0 d: 219487 5355684.2BSD 1024 819216 e: 4000122 67473634.2BSD 1024 819216 i: 256977 63ext2fs l: 5992245 755055 MSDOS m: 45351432 10747548 MSDOS n: 32001417 56099043 MSDOS o: 32001417 88100523 MSDOS It took me ages to figure out how to achieve this under OpenBSD, and then after install I couldn't get X to work. So I'm trying FreeBSD - of course bsdlabel only supports slices a-h for some reason that is never explained, so I have to delete half of the slices. Fine, I do that. So with a heavily edited label file I try: bsdlabel -R /dev/ad2s0 bsdlabel_file Every slice starts "after end of unit" and "extends beyond end of unit." The c slice "doesn't cover entire unit!" Okay, I can deal with that, I think - just extend the c slice to cover the entire disk, use "bsdlabel -A" (after a "bsdlabel -w") to read the disk configuration and edit it to ensure that it's not broken, and try again. I get the same errors. How can the first slice possibly begin "after end of unit" and what do I do to fix this? How are these "unit"-related numbers calculated? Does "unit"===entire-hard-disk? Why does this fail even when I make the c slice cover the entire hard disk? Also, I'd like to have the a slice to be a small one from the main partition table, and /usr mounted on a larger slice within the extended partition table. I managed this under OpenBSD with the table above - is there a problem (other than the one I mentioned) with using this type of table in FreeBSD? Finally, before you tell me to try sysinstall - I tried it. I'm sure it has its uses, but the interactive fdisk part is unable to understand extended partitions, and the interactive disklabel does not allow you to specify your own begin/end for slices, either in sectors, or in cyl/trk/head. So it's useless for my purposes. The only possible use I can see for it is for people who want to devote their entire machine to FreeBSD. That's something I noticed in OpenBSD also - both OSs seem about 10 years behind when it comes to supporting mutli-boot systems :( Anyway, any help would be appreciated... __ Find People and Businesses at http://www.SearchBug.com Innovative Messaging Solutions by GMSI, http://www.gmsi1.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
