Sponsored Content
Operating Systems Solaris Install SUN O/S 5.9 on Sparc Sunfire 280R Post 302279590 by lamoul on Friday 23rd of January 2009 07:29:18 AM
Old 01-23-2009
Thanks. I'll try it again today to burn those CD.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun Sparc 20 Jumpstart install :(

Hello, I'm having all kinds of trouble jumpstarting some SS20's. After hunting around the newsgroups I find that this seems to be a fairly common problem with no real answer. Here's a brief: SS20, 50mhz, 256mb blah blah. - Client E250 blah blah - J/start server. 10/100bt Network.... (4 Replies)
Discussion started by: itsupplies
4 Replies

2. Solaris

pls help urgently....for SUNfire 280R

hi, i hv received SUNfire 280R system ........for its initial configuration i want to connect to it through hyperterminal from the windows system..........i hv got one serial port to RJ-45 port converter with the system............can anybody tell me the normal console cable which is used to... (3 Replies)
Discussion started by: girish_shukla
3 Replies

3. Solaris

Sunfire 280R disks ?

Hi there Does anybody know what the biggest capacity disk I can get into a Sunfire 280R I currently have two 73gb disks , but I need to get these up to the biggest available Any help would be greatly appreciated (4 Replies)
Discussion started by: hcclnoodles
4 Replies

4. Solaris

Sun OS version 9 Sparc Sunfire 280

Hi, Could someone please explain it to me how much space in MG or GIG available if i can create another mount point or another slice by looking at this output: # prtvtoc /dev/rdsk/c1t1d0s0 * /dev/rdsk/c1t1d0s0 partition map * * Dimensions: * 512 bytes/sector * 424 sectors/track... (2 Replies)
Discussion started by: lamoul
2 Replies

5. Solaris

Sunfire 280R Solaris 5.9 booting

Hi, I have to question: 1) when O/S is booting, i see messages: /dev/rdsk/c1t0d0s5: is logging /dev/rdsk/c1t0d0s3: is logging /dev/rdsk/c1t0d0s7: is logging i partitioned these slices during installation of O/S 5.9. I can access to these mountpoint no problem. But... (3 Replies)
Discussion started by: lamoul
3 Replies

6. Solaris

Install Network component on Sunfire 280R Solaris 5.9

hi, i just completed installing O/S 5.9 on Sunfire 280R with O/S 5.9. During installation, i wasn't able to add IP, Default gateway, NDS and netmask because the lan port wasn't not active yet. Now that i have a lan port active, how to add network components onto the system? I did ifconfig to... (1 Reply)
Discussion started by: lamoul
1 Replies

7. Solaris

Patch update on sunfire 280R sparc for solaris 5.9

Hi, i just finished installing solaris 5.9 and I'm looking for the tools to tell me if i should update the patches or how to make sure that the current patches are ok? thanks (2 Replies)
Discussion started by: lamoul
2 Replies

8. Hardware

Updating OBP on a Sun Sunfire 280R

Hi, I'm a newbie in the Unix world... :confused: I own a Sun Sunfire 280R computer with one 750Mhz CPU. I ordered two CPU of 900Mhz to replace it; however in the Service manual from Sun I read that to use 900Mhz CPU i will need to have a OBP of at least version 4.5.16. When I type .version in... (2 Replies)
Discussion started by: Monkey114
2 Replies

9. Hardware

SunFire 280R maintenance LED is on and no display

I got the system couple of days back from one of my friend. Last night I turned it on and I noticed that maintenance LED is on. At the same time I added an LCD monitor via VGA and nothing was showing on the screen. Though the system does not have any HDD So not sure if system will even show a BIOS... (3 Replies)
Discussion started by: pgirish007
3 Replies

10. Solaris

SUN 10 OS on Sparc T4-2, how to install?

Dear all! I've received 4 servers Sparc T4-2 on a rack, those servers was built in Solaris 11 ZFS bundled. Our Application is not coporated with the Sun 11, so, I must reinstall them. However, whenever I ran cdrom in "ok prompt> bood cdrom", I received the line "Can not load cdrom". Recheck... (9 Replies)
Discussion started by: trantuananh24hg
9 Replies
gdal_rasterize(1)					      General Commands Manual						 gdal_rasterize(1)

