Re: Problem attempting to use xorriso

[Richard Owlett]

On 11/10/2016 9:49 PM, David Wright wrote:

On Thu 10 Nov 2016 at 17:05:06 (-0600), Richard Owlett wrote:

On 11/10/2016 1:52 PM, David Wright wrote:

On Thu 10 Nov 2016 at 04:53:47 (-0600), Richard Owlett wrote:


Yes, but not in the context of a sub-project from last few days.
I suspect what I aiming at might look like - the groups and
permission bits set at time partition created, thus avoiding games
with /etc/fstab .

richard@jessie-defaults:~$
richard@jessie-defaults:~$ ls -l /dev/sd*
brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1


 ↑ is there a purpose behind the missing w ?


Yes. My rational is in my rather verbose post
https://lists.debian.org/debian-user/2016/11/msg00361.html .
Linux evidently does not do things "my way" [apologies to a fast
food chain].


Should I take it that last sentence means you are aware root can write
over a file even if the permission is - , let alone r ,
so you have no precaution as well as no protection.

Cheers,
David.




It was a description of what I wanted, not what I could get. I 
suspect thinking in detail about "corner cases" is a good education.

Re: Problem attempting to use xorriso

[Curt]

On 2016-11-10, Richard Owlett  wrote:
>
> It may be close, I pre-date the Harvard MarkI. I am definitely 
> older than Linus Torvalds father ;)
>>

Is this the senile equivalent of a pissing contest? Or the pissing
equivalent of a senile contest?

-- 
“It is enough that the arrows fit exactly in the wounds that they have made.”
Franz Kafka

Re: Problem attempting to use xorriso

[Lisi Reisz]

On Friday 11 November 2016 10:07:42 Curt wrote:
> On 2016-11-10, Richard Owlett  wrote:
> > It may be close, I pre-date the Harvard MarkI. I am definitely
> > older than Linus Torvalds father ;)
>
> Is this the senile equivalent of a pissing contest? Or the pissing
> equivalent of a senile contest?

The pissing equivalent of a senile contest.

Lisi

Re: parted is ALMOST suitable

[Pascal Hambourg]

Le 08/11/2016 à 00:54, Brian a écrit :


When blkid is run as root it creates the file
/run/blkid/blkid.tab. A user running blkid only gets to see the contents
of blkid.tab.


That does not appear to be completely correct.
If I run blkid as a standard user after plugging a USB drive, it lists 
the USB drive partition, although blikd.tab was not modified.


$ /sbin/blkid | grep sdb
/dev/sdb1: LABEL="USB DISK" UUID="48DB-E077" TYPE="vfat"

$ grep sdb /etc/blkid.tab || echo not found
not found

However note that /dev/sdb* is owned by group "floppy" and my standard 
user account is a member of this group.

Re: parted is ALMOST suitable

[Brian]

On Fri 11 Nov 2016 at 15:38:07 +0100, Pascal Hambourg wrote:

> Le 08/11/2016 à 00:54, Brian a écrit :
> >
> >When blkid is run as root it creates the file
> >/run/blkid/blkid.tab. A user running blkid only gets to see the contents
> >of blkid.tab.
> 
> That does not appear to be completely correct.
> If I run blkid as a standard user after plugging a USB drive, it lists the
> USB drive partition, although blikd.tab was not modified.
> 
> $ /sbin/blkid | grep sdb
> /dev/sdb1: LABEL="USB DISK" UUID="48DB-E077" TYPE="vfat"
> 
> $ grep sdb /etc/blkid.tab || echo not found
> not found

As the manual says:

 CACHE_FILE=
   Overrides the standard location of the cache file. This setting
   can be overridden by the environment variable BLKID_FILE. Default
   is /run/blkid/blkid.tab, or /etc/blkid.tab on systems without a
   /run directory.
 
> However note that /dev/sdb* is owned by group "floppy" and my standard user
> account is a member of this group.

If you are on Jessie (and have not altered any udev rules) you have a
broken system. Please post the output of 'ls -l /etc/udev/rules.d'.

-- 
Brian.

Re: dd - proper use or more suitable program

[Andy Smith]

Hi Richard,

On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
> I was considering using dd to copy the entire drive to a *SINGLE*
> partition of a 1 TB drive with the intention making a "byte perfect"
> of of the defective drive to a new 300 GB drive at a later time to
> then attempt "data rescue". Partitions other than the first are
> evidently readable.
> 
> Suggestions/comments please.

You are better off using GNU ddrescue for taking images of
possibly-failing devices.

Amongst other issues, dd will either give up or produce zeroes when
it encounters problems whereas ddrescue will keep track of where it
was unable to read and keep trying.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: parted is ALMOST suitable

[Pascal Hambourg]

Le 11/11/2016 à 17:24, Brian a écrit :


As the manual says:

 CACHE_FILE=
   Overrides the standard location of the cache file. This setting
   can be overridden by the environment variable BLKID_FILE. Default
   is /run/blkid/blkid.tab, or /etc/blkid.tab on systems without a
   /run directory.


In Wheezy the man page does not mention /run, and there is no 
/run/blkid/blkid.tab.



However note that /dev/sdb* is owned by group "floppy" and my standard user
account is a member of this group.


If you are on Jessie (and have not altered any udev rules) you have a
broken system.


This computer runs Wheezy and I did not alter udev rules. Looks like 
things have changed with Jessie.

Re: parted is ALMOST suitable

[Brian]

On Fri 11 Nov 2016 at 18:09:33 +0100, Pascal Hambourg wrote:

> Le 11/11/2016 à 17:24, Brian a écrit :
> >
> >As the manual says:
> >
> > CACHE_FILE=
> >   Overrides the standard location of the cache file. This setting
> >   can be overridden by the environment variable BLKID_FILE. Default
> >   is /run/blkid/blkid.tab, or /etc/blkid.tab on systems without a
> >   /run directory.
> 
> In Wheezy the man page does not mention /run, and there is no
> /run/blkid/blkid.tab.
> 
> >>However note that /dev/sdb* is owned by group "floppy" and my standard user
> >>account is a member of this group.
> >
> >If you are on Jessie (and have not altered any udev rules) you have a
> >broken system.
> 
> This computer runs Wheezy and I did not alter udev rules. Looks like things
> have changed with Jessie.

Wheezy has /etc/udev/rules.d/91-permissions.rules; Jessie doesn't.

This thread has a short discussion on gparted and bug #439409. The bug
report was submitted for Wheezy and the behaviour you observe formed
the basis of an argument. The bug report now has a different complexion
but has still not been updated to reflect the altered situation.

-- 
Brian.

Re: dd - proper use or more suitable program

[Christian Seiler]

Hi,

Am 11. November 2016 17:57:27 MEZ, schrieb Andy Smith :
>Hi Richard,
>
>On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
>> I was considering using dd to copy the entire drive to a *SINGLE*
>> partition of a 1 TB drive with the intention making a "byte perfect"
>> of of the defective drive to a new 300 GB drive at a later time to
>> then attempt "data rescue". Partitions other than the first are
>> evidently readable.
>> 
>> Suggestions/comments please.
>
>You are better off using GNU ddrescue for taking images of
>possibly-failing devices.

Full ACK: GNU ddrescue has saved my data multiple times in the past, I can 
really recommend it. (The "log file" is very helpful with resuming at a later 
point in time if you had to cancel it.)

Just don't confuse it with dd_rescue, which I don't recommend unless you are an 
expert and have a very special case.

Regards,
Christian

Re: dd - proper use or more suitable program

[Nicolas George]

Le primidi 21 brumaire, an CCXXV, Andy Smith a écrit :
> You are better off using GNU ddrescue for taking images of
> possibly-failing devices.

IIRC, there is a catch there: there is another program with a very
similar name that does not work the same way. Be careful when installing
it.

> Amongst other issues, dd will either give up or produce zeroes when
> it encounters problems whereas ddrescue will keep track of where it
> was unable to read and keep trying.

For the record, when using dd to copy data from a damaged medium, always
use conv=noerror,sync. Without noerror, dd would stop at the first
error and without sync it would just skip the block, making the dump
useless.

But of course, as you say, ddrescue keeps a log of the parts that could
not be read, which is even more useful.

Also, I would advise to dump to a file, not a raw partition.


signature.asc
Description: Digital signature

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 09:47:40 -0600, Richard Owlett wrote:

> Several years ago I purchased an external 1 TB USB connected drive for
> backups.
> The base of the enclosure says it is a Seagate drive.
> Partitions:
>   #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
>   #2 is extended partition for remainder of drive
>   #5 is fat32 62.5 GiB [31.5 GiB used] with no label
> 
> 
> I successfully mounted partitions 1 and 5.  Both are readable and contain
> files from unknown Windows machines. On my Windows Desktop hardware
> C:\Documents and Settings\user\Recent indicates that it had been used on
> that machine back in 2011. There is similar evidence that it had been used
> on my Windows Laptop in 2012. Neither machine reports files with "goflex" in
> filename {case insensitive search}.
> 
> I attempted to label partition 5 with Gparted, but the "Label" menu option
> was greyed out.
> The "Label" option was available for partition 1. I had no problem creating
> partition 6 as fat32 and labeling it.
> 
> Any suggestions as to what the problem is?
> Is there another option that would allow me to label the partition with no
> other effects on that partition?

gparted for labelling a partition is overkill. Use dosfslabel.

-- 
Brian.

Re: Gparted will not label an existing FAT32 partition

[Nicolas George]

Le primidi 21 brumaire, an CCXXV, Brian a écrit :
> gparted for labelling a partition is overkill. Use dosfslabel.

dosfslabel label will not label a partition, it will label a filesystem.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: dd - proper use or more suitable program

[The Wanderer]

On 2016-11-11 at 12:37, Christian Seiler wrote:

> Hi,
> 
> Am 11. November 2016 17:57:27 MEZ, schrieb Andy Smith
> :
> 
>> Hi Richard,
>> 
>> On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:
>> 
>>> I was considering using dd to copy the entire drive to a
>>> *SINGLE* partition of a 1 TB drive with the intention making a
>>> "byte perfect" of of the defective drive to a new 300 GB drive at
>>> a later time to then attempt "data rescue". Partitions other than
>>> the first are evidently readable.
>>> 
>>> Suggestions/comments please.
>> 
>> You are better off using GNU ddrescue for taking images of
>> possibly-failing devices.
> 
> Full ACK: GNU ddrescue has saved my data multiple times in the past,
> I can really recommend it. (The "log file" is very helpful with
> resuming at a later point in time if you had to cancel it.)
> 
> Just don't confuse it with dd_rescue, which I don't recommend unless
> you are an expert and have a very special case.

There's also myrescue, which is similar in function to both but which
I've found easier and less confusing to use in the past - if perhaps
only because it eliminates the confusion about remembering which of the
other two is the one which is more problematic.

The trouble with all of these is that not only do you need a device with
enough space to store the entire device you're drawing from (ideally in
a file rather than on the device directly), to do it properly and safely
you also need enough extra space - on another device is fine - to store
the log file which gets created during the rescue process.

-- 
   The Wanderer can't figure out why he's now thinking of the game IVAN

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

wheezy, cannot change the address of eth1

[Gene Heskett]

Greetings folks;

I just bought an ethernet switch, but it is a smart switch, so I needed 
to bring up my eth1 interface at an address in the 192.168.0.xx range so 
I can talk to it.  But despite the fact that it is so specified 
in /etc/network/interfaces, no amount of stopping and restarting the 
networking makes it take effect, its stuck at the old 192.168.1.3 
address.

The output on screen for an /etc/init.d/networking restart for eth1 is:
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255   dev eth1 
label eth1
ip link set dev eth1   up
 ip route add default via 192.168.0.1  dev eth1 
RTNETLINK answers: File exists
Failed to bring up eth1.

I cannot change it with ifconfig either. And the manpage for ip may as 
well be in swahili, lots of unexplained terminology.

So, short of rebooting so the changed interfaces might take effect, but 
will they, what is this "File exists" error?.

Does anyone have a clue what may be wrong?

And 5 years after I had a big fight with RTNETLINK, whatever the heck 
that is, it is still keeping the cause of the error secret.

So, net experts, what do I do?

Thanks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Problem attempting to use xorriso

[Gene Heskett]

On Friday 11 November 2016 05:07:42 Curt wrote:

> On 2016-11-10, Richard Owlett  wrote:
> > It may be close, I pre-date the Harvard MarkI. I am definitely
> > older than Linus Torvalds father ;)
>
> Is this the senile equivalent of a pissing contest? Or the pissing
> equivalent of a senile contest?

And at 82, I suspect I am the older, but with a psa in the 10+ range, I 
don't enter any pissing contests. :(

How the heck did this thread degenerate to this?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Gparted will not label an existing FAT32 partition

[Reco]

Hi.

On Fri, 11 Nov 2016 18:59:29 +0100
Nicolas George  wrote:

> Le primidi 21 brumaire, an CCXXV, Brian a écrit :
> > gparted for labelling a partition is overkill. Use dosfslabel.
> 
> dosfslabel label will not label a partition, it will label a filesystem.

gparted does not label partitions either, it does label any supported
filesystem or swap inside a partition. Brian's advice is valid.

As for the original problem - gparted is a GNOME application, so it's
expected to silently refuse doing potentially dangerous operations.

Reco

Re: wheezy, cannot change the address of eth1

[Greg Wooledge]

On Fri, Nov 11, 2016 at 01:13:56PM -0500, Gene Heskett wrote:
> The output on screen for an /etc/init.d/networking restart for eth1 is:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 dev 
> eth1 
> label eth1
> ip link set dev eth1   up
>  ip route add default via 192.168.0.1  dev eth1 
> RTNETLINK answers: File exists
> Failed to bring up eth1.

Start by showing the contents of /etc/network/interfaces.

Then find out whether a DHCP client daemon is already running.  If you
installed with DHCP (the default) and then edited /e/n/i but didn't stop
dhclient beforehand, then ifdown won't know to kill dhclient and you'll
have to kill it by hand (or reboot).

ps auxw | egrep 'dhclient|dhcpcd'
kill if necessary
ifdown eth1
edit /etc/network/interfaces if necessary
ifup eth1

If this doesn't work, then show the output of "ip addr show eth1"
and the network-relevant parts of dmesg (e.g. "dmesg | grep eth" is
often a good start).

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 21:33:58 +0300, Reco wrote:

> As for the original problem - gparted is a GNOME application, so it's
> expected to silently refuse doing potentially dangerous operations.

And yet gparted(8) and the manual at

  http://gparted.org/display-doc.php%3Fname%3Dhelp-manual

indicate setting a file system label is supported. Are we looking at a
bug in gparted?

-- 
Brian.

Re: Gparted will not label an existing FAT32 partition

[Pascal Hambourg]

Le 11/11/2016 à 16:47, Richard Owlett a écrit :

Partitions:
  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
  #2 is extended partition for remainder of drive
  #5 is fat32 62.5 GiB [31.5 GiB used] with no label

(...)

I attempted to label partition 5 with Gparted, but the "Label" menu
option was greyed out.
The "Label" option was available for partition 1. I had no problem
creating partition 6 as fat32 and labeling it.


Gparted needs external software to enable some features.
According to , mtools is 
required to change the label on a FAT filesystem.

Re: Gparted will not label an existing FAT32 partition

[Reco]

Hi.

On Fri, 11 Nov 2016 18:52:06 +
Brian  wrote:

> On Fri 11 Nov 2016 at 21:33:58 +0300, Reco wrote:
> 
> > As for the original problem - gparted is a GNOME application, so it's
> > expected to silently refuse doing potentially dangerous operations.
> 
> And yet gparted(8) and the manual at
> 
>   http://gparted.org/display-doc.php%3Fname%3Dhelp-manual
> 
> indicate setting a file system label is supported. Are we looking at a
> bug in gparted?

Beats me as I don't know C++ gparted is written in, nor have any desire
to learn it. Plain C is enough for me, and there's strace for the cases
when it does not.

Presumably gparted checks if a partition is used by something (a mounted
filesystem maybe?) and fails silently (i.e. makes a button inactive) if
it considers such check successful.

Whenever such check is justified, and whenever the implementation of
the check is flawless is something left to be seen.

Personally I'd say it's not worth the trouble to investigate the
issue as dosfslabel should do the job without the (potentially
dangerous) need to run GUI tool as root. There's a reason they use
PolicyKit for nearly everything else which requires root in a modern
GNOME, after all.

Reco

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 20:07:24 +0100, Pascal Hambourg wrote:

> Le 11/11/2016 à 16:47, Richard Owlett a écrit :
> >Partitions:
> >  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
> >  #2 is extended partition for remainder of drive
> >  #5 is fat32 62.5 GiB [31.5 GiB used] with no label
> (...)
> >I attempted to label partition 5 with Gparted, but the "Label" menu
> >option was greyed out.
> >The "Label" option was available for partition 1. I had no problem
> >creating partition 6 as fat32 and labeling it.
> 
> Gparted needs external software to enable some features.
> According to , mtools is
> required to change the label on a FAT filesystem.

A nice resolution of the issue; tested to work. mtools is a Suggests: of
gparted. People will not get it on a default Debian.

-- 
Brian.

Re: wheezy, cannot change the address of eth1

[David Wright]

On Fri 11 Nov 2016 at 13:13:56 (-0500), Gene Heskett wrote:
> Greetings folks;
> 
> I just bought an ethernet switch, but it is a smart switch, so I needed 
> to bring up my eth1 interface at an address in the 192.168.0.xx range so 
> I can talk to it.  But despite the fact that it is so specified 
> in /etc/network/interfaces, no amount of stopping and restarting the 
> networking makes it take effect, its stuck at the old 192.168.1.3 
> address.
> 
> The output on screen for an /etc/init.d/networking restart for eth1 is:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 dev 
> eth1 
> label eth1
> ip link set dev eth1   up
>  ip route add default via 192.168.0.1  dev eth1 
> RTNETLINK answers: File exists
> Failed to bring up eth1.
> 
> I cannot change it with ifconfig either. And the manpage for ip may as 
> well be in swahili, lots of unexplained terminology.
> 
> So, short of rebooting so the changed interfaces might take effect, but 
> will they, what is this "File exists" error?.
> 
> Does anyone have a clue what may be wrong?
> 
> And 5 years after I had a big fight with RTNETLINK, whatever the heck 
> that is, it is still keeping the cause of the error secret.
> 
> So, net experts, what do I do?

Googling your error message, I think the third link tells you what it means
http://www.linuxquestions.org/questions/linux-networking-3/rtnetlink-answers-file-exists-error-when-doing-ifup-on-alias-eth1-1-on-rhel5-710766/
and the second might be a fix.
http://unix.stackexchange.com/questions/100588/using-ip-addr-instead-of-ifconfig-reports-rtnetlink-answers-file-exists-on-de

Cheers,
David.

Re: Gparted will not label an existing FAT32 partition

[David Wright]

On Fri 11 Nov 2016 at 18:59:29 (+0100), Nicolas George wrote:
> Le primidi 21 brumaire, an CCXXV, Brian a écrit :
> > gparted for labelling a partition is overkill. Use dosfslabel.
> 
> dosfslabel label will not label a partition, it will label a filesystem.

Does a partition have a label?

Cheers,
David.

Re: Gparted will not label an existing FAT32 partition

[Doug]

On 11/11/2016 01:07 PM, Pascal Hambourg wrote:

Le 11/11/2016 à 16:47, Richard Owlett a écrit :

Partitions:
  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
  #2 is extended partition for remainder of drive
  #5 is fat32 62.5 GiB [31.5 GiB used] with no label

(...)

I attempted to label partition 5 with Gparted, but the "Label" menu
option was greyed out.
The "Label" option was available for partition 1. I had no problem
creating partition 6 as fat32 and labeling it.


Gparted needs external software to enable some features.
According to , mtools is 
required to change the label on a FAT filesystem.



I wonder if there is a LIVE disk that includes the various external 
software files? It would be handy to have such a disk.

If anyone knows of such, please advise.

--doug

Re: Gparted will not label an existing FAT32 partition

[Nicolas George]

Le primidi 21 brumaire, an CCXXV, David Wright a écrit :
> Does a partition have a label?

Yes, depending on the partition scheme.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Layers for the package manager

[Nicolas George]

There is a feature in Debian that I find missing in Debian, I wonder if
other people would agree with me.

I call that feature "layered package manager".

Here is what it means. The system has "layers" defined, organized as a
directed acyclic graph, and packages are contained in layers. For example:

 base
   /   |  \
  /|   \
 v vv
nonfree  gnome  texlive
 \|  |
  \   |  |
   v  v  |
 proprep |
\|
 \   |
  v  v
   all

The idea is this: packages in a layer "see" the packages in the same layers
and in lower layers but not the packages in higher layers (in the drawing,
low and high are reversed). By "see", I mean the dependencies: a broken
dependencies in the proprep layer does not prevent me from upgrading
something in the gnome layer, or a broken dependency in the nonfree layer
does not block an upgrade in base.

When working in a layer, everything works exactly as if the higher layers
did not exist.

The lower layers are visible, though, and merged. For example, in the above
example, when installing something in proprep, if it needs a dependency that
is installed in either nonfree, base or gnome, it will just use it. If is is
not installer anywhere, then it gets installed in proprep itself.

Of course, it means that packages in higher layers can easily become broken.
It is not a bug, it is a feature. Better a system with a few inessential
packages partially broken than a system vulnerable because a security
upgrade on a base package could not be performed. Or than removing the
packages altogether.

A higher-level tool would be necessary to help handling things. For example,
if I try to remove a gnome package necessary for proprep, it proposes me to
reinstall it in proprep instead. Or it would propose a command to perform a
full upgrade in each layer in turn, in a single step.

Users need to be able to choose in which layer they work, including changing
on the fly. The admin should be able to choose the layer for all daemons
too.

Of course, a lot of details would need to be ironed. What happens if the
same package comes in different version from several parents? Can we remove
(=hide) in a higher layer a package from a lower one? Etc.

But I think it would make a very useful tool. Here are the benefits I
expect:

Being able to install incompatible packages at the same time. Of course, I
would need to switch layer to use them both, but that is not a big deal.

Isolate servers. Run servers in a layer where the compilers and other
development tools are not visible. It does not actually add any security but
it may help mitigate or slow down an attack.

Install packages on different filesystems depending on their usefulness:
base system on small SSD, desktop environment and other large packages on
larger but slower HDD, huge docs and games on even slower NAS.

Most important: Being able to add third-party repositories with less worry.

Right now, if I consider adding a third-party repository, or installing a
third-party package, I need to trust both its honesty (of course, any
package can contain a backdoor and take root access) and it seriousness.
With layers, I still need to trust its honesty, of course, but if I install
it in a separate layer, I do not have to worry that it may break something
else or block a security upgrade. It isolated.

So, this is what I dream of. Does anybody have remarks? Know projects with
similar goals? Distributions that have that feature? Other means of
achieving a similar result with Debian?

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 19:30:51 -0600, Doug wrote:

> 
> On 11/11/2016 01:07 PM, Pascal Hambourg wrote:
> >Le 11/11/2016 à 16:47, Richard Owlett a écrit :
> >>Partitions:
> >>  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
> >>  #2 is extended partition for remainder of drive
> >>  #5 is fat32 62.5 GiB [31.5 GiB used] with no label
> >(...)
> >>I attempted to label partition 5 with Gparted, but the "Label" menu
> >>option was greyed out.
> >>The "Label" option was available for partition 1. I had no problem
> >>creating partition 6 as fat32 and labeling it.
> >
> >Gparted needs external software to enable some features.
> >According to , mtools is
> >required to change the label on a FAT filesystem.
> >
> >
> I wonder if there is a LIVE disk that includes the various external software
> files? It would be handy to have such a disk.
> If anyone knows of such, please advise.

  http://cdimage.debian.org/debian-cd/current-live/i386/iso-hybrid/

has files with package contents. Any use?

-- 
Brian.

Re: Gparted will not label an existing FAT32 partition

[David Wright]

On Fri 11 Nov 2016 at 20:32:52 (+0100), Nicolas George wrote:
> Le primidi 21 brumaire, an CCXXV, David Wright a écrit :
> > Does a partition have a label?
> 
> Yes, depending on the partition scheme.

Any reference. You see, I find label a very slippery word.
You can label a disk at almost every level: a sticky label,
a disklabel (partition table), a filesystem label, a volume label
(perhaps those two are equivalent), and whatever is handled by
devlabel (which might be historic).

So I'm unsure what you mean by a partition label, where it's
stored, and how it differs from a filesystem label.
Is it new-fangled?

Cheers,
David.

Re: Gparted will not label an existing FAT32 partition

[Michael Milliman]

On 11/11/2016 09:47 AM, Richard Owlett wrote:
Several years ago I purchased an external 1 TB USB connected drive for 
backups.

The base of the enclosure says it is a Seagate drive.
Partitions:
  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
  #2 is extended partition for remainder of drive
  #5 is fat32 62.5 GiB [31.5 GiB used] with no label


I successfully mounted partitions 1 and 5.  Both are readable and 
contain files from unknown Windows machines. On my Windows Desktop 
hardware C:\Documents and Settings\user\Recent indicates that it had 
been used on that machine back in 2011. There is similar evidence that 
it had been used on my Windows Laptop in 2012. Neither machine reports 
files with "goflex" in filename {case insensitive search}.


I attempted to label partition 5 with Gparted, but the "Label" menu 
option was greyed out.
The "Label" option was available for partition 1. I had no problem 
creating partition 6 as fat32 and labeling it.


It has been some time since I have had to do anything similar. However, 
as I recall, if the partition is mounted, gparted will not add/change 
the label.  You have to unmount the partition first, which gparted will 
do (with a different command).  Once unmounted, gparted is then willing 
to modify the partition.  I know this sounds obvious, but then sometimes 
it is the most obvious things we overlook:-)



Any suggestions as to what the problem is?
Is there another option that would allow me to label the partition 
with no other effects on that partition?




TIA



--
73's
Mike, WB5VQX

Re: Gparted will not label an existing FAT32 partition

[Seeker]

On 11/11/2016 5:30 PM, Doug wrote:


On 11/11/2016 01:07 PM, Pascal Hambourg wrote:

Le 11/11/2016 à 16:47, Richard Owlett a écrit :

Partitions:
  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
  #2 is extended partition for remainder of drive
  #5 is fat32 62.5 GiB [31.5 GiB used] with no label

(...)

I attempted to label partition 5 with Gparted, but the "Label" menu
option was greyed out.
The "Label" option was available for partition 1. I had no problem
creating partition 6 as fat32 and labeling it.


Gparted needs external software to enable some features.
According to , mtools is
required to change the label on a FAT filesystem.



I wonder if there is a LIVE disk that includes the various external
software files? It would be handy to have such a disk.
If anyone knows of such, please advise.

--doug



I like SystemRescueCd for partitioning/troubleshooting.

https://www.system-rescue-cd.org/SystemRescueCd_Homepage

Later, Seeker

Re: Gparted will not label an existing FAT32 partition

[Nicolas George]

Le primidi 21 brumaire, an CCXXV, David Wright a écrit :
> Any reference. You see, I find label a very slippery word.
> You can label a disk at almost every level: a sticky label,

True, but not really relevant.

> a disklabel (partition table),

This is BSD slang. But this was what I was referring to.

>a filesystem label,

Indeed. That is the most common one.

>a volume label
> (perhaps those two are equivalent),

I do not think "volume" means anything in the Linux world.

> and whatever is handled by
> devlabel (which might be historic).

It looks like a tool to make symlinks based on the above labels.

> So I'm unsure what you mean by a partition label, where it's
> stored, and how it differs from a filesystem label.

Well, the filesystem label is stored in the filesystem metadata, i.e.
probably the superblock. The partition label is stored in the partitions
metadata, i.e. the "partition table".

> Is it new-fangled?

MBR-style partition tables do not contain labels, if that is what you
are asking. But GPT does.


signature.asc
Description: Digital signature

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 13:51:41 -0600, Michael Milliman wrote:

> On 11/11/2016 09:47 AM, Richard Owlett wrote:
> >Several years ago I purchased an external 1 TB USB connected drive for
> >backups.
> >The base of the enclosure says it is a Seagate drive.
> >Partitions:
> >  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
> >  #2 is extended partition for remainder of drive
> >  #5 is fat32 62.5 GiB [31.5 GiB used] with no label
> >
> >
> >I successfully mounted partitions 1 and 5.  Both are readable and contain
> >files from unknown Windows machines. On my Windows Desktop hardware
> >C:\Documents and Settings\user\Recent indicates that it had been used on
> >that machine back in 2011. There is similar evidence that it had been used
> >on my Windows Laptop in 2012. Neither machine reports files with "goflex"
> >in filename {case insensitive search}.
> >
> >I attempted to label partition 5 with Gparted, but the "Label" menu option
> >was greyed out.
> >The "Label" option was available for partition 1. I had no problem
> >creating partition 6 as fat32 and labeling it.
> >
> It has been some time since I have had to do anything similar. However, as I
> recall, if the partition is mounted, gparted will not add/change the label.
> You have to unmount the partition first, which gparted will do (with a
> different command).  Once unmounted, gparted is then willing to modify the
> partition.  I know this sounds obvious, but then sometimes it is the most
> obvious things we overlook:-)

You are 100% correct about not having the partition mounted. It does
lead to the labelling option being greyed out. Easy enough to overlook,
as you say.

It turns out the actual issue is one of not having a suggested package,
mtools, installed.

-- 
Brian.

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 20:53:17 +0100, Nicolas George wrote:

> Le primidi 21 brumaire, an CCXXV, David Wright a écrit :
> > Any reference. You see, I find label a very slippery word.
> > You can label a disk at almost every level: a sticky label,
> 
> True, but not really relevant.
> 
> > a disklabel (partition table),
> 
> This is BSD slang. But this was what I was referring to.
> 
> >  a filesystem label,
> 
> Indeed. That is the most common one.
> 
> >  a volume label
> > (perhaps those two are equivalent),
> 
> I do not think "volume" means anything in the Linux world.
> 
> >   and whatever is handled by
> > devlabel (which might be historic).
> 
> It looks like a tool to make symlinks based on the above labels.
> 
> > So I'm unsure what you mean by a partition label, where it's
> > stored, and how it differs from a filesystem label.
> 
> Well, the filesystem label is stored in the filesystem metadata, i.e.
> probably the superblock. The partition label is stored in the partitions
> metadata, i.e. the "partition table".
> 
> > Is it new-fangled?
> 
> MBR-style partition tables do not contain labels, if that is what you
> are asking. But GPT does.

May I say I appreciated the correction about labels being applied to
file systems and not partitions. I'd done a copy and paste (with a
change to a spelling) without any thought in mind to disabuse the OP
about the technical aspects. It seemed more important to get him on
the road.

But, this is getting interesting.

-- 
Brian.

Re: Gparted will not label an existing FAT32 partition

[Richard Owlett]

On 11/11/2016 11:57 AM, Brian wrote:

On Fri 11 Nov 2016 at 09:47:40 -0600, Richard Owlett wrote:


Several years ago I purchased an external 1 TB USB connected drive for
backups.
The base of the enclosure says it is a Seagate drive.
Partitions:
   #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex Drive"
   #2 is extended partition for remainder of drive
   #5 is fat32 62.5 GiB [31.5 GiB used] with no label


I successfully mounted partitions 1 and 5.  Both are readable and contain
files from unknown Windows machines. On my Windows Desktop hardware
C:\Documents and Settings\user\Recent indicates that it had been used on
that machine back in 2011. There is similar evidence that it had been used
on my Windows Laptop in 2012. Neither machine reports files with "goflex" in
filename {case insensitive search}.

I attempted to label partition 5 with Gparted, but the "Label" menu option
was greyed out.
The "Label" option was available for partition 1. I had no problem creating
partition 6 as fat32 and labeling it.

Any suggestions as to what the problem is?
Is there another option that would allow me to label the partition with no
other effects on that partition?


gparted for labelling a partition is overkill. Use dosfslabel.



But Gparted was already active for other reasons ;/

set domain name in Debian `

[Glenn English]

This seems to be a common question -- it's all over the 'Net. 

I have to change the domain name of a Jessie server I'm working on. How do you 
do it? (Aside from putting the FQDN in /etc/hostname, which kinda works.)

I've seen several posts on the subject, all contradicting each other, and none 
of them work. The answer must be in this list's archive, but I can't find it. 

The most common answer has to do with /etc/hosts, but the data is already in 
there (at the top, with the correct IP), and the system isn't impressed 
(rebooting makes no difference). Man is no help. Editing /etc/resolv.conf has 
no effect. Books on Debian and Linux don't help, although it seems to be 
trivial on RedHat.

/proc/sys/domainname says "(none)". hostname -f gives the old domain name 
(where does it get it). grep -ir doesn't find the old name string anywhere in 
/etc or in /lib.

I know it must be simple to do -- the installer does it without downloading a C 
library, but it must be in a secret place I don't know about...

-- 
Glenn English

Re: Gparted will not label an existing FAT32 partition

[Richard Owlett]

On 11/11/2016 1:22 PM, David Wright wrote:

On Fri 11 Nov 2016 at 18:59:29 (+0100), Nicolas George wrote:

Le primidi 21 brumaire, an CCXXV, Brian a écrit :

gparted for labelling a partition is overkill. Use dosfslabel.


dosfslabel label will not label a partition, it will label a filesystem.


Does a partition have a label?

Cheers,
David.




Apparently it does according to the authors of Gparted.
Who am I to argue?

Re: set domain name in Debian `

[Greg Wooledge]

On Fri, Nov 11, 2016 at 01:27:28PM -0700, Glenn English wrote:
> This seems to be a common question -- it's all over the 'Net. 
> 
> I have to change the domain name of a Jessie server I'm working on. How do 
> you do it? (Aside from putting the FQDN in /etc/hostname, which kinda works.)

That depends on what you mean.

Normally the only time a domain name is used is when you look up a
hostname in DNS but you don't specify the fully qualified name.  Like,
if you're on your corporate LAN and you type "ping server7", your system
is probably configured so that it knows to look up "server7.example.com"
or whatever is appropriate for your organization.

That usage of the concept of "domain name" is defined by the "search"
lines in /etc/resolv.conf.  If your corporate environment is set up for
it, then you probably get these lines added to your resolv.conf by DHCP
and you don't have to do anything at all.

If your resolv.conf doesn't get the default search domain that you want,
then you can edit /etc/dhcp/dhclient.conf to fix things.

Now, on the other hand, you might mean something like "I am setting up
a web server on the Internet and I want people to be able to get to it
under such-and-such a name."  Then it's an ENTIRELY different question
and it has nothing at all to do with your /etc/hosts or /etc/resolv.conf
files.  It has to do with domain name registrars and DNS configuration,
and then (probably) with web server virtual host configuration.
What you see when you type "hostname" is COMPLETELY IRRELEVANT.

There's another variant of this question that involves email server
configuration, but I consider this the least likely interpretation.

Then, there's a concept of domain names in NIS, and probably in Kerberos,
and probably in LDAP, though of those things I only know NIS.

So... what are you actually trying to do?  Be very specific.

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 14:45:16 -0600, Richard Owlett wrote:

> On 11/11/2016 1:22 PM, David Wright wrote:
> >On Fri 11 Nov 2016 at 18:59:29 (+0100), Nicolas George wrote:
> >>Le primidi 21 brumaire, an CCXXV, Brian a écrit :
> >>>gparted for labelling a partition is overkill. Use dosfslabel.
> >>
> >>dosfslabel label will not label a partition, it will label a filesystem.
> >
> >Does a partition have a label?
> >
> >Cheers,
> >David.
> >
> >
> 
> Apparently it does according to the authors of Gparted.
> Who am I to argue?

How relevant is that to your immediate problem? Or have you forgotten
about what you asked?

Did installing mtools solve it? That is the essential point.

Once you sort that you can argue to your heart's content about labels
and what gparted says.

-- 
Brian.

Re: Gparted will not label an existing FAT32 partition

[Doug]

On 11/11/2016 01:42 PM, Brian wrote:

On Fri 11 Nov 2016 at 19:30:51 -0600, Doug wrote:


On 11/11/2016 01:07 PM, Pascal Hambourg wrote:



/snip/

Gparted needs external software to enable some features.
According to , mtools is
required to change the label on a FAT filesystem.



I wonder if there is a LIVE disk that includes the various external software
files? It would be handy to have such a disk.
If anyone knows of such, please advise.

   http://cdimage.debian.org/debian-cd/current-live/i386/iso-hybrid/

has files with package contents. Any use?

I'll take a look at that--thanx!

--doug

Re: Gparted will not label an existing FAT32 partition

[Richard Owlett]

On 11/11/2016 7:30 PM, Doug wrote:


On 11/11/2016 01:07 PM, Pascal Hambourg wrote:

Le 11/11/2016 à 16:47, Richard Owlett a écrit :

Partitions:
  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex
Drive"
  #2 is extended partition for remainder of drive
  #5 is fat32 62.5 GiB [31.5 GiB used] with no label

(...)

I attempted to label partition 5 with Gparted, but the "Label"
menu
option was greyed out.
The "Label" option was available for partition 1. I had no
problem
creating partition 6 as fat32 and labeling it.


Gparted needs external software to enable some features.
According to ,
mtools is required to change the label on a FAT filesystem.



I wonder if there is a LIVE disk that includes the various
external software files? It would be handy to have such a disk.
If anyone knows of such, please advise.

--doug




YES there is. Goto http://gparted.org/download.php .

Re: Gparted will not label an existing FAT32 partition

[Richard Owlett]

On 11/11/2016 1:51 PM, Michael Milliman wrote:



On 11/11/2016 09:47 AM, Richard Owlett wrote:

Several years ago I purchased an external 1 TB USB connected
drive for backups.
The base of the enclosure says it is a Seagate drive.
Partitions:
  #1 is ntfs 293 GiB [146 GiB used] labeled "FreeAgent GoFlex
