FreeBSD compatibility with Solaris UFS filesystem?


 
Thread Tools Search this Thread
Operating Systems BSD FreeBSD compatibility with Solaris UFS filesystem?
# 1  
Old 06-01-2009
FreeBSD compatibility with Solaris UFS filesystem?

Hi, I'm new to BSD and would like to create a dual-boot between Solaris Express Community Edition and FreeBSD.

I would just like to know if the Solaris UFS file system can be written to by BSD?

I know that BSD uses UFS2, but I'm hoping that it is backwards compatible with UFS1 provided that Sun haven't or BSD for that matter haven't put any proprietary extensions on the fs.....

Also since I have Debian Linux on my machine right now is it recommended to write to ext3 file system either? I know that ext2 is compatible and I've read that ext3 can be written to but then you don't take advantage of the journal?

Any advice would be great!!

I've tried another forum which told me to use the BSD mailing list, I tried the mailing list and it seems to be dead....?

This is my last chance before either making or breaking the system so I would be ever so grateful for any responses Smilie

Kind regards
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

How to increase the /var (UFS) filesystem and root disk under veritas control?

I need to increase the /var (UFS) filesystem and root disk under veritas control or root disk is encapsulated # df -k /var Filesystem kbytes used avail capacity Mounted on /dev/vx/dsk/var 13241195 12475897 674524 96% /var # fstyp /dev/vx/dsk/var ufs # pkginfo... (1 Reply)
Discussion started by: amity
1 Replies

2. Solaris

Deep checking Solaris ufs filesystem

I'm prompted to start this thread following my attempt to help on this thread here (see my posts). I was proposing the OP deep checked a Solaris ufs filesystem using: # fsck -o full <filesystem node> however this option does not appear to be valid on Solaris 10. I've used... (8 Replies)
Discussion started by: hicksd8
8 Replies

3. Solaris

unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)

What can I fix this issue? I have ran below commands but everything is same.:confused: WARNING: Last shutdown is later than time on time-of-day chip: check date. The / file system (/dev/rdsk/c1t0d0s0) is being checked WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies

4. Solaris

How to increase or decrease inode number of the particular UFS filesystem

Hi Gurus I want to know the command & tips regarding, how to increase or decrease inode number of the particular ufs filesystem. Is it possible to do it in a live/production environment. Regards (3 Replies)
Discussion started by: girish.batra
3 Replies

5. Solaris

UFS filesystem mounted on 2 hosts question

I have two Unix (Solaris) hosts that are both attached to our SAN. They are both presented with the same luns. What I want to do is have the same UFS filesystem mounted on both hosts at the same time. What I am trying to accomplish is creating a zone that will reside on both hosts but only... (2 Replies)
Discussion started by: beaker457
2 Replies

6. Solaris

How can I mount a ufs filesystem on a solaris 10 sparc onto a Linux server

Hi there, I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server. *I have re-compiled the linux kernel t support ufs fstype with ro mount support. filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies

7. UNIX for Dummies Questions & Answers

FreeBSD filesystem is full error by Noob

Hello, Max here, I have installed FreeBSD on a compaq Intel box an have filesystem problems. I am now on install number 3 and encounter the same error. This time after DL the ports list and DL a number of programs the DL stopped and I got an error message that the filesystem is full I am looking... (6 Replies)
Discussion started by: madMax8911
6 Replies

8. Solaris

How to create a 2 TB UFS filesystem?

Hi, I have a 2,1 TB RAID0 Array (3- 750GB discs). I have Solaris 10 x86 installed. When I try to create a volume on this drive I receive the following error: " WARNING: /pci@0/pci8086/..../sd@6,0 (sd7) disk capacity is too large for current cbd length " I assume I can not format... (5 Replies)
Discussion started by: narrok
5 Replies

9. UNIX for Dummies Questions & Answers

limit of files in the ufs filesystem

Hello ! Does anyone knows which de limit of files in the ufs filesystem in the Solaris 2.6 ?? Danke, Witt (2 Replies)
Discussion started by: witt
2 Replies
Login or Register to Ask a Question
GPTBOOT(8)						    BSD System Manager's Manual 						GPTBOOT(8)

NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par- tition with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less. PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions. bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each one until successful. bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme attribute. Multiple partitions may have the bootonce and bootme attributes set. bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by the system. See BOOTING and POST-BOOT ACTIONS below for details. USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition found. The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files. After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions with bootme attributes are found, booting will be attempted from the first UFS partition found. BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and bootonce attributes set on those partitions. bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each partition, the bootme attribute is removed and the boot attempted. bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute. If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk. POST-BOOT ACTIONS The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions. The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these. FILES
/boot/gptboot bootcode binary /boot.config parameters for the boot blocks (optional) EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically installed in combination with gptboot. Install gptboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 gptboot can also be installed without the PMBR: gpart bootcode -p /boot/gptboot -i 1 ada0 Set the bootme attribute for partition 2: gpart set -a bootme -i 2 ada0 Set the bootonce attribute for partition 2, automatically also setting the bootme attribute: gpart set -a bootonce -i 2 ada0 SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8) HISTORY
gptboot appeared in FreeBSD 7.1. AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>. BSD
February 5, 2014 BSD