Today (Saturday) We will make some minor tuning adjustments to MySQL.

You may experience 2 up to 10 seconds "glitch time" when we restart MySQL. We expect to make these adjustments around 1AM Eastern Daylight Saving Time (EDT) US.


Endian vs pfsense??

Login or Register to Reply

 
Thread Tools Search this Thread
# 1  
Endian vs pfsense??

Hi
Endian firewall free version if we do compare pfsense
For a LAN network with active user 1000
Which do you recommend
Share
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

1 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Migrating Oracle from Big Endian to Little Endian Platorm

Hi, We are trying to migrate an oracle database from Sun Solaris (SunOS 5.9 Generic_118558-28 sun4u sparc SUNW,Ultra-60) to Linux 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux which is basically a Big Endian to Little Endian conversion. We shutdown... (3 Replies)
Discussion started by: luft
3 Replies
DCTOPNM(1)						DICOM PS3 - DICOM image to PNM file						DCTOPNM(1)

NAME
dctopnm - ACR/NEMA DICOM PS3 ... DICOM PS3 - DICOM image to PNM file
SYNOPSIS
dctopnm [ -v|verbose ] [ -quiet|silent ]
DESCRIPTION
dctopnm reads the named dicom or acr-nema input file and copies the raw image pixel data to a PNM file after adding a PGM or PPM header. The input file must be unencapsulated, and in the case of > 8 bit data, in the same byte order as desired in the output, since the raw bytes are copied from input to output without any conversion. Use dccp(1) first to change the encoding if necessary. Only the necessary number of bytes to encode the pixel data will be written (based on rows, columns, number of frames, samples per pixel and bits allocated); this means that for an odd number of bytes the extra DICOM padding byte will not be copied to the raw output. This prevents netpbm utilities freaking out with an error "reading magic number" if the padding byte is present. If any of the necessary attributes to calculate the correct pixel data length are missing, all encoded bytes will be written.
OPTIONS
The PNM output goes where it is specified or standard out. The verbose output goes to standard error. The basic input switches are described in dcintro(1). Options specific to this program are: -quiet|silent Suppress the normal description of image parameters. -verbose Display byte offset from file start and message start, in hexadecimal, and dump contents while reading, once read, during replace- ment, and before writing.
ENVIRONMENT
EXAMPLES
% dcfile big.dc3 Meta: UID 1.2.840.10008.1.2.1 Meta: Description "Explicit VR Little Endian" Meta: ByteOrder Little Meta: VR Explicit Meta: Encapsulated No Data: UID 1.2.840.10008.1.2.2 Data: Description "Explicit VR Big Endian" Data: ByteOrder Big Data: VR Explicit Data: Encapsulated No % dctopnm big.dc3 big.pgm -endian big Rows = 512 Columns = 512 NumberOfFrames = 0 PhotometricInterpretation = MONOCHROME2 SamplesPerPixel = 1 BitsAllocated = 16 BitsStored = 16 HighBit = 15 PixelRepresentation = 1 PlanarConfiguration = 0x0 Rows*Columns*SamplesPerPixel*BitsAllocated/8 = 0x80000 Writing ...
FILES
SEE ALSO
dccp(1), pnmtodc(1), rawtodc(1), dctoraw(1), dctopgm8(1), dcintro(1)
AUTHOR
Copyright (C) 1993-2012. David A. Clunie DBA PixelMed Publishing. All rights reserved.
BUGS
DICOM PS3 13 April 2012 DCTOPNM(1)

Featured Tech Videos