10-19-2016
Thank you, Corona. I could perform the dumping from either a Windows or a Linux machine. The machine I want to install Solaris on is a Dell x86_64. I am not familiar with "dumping raw". Is there a more formal term I can search on? Or, can you, or someone else, tell me how or point me to where I can find out how to do this?
9 More Discussions You Might Find Interesting
1. Cybersecurity
it's true that USB port has no security?? (0 Replies)
Discussion started by: lolo_vang
0 Replies
2. Programming
Hi,
I am working with Sun Solaris 9(Generic_112233-07 sun4u sparc SUNW,Sun-Blade-100)and I need to develop the USB part in our application using C/C++.In our application,we are monitoring the UPS by Serial port and now I have to develop the USB part to mointor the UPS.
So I need your help to... (0 Replies)
Discussion started by: smartgupta
0 Replies
3. UNIX for Dummies Questions & Answers
Is there an easy way to setup a cross-over cable (USB-USB) between a linux box and a windows PC? My 2 machines are next to each other but I really do not want to keep transfering my files using my USB drive.
Thanks! (4 Replies)
Discussion started by: Xterra
4 Replies
4. Shell Programming and Scripting
There is a same named log file that I have on my 2 different android phones. When I plug it into my computer, it appears in the media folder, For example the first android phone:
/media/F6BA-0AF5/folder/A.log
I want to put that into a variable to be manipulated.... (3 Replies)
Discussion started by: tobenguyen
3 Replies
5. OS X (Apple)
I'm trying to get a MacBook Air (MBA) running 10.6.5 to recognize a Samsung Galaxy S (Android 2.2) vis the USB interface for simple file transfers back and forth. Nothing works so far. I've tried many things! :wall:
I noticed when I connect my phone to the MBA, there is a message in system.log... (2 Replies)
Discussion started by: Neo
2 Replies
6. Solaris
Greetings.
I am trying to save a file to a usb from solaris 10.
If I do rmformat, I see my usb, but can't find a location to tell things to save to or figure out how to save/view the files on the disk.
Any help/thoughts/etc would be appreciated.
Thanks!
~K (20 Replies)
Discussion started by: kuriosity_prime
20 Replies
7. UNIX for Advanced & Expert Users
Hi,
I have posted several times regarding my application.
In a nutshell, I have a server application that logs attached instrument data over USB and Ethernet. My restriction here is having two wires or more to plug all instrumentation in - at least one for USB and at least one for ethernet.
... (16 Replies)
Discussion started by: fedora18
16 Replies
8. UNIX for Advanced & Expert Users
Hello Experts,
I hope I'm writing to the correct category for my question.
I have a very basic shell script for doing file archiving to the external usb hard drive (WD studio edition II 2TB formatted as FAT32 for compatibility). The shell script only needs to run once per day. It basically... (8 Replies)
Discussion started by: johankor
8 Replies
9. AIX
We have an IBM Power 710. It has a USB port on the front. I have done some searching and see that there is information out there on how to create a JFS2 file system on USB drives. A few have commented that they would not recommend it, if the server is important, may crash the server... Just... (0 Replies)
Discussion started by: mbenedi
0 Replies
LEARN ABOUT POSIX
systemd-machine-id-setup
SYSTEMD-MACHINE-ID-SETUP(1) systemd-machine-id-setup SYSTEMD-MACHINE-ID-SETUP(1)
NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id
SYNOPSIS
systemd-machine-id-setup
DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with
a provisioned or randomly generated ID. See machine-id(5) for more information about this file.
If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty.
The new machine ID will be acquired in the following fashion:
1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID
in /etc/machine-id.
2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID.
The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM.
3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the
machine ID. For details, see the documentation of the Container Interface[1].
4. Otherwise, a new ID is randomly generated.
The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below.
Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images.
OPTIONS
The following options are understood:
--root=root
Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for
/etc/machine-id itself.
--commit
Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient
machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of
the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point.
This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The
command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure
that this file is always valid and accessible for other processes.
This command is primarily used by the systemd-machine-id-commit.service(8) early boot service.
--print
Print the machine ID generated or committed after the operation is complete.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1)
NOTES
1. Container Interface
https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)