From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] History of chown semantics
Date: Wed, 15 Jan 2014 04:39:38 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1401150438060.45243@localhost> (raw)
In-Reply-To: <20140115040234.GF75847@eschaton.local>
On Tue, 14 Jan 2014, Chris Nehren wrote:
> On Tue, Jan 14, 2014 at 21:13:55 -0500, John Cowan wrote:
>> Larry McVoy scripsit:
>>
>>> But with disk so bloody cheap and VMs working so bloody well, it's pretty
>>> easy to spin up a VM and give it to some idiot who thinks they need root.
>>
>> ./configure or not, it's damned hard to install large amounts of software
>> without root. You can do it, but it's hard, especially if some of it
>> is really really expensive to build from source, since you're blocked
>> from using the distro's own install tool.
>
> How is this difficult? I've not had any problems that are
> specific to the software not wanting to be installed as non-root.
> You need to know some compiler flags like -R and ./configure
> variables like CFLAGS and LDFLAGS, but other than that I've not
> seen any problems that really stick out in my memory.
>
>> Most people who use Unix today are the only ones there. Someone should
>> really rewrite finger(1) to do something different.
>
> What do you do that this is the case? I'd literally be out of a
> job if I didn't have a gaggle of users to look after. And so
> would my entire team of coworkers. This is such a bewildering
> claim to me and everyone I know that we can't fathom how it's
> true.
>
>
You'd be surprised. Over on hoshinet, we actually share Linux and FreeBSD
servers among each other. My virtual root has 2 actual users and the
server it's hosted on has 4 actual users.
-uso.
next prev parent reply other threads:[~2014-01-15 4:39 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1389661202.22836.tuhs@minnie.tuhs.org>
2014-01-14 22:44 ` Pepe
2014-01-15 1:33 ` Warner Losh
2014-01-15 1:43 ` Larry McVoy
2014-01-15 2:13 ` John Cowan
2014-01-15 4:02 ` Chris Nehren
2014-01-15 4:39 ` Steve Nickolas [this message]
2014-01-16 8:56 Brian S Walden
-- strict thread matches above, loose matches on Subject: below --
2014-01-10 17:08 Brian S Walden
2014-01-10 14:55 Brian S Walden
2014-01-10 17:05 ` Ron Natalie
2014-01-10 1:41 Brian S Walden
2014-01-10 13:17 ` scj
2014-01-10 14:03 ` Ronald Natalie
2014-01-10 0:15 Brian S Walden
2014-01-10 1:01 ` Larry McVoy
2014-01-10 15:16 ` Clem Cole
2014-01-10 15:21 ` Larry McVoy
2014-01-09 21:43 Doug McIlroy
2014-01-09 21:29 Brian S Walden
2014-01-09 22:03 ` Clem Cole
2014-01-10 0:59 ` John Cowan
2014-01-10 4:28 ` Greg 'groggy' Lehey
2014-01-10 10:15 ` Tim Bradshaw
2014-01-09 19:23 Brian S Walden
2014-01-09 19:51 ` Clem Cole
2014-01-09 10:59 Tim Bradshaw
2014-01-09 12:46 ` Ronald Natalie
2014-01-09 14:56 ` Clem Cole
2014-01-09 15:17 ` Tim Bradshaw
2014-01-09 15:31 ` Clem Cole
2014-01-09 18:18 ` Dario Niedermann
2014-01-09 18:31 ` Ron Natalie
2014-01-09 18:48 ` Clem Cole
2014-01-09 19:48 ` Armando Stettner
2014-01-09 19:52 ` Clem Cole
2014-01-09 18:37 ` Tim Bradshaw
2014-01-09 18:55 ` Warner Losh
2014-01-10 16:20 ` Ed Carp
2014-01-09 17:01 ` Jeremy C. Reed
2014-01-09 18:40 ` Clem Cole
2014-01-09 19:13 ` John Cowan
2014-01-09 20:19 ` Tim Newsham
2014-01-09 20:43 ` Warner Losh
2014-01-10 10:09 ` Tim Bradshaw
2014-01-10 17:18 ` John Cowan
2014-01-12 21:19 ` Tim Bradshaw
2014-01-13 7:05 ` John Cowan
2014-01-13 10:37 ` Tim Bradshaw
2014-01-13 16:15 ` John Cowan
2014-01-13 16:53 ` SZIGETI Szabolcs
2014-01-13 18:16 ` John Cowan
2014-01-09 22:57 ` Cyrille Lefevre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1401150438060.45243@localhost \
--to=usotsuki@buric.co \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).