Sponsored Content
Operating Systems Linux Fedora Unix which can easily boot from a DVD Post 302346587 by jlliagre on Sunday 23rd of August 2009 08:29:17 AM
Old 08-23-2009
Quote:
Originally Posted by Rich147
(Oh and I did have a shot at downloading and installing Solaris, but I think I would need to partition my HDD and I'm not really up for that).
You don't with OpenSolaris which is a live distributions that can be run out of a CD (or DVD) without altering the existing disk partitions.
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies

2. UNIX for Advanced & Expert Users

Change password script in Unix easily..

I have more than 50 server unix's password need to change, usually I assign one password for all hosts, for easy remember, but I need to change password every two months..it's very tried to change password every 2 months, is there any unix script that can change password easily? ie ' script... (4 Replies)
Discussion started by: zp523444
4 Replies

3. Solaris

Boot options - DVD drive read error

I was wondering if there was a way to boot from openboot from the dvd drive. I was thinking about imaging the dvd to a blank drive and going about it that way. I just need to do a flash install. (5 Replies)
Discussion started by: adelsin
5 Replies

4. Solaris

Ultra 5 will not boot from DVD ROM :(

Hi, I just got a new Ultra 5 and replaced the CD-ROM with an LG DVD-ROM (approved and listed in Sun HCL). Got the DVD-ROM installed to install Solaris 10. Im just learning and new to Solaris installation. When I insert a Solaris 10 DVD I see that it gets mounted and File Manager opens and... (8 Replies)
Discussion started by: greypilgrim
8 Replies

5. Solaris

DVD Solaris System Not able to Mount and Boot

Hi, I have a .ISO file of Solaris system burned into a DVD+ROM, and I encounter the following problems, I am using Sun V440 server, (1) Not able to detect the DVD contents under /cdrom. (2) After reboot with this bootable DVD, I get the following errors, ... (1 Reply)
Discussion started by: Paris Heng
1 Replies

6. Solaris

Can't boot from burned Sol 10 x86 DVD

Hi all- I am trying to boot from a Solaris 10 DVD which I burned from the ISO I d/l from Sun(Oracle). I checked the byte counts of the image on Sun's website and my system and they are the same. I and using cdrecord from Schilly and burning the DVD like so: cdrecord -v dev=0,0,0 -dao... (0 Replies)
Discussion started by: bluescreen
0 Replies

7. Red Hat

Fedora 16 (i686) DVD boot issue in x86 (32bit)

Hi, I'm using fedora for 5 years. recently i decided to install new version (16). after i reboot the computer and want to boot from dvd nothing happen's and system boot's from hard disk (i have setup the bios to directly boot from dvd-rom and my dvd-rom is ok). i have downloaded (again) fc16 dvd... (3 Replies)
Discussion started by: ba$h
3 Replies

8. Solaris

Boot Solaris 10 U1 for x86 from DVD

Is it possible to boot an existing Solaris 10 update 1 from boot dvd that I run on p3(1 ghz -512 mb ram). I have got a dual boot sys - the other os is win xp that I need to reinstall but that removes the mbr so, is there any way to recover mbr after the installation of xp? Thanks. (3 Replies)
Discussion started by: vectrum
3 Replies
fmthard(1M)                                                                                                                            fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 01:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy