Sponsored Content
Operating Systems Linux SuSE Linux/Ubuntu Mondo/Mindi question, please help... Post 302217666 by needhelpplease on Wednesday 23rd of July 2008 09:44:01 AM
Old 07-23-2008
I tried again to back up to ISOs and this time I stopped the server and did it.
But again when I go to 'restore' it to new machine (which mirrors the original machine), I still get the same errors ....
Does anyone have any ideas?
'reborg', you asked how much memory the machine has that I am restoring to, and it has 1.0 Gig ; which is the same amount of RAM the original server has ....
Is there a reason why I would need more ram?
 

6 More Discussions You Might Find Interesting

1. Linux

HELP! Problems with Mondo Archiver

I'm running Centos 5 and have compiled the latest and greatest version of Mondo Archiver. I can run the back up manually by just running mondoarchiver with no arguments and answering all of the questions. My problem is that when I try to run it from a batch file so I can use run it... (0 Replies)
Discussion started by: wpflum
0 Replies

2. UNIX for Dummies Questions & Answers

ubuntu 9.04 router question

Hello I am new to Ubuntu and I have a quick question about router settings. When I connect directly to my cable Internet ubuntu works fine. But when I connect it to my router I can't get connectivity. I am using ubuntu 9.04 and am using D-link DI-604 router. I have reset both my router and modem... (0 Replies)
Discussion started by: jae99
0 Replies

3. Filesystems, Disks and Memory

How to create mondo backup for size > 4.5 GB

Hello Friends, I use mondoarchive to take a bootable backup of my system on a DVD. But whenever there are large files on the system, i.e. the size of the entire backup increases beyond 4.5 GB, the mondoarchive utility does not take any backup. This is quite obvious because the size of DVD is... (1 Reply)
Discussion started by: shamik
1 Replies

4. Ubuntu

XP and Linux (Ubuntu) on same disk, Can I install Ubuntu on not-yet partitioned portion of disk?

My PC (Esprimo, 3 yeas old) has one hard drive having 2 partitions C: (80 GB NTFS, XP) and D: (120 GB NTFS, empty) and and a 200 MB area that yet is not-partitioned. I would like to try Ubuntu and to install Ubuntu on the not-partitioned area . The idea is to have the possibility to run... (7 Replies)
Discussion started by: C.Weidemann
7 Replies

5. Programming

Help with C in linux Ubuntu 12.04

I'm trying to use the sytem() to send a terminal command. I haven't been able to run the program. Can someone show me how am I suppose to write this command: (echo "#o1" > /dev/ttyUSB1). Is there a better way to use the command on the C file so that when I call the file and run it on the terminal... (11 Replies)
Discussion started by: Hector M.
11 Replies

6. Ubuntu

Question about installing Cinnamon in Ubuntu

Hi, If I install Cinnamon according to the instruction in the following link: Ubuntu + Cinnamon - A good idea? No. A great one. will I still have unity, and will I still be able to choose unity when my ubuntu will start? Thank in advance ---------- Post updated at 09:48 PM ----------... (0 Replies)
Discussion started by: programAngel
0 Replies
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)
All times are GMT -4. The time now is 04:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy