On 1/2/2018 8:16 AM, john doe wrote:
On 1/2/2018 8:01 AM, Tom Furie wrote:
On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:
My default route is not 192.168.1.1 and host(1) gives me that same
error.
What the error actually means is that there is no reverse DNS resolution
for that IP
On 1/2/2018 8:01 AM, Tom Furie wrote:
On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:
My default route is not 192.168.1.1 and host(1) gives me that same error.
What the error actually means is that there is no reverse DNS resolution
for that IP address, in other words the IP address
On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote:
> My default route is not 192.168.1.1 and host(1) gives me that same error.
What the error actually means is that there is no reverse DNS resolution
for that IP address, in other words the IP address cannot be resolved to
its hostname. It
On 1/2/2018 7:45 AM, Tom Furie wrote:
On Tue, Jan 02, 2018 at 07:38:54AM +0100, john doe wrote:
Looks like 192.168.1.1 is not your default route.
What led you to that conclusion?
My default route is not 192.168.1.1 and host(1) gives me that same error.
--
John Doe
On Tue, Jan 02, 2018 at 07:38:54AM +0100, john doe wrote:
> Looks like 192.168.1.1 is not your default route.
What led you to that conclusion?
Cheers,
Tom
--
A good scapegoat is hard to find.
A guilty conscience is the mother of invention.
-- Carolyn Wells
signature.asc
Descr
On 1/2/2018 7:15 AM, David Wright wrote:
On Tue 02 Jan 2018 at 06:25:29 (+0100), john doe wrote:
On 1/2/2018 12:12 AM, Max Power wrote:
Hi guys,
with the new release of Debian 'Stretch', the route command has been replaced
but what other command returns the hostname of the modem/router gateway.
On Tue 02 Jan 2018 at 06:25:29 (+0100), john doe wrote:
> On 1/2/2018 12:12 AM, Max Power wrote:
> >Hi guys,
> >with the new release of Debian 'Stretch', the route command has been replaced
> >but what other command returns the hostname of the modem/router gateway...?
> ># route
> >gateway = home.t
On 1/2/2018 12:12 AM, Max Power wrote:
Hi guys,
with the new release of Debian 'Stretch', the route command has been replaced
but what other command returns the hostname of the modem/router gateway...?
# route
gateway = home.telecomitalia.it
# ip route
gateway = 192.168.1.1
Thanks for reply, Max
On 12/31/17 14:45, Sven Hartge wrote:
David Christensen wrote:
$ man 4 md
SCRUBBING AND MISMATCHES
...
If check was used, then no action is taken to handle the mismatch, it
is simply recorded. If repair was used, then a mismatch will be
repaire
On 01/01/2018 02:46 AM, Pascal Hambourg wrote:
> Le 01/01/2018 à 06:51, Tom Dial a écrit :
>> Upgrading a workstation from Jessie to Stretch I found that the original
>> disk partitioning left insufficient space for grub (re)install. The
>> system has two identical ~233 GiB disks, sda and sdb, par
Hi guys,
with the new release of Debian 'Stretch', the route command has been replaced
but what other command returns the hostname of the modem/router gateway...?
# route
gateway = home.telecomitalia.it
# ip route
gateway = 192.168.1.1
Thanks for reply, Max Power.
On Mon 01 Jan 2018 at 05:37:15 -0600, Richard Owlett wrote:
> On 01/01/2018 05:23 AM, Richard Owlett wrote:
> > As user "richard" I created 3 files.
> > I later wanted to protect them totally from accidental change.
> > For each file, I went to Properties->Permissions and changed Access for
> > Ow
Hi,
Richard Owlett
> I used "linux tutorial chmod chattr" [w/o quotes] in both DuckDuckGo and
> Google.
A general search topic would be "linux file permissions" and "chattr".
I can show you an example shell session on an ext4 filesystem.
I create a directory with a file and take away w-permissi
On Mon, Jan 01, 2018 at 07:13:19PM +0100, to...@tuxteam.de wrote:
The nice thing about chattr is that you can protect the
file's directory entry (which one?) from being deleted.
But I agree that using chattr without having first
understood chmod is like using a circular saw without
having first m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 01, 2018 at 06:11:59PM -, Dan Purgert wrote:
[...]
> Note that "write" permissions on a file only really comes into play when
> you're messing with a file in an editor (e.g. vim, emacs, nano,
> whatever). It does not necessarily prev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Owlett wrote:
> [...]
> I need a tutorial. Man pages are unsatisfactory. Sort of like giving
> someone a dictionary and expecting them to become competent writers.
In brief:
chmod - change "mode" bits (i.e. read / write / execute) based on
wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 01, 2018 at 01:01:50PM -0500, Michael Stone wrote:
> And forget chattr, it's just going to confuse things.
The nice thing about chattr is that you can protect the
file's directory entry (which one?) from being deleted.
But I agree that usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 01, 2018 at 11:49:01AM -0600, Richard Owlett wrote:
[...]
> It's one of those theory and ability to apply.
> That's why I asked for pointer suitable tutorial.
> [https://lists.debian.org/debian-user/2018/01/msg8.html]
Roughly in this
And forget chattr, it's just going to confuse things.
On 01/01/2018 11:34 AM, Michael Stone wrote:
On Mon, Jan 01, 2018 at 11:28:37AM -0600, Richard Owlett wrote:
WHY should one with "Read-only" access be able to delete it?
A number of people have already explained that the ability delete
requires write permission on the directory containing the
On Mon, Jan 01, 2018 at 11:28:37AM -0600, Richard Owlett wrote:
WHY should one with "Read-only" access be able to delete it?
A number of people have already explained that the ability delete
requires write permission on the directory containing the file. You
don't seem to have acknowledged th
On 01/01/2018 10:23 AM, David Wright wrote:
On Mon 01 Jan 2018 at 05:23:29 (-0600), Richard Owlett wrote:
As user "richard" I created 3 files.
I later wanted to protect them totally from accidental change.
For each file, I went to Properties->Permissions and changed Access
for Owner, Group, and
On Sunday, 31 Dec 2017 at 19:53, Brian wrote:
> Indeed; especially if you are coming from apt-get. But, if you think
> about it, do users want to keep all the debs they have downloaded?
I agree: removing the .deb files makes sense for most use cases.
> I'm moved to suggest that apt rather than a
On 01/01/2018 06:01 AM, Thomas Schmitt wrote:
Hi,
Richard Owlett wrote:
As user "richard" I was able to delete them with Caja.
To prevent renaming or deletion of a file, you need to prevent writing
to the directory which hosts it. (Actually you delete the "dirent", which
points to the inode.
On Mon 01 Jan 2018 at 05:23:29 (-0600), Richard Owlett wrote:
> As user "richard" I created 3 files.
> I later wanted to protect them totally from accidental change.
> For each file, I went to Properties->Permissions and changed Access
> for Owner, Group, and Others to "Read Only".
No, you set the
Hi,
Richard Owlett wrote:
> As user "richard" I was able to delete them with Caja.
To prevent renaming or deletion of a file, you need to prevent writing
to the directory which hosts it. (Actually you delete the "dirent", which
points to the inode. The inode gets deleted when its last dirent is g
On Mon 01 Jan 2018 at 05:37:15 -0600, Richard Owlett wrote:
> On 01/01/2018 05:23 AM, Richard Owlett wrote:
> > As user "richard" I created 3 files.
> > I later wanted to protect them totally from accidental change.
> > For each file, I went to Properties->Permissions and changed Access for
> > Ow
On 01/01/2018 05:23 AM, Richard Owlett wrote:
As user "richard" I created 3 files.
I later wanted to protect them totally from accidental change.
For each file, I went to Properties->Permissions and changed Access for
Owner, Group, and Others to "Read Only".
As user "richard" I was able to delete
On Mon, Jan 01, 2018 at 05:23:29AM -0600, Richard Owlett wrote:
> As user "richard" I created 3 files.
> I later wanted to protect them totally from accidental change.
> For each file, I went to Properties->Permissions and changed Access for
> Owner, Group, and Others to "Read Only".
> As user "ric
As user "richard" I created 3 files.
I later wanted to protect them totally from accidental change.
For each file, I went to Properties->Permissions and changed Access for
Owner, Group, and Others to "Read Only".
As user "richard" I was able to delete them with Caja.
*UNDESIRABLE*
As "root" I ch
Le 01/01/2018 à 06:51, Tom Dial a écrit :
Upgrading a workstation from Jessie to Stretch I found that the original
disk partitioning left insufficient space for grub (re)install. The
system has two identical ~233 GiB disks, sda and sdb, partitioned
identically:
Disk /dev/sda: 232.9 GiB, 25005935
31 matches
Mail list logo