Drive"
  #2 is extended partition for remainder of drive
  #5 is fat32 62.5 GiB [31.5 GiB used] with no label


I successfully mounted partitions 1 and 5.  Both are readable
and contain files from unknown Windows machines. On my Windows
Desktop hardware C:\Documents and Settings\user\Recent
indicates that it had been used on that machine back in 2011.
There is similar evidence that it had been used on my Windows
Laptop in 2012. Neither machine reports files with "goflex" in
filename {case insensitive search}.

I attempted to label partition 5 with Gparted, but the "Label"
menu option was greyed out.
The "Label" option was available for partition 1. I had no
problem creating partition 6 as fat32 and labeling it.


It has been some time since I have had to do anything similar.
However, as I recall, if the partition is mounted, gparted will
not add/change the label.  You have to unmount the partition
first, which gparted will do (with a different command).  Once
unmounted, gparted is then willing to modify the partition.  I
know this sounds obvious, but then sometimes it is the most
obvious things we overlook:-)


Any suggestions as to what the problem is?
Is there another option that would allow me to label the
partition with no other effects on that partition?



TIA





I've been bit by that a number of times. None of the partitions 
had been mounted.


The problem was missing mtools. When I had used Synaptic to 
install Gparted it had pulled in dostools but not mtools. Is that 
a "bug" or "annoyance"?

Re: wheezy, cannot change the address of eth1

[Darac Marjal]

On 11/11/16 18:13, Gene Heskett wrote:
> Greetings folks;
>
> I just bought an ethernet switch, but it is a smart switch, so I needed 
> to bring up my eth1 interface at an address in the 192.168.0.xx range so 
> I can talk to it.  But despite the fact that it is so specified 
> in /etc/network/interfaces, no amount of stopping and restarting the 
> networking makes it take effect, its stuck at the old 192.168.1.3 
> address.
>
> The output on screen for an /etc/init.d/networking restart for eth1 is:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 dev 
> eth1 
> label eth1
> ip link set dev eth1   up
>  ip route add default via 192.168.0.1  dev eth1 
> RTNETLINK answers: File exists
> Failed to bring up eth1.
>
> I cannot change it with ifconfig either. And the manpage for ip may as 
> well be in swahili, lots of unexplained terminology.
>
> So, short of rebooting so the changed interfaces might take effect, but 
> will they, what is this "File exists" error?.

"File exists" is, I think, a generic translation of an error code. "ip"
is trying to create a default route and is told, by the kernel, "that
route already exists: EEXISTS". "ip" then passes "EEXISTS" to an error
code translation routing which spits out "File exists".

To cut a long story short, you can't add a default route if you already
have one (well, technically you can, but you'd need to provide more
information). You probably have a default route sending traffic over eth0.

>
> Does anyone have a clue what may be wrong?
>
> And 5 years after I had a big fight with RTNETLINK, whatever the heck 
> that is, it is still keeping the cause of the error secret.
>
> So, net experts, what do I do?
>
> Thanks.
>
> Cheers, Gene Heskett




signature.asc
Description: OpenPGP digital signature

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Jonathan Dowland]

On Thu, Nov 10, 2016 at 07:39:22PM +0100, Thomas Schmitt wrote:
> > Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.
> 
> Was that already with -read_fs "norock" ?

No, I didn't try that yet; I'll try that when I next take a look (probably
Monday). Thanks for the suggestion!

> Name collisions should not occur in any filesystem tree.
> There is a limit of 255 characters per path component. Longer names get
> truncated and could then collide. But that's very unlikely because the
> truncated names contain a string with the MD5 of the untruncated name.
> 
> Are there preceeding warnings of form
> 
>   File name collision resolved with %s . Now: %s
> 
> ?
> The path and file name inserted into "%s" would be of interest.

Yep - I'll put a full log of the output up somewhere and reply with it.
(I'm hoping to be able to either provide some interesting ISOs or zero
the file contents and provide the result or truncate after the TOC,
depending on what is one the discs!)

> Might "240206" be a date stamp ? (24 Feb 2006 ?)

Yep quite likely. That means I didn't burn it, which isn't that
surprising I suppose, because I can't remember burning it :) (stuff
of my Wife's)

> Have a nice day :)

you too!

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: Gparted will not label an existing FAT32 partition

[Thomas Schmitt]

Hi,

David Wright wrote:
> So I'm unsure what you mean by a partition label, where it's
> stored, and how it differs from a filesystem label.

See "Partition name (36 UTF-16LE code units)" in
  https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_entries

This describes the GPT partition table which is the newer of the
two usual partition table formats. Lots of partitions are possible
on a disk.

The older format is MBR with 4 primary partitions and 4 logical
ones in one of the primary partitions. Also known as "MSDOS"
partition table. No partition names there.


Have a nice day :)

Thomas

RTL8192CE PCIe Wireless Network Adapter not working

[Rainer Dorsch]

Hi,

I run a 

root@Silberkiste:~# lspci |grep Network
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192CE PCIe 
Wireless Network Adapter (rev 01)
root@Silberkiste:~# 

on Debian jessie with a recent kernel from backports

root@Silberkiste:~# uname -a
Linux Silberkiste 4.7.0-0.bpo.1-amd64 #1 SMP Debian 4.7.8-1~bpo8+1 (2016-10-19) 
x86_64 GNU/Linux
root@Silberkiste:~# 

I added the adapter to /etc/network/interfaces:

root@Silberkiste:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

# WLAN interface
allow-hotplug wlan0



iface wlan0 inet dhcp
wpa-ssid LS6
wpa-psk 
#wpa-driver wext
#wpa-key-mgmt WPA-PSK

root@Silberkiste:~# 


But I do not get the network up and running:

dmesg states

[3.787915] rtl8192ce: Using firmware rtlwifi/rtl8192cfw.bin
[3.788155] [drm] ring test on 0 succeeded in 2 usecs
[3.789155] [drm] ring test on 1 succeeded in 2 usecs
[3.789195] [drm] ring test on 2 succeeded in 3 usecs
[3.789428] [drm] ring test on 3 succeeded in 4 usecs
[3.789437] [drm] ring test on 4 succeeded in 4 usecs
[3.792511] usbcore: registered new interface driver snd-usb-audio
[3.794410] rtl8192ce :01:00.0: firmware: direct-loading firmware 
rtlwifi/rtl8192cfw.bin
[3.807820] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[3.808174] rtlwifi: rtlwifi: wireless switch is on
[3.837689] [drm] ring test on 5 succeeded in 1 usecs
[3.839324] input: PC Speaker as /devices/platform/pcspkr/input/input9
[3.845309] random: nonblocking pool is initialized
[3.857768] [drm] UVD initialized successfully.
[3.882699] AVX version of gcm_enc/dec engaged.
[3.882705] AES CTR mode by8 optimization enabled
[3.924616] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[3.956481] r8169 :02:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8168e-3.fw
[3.969039] [drm] ring test on 6 succeeded in 16 usecs
[3.969054] [drm] ring test on 7 succeeded in 3 usecs
[3.969056] [drm] VCE initialized successfully.
[3.971066] [drm] ib test on ring 0 succeeded in 0 usecs
[4.079816] r8169 :02:00.0 eth0: link down
[4.079917] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[4.080361] r8169 :02:00.0 eth0: link down
[4.089391] Adding 7815616k swap on /dev/sdb2.  Priority:-1 extents:1 
across:7815616k FS
[4.089836] kvm: Nested Virtualization enabled
[4.089841] kvm: Nested Paging enabled
[4.469553] [drm] ib test on ring 1 succeeded in 0 usecs
[4.678134] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready


/sbin/ifconfig shows:

root@Silberkiste:~# /sbin/ifconfig 
eth0  Link encap:Ethernet  Hardware Adresse 74:d4:35:7b:0d:c4  
  inet Adresse:192.168.178.56  Bcast:192.168.178.255  
Maske:255.255.255.0
  inet6-Adresse: fd00::76d4:35ff:fe7b:dc4/64 Gültigkeitsbereich:Global
  inet6-Adresse: fe80::76d4:35ff:fe7b:dc4/64 
Gültigkeitsbereich:Verbindung
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
  RX packets:3582 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2828 errors:0 dropped:0 overruns:0 carrier:0
  Kollisionen:0 Sendewarteschlangenlänge:1000 
  RX bytes:2784351 (2.6 MiB)  TX bytes:534169 (521.6 KiB)

loLink encap:Lokale Schleife  
  inet Adresse:127.0.0.1  Maske:255.0.0.0
  inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
  UP LOOPBACK RUNNING  MTU:65536  Metrik:1
  RX packets:110 errors:0 dropped:0 overruns:0 frame:0
  TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
  Kollisionen:0 Sendewarteschlangenlänge:1 
  RX bytes:15055 (14.7 KiB)  TX bytes:15055 (14.7 KiB)

wlan0 Link encap:Ethernet  Hardware Adresse 30:5a:3a:5d:6f:df  
  UP BROADCAST MULTICAST  MTU:1500  Metrik:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  Kollisionen:0 Sendewarteschlangenlänge:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@Silberkiste:~# 

Any idea why that is not working is welcome.

Many thanks
Rainer


-- 
Rainer Dorsch
http://bokomoko.de/

Re: dd - proper use or more suitable program

[Richard Owlett]

On 11/11/2016 12:13 PM, The Wanderer wrote:

On 2016-11-11 at 12:37, Christian Seiler wrote:


Hi,

Am 11. November 2016 17:57:27 MEZ, schrieb Andy Smith
:


Hi Richard,

On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:


I was considering using dd to copy the entire drive to a
*SINGLE* partition of a 1 TB drive with the intention making a
"byte perfect" of of the defective drive to a new 300 GB drive at
a later time to then attempt "data rescue". Partitions other than
the first are evidently readable.

Suggestions/comments please.


You are better off using GNU ddrescue for taking images of
possibly-failing devices.


Full ACK: GNU ddrescue has saved my data multiple times in the past,
I can really recommend it. (The "log file" is very helpful with
resuming at a later point in time if you had to cancel it.)

Just don't confuse it with dd_rescue, which I don't recommend unless
you are an expert and have a very special case.


There's also myrescue, which is similar in function to both but which
I've found easier and less confusing to use in the past - if perhaps
only because it eliminates the confusion about remembering which of the
other two is the one which is more problematic.


http://myrescue.sourceforge.net/ doesn't indicate whether it will 
attempt to do what I want.
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html 
is long and not oriented to first time user. But explicitly 
claims to do what I want. I'll have to re-read after a good 
night's sleep.





The trouble with all of these is that not only do you need a device with
enough space to store the entire device you're drawing from (ideally in
a file rather than on the device directly), to do it properly and safely
you also need enough extra space - on another device is fine - to store
the log file which gets created during the rescue process.



How big might the logfile be when trying to recover a known flaky 
300 GB drive. I've lots of space? Some convienient, some not.

Re: dd - proper use or more suitable program

[Richard Owlett]

On 11/11/2016 11:49 AM, Nicolas George wrote:

Le primidi 21 brumaire, an CCXXV, Andy Smith a écrit :

You are better off using GNU ddrescue for taking images of
possibly-failing devices.


IIRC, there is a catch there: there is another program with a very
similar name that does not work the same way. Be careful when installing
it.


Jessie DVD's catch that. What Synaptic fetches is gddrescue, but 
after loading you invoke it as just ddrescue.





Amongst other issues, dd will either give up or produce zeroes when
it encounters problems whereas ddrescue will keep track of where it
was unable to read and keep trying.


For the record, when using dd to copy data from a damaged medium, always
use conv=noerror,sync. Without noerror, dd would stop at the first
error and without sync it would just skip the block, making the dump
useless.

But of course, as you say, ddrescue keeps a log of the parts that could
not be read, which is even more useful.

Also, I would advise to dump to a file, not a raw partition.



I was wondering about that.
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html 
is not first time user friendly. Will re-read after a good 
night's sleep. Will also look for appropriate tutorials. Suggestions?

Re: Gparted will not label an existing FAT32 partition

[Doug]

/snip/

Gparted needs external software to enable some features.
According to ,
mtools is required to change the label on a FAT filesystem.



I wonder if there is a LIVE disk that includes the various
external software files? It would be handy to have such a disk.
If anyone knows of such, please advise.

--doug




YES there is. Goto http://gparted.org/download.php .




OK, Thanx. I have an older copy--I don't know if it has all the supplemental
files--so I just downloaded this one and I'll burn a copy. This program 
is one

of the most useful programs that one should have in his arsenal! It is
perfectly clear as to what's going on, where, and I use it in prep for any
new install, rather than whatever is on the install disk, since it shows
everything on the drive, where it is, how big it is, etc., and allows you to
move and shrink things that may make the new install fit and work
better. (You can even shrink Windows with it!)

--doug

Re: Gparted will not label an existing FAT32 partition

[Richard Owlett]

On 11/11/2016 9:38 PM, Doug wrote:

/snip/

Gparted needs external software to enable some features.
According to ,
mtools is required to change the label on a FAT filesystem.



I wonder if there is a LIVE disk that includes the various
external software files? It would be handy to have such a disk.
If anyone knows of such, please advise.

--doug




YES there is. Goto http://gparted.org/download.php .




OK, Thanx. I have an older copy--I don't know if it has all the
supplemental
files--so I just downloaded this one and I'll burn a copy. This
program is one
of the most useful programs that one should have in his arsenal!
It is
perfectly clear as to what's going on, where, and I use it in
prep for any
new install, rather than whatever is on the install disk, since
it shows
everything on the drive, where it is, how big it is, etc., and
allows you to
move and shrink things that may make the new install fit and work
better. (You can even shrink Windows with it!)

--doug


My Live CD is rev 0.11.0 , it apparently has everything.
Jessie has 0.19.0 .
The website, I noticed, has a later rev.

Re: Gparted will not label an existing FAT32 partition

[Brian]

On Fri 11 Nov 2016 at 15:03:57 -0600, Richard Owlett wrote:

> The problem was missing mtools. When I had used Synaptic to install Gparted
> it had pulled in dostools but not mtools. Is that a "bug" or "annoyance"?

Not installing a recommended package on a default Debian would be a bug.
Not installing a suggested package isn't.

-- 
Brian.

Re: set domain name in Debian `

[Glenn English]

> On Nov 11, 2016, at 1:52 PM, Greg Wooledge  wrote:
> 
> So... what are you actually trying to do?  Be very specific.

Well, I'd like the domain name to be the same everywhere. hostname -f and whois 
 (that currently returns the ISP's info) and /etc/hosts and host  and a 
DNS lookup and everything else I can't think of right now should all report the 
same thing: the name of the domain I'm trying to set up this server for.

As yet, I'm looking at hostname -f (plain hostname gets the host right), and 
ping'ing and SSH'ing using /etc/hosts (that works). I've set my local DNS to 
look first at hosts, then at DNS.

The DNS server isn't set up yet. mailname is just the host. postfix is the SMTP 
server -- editing its config doesn't seem to do anything.

I've moved to a new domain, and I copied lots of data from the old server. The 
domain name I see is that of the old server.

-- 
Glenn English

Re: Gparted will not label an existing FAT32 partition

[Pascal Hambourg]

Le 11/11/2016 à 22:17, Thomas Schmitt a écrit :


The older format is MBR with 4 primary partitions and 4 logical
ones in one of the primary partitions.


Huh ? The number of logical partitions is unlimited.

Does hdparm not run at startup anymore?

[Rainer Dorsch]

Hi,

I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, apm 
does not change. Interesting enough a /etc/init.d/hdparm restart fixes the 
problem:


root@Silberkiste:~# cat /etc/hdparm.conf
## This is the default configuration for hdparm for Debian.  It is a 
## rather simple script, so please follow the following guidelines :)
## Any line that begins with a comment is ignored - add as many as you 
## like.  Note that an in-line comment is not supported.  If a line 
## consists of whitespace only (tabs, spaces, carriage return), it will be
## ignored, so you can space control fields as you like.  ANYTHING ELSE
## IS PARSED!!  This means that lines with stray characters or lines that 
## use non # comment characters will be interpreted by the initscript.  
## This has probably minor, but potentially serious, side effects for your 
## hard drives, so please follow the guidelines.  Patches to improve 
## flexibilty welcome.  Please read /usr/share/doc/hdparm/README.Debian for 
## notes about known issues, especially if you have an MD array.
##
## Note that if the init script causes boot problems, you can pass 'nohdparm' 
## on the kernel command line, and the script will not be run.
##
## Uncommenting the options below will cause them to be added to the DEFAULT
## string which is prepended to options listed in the blocks below.
##
## If an option is listed twice, the second instance replaces the first.
##
## /sbin/hdparm is not run unless a block of the form:
##  DEV {
## option
## option
## ...
##  }
## exists.  This blocks will cause /sbin/hdparm OPTIONS DEV to be run.
## Where OPTIONS is the concatenation of all options previously defined
## outside of a block and all options defined with in the block.

# -q be quiet
quiet 
# -a sector count for filesystem read-ahead
#read_ahead_sect = 12
# -A disable/enable the IDE drive's read-lookahead feature
#lookahead = on
# -b bus state
#bus = on
# -B apm setting
#apm = 255
# -B apm setting when on battery
#apm_battery = 127
# -c enable (E)IDE 32-bit I/O support - can be any of 0,1,3
#io32_support = 1
# -d disable/enable the "using_dma" flag for this drive
#dma = off
# -D enable/disable the on-drive defect management
#defect_mana = off
# -E cdrom speed
#cd_speed = 16
# -k disable/enable the "keep_settings_over_reset" flag for this drive
#keep_settings_over_reset = off
# -K disable/enable the drive's "keep_features_over_reset" flag
#keep_features_over_reset = on
# -m sector count for multiple sector I/O
#mult_sect_io = 32
# -P maximum sector count for the drive's internal prefetch mechanism
#prefetch_sect = 12
# -r read-only flag for device
#read_only = off
# -s Turn on/off power on in standby mode
# poweron_standby = off
# -S standby (spindown) timeout for the drive
#spindown_time = 24
# -u interrupt-unmask flag for the drive
#interrupt_unmask = on
# -W Disable/enable the IDE drive's write-caching feature
#write_cache = off
# -X IDE transfer mode for newer (E)IDE/ATA2 drives
#transfer_mode = 34
# -y force to immediately enter the standby mode
#standby
# -Y force to immediately enter the sleep mode
#sleep
# -Z Disable the power-saving function of certain Seagate drives
#disable_seagate
# -M Set the acoustic management properties of a drive
#acoustic_management
# -p Set the chipset PIO mode
# chipset_pio_mode
# --security-freeze Freeze the drive's security status
# security_freeze
# --security-unlock Unlock the drive's security
# security_unlock = PWD
# --security-set-pass Set security password
# security_pass = password
# --security-disable Disable drive locking
# security_disable
# --user-master Select password to use
# user-master = u
# --security-mode Set the security mode
# security_mode = h

# Root file systems.  Please see README.Debian for details
# ROOTFS = /dev/hda

## New note - you can use straight hdparm commands in this config file 
## as well - the set up is ugly, but it keeps backwards compatibility
## Additionally, it should be noted that any blocks that begin with 
## the keyword 'command_line' are not run until after the root filesystem
## is mounted.  This is done to avoid running blocks twice.  If you need 
## to run hdparm to set parameters for your root disk, please use the 
## standard format.

#Samples follow:
#First three are good for devfs systems, fourth one for systems that do 
#not use devfs.  The fifth example uses straight hdparm command line
#syntax.  Any of the blocks that use command line syntax must begin with
#the keyword 'command_line', and no attempt is made to validate syntax.  
#It is provided for those more comfortable with hdparm syntax. 

#/dev/discs/disc0/disc {
#   mult_sect_io = 16
#   write_cache = off
#   spindown_time = 240
#}

#/dev/discs/disc1/disc {
#   mult_sect_io = 32
#   spindown_time = 36
#   write_cache = off
#}

#/dev/cdroms/cdrom0 {
#   dma = on   
#   interrupt_unmask = on
#   io32_support = 0
#}

#/d

Re: Gparted will not label an existing FAT32 partition

[David Wright]

On Fri 11 Nov 2016 at 20:18:59 (+), Brian wrote:
> On Fri 11 Nov 2016 at 20:53:17 +0100, Nicolas George wrote:
> 
> > Le primidi 21 brumaire, an CCXXV, David Wright a écrit :
> > > Any reference. You see, I find label a very slippery word.
> > > You can label a disk at almost every level: a sticky label,
> > 
> > True, but not really relevant.
> > 
> > > a disklabel (partition table),
> > 
> > This is BSD slang. But this was what I was referring to.
> > 
> > >a filesystem label,
> > 
> > Indeed. That is the most common one.
> > 
> > >a volume label
> > > (perhaps those two are equivalent),
> > 
> > I do not think "volume" means anything in the Linux world.
> > 
> > > and whatever is handled by
> > > devlabel (which might be historic).
> > 
> > It looks like a tool to make symlinks based on the above labels.
> > 
> > > So I'm unsure what you mean by a partition label, where it's
> > > stored, and how it differs from a filesystem label.
> > 
> > Well, the filesystem label is stored in the filesystem metadata, i.e.
> > probably the superblock. The partition label is stored in the partitions
> > metadata, i.e. the "partition table".
> > 
> > > Is it new-fangled?
> > 
> > MBR-style partition tables do not contain labels, if that is what you
> > are asking. But GPT does.
> 
> May I say I appreciated the correction about labels being applied to
> file systems and not partitions. I'd done a copy and paste (with a
> change to a spelling) without any thought in mind to disabuse the OP
> about the technical aspects. It seemed more important to get him on
> the road.
> 
> But, this is getting interesting.

Yes, I guess we have to be more careful about distinguishing partition
and filesystem labels now that GPT is common. In the OP's instance, we
know that filesystem labels were meant because "extended partition"
was mentioned, so it's an MBR with no partition labels sensu stricto.

Cheers,
David.

Re: Gparted will not label an existing FAT32 partition

[Thomas Schmitt]

Hi,

i wrote:
> > The older format is MBR with 4 primary partitions and 4 logical
> > ones in one of the primary partitions.

Pascal Hambourg wrote:
> Huh ? The number of logical partitions is unlimited.

You are right. Must have been some mislead memory from old experience
with partitioning tools.


Have a nice day :)

Thomas

Re: Layers for the package manager

[Eduardo M KALINOWSKI]

On 11-11-2016 17:34, Nicolas George wrote:
> Being able to install incompatible packages at the same time.
>
> Isolate servers. Run servers in a layer where the compilers and other
> development tools are not visible. It does not actually add any security but
> it may help mitigate or slow down an attack.
>
> Most important: Being able to add third-party repositories with less worry.
>
> So, this is what I dream of. Does anybody have remarks? Know projects with
> similar goals? Distributions that have that feature? Other means of
> achieving a similar result with Debian?

docker does not work as you describe (and I know of nothing that does
anything close to your idea), but it does suit some of the uses you
mentioned (the ones quoted).


-- 
Preguiça é o habito de descansar antes da fadiga.

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: set domain name in Debian `

[Greg Wooledge]

On Fri, Nov 11, 2016 at 02:47:48PM -0700, Glenn English wrote:
> > On Nov 11, 2016, at 1:52 PM, Greg Wooledge  wrote:
> > 
> > So... what are you actually trying to do?  Be very specific.
> 
> Well, I'd like the domain name to be the same everywhere. hostname -f

hostname -f is totally useless.  Why do people even KNOW about it, let
alone use it? :(

wooledg@wooledg:~$ hostname
wooledg
wooledg@wooledg:~$ hostname -f
wooledg

The output of hostname is largely irrelevant.  The only purpose it serves
is to help you, the sysadmin or competent user, remember which system
you're currently logged into.

Including a domain name in that output is ridiculous if all of your
systems are used within the same organization.

> and whois  (that currently returns the ISP's info)

This is a DNS registrat thing.  It has nothing to do with Debian, or
anything that you do on your own computer.  You need to contact the
hosting provider, or ISP, or whoever owns this block of IP addresses
and have them set it up.

It's incredibly cosmetic.

> and /etc/hosts

This is used only by the local processes on the computer, and it's used
mostly to find OTHER computers that aren't in DNS.  Either because your
organization is so small that you don't even bother to use DNS (say,
half a dozen computers or less), or because your network was set up
by less than competent admins back in the 1990s.

If your computer has a preferred fully qualified domain name, then you
can put it in there.  Debian puts the computer's own hostname (with or
without an attached domain name) on the IP 127.0.1.1, thus:

127.0.0.1   localhost
127.0.1.1   wooledg

If I cared about writing out really long domain names in /etc/hosts
then I might change the second line to:

127.0.1.1   wooledg.eeg.ccf.org wooledg

This is largely pointless.

> and host  and a DNS lookup

host(1) is indeed one of the many commands that can look up a name in
DNS.  As I said before, if you don't specify a fully qualifed domain
name, then the "search" line(s) in /etc/resolv.conf will tell the
resolver which domain names to slap onto the end of the hostname before
looking it up.

wooledg@wooledg:~$ cat /etc/resolv.conf
search eeg.ccf.org
nameserver 10.76.142.103
nameserver 10.76.142.42
nameserver 172.28.254.24

wooledg@wooledg:~$ host wooledg
wooledg.eeg.ccf.org has address 10.76.172.109

