Skip to main content
10 events
when toggle format what by license comment
Aug 16, 2019 at 6:12 comment added Shahbaz @JohannesSchaub-litb, no that's the point. The files are not owned by root, but inside a fakeroot shell, they look like they are. When the .deb package is created inside this shell, the file owner is read from the file system (which fakeroot intercepts and returns root) and stored in the package. When installing the package, dpkg then requires root access because the package indicates the file should be owned by root.
Oct 12, 2018 at 13:32 comment added Johannes Schaub - litb Sorry, I don't understand the description. Why not patch the tools so that they won't complain if you are not root? As a related question: After all, the files that you create under fakeroot are not actually owned by root. Wouldn't this imply that when I install such a .deb file, all my /usr files are owned by whoever user called fakeroot?
Jan 7, 2015 at 20:24 comment added Shahbaz It was all very confusing until I read @ntzrmtthihu777's comment!
Dec 16, 2014 at 14:38 comment added hanetzer No good. I tried this out myself. Primary reason for fakeroot is to get ownership root:root into built packages without actually being root. installed packages will have proper perms, though.
Oct 3, 2014 at 21:14 comment added Frizlab Isn’t faker dangerous? If I create a file with the suid bit and rx perm, the file will be created owned by root, executable by anyone, as root! Or maybe setting the suid bit won’t work?
Sep 4, 2014 at 23:44 history edited Ramesh CC BY-SA 3.0
deleted 1 character in body
Oct 30, 2012 at 9:57 history edited MortenSickel CC BY-SA 3.0
added another point.
S Oct 25, 2012 at 10:36 review Late answers
Oct 25, 2012 at 11:38
S Oct 25, 2012 at 10:36 review First posts
Oct 25, 2012 at 20:52
Oct 25, 2012 at 10:16 history answered MortenSickel CC BY-SA 3.0