-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jul 16, 2017 at 09:42:46AM -0400, RavenLX wrote:
[...]
> I use a laptop but I've never needed to ssh into a laptop computer.
> Also, if you want to set up ssh, add ssh client and set up your user
> (sudo enabled) account and random obscure
On 07/12/2017 09:21 AM, to...@tuxteam.de wrote:
[snip]
I've been following this back-and-forth for a while. Yes, I think it's
a good idea to use the root account as little as possible. Myself, I
use sudo in the overwhelming majority of cases.
But I learnt the hard way that sometimes it's a
On Thu 13 Jul 2017 at 15:11:59 (+0200), to...@tuxteam.de wrote:
> On Thu, Jul 13, 2017 at 01:34:39PM +0200, Kaj Persson wrote:
>
> [...]
>
> [added cc debian-user]
>
> > Can you have this defined from /etc/fstab too? I have had no success
> > in that.
>
> This line in the fstab works for me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 13, 2017 at 08:12:46AM -0400, Fungi4All wrote:
> > UTC Time: July 13, 2017 11:13 AM
> > From: to...@tuxteam.de
> > To: debian-user@lists.debian.org
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > On Thu, Jul 13, 2017 at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 13, 2017 at 01:34:39PM +0200, Kaj Persson wrote:
[...]
[added cc debian-user]
> Can you have this defined from /etc/fstab too? I have had no success
> in that.
This line in the fstab works for me (note: no systemd here; systemd
is
> UTC Time: July 13, 2017 11:13 AM
> From: to...@tuxteam.de
> To: debian-user@lists.debian.org
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> On Thu, Jul 13, 2017 at 12:08:27PM +0200, Kaj Persson wrote:
> [...]
>> As always only root can mount a file system. In the case vfat, which
>> does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 13, 2017 at 12:08:27PM +0200, Kaj Persson wrote:
[...]
> As always only root can mount a file system. In the case vfat, which
> does not have an access system by its own, the owner of the mounted
> system will be root.
As a hint (I'm
On 2017-07-12 at 03:49, Felix Miata wrote:
Kaj Persson composed on 2017-07-11 22:29 (UTC+0200):
...
ls -Al /home:
drwxr-xr-x 39 kaj kaj 16384 jul 11 17:23 kaj
OK...
and from the command
tree -qpadxugL 2 /home:
/home
...
│ ├── [drwxrwx--- root kaj ] DATA
...
│ ├──
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jul 12, 2017 at 08:30:12AM -0400, RavenLX wrote:
[...]
> To remove the root password so root can't log in again:
>
> sudo passwd -l root
I've been following this back-and-forth for a while. Yes, I think it's
a good idea to use the root
On 07/09/2017 06:11 PM, Kaj Persson wrote:
Hi Jimmy,
Well, I did not follow your suggestion exactly, but as people has said,
the root account is already and always there, even it has not been
assigned a password. So, against my real whish, not to activate the root
account, I gave the command
On Tue, Jul 11, 2017 at 09:49:15PM -0400, Felix Miata wrote:
> Again:
>
> chown -R 1000:1000 /home/kaj/
>
> as root should fix them all. If it doesn't, chown would seem to be broken.
Looks correct.
> Maybe this in addition?
>
> chown -R 1000:1000 /home/kaj/.*
No, NOT correct. Do
Kaj Persson composed on 2017-07-11 22:29 (UTC+0200):
...
> ls -Al /home:
> drwxr-xr-x 39 kaj kaj 16384 jul 11 17:23 kaj
OK...
> and from the command
> tree -qpadxugL 2 /home:
> /home
...
> │ ├── [drwxrwx--- root kaj ] DATA
...
> │ ├── [drwxrwx--- root kaj ] Hämtningar
On Tue, Jul 11, 2017 at 03:54:21PM -0500, David Wright wrote:
> $ find ~ -mount -not -group 1000 -exec ls -ld {} \; -o -not -user 1000 -exec
> ls -ld {} \;
find ~ -mount \( ! -group 1000 -o ! -user 1000 \) -ls
(You could also use DeMorgan's laws to factor out the "!", but this
way seems a
On Tue 11 Jul 2017 at 22:29:45 (+0200), Kaj Persson wrote:
[...]
> I see nothing which gives me an idea of what is wrong. Are there any
> more files or directories to look at? In /etc perhaps?
I don't know whether this would be useful, but
# find / -mount -not -group 0 -exec ls -ld {} \; -o -not
On 2017-07-10 at 01:36, Felix Miata wrote:
Kaj Persson composed on 2017-07-09 14:54 (UTC+0200):
* Regarding access to my user directory: During my search I did in fact
find some files and directories owned by user root or group root. These
are changed to be owned by my user id and group id,
On 10-07-17, Kaj Persson wrote:
> Hi Jimmy,
> Well, I did not follow your suggestion exactly, but as people has said, the
> root account is already and always there, even it has not been assigned a
> password. So, against my real whish, not to activate the root account, I
> gave the command sudo
On Mon, Jul 10, 2017 at 7:11 AM, Kaj Persson wrote:
> Hi Jimmy,
> Well, I did not follow your suggestion exactly, but as people has said, the
> root account is already and always there, even it has not been assigned a
> password. So, against my real whish, not to activate
Kaj Persson composed on 2017-07-09 14:54 (UTC+0200):
> * Regarding access to my user directory: During my search I did in fact
> find some files and directories owned by user root or group root. These
> are changed to be owned by my user id and group id, but this did not
> help. By the way, On
On 07/09/2017 03:11 PM, Kaj Persson wrote:
Hi Jimmy,
Well, I did not follow your suggestion exactly, but as people has said,
the root account is already and always there, even it has not been
assigned a password. So, against my real whish, not to activate the root
account, I gave the command
Hi Jimmy,
Well, I did not follow your suggestion exactly, but as people has said,
the root account is already and always there, even it has not been
assigned a password. So, against my real whish, not to activate the root
account, I gave the command sudo passwd root, and entered a password.
Yes, a good try, but ...
Owner and group for /home is root resp. root,
and for /home/cookoo (to use your example) is the correct user name
resp. group.
I have also looked one level further, hence /home/cookoo/subdir/, and
all directories on this level have the same ownership (=user name -
On 07/08/2017 02:57 PM, Kaj Persson wrote:
Hi all,
So can someone help me get the command back, or do I have to make a new
reinstall, hoping for better luck. Possibly setting a password on the
Admin, hence activating that account, which I would prefer not having to.
Thank you in advance
Kaj
Well, as I wrote my /home is an own partition, and so it has been for a
long time. So it is not a new copy but a new mount. Certainly it
therefore contains old config files that maybe ought to be removed. But
on the other hand almost all of them are reused, since many of them
belong to
Again, did you copy your /home from a previous system or is it a new
configuration that locked your panels?
> UTC Time: July 9, 2017 12:54 PM
> From: 70147pers...@telia.com
> To: debian-user@lists.debian.org
> Thank you all for thoughts and viewpoints on what can be wrong in my
> installation of
On 09-07-17, Eike Lantzsch wrote:
> On Sunday, 9 July 2017 14:54:02 -04 Kaj Persson wrote:
> >
> > * Configuring sudo? No I have not done that explicitly, not more than
> > what the install program did itself. I have looked at /etc/sudoers and
> > what I think the important lines are:
> >
> >
On Sunday, 9 July 2017 14:54:02 -04 Kaj Persson wrote:
> Thank you all for thoughts and viewpoints on what can be wrong in my
> installation of Debian 9. I have looked through places I might expect
> can contain some explanation, but so far I have not been able to exclaim
> an "Ah, that's it!".
Thank you all for thoughts and viewpoints on what can be wrong in my
installation of Debian 9. I have looked through places I might expect
can contain some explanation, but so far I have not been able to exclaim
an "Ah, that's it!". Here are some of my observations:
* First source of install:
On 07/09/2017 05:08 AM, Fungi4All wrote:
From: david...@freevolt.org
To: debian-user@lists.debian.org
As they say[1],[2],[3], do not use a live image for installs.
1. https://lists.debian.org/debian-user/2017/06/msg00723.html
2. https://lists.debian.org/debian-user/2017/06/msg00740.html
3.
> From: david...@freevolt.org
> To: debian-user@lists.debian.org
> As they say[1],[2],[3], do not use a live image for installs.
> 1. https://lists.debian.org/debian-user/2017/06/msg00723.html
> 2. https://lists.debian.org/debian-user/2017/06/msg00740.html
> 3.
On 09-07-17, Anders Andersson wrote:
> On Sun, Jul 9, 2017 at 12:51 AM, Fungi4All wrote:
>
> > On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
> >
> > > But now I discovered an issue, I cannot manage my desktop. I have
> > > always at the previous installations,
On Sun, Jul 9, 2017 at 12:51 AM, Fungi4All wrote:
> On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
>
> > But now I discovered an issue, I cannot manage my desktop. I have
> > always at the previous installations, and they are quite many now, been
> > advised to,
On Sat, 8 Jul 2017, Kaj Persson wrote:
Hi all,
Anyone having an idea how to get back the command over my desktop,
including the panels? Until two weeks ago I ran Debian 8 ("jessie"),
but after a unsuccessful clean-up operation the whole system became
totally corrupted, and I decided to to a
> From: oflam...@gmail.com
> To: Kaj Persson <70147pers...@telia.com>, debian-user@lists.debian.org
> Did you remember to reconfigure sudo? What Desktop Environment are you
> using?
He said Mate
> On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
>> But now I discovered an issue, I cannot
Did you remember to reconfigure sudo? What Desktop Environment are you
using?
On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
> Hi all,
>
> Anyone having an idea how to get back the command over my desktop,
> including the panels? Until two weeks ago I ran Debian 8 ("jessie"),
> but
>
Hi all,
Anyone having an idea how to get back the command over my desktop,
including the panels? Until two weeks ago I ran Debian 8 ("jessie"), but
after a unsuccessful clean-up operation the whole system became totally
corrupted, and I decided to to a complete new install of the new Debian
35 matches
Mail list logo