As you can see here, host told the resolver to look up "wooledg", and
the resolver looked in /etc/resolv.conf and found the default search
domain, and appended that, and then did a DNS lookup of
"wooledg.eeg.ccf.org".

The default search domain doesn't even have to be one of the domain names
by which your machine is known to others.  It can be whatever you want
for your own convenience.  USUALLY your machine's default search domain
and "self-idenfies as" domain name will be the same.

> and everything else I can't think of right now

What your server calls itself doesn't really matter.

What matters is how OTHER COMPUTERS reach you.

Thus, you need to be looking at your DNS setup with your domain registrar.

> The DNS server isn't set up yet.

That should be your top priority.

> mailname is just the host. postfix is the SMTP server

Configuring mail without having working DNS is just an exercise in
frustration.  Get DNS correct first, and then get mail working.

Since you've "changed" your "domain" (which I interpret to mean
"I have a server on the Internet, and it used to receive mail sent
to u...@example1.com and now I want it to receive mail sent to
u...@example2.com") you probably really want your mail server to
continue to receive email for BOTH of these domains, at least for a
transitional period during which people might still be sending to the
original domain name.

Once you've got DNS set up correctly, you'll want to tell your mail
server "accept mail for example1.com and example2.com".  I don't
know how to do that with Postfix specifically.

Also, while you're in there, tell Postfix that you would like outgoing
mail to appear as coming from "example2.com".  Again, I don't know how
to do this with Postfix, but it should be relatively straightforward
once you find the documentation.

After a year or so, then you might choose to stop accepting mail sent
to example1.com, but that's up to you.

For a server on the public Internet, the output of hostname is completely
irrelevant.  All that matters is what's in DNS.

Example: I have a VPS on the public Internet.  It processes web requests
sent to the hostnames "wooledge.org" and "mywiki.wooledge.org".
Neither of these names is present in the output of "hostname".
The web server simply does not care what "hostname" is set to.  It only
cares about the hostname used in the HTTP requests that are sent to it.

Set the local hostname to something that will help you remember which
machine you're logged into.  That's all.

Re: set domain name in Debian `

[Joe]

On Fri, 11 Nov 2016 14:47:48 -0700
Glenn English  wrote:

> > On Nov 11, 2016, at 1:52 PM, Greg Wooledge 
> > wrote:
> > 
> > So... what are you actually trying to do?  Be very specific.  
> 
> Well, I'd like the domain name to be the same everywhere. hostname -f
> and whois  (that currently returns the ISP's info) and /etc/hosts
> and host  and a DNS lookup and everything else I can't think of
> right now should all report the same thing: the name of the domain
> I'm trying to set up this server for.
> 
> As yet, I'm looking at hostname -f (plain hostname gets the host
> right), and ping'ing and SSH'ing using /etc/hosts (that works). I've
> set my local DNS to look first at hosts, then at DNS.
> 
> The DNS server isn't set up yet. mailname is just the host. postfix
> is the SMTP server -- editing its config doesn't seem to do anything.
> 
> I've moved to a new domain, and I copied lots of data from the old
> server. The domain name I see is that of the old server.
> 

I think we still do not have the terms of reference straight.

First of all, it's a server. Who is it serving? People within the local
network only, people out on the Net, or both?

You're replacing an older server. If you are serving to the Net, are
you on a new ISP connection or still the one which has worked until
now? I.e., has the public IP address and any external DNS changed?

Are there DNS servers out on the Net which hold information for this
domain? If so, using a local DNS server with records for other local
hostnames on the same domain becomes problematic, and the question of
what IP address is returned if you ask for the usual hostname of your
public IP address may be dependent on the behaviour of your router.

To sum up, we need to know who sees this domain, and from where, and
for what services.

Internet email, for example, needs your mail server to know the domain,
and for a public DNS MX record for that domain to point to a hostname
which resolves to your public IP address, and not much more. A server
can host many email domains, none of which need to be related to the
domain in which the server lives, if any. A public web server might
need to know the domain name, and again may serve multiple domains, but
for simple sites, it will not need to know. A computer in a private
network, even when providing public Internet services, does not
inherently belong to any domain, but it may be administratively
convenient if it is assigned one. It may well have a hostname
completely different to any hostname which resolves to it from the Net.

-- 
Joe

Re: Gparted will not label an existing FAT32 partition

[David Wright]

On Fri 11 Nov 2016 at 23:22:36 (+0100), Thomas Schmitt wrote:
> Hi,
> 
> i wrote:
> > > The older format is MBR with 4 primary partitions and 4 logical
> > > ones in one of the primary partitions.
> 
> Pascal Hambourg wrote:
> > Huh ? The number of logical partitions is unlimited.
> 
> You are right. Must have been some mislead memory from old experience
> with partitioning tools.

There was a period (rex) when Debian only created /dev/sda[1-8]
on SCSI disks, though this only affected whether you could *access*
a greater number of partitions, not *create* them.

Cheers,
David.

Re: Gparted will not label an existing FAT32 partition

[rhkramer]

On Friday, November 11, 2016 04:58:41 PM Pascal Hambourg wrote:
> Le 11/11/2016 à 22:17, Thomas Schmitt a écrit :
> > The older format is MBR with 4 primary partitions and 4 logical
> > ones in one of the primary partitions.
> 
> Huh ? The number of logical partitions is unlimited.

Ok, just to be part of this ongoing saga, I think the number of logical 
partitions is limited to something like 12 or 16 (or maybe the total number of 
partitions, primary plus logical is limited to 16.  (And maybe that's a limit 
of one or more OSs rather than a universal limit.)

Re: set domain name in Debian `

[Glenn English]

> On Nov 11, 2016, at 3:45 PM, Joe  wrote:
> 
> I think we still do not have the terms of reference straight.
> 
> First of all, it's a server. Who is it serving? People within the local
> network only, people out on the Net, or both?

Both. It's on the 'Net, but it's also where the email comes in.

And do you guys need to know it's a /29 namespace with fixed IPs on a T1 
connection?

> You're replacing an older server. If you are serving to the Net, are
> you on a new ISP connection or still the one which has worked until
> now? I.e., has the public IP address and any external DNS changed?

