Upstart runs all shell scripts with set -e by default
IMHO, Upstart should also set -u by default.
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
https://bugs.launchpad.net/bugs/557177
You received this bug notification because you are a member of
Scott, Your doing a great job and appreciate the patch. Ubuntu is a
great OS and I have switched all my PCs and families PCs over and
created two servers with Ubuntu. It is in fact a great OS system.
James
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
dear scott, as you failed to see the problem in having a script in
upstart that recursively wipes all file systems when called according to
the man page I would rather not have upstart on my systems. please make
upstart an optional feature and let people stick with the robust sysv
init where a
On Fri, 2010-04-23 at 17:02 +, Thomas Zehetbauer wrote:
dear scott, as you failed to see the problem in having a script in
upstart that recursively wipes all file systems when called according to
the man page I would rather not have upstart on my systems.
I not only fixed the problem
you don't know this script is dangerous before you
executed it.
Then you should not execute it.
A single bug in let's say firefox may delete your $HOME.
Do you study every line of code before you launch it?
--
init: support mandatory arguments, or prevent starting of tasks without any
On Fri, 2010-04-09 at 13:39 +, Bernd Zeimetz wrote:
Upstart runs all shell scripts with set -e by default.
So what if the script is *not* run by upstart, but by somebody trying to
figure out why things work (or not)?
If you need to assume that a piece of shell code is executed with -e
On Thu, 2010-04-08 at 23:17 +, dedded wrote:
Is there any possibility that this script, as patched, still fails
catastrophically if MOUNTPOINT is defined to a non-existent directory,
or if /tmp doesn't exist?
The cd ${MOUNTPOINT} will fail, and the script will exit; that's why
it's
Upstart runs all shell scripts with set -e by default.
So what if the script is *not* run by upstart, but by somebody trying to figure
out why things work (or not)?
If you need to assume that a piece of shell code is executed with -e being set,
add a set -e before that piece of code. Don't
** Tags added: patch
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
https://bugs.launchpad.net/bugs/557177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package mountall - 2.11
---
mountall (2.11) lucid; urgency=low
[ Scott James Remnant ]
* conf/mounted-*.conf: Add defaults for $MOUNTPOINT just in case somebody
tries to run this by hand. LP: #557177.
[ Dustin Kirkland ]
*
Re: Chris Ladd's comment #20
Is there any possibility that this script, as patched, still fails
catastrophically if MOUNTPOINT is defined to a non-existent directory,
or if /tmp doesn't exist?
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
(The Launchpad flaws that resulted in people thinking this bug report
had just been marked Invalid instead of merely refiled are, in order
of proximity, bug 558822, bug 80902, and bug 76416.)
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
from:
http://news.ycombinator.com/reply?id=1248952whence=item%3fid%3d1248725
I have a patch
if [ -z $MOUNTPOINT ]; then
echo MOUNTPOINT not defined. Not deleting your file system.;
exit(1);
fi
This patch will be included in Zippy Zebra due out in 2018
--
init: support
Whether or not a fix to upstart (Scott, #10) gets implemented, please
fix mounted-tmp.conf as well (e.g. per Chris, #20). The current version
is way too dangerous to have lying around. AndyOsi (#13) is correct that
such landmines are not to be expected in a *nix system.
--
init: support
I've submitted a one-line change to make this fail safely in
https://code.edge.launchpad.net/~mdz/ubuntu/lucid/mountall/bug-557177
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
https://bugs.launchpad.net/bugs/557177
You received this bug notification
** Branch linked: lp:~mdz/ubuntu/lucid/mountall/bug-557177
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
https://bugs.launchpad.net/bugs/557177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wow.
You guys need to chill out ;-)
I'm sorry that you got confused that moving the bug from upstart
(Ubuntu) to just upstart involved marking it as _Invalid_ and opening
a new task; I think that's one of Launchpad's more idiotic design flaws
too.
I'm also sorry that I receive literally
(it got pointed out to me that this bug was missing the reference to the
mountall package, which has the bug fix, added)
** Also affects: mountall (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu)
Status: New = Triaged
** Changed in: mountall (Ubuntu)
@Scott: thank you for the explanation in #24. Those few minutes to write
this comment we're well spent. Did get a wrong impression because of the
marking as invalid, too...
Even though you're paid to work on Ubuntu, I'd like to thank your for
all the ways you've made Ubuntu a better distro;-)
--
with all due respect to scott, it wasn't just the -- Invalid that
caused this tempest. it was the somewhat dismissive sounding 'Sorry,
the only response here is Don't Do That Then', which helped reinforce
the impression that this was a won't fix situation.
but that aside, this thread was at
Mr. Remnant, you have an incredibly condescending attitude and your
comments have ensured that I will seek alternatives to upstart and
Ubuntu in general for my deployments.
Insulting competing websites, insinuating that people are children for
being upset about WIPED FILE SYSTEMS, mocking them
@Matt: I lol'd
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
https://bugs.launchpad.net/bugs/557177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Count me in support for sjr here. It's a thankless task to maintain
software--every fix like this has to be weighed in priority against all
the other bugs people are complaining about, and it seems like the
bugmail never stops--and I know the temptation to respond tersely. On
the other side, I'd
Just to clarify: Neither I nor Thomas escalated this bug to any list -
especially because I never experienced bringing in the trolls helps in
any way. Besides: There are other ubuntu issues that permanently annoy
me again, while I am very certain that I will never again run in the bug
described
With all due respect, this is more serious than a Wishlist item. A
script that can be executed which will destroy a server's filesystem is
a serious problem. I cannot think of any usage case where it would be
preferable for a script to destroy the entire filesystem. Additionally,
the script name
I must say I find the response of the maintainer here totally
unacceptable. This bug should be marked release-critical not wishlist.
The bug-fix should be released to the ubuntu security distributions.
What is the point of protecting your system from outside attacks when
the system itself will
The maintainer here is evidently hasn't a clue about anything. I'm no
veteran but I've worked with several varieties of UNIX OSes throughout
the years and NONE of them have ever had a plain executable destroy a
filesystem without corresponding arguments. The user has no idea of when
an executable
From: http://www.ubuntu.com/education
Above all, Ubuntu is set apart from other operating systems by its
unwavering focus on simplicity and ease of use. Ubuntu's motto is Linux
for Human Beings and every development decision and application has
that goal in mind.
--
init: support mandatory
EPIC FAIL! hahaha
--
init: support mandatory arguments, or prevent starting of tasks without any
arguments
https://bugs.launchpad.net/bugs/557177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
If we can't get anything more than a dismissive attitude from Mr.
Remnant, Mark Shuttleworth might care about this bug. Contact details
are available on his blog at http://www.markshuttleworth.com/contact-
details
--
init: support mandatory arguments, or prevent starting of tasks without any
Scott: in case you are wondering why abuse is suddenly being heaped on
you, it's because the moral outrage brigade from Reddit and Hacker News
have come to exercise their moral outrage on something that has never
touched them, will never touch them, have no responsibility over and nor
desire to
Actually Bjorn, I know about this bug through Microsoft employees
throwing it in my face. If you think Microsoft won't use this against
Ubuntu (and/or Linux in general) you've got another thing coming. This
is a bug that affects every Ubuntu user and system administrator out
there. Being
Could people please read all the comments before judging so quickly? I
was thinking the same thing at first, but if you read message #10 he
rethinks his position and marks it to be fixed. I would be more likely
myself to mark it as critical rather than wishlist, but the maintainer
has
Here is a patch to mounted-tmp.conf (part of the 'mountall' package)
that will set a sane default if $MOUNTPOINT isn't defined.
** Patch added: mounted-tmp.conf.patch
http://launchpadlibrarian.net/43406743/mounted-tmp.conf.patch
--
init: support mandatory arguments, or prevent starting of
34 matches
Mail list logo
