> _null="/dev/null 2>&1"
>
> if mount.back $pkgname $pkgmnt > $_null ; then
> lrcfg.back.script $pkgname ON ON Full
> umount $pkgmnt > $_null
> else
> echo "Could not mount backup device."
> sleep 2
> fi
aslkhfalkjd
234lkj234j
l;j2h345783y2407uh5
You know, I realized you can't put redirection in a variable this way a
long time ago, don't know where my head was. Might there be some other
way to do this?
Here's how this part of the script should have been (now more ugly):
First, delete this stupid thing: _null="/dev/null 2>&1"
then....
if mount.back $pkgname $pkgmnt > /dev/null 2>&1 ; then
lrcfg.back.script $pkgname ON ON Full
umount $pkgmnt > /dev/null 2>&1
else
echo "Could not mount backup device."
sleep 2
fi
:)
cpu memhd wrote:
>Charles,
>
>I use the svi command all the time. I added kernel support for the
vga=
>option a long time ago, w00t! My console is set at 30 lines. Though I
>use putty mostly.
>
>Regarding the scroll back function, do you know how to increase the
>buffer size?
>
>I should mention, I really don't use lrcfg for anything other than my
>own custom packages. About 97% of my config files are extracted on the
>fly with a utility I wrote in awk. My entire shorewall config is in
one
>file, as well as a good percentage of my etc config files. Hell, even
>my shorewall actions are created on the fly depending on whether or
not
>they're specified in rules.
>
>Anyway, my original lrcfg backup modification was a bit simplistic,
>plus it made some false assumptions... and it used an external
>script... and you couldn't backup etc.lrp. I just redid it. Use at
your
>own risk, I'm still testing.
>
>Usage: type the letter "b" from within a package config menu, or
>Network or System config.
>
>Limitations: writes to temp; writes are confirmed; only does Full
>backups.
>
>You can paste this right after the "case $OPT in" line in
>/usr/sbin/lrcfg.conf:
>
> b|B )
> pkgconf=$3
> if [ "$pkgconf" = '$LRPKG/etc.net.conf' ] || \
> [ "$pkgconf" = '$LRPKG/etc.sys.conf' ]; then
> pkgconf=etc.conf
> elif [ `dirname $pkgconf` = '$LRPKG' ]; then
> echo "Not a package."
> sleep 1
> continue
> fi
>
> pkgmnt=$LRPKG/mnt
> pkgname=${pkgconf#$LRPKG/}
> pkgname=${pkgname%.conf}
>
> _null="/dev/null 2>&1"
>
> if mount.back $pkgname $pkgmnt > $_null ; then
> lrcfg.back.script $pkgname ON ON Full
> umount $pkgmnt > $_null
> else
> echo "Could not mount backup device."
> sleep 2
> fi
> ;;
>
>Charles Steinkuehler wrote:
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Eric Spakman wrote:
>>
>>| Hello cpu,
>>|
>>|>Anyhow, I feel that lrcfg is in need of a major overhaul. I?m sure
>
>many
>
>>|>will disagree, but, you can?t start/stop services from within
>
>lrcfg.
>
>>|
>>| That would be a nice addition.
>>
>>There's the command-line "svi", but you can't call this while inside
>
>lrcfg.
>
>>|>And it would be nice to be able to save a package while in a
>
>package
>
>>|>menu (incidentally, I added this capability :).
>>|
>>| Why not share your work with the community ;-)
>>
>>This does sound handy.
>>
>>|>Another problem with
>>|>lrcfg is that once you have more than 20 config options they scroll
>
>off
>
>>|>the screen.
>>|>
>>| True, that's becoming an issue with the shorwall package. Someone
>
>having a
>
>>solution for it?
>>
>>I use ssh, and just drag the window to a larger size. :-)
>>
>>If you're stuck at the (real) console screen, <shift><page-up> still
>
>works.
>
>>Also, you can always pass vga=<whatever> to the kernel (assuming this
>>functionality has been left in the Bering kernels) to get more
>
>characters on
>
>>the screen. There's probably a way to do this at runtime as well,
>
>but it's
>
>>been so long since I messed with an actual console (most of my
>
>systems are
>
>>now "headless" with serial terminal consoles & BIOS redirection) I
>
>don't
>
>>remember how...
>>
>>- --
>>Charles Steinkuehler
>>[EMAIL PROTECTED]
>>-----BEGIN PGP SIGNATURE-----
>>Version: GnuPG v1.4.0 (MingW32)
>>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>>iD8DBQFCyvU/LywbqEHdNFwRAtW1AKC8AS5FxLyqdg6lwlDzHW2yc9egfQCgi4tz
>>RONLcDCQaP1irrbCdAIWeH0=
>>=4n3W
>>-----END PGP SIGNATURE-----
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by: Discover Easy Linux Migration
>
>Strategies
>
>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>informative Webcasts and more! Get everything you need to get up to
>>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>
>------------------------------------------------------------------------
>
>>leaf-user mailing list: leaf-user@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/leaf-user
>>Support Request -- http://leaf-project.org/
>>
>>
>
>
>
>
>
>____________________________________________________
>Sell on Yahoo! Auctions no fees. Bid on great items.
>http://auctions.yahoo.com/
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>------------------------------------------------------------------------
>leaf-user mailing list: leaf-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/leaf-user
>Support Request -- http://leaf-project.org/
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
