Sponsored Content
Operating Systems BSD Move from Solaris: ARM 64 Bit Post 302928997 by Reclzz on Tuesday 16th of December 2014 05:53:32 PM
Old 12-16-2014
Move from Solaris: ARM 64 Bit

Hey all

I've been thinking of switching my x86 Solaris out with ARM 64 Bit and FreeBSD.
Now i know i can migrate my striped-mirror ZFS to FreeBSD.

So to get to the point.
I take advantage of Kernel Zones on Solaris (Routing, Firewall, Web Access and Web Page etc.) and from time to time need access to Windows Server VM.
But Solaris doesn't support ARM hardware (and probably won't).

I'll be replacing both server and Workstation.
I haven't used FreeBSD before, but guessing it won't be fundamentally different.
I know Solaris is maintained by Oracle but does that mean FreeBSD isn't as "polished"?
And can i get same functionality with FreeBSD as i currently have with Solaris?

I'm a fairly adaquate C/C++ programmer, will it be rather difficult to customize the kernel to only support my current hardware?
If so, are there any "industry secret" guide on how to do it?

Cheers
Bo Handskemager Sørensen
Denmark
9900-FRH
 

8 More Discussions You Might Find Interesting

1. Solaris

64 bit solaris 9

How can I tell if im running a 64 bit version of solaris? (1 Reply)
Discussion started by: csaunders
1 Replies

2. Solaris

32 / 64 bit OS in Solaris

Dear All, This is Viswanadhan, new to Sun Solaris domain. In Sun Solaris ( SPARC ) has 32 bit and 64 bit OS. While insallation of OS there no specific option for 32 / 64 bit OS .On which basis OS installs for 32 / 64 bit OS ? Regards, Viswanadhan. (1 Reply)
Discussion started by: viswanadhan
1 Replies

3. Solaris

Which version and Bit of Solaris OS

Hello 1) How can I find what bit of OS I am running on? 16 bit, 64 bit? 2) What is the difference in having different bits? 3) Below is the output of /etc/release/ what are all these components meaning? $ more /etc/release Solaris 10 11/06 s10x_u3wos_10 X86 $ Thank... (7 Replies)
Discussion started by: panchpan
7 Replies

4. Solaris

Solaris 64-bit to 32-bit

I had previous implemented the following in my menu.lst to be able to get to 32-bit operations. # title Solaris 10 32-bit root (hd0,0,a) kernel /platform/i86pc/multiboot kernel/unix module /platform/i86pc/boot_archive </code> Now, it is not working as I get the following error : ... (0 Replies)
Discussion started by: praveenr
0 Replies

5. Solaris

Porting C++ 32-bit code on 64-bit Solaris

Hi, I am trying to convert 32-bit code to 64-bit. I have defined function int main() { int* l; size_t len1; fun(len1); return 0; } void fun(int* ptr) { cout<<"\nsizeof(ptr)"<<sizeof(ptr); } However while compiling getting error as : Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies

6. Solaris

Solaris os 32 bit or 64 bit

:confused: how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6. also i want to know the difference between 32 bit and 64bit os. any help will be much appreciated as i am in urgent need of this information (6 Replies)
Discussion started by: asalman.qazi
6 Replies

7. Solaris

VCS for Solaris 32 bit OS

Hi Admins, I know that VCS supports Solaris x86-64bit only...and I need vcs for Solaris 32 bit-x86..running on vmware workstation.. I need to run vcs on vmware workstation...And my laptop support only 32bit... Please suggest.. Thanks.. (1 Reply)
Discussion started by: snchaudhari2
1 Replies

8. Solaris

Solaris sticky bit

i got this archive file on sticky bit mode. somehow i could not remove the sticky bit. i could not even copy or view the view using file user account or root account. -rw-r--r-T 1 mark support 875166720 Mar 23 2005 file_mig.dat anybody encounter this type of problem? i have done running... (11 Replies)
Discussion started by: uwagon
11 Replies
MEMDUMP(1)						      General Commands Manual							MEMDUMP(1)

NAME
memdump - memory dumper SYNOPSIS
memdump [-kv] [-b buffer_size] [-d dump_size] [-m map_file] [-p page_size] DESCRIPTION
This program dumps system memory to the standard output stream, skipping over holes in memory maps. By default, the program dumps the con- tents of physical memory (/dev/mem). Output is in the form of a raw dump; if necessary, use the -m option to capture memory layout information. Output should be sent off-host over the network, to avoid changing all the memory in the file system cache. Use netcat, stunnel, or openssl, depending on your requirements. The size arguments below understand the k (kilo) m (mega) and g (giga) suffixes. Suffixes are case insensitive. Options -k Attempt to dump kernel memory (/dev/kmem) rather than physical memory. Warning: this can lock up the system to the point that you have to use the power switch (for example, Solaris 8 on 64-bit SPARC). Warning: this produces bogus results on Linux 2.2 kernels. Warning: this is very slow on 64-bit machines because the entire memory address range has to be searched. Warning: kernel virtual memory mappings change frequently. Depending on the operating system, mappings smaller than page_size or buffer_size may be missed or may be reported incorrectly. -b buffer_size (default: 0) Number of bytes per memory read operation. By default, the program uses the page_size value. Warning: a too large read buffer size causes memory to be missed on FreeBSD or Solaris. -d dump-size (default: 0) Number of memory bytes to dump. By default, the program runs until the memory device reports an end-of-file (Linux), or until it has dumped from /dev/mem as much memory as reported present by the kernel (FreeBSD, Solaris), or until pointer wrap-around happens. Warning: a too large value causes the program to spend a lot of time skipping over non-existent memory on Solaris systems. Warning: a too large value causes the program to copy non-existent data on FreeBSD systems. -m map_file Write the memory map to map_file, one entry per line. Specify -m- to write to the standard error stream. Each map entry consists of a region start address and the first address beyond that region. Addresses are separated by space, and are printed as hexadecimal numbers (0xhhhh). -p page_size (default: 0) Use page_size as the memory page size. By default the program uses the system page size. Warning: a too large page size causes memory to be missed while skipping over holes in memory. -v Enable verbose logging for debugging purposes. Multiple -v options make the program more verbose. BUGS
On many hardware platforms the firmware (boot PROM, BIOS, etc.) takes away some memory. This memory is not accessible through /dev/mem. This program should produce output in a format that supports structure information such as ELF. LICENSE
This software is distributed under the IBM Public License. AUTHOR
Wietse Venema IBM T.J. Watson Research P.O. Box 704 USA MEMDUMP(1)
All times are GMT -4. The time now is 06:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy