similar to: Run as root on reboot

At 07:10 PM 10/28/2020, Kenneth Porter wrote: >--On Wednesday, October 28, 2020 5:34 PM -0700 david <david at daku.org> wrote: > >>During initial setup, I'd like to avoid the manual actions of logging on >>as root and executing a command, but instead have that command run >>without intervention. > >"During initial setup" is vague. Lots of stuff

--On Wednesday, October 28, 2020 5:34 PM -0700 david <david at daku.org> wrote: > During initial setup, I'd like to avoid the manual actions of logging on > as root and executing a command, but instead have that command run > without intervention. "During initial setup" is vague. Lots of stuff happens during startup. With systemd, you can control what triggers your

Folks I have several remotely-located servers, donated by folks not all of whom are computer geeks, let-alone Linux aware. In earlier versions of Centos, I directed them to perform a minimal NetInstall (not too difficult to direct over the phone), and then issue two commands after the first boot. One was a 'curl' to download a script of mine, and the second was a dot-command to run

At 04:47 PM 10/28/2020, Frank Cox wrote: >On Wed, 28 Oct 2020 16:34:32 -0700 >david wrote: > > > Is there a way to reboot and have a script run without > > intervention. > >rc.local > >-- Alas, I think rc.local has become irrelevant with systemd, which is most Linux distros is the way forward.

Hi Ovirt node image build problem? Node image build my system OS Fedora core 14. I am have a question about installation process of oVirt project. Install DOC : https://fedorahosted.org/ovirt/wiki/Build But node-image build error? [root at Ovirt-T node]# ./autobuild.sh Running oVirt Node Autobuild test -f Makefile && make -k distclean || :

Stephen John Smoogen writes: > On Fri, 14 Dec 2018 at 05:02, isdtor <isdtor at gmail.com> wrote: > > > > Is it not possible to use an nfs based repo for kickstart under CentOS 7.5? > > > > E.g. > > > > repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel > > > > So the syntax looks to be > > repo --name=epel

On Fri, Dec 14, 2018 at 10:04 AM isdtor <isdtor at gmail.com> wrote: > > > > So the syntax looks to be > > > > > > repo --name=epel --baseurl=nfs://server:/path > > > > > > that colon after server is not a spelling error. > > > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48 > > > > That seems to work

Is it not possible to use an nfs based repo for kickstart under CentOS 7.5? E.g. repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel With trial and error I figured out that this is the correct syntax to use for an nfs-based repo. But packages from this repo in the %packages section are not found. You have specificed that the package 'bla' should be installed. This

I was trying to think of a way to set compression=on at the beginning of a jumpstart. The only idea I''ve come up with is to do so with a flash archive predeployment script. Has anyone else tried this approach? Thanks, Chad -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Wed, 28 Oct 2020 16:34:32 -0700 david wrote: > Is there a way to reboot and have a script run without > intervention. rc.local -- Can we uninstall 2020 and install it again? This one has a virus. MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

Dear Experts, Could somebody point to kicstart HOWTO specific for CentOS 7? On CentOS 7 I somehow am always given human intervention questions about drive which defeats unattended ks install. <rant ??> I'm doing kickstart installations for quite some time, normally I was just installing system when new release comes, and am basing kickstart file on anaconda-ks.cfg - with some

On Thu, August 4, 2016 7:13 pm, Paul Heinlein wrote: > On Thu, 4 Aug 2016, Valeri Galtsev wrote: > >> Dear Experts, >> >> Could somebody point to kicstart HOWTO specific for CentOS 7? >> >> On CentOS 7 I somehow am always given human intervention questions >> about drive which defeats unattended ks install. >> >> At least one snag I hit

I have just upgraded my jumpstart server to S10 u2 b9a. It is an Ultra 10 with two 120GB EIDE drives. The second drive (disk1) is new, and has u2b9a installed on a slice, with most of the space in slice 7 for the ZFS pool I created pool1 on disk1, and created the filesystem pool1/ro (for legacy reasons). I them moved my data from the original disk0 UFS file system to pool1/ro. Initially I

Hi folks, As a breather from the "thread-now-wider-than-my-headers-window-in-thunderbird" conversation re: mixing repos, I have a question regarding a machine I'm about to put online. :) I run a web hosting company and my secondary (primary to the world) DNS box died from a massive rootkit/hack last night. It was running an old Slackware 9.1 installation and I will be completely

Hi All, Now that we have multiboot capable pxelinux, thanks to mboot.c32, I decided to try and remove pxegrub from my x86 jumpstart infrastructure since, in theory, pxelinux can now do it all. The problem I'm having is I'm not very sure I'm following Tim's documentation correctly... I'm not 100% what comes after the --- and whether the Sun kernel needs it's arguments

Folks; During a jumpstart (2nd boot) of a Sun Fire 240 with Solaris 10 Update 3 (11/06), I noticed the following message; Jun 27 11:43:33 first fbt: NOTICE: cannot instrument return of fd_intr at 7b7d6278: non-canonical return instruction Kernel level was Generic_118833-33. Jumpstart was conducted using the standard JET modules. What gives? The jumpstart worked though. Solaris 10 installed

Hello, I don't know how off the wall this question will be, but first let me say that I've found your buildpkg.sh script very useful in creating an OpenSSH package for use on my Solaris systems. Currently I'm trying to set up a fully automated JumpStart system at my workplace, and I'm realizing that the 'postinstall' script (and possibly some of the other install scripts)

Hi, We've got some units in client's vehicles which are running Fedora core 1. We've can log into them over ssh remotely there is no console attached to them. I suspect one of them has some filesystem corruption, and I'd like to both force a fsck at next reboot (which I think I can do with shutdown -F) but I'd also like to make this fsck not require any human intervention.

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

Hi all, I still use the following kickstart partition scheme for C7 installations (via virt-install): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4"