Same ISP, new piece of wire, new IPs, new domain name (I have 
slsware.com/net/org -- I'm moving from .net to the unused .org.) At the old 
place, I NAT'ed the globals to 1918 IPs on a DMZ and a LAN. 

> Are there DNS servers out on the Net which hold information for this
> domain?

Not yet. I haven't told the registrar about the new nameserver IPs. 

I just configured DNS. BIND says there are no errors. But there are; I deleted 
the SFP records from all the virtual domains to make it shut up. I haven't yet 
tried to figure out why BIND was unhappy with the SFPs. Nor have I tested it 
significantly. But DNS is there.

> If so, using a local DNS server with records for other local
> hostnames on the same domain becomes problematic,

I've done that for years with no problems. They're sometimes even the same 
host/IP, with different names. If you ask for a function, you get the IP. If 
you ask for a reverse on an IP, I don't know what you get. I have a feeling 
that I should go the CNAME route (and I have more recently), but I've never 
really needed to.

> and the question of
> what IP address is returned if you ask for the usual hostname of your
> public IP address may be dependent on the behaviour of your router.

No. The router has nothing to do with it, in my experience. I don't do DHCP, 
not at the server anyway, and the router has no DMS table(s).

> To sum up, we need to know who sees this domain, and from where, and
> for what services.

Everybody, internal (LAN, DMZ) and external (WAN). 

Same: internal and external. 

For your standard 'Net services (HTTP, SMTP, SSH, FTP, IMAP, POP3, etc.)

-- 
Glenn English

Re: Gparted will not label an existing FAT32 partition

[Felix Miata]

rhkra...@gmail.com composed on 2016-11-11 18:36 (UTC-0500):


Pascal Hambourg wrote:



Thomas Schmitt composed:



> The older format is MBR with 4 primary partitions and 4 logical
> ones in one of the primary partitions.



Huh ? The number of logical partitions is unlimited.



Ok, just to be part of this ongoing saga, I think the number of logical
partitions is limited to something like 12 or 16 (or maybe the total number of
partitions, primary plus logical is limited to 16.  (And maybe that's a limit
of one or more OSs rather than a universal limit.)


When libata was a juvenile it inherited SCSI's maximum block id minor number 
15, making /dev/sd#15 the limit. It took awhile before the new major number 
259 was provided with a larger maximum minor, 127 IIRC, to boost the libata 
limit past 15.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Gparted will not label an existing FAT32 partition

[David Wright]

On Fri 11 Nov 2016 at 18:36:15 (-0500), rhkra...@gmail.com wrote:
> On Friday, November 11, 2016 04:58:41 PM Pascal Hambourg wrote:
> > Le 11/11/2016 à 22:17, Thomas Schmitt a écrit :
> > > The older format is MBR with 4 primary partitions and 4 logical
> > > ones in one of the primary partitions.
> > 
> > Huh ? The number of logical partitions is unlimited.
> 
> Ok, just to be part of this ongoing saga, I think the number of logical 
> partitions is limited to something like 12 or 16 (or maybe the total number 
> of 
> partitions, primary plus logical is limited to 16.  (And maybe that's a limit 
> of one or more OSs rather than a universal limit.)

That doesn't seem to square with
http://forums.justlinux.com/showthread.php?147959-How-to-install-and-boot-145-operating-systems-in-a-PC
(Scroll down to "Partition Tables".)

Cheers,
David.

Regles d'utilisation de la mailing-list FRnOG / FRnOG mailing-list rules of usage

[Gestionnaire de Liste FRnOG]

Bonjour,

Afin d'aider à la catégorisation des e-mails, il est nécessaire de modifier le
"Sujet/Objet/Subject" de celui-ci avec un Tag en fonction du contenu.

Voici la règle à respecter pour poster sur cette mailing-list:
  
  | Sujet de votre e-mail | Tag à utiliser OU Destinataire à utiliser|
  |--|
  |Alerte ou Incident |   [ALERT]  ||  frnog-al...@frnog.org |
  | sur Internet ou un DC ||||
  ||||
  |  Discussion technique |[TECH]  ||   frnog-t...@frnog.org |
  ||||
  | Sujet Système / FLOSS |[MISC]  ||   frnog-m...@frnog.org |
  |   et/ou philosophique ||||
  ||||
  |  Recherche ou annonce |[JOBS]  ||   frnog-j...@frnog.org |
  | d'emploi sys & réseau ||||
  ||||
  |Demande et réponse | [BIZ]  ||frnog-...@frnog.org |
  |   commerciale ||||
  |  Offre ou annonce ||||
  |  *interdite* sauf ||||
  |   occasion ou don ||||
  

Les adresses frnog-*@ modifient automatiquement votre message pour y inclure le
bon tag dans le sujet (frnog-tech@ => Sujet: [TECH] ...).

=== ENGLISH ===

Hi,

In order to help categorize e-mails it is now mandatory to tag the Subject
depending on the content of your message.

Here is the rule you have to follow for posting to this mailing-list:
  
  |  Topic of your e-mail | Tag to use OR   Recipient to use |
  |--|
  | Alert or Incident |   [ALERT]  ||  frnog-al...@frnog.org |
  | @ Internet or in a DC ||||
  ||||
  |  Technical discussion |[TECH]  ||   frnog-t...@frnog.org |
  ||||
  | System / FLOSS and/or |[MISC]  ||   frnog-m...@frnog.org |
  |  philosophical Topics ||||
  ||||
  | sys & network job |[JOBS]  ||   frnog-j...@frnog.org |
  |search & offer ||||
  ||||
  | Sales Q&A | [BIZ]  ||frnog-...@frnog.org |
  |   Unsolicited ||||
  | offer or announcement ||||
  | is strictly forbidden ||||
  

When you send to a frnog-*@ e-mail address, the tag is automatically inserted
in the Subject.


Cordialement / Sincerely,
Philippe Bourcier

Re: Gparted will not label an existing FAT32 partition

[Joseph Loo]

On 11/11/2016 04:39 PM, David Wright wrote:
> On Fri 11 Nov 2016 at 18:36:15 (-0500), rhkra...@gmail.com wrote:
>> On Friday, November 11, 2016 04:58:41 PM Pascal Hambourg wrote:
>>> Le 11/11/2016 à 22:17, Thomas Schmitt a écrit :
 The older format is MBR with 4 primary partitions and 4 logical
 ones in one of the primary partitions.
>>>
>>> Huh ? The number of logical partitions is unlimited.
>>
>> Ok, just to be part of this ongoing saga, I think the number of logical 
>> partitions is limited to something like 12 or 16 (or maybe the total number 
>> of 
>> partitions, primary plus logical is limited to 16.  (And maybe that's a 
>> limit 
>> of one or more OSs rather than a universal limit.)
> 
> That doesn't seem to square with
> http://forums.justlinux.com/showthread.php?147959-How-to-install-and-boot-145-operating-systems-in-a-PC
> (Scroll down to "Partition Tables".)
> 
> Cheers,
> David.
> 
Your URL is talking about gpt scheme. The limitation is in the MSDOS
partition scheme

-- 
Joseph Loo
j...@acm.org

Re: Gparted will not label an existing FAT32 partition

[David Wright]

On Fri 11 Nov 2016 at 16:45:40 (-0800), Joseph Loo wrote:
> On 11/11/2016 04:39 PM, David Wright wrote:
> > On Fri 11 Nov 2016 at 18:36:15 (-0500), rhkra...@gmail.com wrote:
> >> On Friday, November 11, 2016 04:58:41 PM Pascal Hambourg wrote:
> >>> Le 11/11/2016 à 22:17, Thomas Schmitt a écrit :
>  The older format is MBR with 4 primary partitions and 4 logical
>  ones in one of the primary partitions.
> >>>
> >>> Huh ? The number of logical partitions is unlimited.
> >>
> >> Ok, just to be part of this ongoing saga, I think the number of logical 
> >> partitions is limited to something like 12 or 16 (or maybe the total 
> >> number of 
> >> partitions, primary plus logical is limited to 16.  (And maybe that's a 
> >> limit 
> >> of one or more OSs rather than a universal limit.)
> > 
> > That doesn't seem to square with
> > http://forums.justlinux.com/showthread.php?147959-How-to-install-and-boot-145-operating-systems-in-a-PC
> > (Scroll down to "Partition Tables".)
> > 
> > Cheers,
> > David.
> > 
> Your URL is talking about gpt scheme. The limitation is in the MSDOS
> partition scheme

You only read the updates at the top!

> > (Scroll down to "Partition Tables".)

... and see

/dev/hda4 367   36483   290109802+   5  Extended
...
/dev/hda60  34658   35265 4883728+  83  Linux

Cheers,
David.

Re: wheezy, cannot change the address of eth1

[Gene Heskett]

On Friday 11 November 2016 13:38:08 Greg Wooledge wrote:

> On Fri, Nov 11, 2016 at 01:13:56PM -0500, Gene Heskett wrote:
> > The output on screen for an /etc/init.d/networking restart for eth1
> > is: Configuring interface eth1=eth1 (inet)
> > run-parts --verbose /etc/network/if-pre-up.d
> > run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> > run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> > ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255   dev
> > eth1 label eth1
> > ip link set dev eth1   up
> >  ip route add default via 192.168.0.1  dev eth1
> > RTNETLINK answers: File exists
> > Failed to bring up eth1.
>
> Start by showing the contents of /etc/network/interfaces.
>
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto lo

# The loopback network interface
iface lo inet loopback
address 127.0.0.1
netmask 255.255.255.0

auto eth0

# regular network for coyote.den
iface eth0 inet static
address 192.168.71.3
netmask 255.255.255.0
gateway 192.168.71.1

auto eth1

# to access reset to 192.168.0.1 routers/switches on the 2nd cat5 port
iface eth1 inet static
address 192.168.0.25
netmask 255.255.255.0
gateway 192.168.0.1



> Then find out whether a DHCP client daemon is already running.  If you
> installed with DHCP (the default) and then edited /e/n/i but didn't
> stop dhclient beforehand, then ifdown won't know to kill dhclient and
> you'll have to kill it by hand (or reboot).

The only dhcp running on this whole network is in a dd-wrt router, and 
out of this things class D.

> ps auxw | egrep 'dhclient|dhcpcd'

The only return is my egrep looking for it.

> kill if necessary
> ifdown eth1
> edit /etc/network/interfaces if necessary

see above.

> ifup eth1
>
> If this doesn't work, then show the output of "ip addr show eth1"
> and the network-relevant parts of dmesg (e.g. "dmesg | grep eth" is
> often a good start).

root@coyote:/etc# ifup eth1
RTNETLINK answers: File exists
Failed to bring up eth1.
root@coyote:/etc# ip addr show eth1
3: eth1:  mtu 1500 qdisc pfifo_fast state DOWN group 
default qlen 1000
link/ether 00:1f:c6:63:07:97 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global eth1
   valid_lft forever preferred_lft forever
inet 192.168.0.253/24 brd 192.168.0.255 scope global eth1
   valid_lft forever preferred_lft forever
inet 192.168.0.25/24 brd 192.168.0.255 scope global secondary eth1
   valid_lft forever preferred_lft forever

From dmesg|grep eth1
root@coyote:/etc# dmesg| grep eth1
[1.940510] forcedeth :00:09.0: ifname eth1, PHY OUI 0x5043 @ 1, 
addr 00:1f:c6:63:07:97
[   29.382766] forcedeth :00:09.0 eth1: MSI enabled
[   29.382987] forcedeth :00:09.0 eth1: no link during initialization
[   29.383422] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[1640002.998274] forcedeth :00:09.0 eth1: link up
[1640002.999087] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[1640455.806412] forcedeth :00:09.0 eth1: MSI enabled
[1640749.873848] forcedeth :00:09.0 eth1: MSI enabled
[1641602.825513] forcedeth :00:09.0 eth1: MSI enabled

that looks like ipv6 is working, but to where? The path ends at the 
uplink input to this new router. And since anything ipv6 is probably at 
least 100 miles away, I have zero experience.  ipv6 will probably not 
arrive at the customer interface of my ISP before I miss roll call for 
good some morning.

Thanks for any additional clues, or data requests.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: wheezy, cannot change the address of eth1

[Gene Heskett]

On Friday 11 November 2016 14:17:07 David Wright wrote:

> On Fri 11 Nov 2016 at 13:13:56 (-0500), Gene Heskett wrote:
> > Greetings folks;
> >
> > I just bought an ethernet switch, but it is a smart switch, so I
> > needed to bring up my eth1 interface at an address in the
> > 192.168.0.xx range so I can talk to it.  But despite the fact that
> > it is so specified in /etc/network/interfaces, no amount of stopping
> > and restarting the networking makes it take effect, its stuck at the
> > old 192.168.1.3 address.
> >
> > The output on screen for an /etc/init.d/networking restart for eth1
> > is: Configuring interface eth1=eth1 (inet)
> > run-parts --verbose /etc/network/if-pre-up.d
> > run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> > run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> > ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255   dev
> > eth1 label eth1
> > ip link set dev eth1   up
> >  ip route add default via 192.168.0.1  dev eth1
> > RTNETLINK answers: File exists
> > Failed to bring up eth1.
> >
> > I cannot change it with ifconfig either. And the manpage for ip may
> > as well be in swahili, lots of unexplained terminology.
> >
> > So, short of rebooting so the changed interfaces might take effect,
> > but will they, what is this "File exists" error?.
> >
> > Does anyone have a clue what may be wrong?
> >
> > And 5 years after I had a big fight with RTNETLINK, whatever the
> > heck that is, it is still keeping the cause of the error secret.
> >
> > So, net experts, what do I do?
>
> Googling your error message, I think the third link tells you what it
> means
> http://www.linuxquestions.org/questions/linux-networking-3/rtnetlink-a
>nswers-file-exists-error-when-doing-ifup-on-alias-eth1-1-on-rhel5-71076
>6/ and the second might be a fix.
> http://unix.stackexchange.com/questions/100588/using-ip-addr-instead-o
>f-ifconfig-reports-rtnetlink-answers-file-exists-on-de
>
> Cheers,
> David.

Yes, and no. What it suggested was bringing up eth0:1, and that worked, 
and I even got past the password & logged in.  But the menu's are, shal 
we say strange. I expected it to have a facility to update its elderly 
firmware, but there's no such thing. I registered it, so I'll taze their 
LL Monday and see if I can find somebody that speaks linux.

Many thanks for the pointer, & URL, that part worked.



Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: dd - proper use or more suitable program

[Mark Fletcher]

On Fri, Nov 11, 2016 at 10:49:37AM -0600, Richard Owlett wrote:

> I had been removed after becoming unreliable. 

Sorry to hear that. Advanced years don't come on their own, do they?

(Sorry, couldn't resist it)

Re: set domain name in Debian `

[Glenn English]

> On Nov 11, 2016, at 3:31 PM, Greg Wooledge  wrote:
> 
> On Fri, Nov 11, 2016 at 02:47:48PM -0700, Glenn English wrote:
>>> On Nov 11, 2016, at 1:52 PM, Greg Wooledge  wrote:
>>> 
>>> So... what are you actually trying to do?  Be very specific.
>> 
>> Well, I'd like the domain name to be the same everywhere. hostname -f
> 
> hostname -f is totally useless.  Why do people even KNOW about it, let
> alone use it? :(
> 
> wooledg@wooledg:~$ hostname
> wooledg
> wooledg@wooledg:~$ hostname -f
> wooledg

I claim you've got the same problem I do :-)

I looked at bit at hostname -f. It goes through a few levels (of .sh, it looks 
like) and finally asks something in a C library. So if hostname -f is giving 
bad data, the shell just doesn't have the right info.

> Including a domain name in that output is ridiculous if all of your
> systems are used within the same organization.

Maybe. But mine aren't. They've been in slsware.net, .dmz, and .lan.

> This is a DNS registrat thing.  It has nothing to do with Debian

OK. Then it's not what I'm looking for. I'm pretty sure what I need very much 
has to do with Debian.

> If your computer has a preferred fully qualified domain name, then you
> can put it in there.  Debian puts the computer's own hostname (with or
> without an attached domain name) on the IP 127.0.1.1, thus:
> 
> 127.0.0.1 localhost
> 127.0.1.1 wooledg

Just did that. Didn't work. Is a reboot required? (This thing takes a long time 
to reboot.)

> host(1) is indeed one of the many commands that can look up a name in
> DNS.  

host www.slsware.org gets the right IP. (localhost; there's no DNS info on the 
'Net about this server yet.)

From an alien domain, running that command, specifying my DNS with an IP, works 
too.

> As I said before, if you don't specify a fully qualifed domain
> name, then the "search" line(s) in /etc/resolv.conf will tell the
> resolver which domain names to slap onto the end of the hostname before
> looking it up.
> 
> wooledg@wooledg:~$ cat /etc/resolv.conf
> search eeg.ccf.org
> nameserver 10.76.142.103
> nameserver 10.76.142.42
> nameserver 172.28.254.24
> 
> wooledg@wooledg:~$ host wooledg
> wooledg.eeg.ccf.org has address 10.76.172.109

Says 'Host slsware not found' here. (Still no reboot.)

> Thus, you need to be looking at your DNS setup with your domain registrar.

Don't need to. I do my own.

> That should be your top priority.

I read that and ran and configured DNS. Nobody cares, AFAICT.

> All that matters is what's in DNS.

I hear you. But it's a nagging piece of config that the kernel doesn't know its 
name. It exists for a reason, and it's built in to the kernel for something. It 
may well be something hanging over from 1975 -- if so, I'd like to know for 
sure, one way or the other.

> Set the local hostname to something that will help you remember which
> machine you're logged into.  That's all.

That's already done. Setting the host's name is easy. It's the domain that's 
making me crazy.

-- 
Glenn English
Did you just click Reply?
If so, change the send
address from gmail to
g...@slsware.net

Re: dd - proper use or more suitable program

[Andy Smith]

Hi Richard,

On Fri, Nov 11, 2016 at 03:31:21PM -0600, Richard Owlett wrote:
> How big might the logfile be when trying to recover a known flaky 300
> GB drive. I've lots of space? Some convienient, some not.

TL;DR: this depends on how many bad sectors you expect to find. If
the number is likely to be low then the map file should be a matter
of kilobytes in size.

I've never looked into this before as it's never been an issue for
me, but looking at:


https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html#Mapfile-structure

The header of the map file looks like:

 # Mapfile. Created by GNU ddrescue version 1.21
 # Command line: ddrescue -d -c18 /dev/fd0 fdimage mapfile
 # Start time:   2015-07-21 09:37:44
 # Current time: 2015-07-21 09:38:19
 # Copying non-tried blocks... Pass 1 (forwards)
 # current_pos  current_status
 0x0012 ?
 #  possize  status

…which is 304 bytes.

After that there is one line for each range of blocks depending on
their status (finished, not tried yet, failed etc).

I am thinking that the absolute worst case in terms of maximal
number of lines in this file would be if every other sector were
failed, so you'd have an alternating sequence of:

0x  0x0001  +
0x0001  0x0001  -
0x0002  0x0001  +
0x0003  0x0001  -

for the entire device. That's 52 bytes for every two blocks.

The default block size is 512 bytes in ddrescue, so two blocks
covers 1024 bytes of your device.

If your device is 300 gigabytes in size—and I'll assume that is SI
power of ten giga- (not binary power of two gibi-) as is common with
drive manufacturers, so 300,000,000,000 bytes—then that's
300,000,000,000 / 1,024 = 292,968,750. That times 54 bytes is
15,820,312,500 bytes. Or 14.73GiB. Plus a ~304 byte header.

As far as I can see that is the absolute worst case and for a more
realistic scenario of a device with only a couple of bad sectors
you'd be looking at mere kilobytes of map file size.

For example, if merely 1% of the sectors were bad (and I would
suggest that even that would represent a catastrophically damaged
device that you will find very difficult to extract any sense out
of) then you'd still only be looking at a map file with 5,859,375
bad blocks in it (5,859,375 bad sectors out of 585,937,500 total
512-byte sectors in a 300,000,000,000 byte device). This would
require 5,859,376 different ranges in the map file, with each range
being 27 bytes, so 27 * 5,859,376 = 158,203,152 bytes = 150.9MiB.

I doubt you will see 5.9 million bad sectors on your 300G drive!

Basically whenever my destination has had noticeably more space than
the source device I haven't spared a thought to this so have never
worked it out before. I think the above is correct but look forward
to a correction from anyone who knows better.

Also do note that should you run out of space when writing the map
file, you still have the map file that has been written to date, so
you can extricate yourself from the situation and rerun ddrescue,
safe in the knowledge that it will pick up from where it got to.

If you are expecting serious numbers of bad sectors then your most
precious resource may actually be time. ddrescue tries REALLY HARD
to read a bad sector with each try potentially taking 2 or more
minutes. So on the hypothetical "1% broken" drive with 5.9 million
bad sectors, a single pass could take upwards of 10 million minutes
(19 years). And sometimes multiple passes are required to read a bad
sector.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: wheezy, cannot change the address of eth1

[Andy Smith]

Hello,

On Fri, Nov 11, 2016 at 09:13:26PM +, Darac Marjal wrote:
> To cut a long story short, you can't add a default route if you already
> have one (well, technically you can, but you'd need to provide more
> information). You probably have a default route sending traffic over eth0.

Yes, I concur. He needs to remove the "gateway" line from his eth1
stanza as he does not need another default route going out of that
interface.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: set domain name in Debian `

[Andy Smith]

Hi Glenn,

On Fri, Nov 11, 2016 at 01:27:28PM -0700, Glenn English wrote:
> I have to change the domain name of a Jessie server I'm working on. How do 
> you do it? (Aside from putting the FQDN in /etc/hostname, which kinda works.)

I normally put the short name in /etc/hostname and then the:

 

in /etc/hosts. That works for me both for setting initial host name
and FQDN, and for changing it later.

After you have done that, what command are you using which shows you
the old/incorrect values?

Note that the domain part comes from name resolution, so will
involve /etc/hosts and potentially DNS or other name services you
have configured in /etc/nsswitch.conf.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: set domain name in Debian `

[Glenn English]

> On Nov 11, 2016, at 9:58 PM, Andy Smith  wrote:
> 
> I normally put the short name in /etc/hostname and then the:
> 
>  
> 
> in /etc/hosts. That works for me both for setting initial host name
> and FQDN, and for changing it later.

Yeah, that's what I hear, and exactly that's in there. IIRC, I've had some 
success with that in the past. But it doesn't work for me today. Debian needs a 
domainname command like hostname. Or maybe a man page explaining what looks up 
what and where the string is. A file in /etc called domainname wouldn't be too 
much to ask, IMHO.

> After you have done that, what command are you using which shows you
> the old/incorrect values?

Mostly hostname - f. That's what I've used in a number if shell scripts, and 
it's always worked (on systems who've been labeled by the installer). hosts and 
DNS can both find the IP, given the FQDN, but hostname -f is wrong. hostname 
returns 'srv' like it should. But hostnane -f returns 'www.slsware.dmz' -- way 
wrong. I've grep'ed for that www string and haven't been able to find it.

> Note that the domain part comes from name resolution, so will
> involve /etc/hosts and potentially DNS or other name services you
> have configured in /etc/nsswitch.conf.

I haven't done nsswitch.conf yet. I'll try it in the morning...

I got curious. nsswitch.conf on the old host (working hostname -f):

> passwd: compat
> group:  compat
> shadow: compat
> 
> hosts:files  dns 
> networks:   files
> 
> protocols:  db files
> services:   db files
> ethers: db files
> rpc:db files
> 
> netgroup:   nis


On the new one (bent hostname -f):

> passwd: compat
> group:  compat
> shadow: compat
> gshadow:files
> 
> hosts:files dns
> networks:   files
> 
> protocols:  db files
> services:   db files
> ethers: db files
> rpc:db files
> 
> netgroup:   nis

See anything interesting? I don't. Except the mention of gshadow on the bad 
one, and I have no idea what that makes happen. Is it possible one of those 
files has bad data in it? If so, what are their names and where are they?

-- 
Glenn English

Re: set domain name in Debian `

[Andy Smith]

Hi Glenn,

On Fri, Nov 11, 2016 at 11:13:02PM -0700, Glenn English wrote:
> > On Nov 11, 2016, at 9:58 PM, Andy Smith  wrote:
> > After you have done that, what command are you using which shows you
> > the old/incorrect values?
> 
> Mostly hostname - f. That's what I've used in a number if shell
> scripts, and it's always worked (on systems who've been labeled by
> the installer).

Okay. So I think we should focus on why "hostname -f" returns the
wrong/outdated info. I'm not sure yet.

Out of interest what does "hostname -d" return? Should be just the
domain name part, so I expect it to say the wrong thing here. And
what is the contents of /etc/hostname and /etc/hosts?

I'm assuming you have actually rebooted at least once after changing
/etc/hostname and /etc/hosts, yes?

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: dd - proper use or more suitable program

[Christian Seiler]

On 11/11/2016 10:38 PM, Richard Owlett wrote:
> I was wondering about that. 
> https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html is
> not first time user friendly. Will re-read after a good night's
> sleep. Will also look for appropriate tutorials. Suggestions?

Well, I would suggest not dumping the result on another partition
but rather into an image file. In that case you'd have the old
drive (not mounted), let's call it /dev/sda, and the new drive
with a partition on it and mounted on /mnt with sufficient free
disk space there.

In the simplest case you'd do:

ddrescue /dev/sda /mnt/defective_drive.img /mnt/defective_drive.log

If the drive is farther gone and has quite a few defective
sectors you may get better results if you use direct disk access
for the phase where you try to read defective sectors. In that case
you'd copy the bulk of the data while disabling the scraping phase
manually,

ddrescue -n /dev/sda /mnt/defective_drive.img /mnt/defective_drive.log

And then use direct access to scrape the rest:

ddrescue -d /dev/sda /mnt/defective_drive.img /mnt/defective_drive.log

Note that ddrescue assumes a default sector size of 512 bytes,
which is likely to be correct for older hard drives smaller than
2 TiB. If you have a newer hard drive, especially if it's rather
large, the physical sector size could be 4096 bytes instead.
(You can check the physical sector size of your disk by running
hdparm -I /dev/sda - that will tell you a lot of things about
your drive, among them the physical sector size in bytes. Note
that the physical sector size is relevant here, not the logical
one.)

In addition, you may also want to specify a number of retries
when trying to read defective sectors. (Default is 0.) You can
do that with the -r flag, e.g. -r3 for three retries per sector.

To recap:

 - Simplest way of calling the program is

   ddrescue /dev/sda output_image_file log_file

 - If the condition of your hard drive is a bit worse, you might
   achieve better results with:

   ddrescue -n /dev/sda output_image_file log_file
   ddrescue -d -r2 /dev/sda output_image_file log_file

   (-r2 is for 2 retries per defective sector, you can change
   that number; you can also call the second ddrescue command
   again in case you want to do more retries.)

 - If you have a new disk with 4096 bytes / sector (not likely)
   please also add a -b4096 to the command line.

 - If your target is not an image file, but a disk drive itself,
   also specify the -f option. (I would really recommend using
   image files though, gives you more flexibility.)

 - I wouldn't really bother with the other options, the default
   behavior is very sensible.

 - Finally, get some coffee or similar, this may take a while.

Regards,
Christian

Re: Does hdparm not run at startup anymore?

[Rainer Dorsch]

+ Alexandre, hdparm maintainer

On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
> Hi,
> 
> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, 
> apm does not change. Interesting enough a /etc/init.d/hdparm restart fixes 
> the problem:
> 
> 
> root@Silberkiste:~# cat /etc/hdparm.conf
> ## This is the default configuration for hdparm for Debian.  It is a 
> ## rather simple script, so please follow the following guidelines :)
> ## Any line that begins with a comment is ignored - add as many as you 
> ## like.  Note that an in-line comment is not supported.  If a line 
> ## consists of whitespace only (tabs, spaces, carriage return), it will be
> ## ignored, so you can space control fields as you like.  ANYTHING ELSE
> ## IS PARSED!!  This means that lines with stray characters or lines that 
> ## use non # comment characters will be interpreted by the initscript.  
> ## This has probably minor, but potentially serious, side effects for your 
> ## hard drives, so please follow the guidelines.  Patches to improve 
> ## flexibilty welcome.  Please read /usr/share/doc/hdparm/README.Debian for 
> ## notes about known issues, especially if you have an MD array.
> ##
> ## Note that if the init script causes boot problems, you can pass 'nohdparm' 
> ## on the kernel command line, and the script will not be run.
> ##
> ## Uncommenting the options below will cause them to be added to the DEFAULT
> ## string which is prepended to options listed in the blocks below.
> ##
> ## If an option is listed twice, the second instance replaces the first.
> ##
> ## /sbin/hdparm is not run unless a block of the form:
> ##  DEV {
> ## option
> ## option
> ## ...
> ##  }
> ## exists.  This blocks will cause /sbin/hdparm OPTIONS DEV to be run.
> ## Where OPTIONS is the concatenation of all options previously defined
> ## outside of a block and all options defined with in the block.
> 
> # -q be quiet
> quiet 
> # -a sector count for filesystem read-ahead
> #read_ahead_sect = 12
> # -A disable/enable the IDE drive's read-lookahead feature
> #lookahead = on
> # -b bus state
> #bus = on
> # -B apm setting
> #apm = 255
> # -B apm setting when on battery
> #apm_battery = 127
> # -c enable (E)IDE 32-bit I/O support - can be any of 0,1,3
> #io32_support = 1
> # -d disable/enable the "using_dma" flag for this drive
> #dma = off
> # -D enable/disable the on-drive defect management
> #defect_mana = off
> # -E cdrom speed
> #cd_speed = 16
> # -k disable/enable the "keep_settings_over_reset" flag for this drive
> #keep_settings_over_reset = off
> # -K disable/enable the drive's "keep_features_over_reset" flag
> #keep_features_over_reset = on
> # -m sector count for multiple sector I/O
> #mult_sect_io = 32
> # -P maximum sector count for the drive's internal prefetch mechanism
> #prefetch_sect = 12
> # -r read-only flag for device
> #read_only = off
> # -s Turn on/off power on in standby mode
> # poweron_standby = off
> # -S standby (spindown) timeout for the drive
> #spindown_time = 24
> # -u interrupt-unmask flag for the drive
> #interrupt_unmask = on
> # -W Disable/enable the IDE drive's write-caching feature
> #write_cache = off
> # -X IDE transfer mode for newer (E)IDE/ATA2 drives
> #transfer_mode = 34
> # -y force to immediately enter the standby mode
> #standby
> # -Y force to immediately enter the sleep mode
> #sleep
> # -Z Disable the power-saving function of certain Seagate drives
> #disable_seagate
> # -M Set the acoustic management properties of a drive
> #acoustic_management
> # -p Set the chipset PIO mode
> # chipset_pio_mode
> # --security-freeze Freeze the drive's security status
> # security_freeze
> # --security-unlock Unlock the drive's security
> # security_unlock = PWD
> # --security-set-pass Set security password
> # security_pass = password
> # --security-disable Disable drive locking
> # security_disable
> # --user-master Select password to use
> # user-master = u
> # --security-mode Set the security mode
> # security_mode = h
> 
> # Root file systems.  Please see README.Debian for details
> # ROOTFS = /dev/hda
> 
> ## New note - you can use straight hdparm commands in this config file 
> ## as well - the set up is ugly, but it keeps backwards compatibility
> ## Additionally, it should be noted that any blocks that begin with 
> ## the keyword 'command_line' are not run until after the root filesystem
> ## is mounted.  This is done to avoid running blocks twice.  If you need 
> ## to run hdparm to set parameters for your root disk, please use the 
> ## standard format.
> 
> #Samples follow:
> #First three are good for devfs systems, fourth one for systems that do 
> #not use devfs.  The fifth example uses straight hdparm command line
> #syntax.  Any of the blocks that use command line syntax must begin with
> #the keyword 'command_line', and no attempt is made to validate syntax.  
> #It is provided for those more comfortable with hdparm syntax. 
> 
> #/dev/