Automatically importing existing users from another unix system isn't a
use case that I think we want to support. Since it is also a new
feature idea, it would be best addressed via a blueprint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Phillip Susi: Did you read the entire bug and comments, or just the
title? As per comment #16, this is clearly an issue that needs to be
addressed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/388943
Chowning all files on an existing drive would be entirely inappropriate.
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/388943
Tit
** Package changed: dolphin (Ubuntu) => ubiquity (Ubuntu)
--
chown all local drives to current user
https://bugs.launchpad.net/bugs/388943
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to dolphin in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-
Since this bug has enough information provided for a developer to begin
work, I'm going to mark it as confirmed and let them handle it from
here.
Although this may be implemented in some distributions, it is a feature
change in this distribution.
Thanks for taking the time to make Ubuntu better!
Fabio, thank you. I am familiar with the behaviour of Ubuntu and other
Linux distributions, though I must admit that I am unfamiliar with the
behaviour of Windows and therefore the comparison to Windows XP is lost
on me.
Fabio, it is not expected that the user will have any access to /home
/other-
dotancohen, if you have installed the O.S. you are the administrator of the
system, but by default, when you start your session you login as normal user
and gain administrative previleges using sudo by terminal.
Ubuntu is not Windows Xp, where any malicious software can do what it want,
Ubuntu i
> This is not a bug but a security option.
Fabio, this is not a security option. Obviously I already have access to
the hardware and just performed an install on the drive! Any other Linux
LiveCD or installer properly configures the system so that all local
drives are accessible.
--
chown all lo
thanks for the reply.
This is not a bug but a security option.
Imagine you are working with other 100 persons.
Imagine that you and another person are using the same pc (for work), are you
happy if he can see somethig personal of you ?
Then is right that the user cannot access to other disks or pa
Thank you Fabio, I did not know to which package to assign this bug. It
is still assigned to "Ubuntu", is there not a better place?
I can reproduce the bug with the current 10.10 alphas.
--
chown all local drives to current user
https://bugs.launchpad.net/bugs/388943
You received this bug notifi
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bugs
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.
** Changed in: ubuntu
Status: New => Incomplete
--
chown all local drives to current user
https://bugs.launchpad.net/bugs/388943
Thank you for bringing this bug to our attention. However, a paper cut
should be a small usability issue , in the default Ubuntu 9.10 install ,
that affects many people and is quick and easy to fix. So this bug can't
be addressed as part of the project.
its a feature request and something that req
I may have misunderstood umask, then. I thought that it applies to Linux
filesystems as well.
No matter how it is accomplished (and I don't think that creating a new
user is the right way to do it), the user should have read/write access
to mounted partitions after presenting credentials (password
Maybe I wasn't clear, forget the /home directory. If the problem is that
on Ubuntu you can't access files created with another linux system,
because there are different uid, I think that a good solution could be
create Ubuntu user with the same uid of the old linux system (see
directories in /home
I am not concerned with existing /home/* directories. If you want we can
file a separate bug on that specific case, which I agree is important.
But let's not hijack this bug.
I am concerned with disks and partitions being mounted under /media/.
And they do not have to be chowned, that is what umas
When you install Ubuntu if there is a directory with the same name of
the user you are creating, that directory will be chowned to the new
uid, so that if that directory was created with i.e. Fedora you will be
the owner of your file. However if there are other directories under
/home I guess it is
This bug seems to fit all five of the "One hundred paper cuts"
requirements, so I am adding that project to the bug. "One hundred paper
cuts" representatives can feel free to remove this bug from their
project at their discretion, I won't be offended.
--
chown all local drives to current user
htt
> If local disks have filesystem that don't support linux permission (like ntfs
> or fat) they
> should be mounted with uid and gid options, so that the user who mount it is
> the owner
> of all files and directories.
Yes, this seems reasonable. I currently do not have any such machines to
test,
If local disks have filesystem that don't support linux permission (like
ntfs or fat) they should be mounted with uid and gid options, so that
the user who mount it is the owner of all files and directories. If
filesystem supports linux permissions (ext,reiserfs,xfs,jfs etc) files
keep the previous
20 matches
Mail list logo
