What is the equivalent of read -r (solaris command ) in Linux ? read utility in solaris will read a single line from standard input and -r option is used not to treat backslash () as an escape character .
I am able to build a shared library under solaris with /usr/local/bin/g++ -G -o output.so file1.o file2.o file3.o. How do I build the shared library under linux using the same files? I have tried to use the same command /usr/local/bin/g++ -g -o but I got some undefined references, even if those references are defined in one of the object files.
I have Preinstalled Xp on my system.I have installed Solaris in one of my unused partition.when i installed the fedora 12 i didnot get the options for solaris booting though i have used different partition for solaris and fedora.How can i get the options for solaris or else i have made a mistake in installing fedora. In either case please guide me though how irritating it may be to guide a newbie.Also if i want to use Archlinux with all three above how can i do it.
i have a linux mechine, in that i want to install solaris throug xen virtualization. (solaris content is in CD) while i am doing this there is an option "local install media" in installation method it was not highlighting so i can't install this. then what can i do now.
I am currently trying to use Kommander editor to create a GUI form to call the bash scripts that i have created. However, when i try to run it on Solaris 10, it says "Failed to execute child process kmdr-editor".
first of all, i will be glad if i can get prebuild toolchain for target=arm1176jzf-s on host= sparc-sun-solaris2.10. ( i hav browsed but can't find prebuild one) so, i tried to establish by myself i hav established binutils first, but while trying to configure& build gcc(gcc4.4.0) , i was interrupted with following error.. error message: this error has come while building boot strap gcc for cross complier tools chain
checking build system type... sparc-sun-solaris2.10 checking host system type... arm-unknown-linux-gnu checking target system
I was wondering if in RHEL5_3 if you can add netgroups to your kickstart file like when you are jumpstarting Solaris boxes? Trying to see if I can have a group of machines use a certain DHCP or DNS server during my kickstart.
Working with a scientific code that uses more RAM+swap then i generally have (system has 12GB RAM + 24GB swap, but this thing is crazy)It's kind of a one use problem, so I'm not looking to get more RAM, is there a quick way to add more swap space (not on the swap partition, because i have that set at 24GB) so that my system can use it immediately?I don't want to drive up to the office tonight to get this fixed, so a command line setup would work best.
We have a 32bit Gui application created using C++. We ported the application from Solaris to Linux. Issue we are facing is the size of the library and executable is very large in LINUX compared to Solaris. Red Hat Enterprise Linux 5.4 is the Linux version we using. Please find a sample dynamic library created. We would like to know the following behavior of LINUX is normal or not. Consider we created two files test1.cc and test2.cc. Both having a single line of code.
RAM for older machines like I use is fairly cheap these days. But flash memory is just as cheap or cheaper. So I'd like to ask about the feasibility of expanding my system's memory using flash memory. And about whether creating a partition for swap on the flash memory, or whether a swap file on the flash device, is the better way to go.
By flash memory I have in mind mainly USB sticks or what are sometimes called "pen drives." But I do also have CF and SD cards that, with the proper cheap adapter (one of which I already own for adapting CF) could be used to create extra swap space. So, what is the current consensus on the feasibility/advisability of using flash memory for swap? I've read about the limited write cycles of flash being an argument against using it for swap. But recent reading indicates to me that the limited write cycles problem applies mostly to older, smaller-capacity flash memory. Some will come out and say that, for larger-capacity flash memory, the life of the device is likely to exceed the amount of time your current computer will be useful (I think I've seen estimates in the range of 3-4 years life--minimum--for newer, higher-capacity flash memory).
A more persuasive argument I've heard against using flash memory for swap is that access times for these devices can be much slower than SATA, and maybe even IDE, hard drives. That would certainly dictate against using flash memory for swap.
So, how about some input on this issue? Anyone using flash memory for swap? If so, what kind (e.g., usb stick or SD/CF)? Are you using a swap file or a swap partition? How's system performance? Likewise, has anyone had flash-memory-used-as-swap die on them? The consequences would undoubtedly be dire. Also, has anyone measured flash memory access times to confirm or refute claims about slow access times? Are some types of flash memory better/worse than others in terms of access times?
FC9 (fresh install) can't NFS mount from Solaris 10 machine called NFSServer.# uname -a Linux myFC9 188.8.131.52-78.2.30.fc9.x86_64.Firewalls and iptables disabled on both hosts. On the client side myFC9 is trying to NFS mount NFSServer:/opt/sysadmin as read-only. On the NFSServer side the filesystem is exported read-only and "visible" as with show-mount.