Skip to main content

SED foo

Uncommenting %wheel NOPASSWD in /etc/sudoers
sudo sed -i -e 's/^#\s*\(%wheel\s\+ALL=(ALL)\s\+NOPASSWD:\s\+ALL\)/\1/' /etc/sudoers

Remove a line from a file
solution:
sed -i -e '/IPADDR/d' /etc/sysconfig/network-scripts/ifcfg-eth6
issue:
I was moving an interface from a Physical NIC (eth6) to a Bridge (brbkup) therefore, I obviously no longer wanted an eth6 IPADDR entry.


Insert text into a file at a specific line
solution:
sed -i -e '26i\ ' /etc/named.conf
sed -i -e '27i\ \ \ \ \ \ \ \ managed-keys-directory\ \"\/var\/named\/dynamic\";' /etc/named.conf

issue
I needed to add a directive into my /etc/named.conf file.  It could not simply be appended and YES, my proposed solution makes quite a few assumptions... most importantly that the location I want my new line is indeed line 26.

Before:
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";
};

After:
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";

        managed-keys-directory "/var/named/dynamic";
};

Note:  This is kind of a big deal for me.  I don't really know why I feel a sense of accomplishment, but I am pretty stoked about this discovery.

Comments

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...