Tails

#4 Updated by mawo 2016-05-02 11:48:58

what an incompetent idiot you are, intrigeri!
Once a squashfs started up it does not matter anymore how it was copied (in this case: to the stick). Pretty basic knowledge!

So this is a plain Tails internal issue, where Tails installer needs sudo to work on some sticks.

What I noted down and what always worked when ppl complained the installer just “disappeared”:
command line for installing tails to 2nd stick:
/usr/bin/python -tt /usr/bin/tails-installer-launcher -u -n —clone -P -m -x
if “OSError: [Errno 13] Permission denied: ‘/lib/live/mount/medium’” —> prepend “sudo”

Get your facts straight and stop blocking the solution of issues out of arrogance and stupidity!
But especially stop blocking the efforts of dedicated devs like “u”,

Regards

P.S. I am sick of getting banned from #tails for just pulling your shit straight vs. fucking users with “write a bug report”! You had this bug report but were Mr. Weisenheimer!

#6 Updated by mawo 2016-05-02 13:56:03

Best sajolida,

as I get already banned every other time from #tails for helping users work around Tails bugs (absolutely within the limits of Tails: I just tell how to run a Tails-internal command as root when it’s necessary - the exact same command that Tails runs, just as root) I simply don’t mind to get banned here too.
If you really think fucking users (the ones looking for help being ill-advised by velope, geb, intrigeri, … by diverting them to obviously useless bug reports) and helpers (the ones telling the Tails compliant solution) by banning from #tails though actually helping is compliant with your CoC I can neither help you nor me.

P.S. Please also read (and understand the implications of) the last paragraph. How does this part fit the banning of users who provide actual (and, once again: Tails-compliant) solutions?!

#7 Updated by mawo 2016-05-02 14:00:48

last paragraph of https://tails.boum.org/contribute/working_together/code_of_conduct/

#8 Updated by sajolida 2016-05-03 06:13:05

The last paragraph of our Code of Conduct is exactly about the issue at stake: disagreeing, or being technically right or wrong is no excuse for poor behavior. And I fully trust geb, velope, and intrigeri for not baning you from #tails because of technical disagreement.

I’m glad you don’t mind getting banned here too. Please go contribute to other projects where I hope you’ll find people more technically competent and more tolerant to insults and disrespectful behavior like yours.

#9 Updated by intrigeri 2016-05-03 10:02:56

JFTR, I still have no plans to support upgrading, with Tails Installer, sticks installed in every possible (unsupported) manner that would creates filesystems in their own, singular way, resulting in the problem this ticket is about, and possibly many more other problems. Supporting the use cases we document is enough work as-is.

Thank you, sajolida, for helping keep this community pleasurable :)

#10 Updated by mawo 2016-05-03 10:40:39

intrigeri,

you’re simply wrong. Wrong!
There are two (2) steps:
a) create a stick by whatever means
b) boot this stick and have Tails running.

As soon as b) completed your argument(s) are simply bullshit: (As you really should know!) Tails uses squashfs.
This squashfs simply cannot be changed during step a) (except you’re paranoid and think NSA wrote a special piece of software to do so).
So as soon as the user works within Tails itself it simply becomes completely irrelevant how he created his intermediary stick.

At the end we only talk about the final stick which obviously is rejected (w/o root) in some cases.
So, once again: Get to know, how your own software works (seeing your approach this might take time)!
After, solve the issues (one issue is inexistent error handling! any serious software would present this “OSError: [Errno 13] Permission denied: ‘/lib/live/mount/medium’” to the users vs. just silently dying).

P.S. Great job, sajolida. Derailing from actual issue to politics is a proven strategy to fuck up projects.
Besides, as told I was banned for suggesting the right, proven, Tails-internal strategies. Your trust in those is unjustified.

#11 Updated by mawo 2016-05-03 11:13:57

@intrigeri:
as a starting point (really easy to get): https://en.wikipedia.org/wiki/SquashFS

#12 Updated by intrigeri 2016-05-03 12:47:22

> This squashfs simply cannot be changed during step a)

I think you’re arguing against something you believe I wrongly think, but that I never stated: nobody referred to the SquashFS being modified by installation tools here.

> So, once again: Get to know, how your own software works (seeing your approach this might take time)!

Please stop sarcasm now (regardless of whether you’re right or wrong).

Let me provide some background info that’s behind my position on this ticket. Tails is not only a SquashFS. It’s a SquashFS + a bootloader + a kernel + initramfs, all that installed in a particular way, on a device partitionned in a particular way, and a filesystem formatted in a particular way. So installing Tails is not merely dropping a SquashFS on a USB stick. What I was referring to is differences implied by random USB installers in this whole thing, and certainly not in the SquashFS. These differences do exist, and create problems, as shown by this ticket, unless we add all kinds of tricks in Tails Installer to support them all. I see little value in doing that, and the cost would be big, that’s why we only support a limited number of installation methods.