06-12-2009
In short,
mkfs -t fat32 /dev/path/to/block/device
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Currently I have a box that I am dual-booting Win98 & Linux on. I have an unformatted 3 gig slice that I would like to install Soloris 8 x86 on. Are there any issues I should be aware of? How close is the x86 install to the sparc install? The Linux partition will be going away but I need to reatain... (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. UNIX for Dummies Questions & Answers
I need an fdisk that will fdisk both parts of my drive. One with dos and the other with linux. Have have messed up my drive and can't fdisk dos or linux.
Can you help?
thank you (1 Reply)
Discussion started by: gparsons70
1 Replies
3. Windows & DOS: Issues & Discussions
:confused: I tryied to use the mount Command (and the msdos.utils) in Darwin 1.4 (OS X) to format a Compact Flash in DOS Format (I had already this native format but I changed it with Disk Utility in MacOS standard and the PC Card slot of a Windows 98-Laptop can't nore read the card) I want to... (1 Reply)
Discussion started by: dreamsurfer
1 Replies
4. UNIX for Dummies Questions & Answers
I have a disk formatted as follows.
Part Flag Tag Cylinders Size
===================================================
0 wm root 0 - 38125 26.18 Gb
1 wu swap 38126 - 49776 8 Gb
2 wm backup 0 - 49779 34.18 Gb
3 wm unassigned
4 wm unassigned
5 wm unassigned
6 wm unassigned... (1 Reply)
Discussion started by: jimthompson
1 Replies
5. Solaris
Hello all,
I have a laptop with a FAT32 files system, and I want to convert to UFS (unix file system) to install Solaris 10.
somebody knows the way to do that?:confused:
Please help
Thank you! (4 Replies)
Discussion started by: Geller
4 Replies
6. Linux
Hello ;
I have a problem running some script on dos .
when i run :
C: ls /temp
ls: cannot access /temp: No such file or directory
but when i run
C: ls \temp
windriver backup remotebackup
also when i run
C: ls temp
windriver backup remotebackup
The... (4 Replies)
Discussion started by: mulder20
4 Replies
7. Solaris
Hello and Merry Christmas...
Quick question after tireless search around the web.
Description:
I have a WD My book world edition II that met an untimely death. However the 2 SATA disks inside seem to be working just fine. Want to add either one of them to my Solaris Desktop.
Since I... (5 Replies)
Discussion started by: michnmi
5 Replies
8. UNIX for Dummies Questions & Answers
I am a new Unix Sys Admin who is learning mostly from books with minimal classroom training (ie: no certificates, training is largely hands-on, conducted at work). I work with Solaris 8 through 10, and with some fairly outdated hardware. In my work restoring old workstations I have been instructed... (2 Replies)
Discussion started by: mia-chan
2 Replies
9. Linux
Hi, I am a long time Windows user and recently try this Debian Wheezy OS. Burn Debian ISO in Windows environment and then select DVD ROM drive to boot first in BIOS.
The first installation of Debian (GNOME) was with multi-boot option that allows booting from hard disk and DVD drive. I then... (4 Replies)
Discussion started by: Linuxmun
4 Replies
LEARN ABOUT SUNOS
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)
systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)