NAME
gdal_rasterize - gdal_rasterize burns vector geometries into a raster SYNOPSIS
Usage: gdal_rasterize [-b band]* [-i] [-at] [-burn value]* | [-a attribute_name] [-3d] [-l layername]* [-where expression] [-sql select_statement] [-of format] [-a_srs srs_def] [-co "NAME=VALUE"]* [-a_nodata value] [-init value]* [-te xmin ymin xmax ymax] [-tr xres yres] [-tap] [-ts width height] [-ot {Byte/Int16/UInt16/UInt32/Int32/Float32/Float64/ CInt16/CInt32/CFloat32/CFloat64}] [-q] <src_datasource> <dst_filename> DESCRIPTION
This program burns vector geometries (points, lines and polygons) into the raster band(s) of a raster image. Vectors are read from OGR supported vector formats. Note that the vector data must in the same coordinate system as the raster data; on the fly reprojection is not provided. Since GDAL 1.8.0, the target GDAL file can be created by gdal_rasterize. One of -tr or -ts option must be used in that case. -b band: The band(s) to burn values into. Multiple -b arguments may be used to burn into a list of bands. The default is to burn into band 1. -i: Invert rasterization. Burn the fixed burn value, or the burn value associated with the first feature into all parts of the image not inside the provided a polygon. -at: Enables the ALL_TOUCHED rasterization option so that all pixels touched by lines or polygons will be updated not just those one the line render path, or whose center point is within the polygon. Defaults to disabled for normal rendering rules. -burn value: A fixed value to burn into a band for all objects. A list of -burn options can be supplied, one per band being written to. -a attribute_name: Identifies an attribute field on the features to be used for a burn in value. The value will be burned into all output bands. -3d: Indicates that a burn value should be extracted from the 'Z' values of the feature. These values are adjusted by the burn value given by '-burn value' or '-a attribute_name' if provided. As of now, only points and lines are drawn in 3D. -l layername: Indicates the layer(s) from the datasource that will be used for input features. May be specified multiple times, but at least one layer name or a -sql option must be specified. -where expression: An optional SQL WHERE style query expression to be applied to select features to burn in from the input layer(s). -sql select_statement: An SQL statement to be evaluated against the datasource to produce a virtual layer of features to be burned in. -of format: (GDAL >= 1.8.0) Select the output format. The default is GeoTIFF (GTiff). Use the short format name. -a_nodata value: (GDAL >= 1.8.0) Assign a specified nodata value to output bands. -init value: (GDAL >= 1.8.0) Pre-initialize the output image bands with these values. However, it is not marked as the nodata value in the output file. If only one value is given, the same value is used in all the bands. -a_srs srs_def: (GDAL >= 1.8.0) Override the projection for the output file. If not specified, the projection of the input vector file will be used if available. If incompatible projections between input and output files, no attempt will be made to reproject features. The srs_def may be any of the usual GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file containing the WKT. -co 'NAME=VALUE': (GDAL >= 1.8.0) Passes a creation option to the output format driver. Multiple -co options may be listed. See format specific documentation for legal creation options for each format. -te xmin ymin xmax ymax : (GDAL >= 1.8.0) set georeferenced extents. The values must be expressed in georeferenced units. If not specified, the extent of the output file will be the extent of the vector layers. -tr xres yres : (GDAL >= 1.8.0) set target resolution. The values must be expressed in georeferenced units. Both must be positive values. -tap: (GDAL >= 1.8.0) (target aligned pixels) align the coordinates of the extent of the output file to the values of the -tr, such that the aligned extent includes the minimum extent. -ts width height: (GDAL >= 1.8.0) set output file size in pixels and lines. Note that -ts cannot be used with -tr -ot type: (GDAL >= 1.8.0) For the output bands to be of the indicated data type. Defaults to Float64 -q: (GDAL >= 1.8.0) Suppress progress monitor and other non-error output. src_datasource: Any OGR supported readable datasource. dst_filename: The GDAL supported output file. Must support update mode access. Before GDAL 1.8.0, gdal_rasterize could not create new output files. EXAMPLE
The following would burn all polygons from mask.shp into the RGB TIFF file work.tif with the color red (RGB = 255,0,0). gdal_rasterize -b 1 -b 2 -b 3 -burn 255 -burn 0 -burn 0 -l mask mask.shp work.tif The following would burn all 'class A' buildings into the output elevation file, pulling the top elevation from the ROOF_H attribute. gdal_rasterize -a ROOF_H -where 'class="A"' -l footprints footprints.shp city_dem.tif AUTHORS
Frank Warmerdam warmerdam@pobox.com GDAL
Tue Sep 18 2012 gdal_rasterize(1)
All times are GMT -4. The time now is 10:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy