| Age | Commit message (Collapse) | Author |
|---|
|
Been deprectated with warning for over a decade. Lets finally remove
them.
|
|
Some shells may apply word splitting after expanding variable in
`local a=$1`. I know just about yash, but since `local` is supposed to
be a builtin *command*, the "correct" behaviour of common shells is
actually a special case for `local` - it doesn't apply for other
commands. See https://osdn.net/projects/yash/ticket/46041.
|
|
'echo -n' and 'echo -e' are not portable, not all commonly used shells
support both of them (in the same way). 'echo -e' is not even defined
in POSIX.
https://pubs.opengroup.org/onlinepubs/009604599/utilities/echo.html:
> New applications are encouraged to use printf instead of echo.
> ...
> Conforming applications that wish to do prompting without <newline>s
> or that could possibly be expecting to echo a -n, should use the
> printf utility derived from the Ninth Edition system.
|
|
|
|
|
|
this was (presumabely) originally intended for testing. We use MOCK
instead nowdays.
|
|
|
|
fixes #10468
|
|
add function for y/n questions
|
|
|
|
vecho should return success even if $VERBOSE is empty. Similar, qecho
should return success even if $QUIET is empty.
fixes !4
|
|
save exit state before cleaning up tempdir so we get the correct exit
code.
This fixes the problem where lbu exit with success on errors where disk
is full or similar.
|
|
|
|
|
|
this makes it work in lxcontainers.
|
|
|
|
/proc/xen/capabilities can be non-existent while /proc/xen
exists.
This behaviour was seen when booting in rescue mode on
Linode.
|
|
|
|
|
|
|
|
|
|
a sorted list of available network interfaces thats not a part of
any bridge or bond
|
|
isin - is element in list
rmel - remove element from list
ask - Ask a question and read response
ask_until - repeat a question til a non-blank response
ask_which - repeat a question til a listed option is entered
|
|
Modified setup-interfaces to create simple bridges (works only with
one interface per bridge). Useful when setting up a Xen system, since
interfaces need to be bridged in order for guests to have networking.
Some distributions automatically create one bridge for each interface
when Xen is installed, but I think this is too aggressive.
Changes since v1:
* Only ask to bridge interfaces if Xen Dom0 is detected
|
|
And print summary of the interface configuration
|
|
new busybox doesnt support the old way we did it.
|
|
|
|
|
|
|
|
|
|
|
