Re: Live Fille System Backup

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 05, 2017 at 01:35:35PM -0700, Sergei G wrote:
> it would be naive at best to think that busy files [...]

What is a "busy" file?

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkNZJkACgkQBcgs9XrR2kYJZACfdF9cY0x4iocuTu6amaWGF1Vk
EsoAnAoJm8i7EwwpxJOo5RluDrvQ/2mu
=x7Yi
-END PGP SIGNATURE-

Re: What On Earth Did I do? (was Boot Drives for older Systems)

[David Christensen]

On 05/05/2017 08:11 PM, Martin McCormick wrote:

This story has a good ending but I am mystified.

Until the new boot drives I ordered get here, I took an
old slow 10GB Maxtor drive and made a new installation of Debian
jessie and got it like I wanted it. It booted fine on the older
Dell system whose drive went to the ultimate bit bucket so I
decided to save the image via dd so as to dd it to other boot drives.

dd if=/dev/sdb of=systemname.bin

The image copied slowly but did appear to copy so I put
the drive that had been copied back in to the system being
repaired and booted up again.  There was that sickening beep-beep
one hears when the game is over before it starts.  I checked the
jumper and it was okay for being the master boot drive.

I tried it on a known good system and no luck there. Did
I accidentally reverse the if and of names?  No because had I
does so, the target would have been trashed. It is also 7 times
bigger than the source so it would have been a bust all round and
the system I had used for the copy was still up and running when
all was done.  I could mount the drive I had copied and read it.
Fdisk showed all the partitions were still there so I decided to
check the boot flag. It obviously had been working at first but
could have gotten modified.

/dev/sda1 is the primary partition with sd5 being swap
off of sd2 which is an extended partition. fdisk told me that the
boot flag defaults to sda5 so I told it to set the flag and
re-wrote the table. A re-running of fdisk confirmed that the *
was now on sda5 so it was time to try to boot again.

It boots again on the old system.  The only event between
the last time it worked and now was the total dd copy.

Any better suggestions as to how the boot flag got
changed are quite welcome. This probably means that the boot flag
in the copy I made is also corrupt and will need to be set when
applied to a new disk. I have used dd many times and never had it
write any changes to the input so I am confused.

Thanks and so far, it is back like it was.


What is the Dell Service Tag for that computer, so we can look it up?

http://www.dell.com/support/home/us/en/19/Products/


What hardware changes have been made since it was shipped?


Have you run memtest86+ for 24+ hours as currently configured in the Dell?


Have you checked the beep code against the Dell Service Manual?  What 
was the beep code?  What does it mean?



What is the model of the 10 GB HDD?


Have you run all of the manufacturer's diagnostics on the 10 GB HDD as 
currently configured in the Dell?


http://www.seagate.com/support/downloads/seatools/



David

Re: What On Earth Did I do?

[Felix Miata]

Martin McCormick composed on 2017-05-05 22:11 (UTC-0500):
...
IIRC, and WRT PCs containing only Debian (and/or another Linux distro), DOS,
OS/2 and/or Windows:

A boot flag is always irrelevant when set on a logical partition.

A boot flag is irrelevant on every Debian system's HD0 not also containing
bootable DOS, Windows and/or OS/2 if Debian bootloader code (Grub, Lilo,
Syslinux, etc.) is present in the MBR of HD0.

The primary purpose of a boot flag is to be found by
DOS/Windows/legacy-compatible MBR code, which can only make use of it if found
on a primary partition that also contains a bootable filesystem or other
bootloader code in the partition's PBR.

A secondary purpose of a boot flag is for legacy operating systems to determine
which primary partition is to be assigned a drive letter.

IOW, if a PC only has Debian and uses Grub, Lilo, Syslinux or other bootloader
packaged by Debian and installed to MBR to boot, a partition boot flag is always
irrelevant.
-- 
"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: Update Notifier

[Debian Mailing Lists]

On Fri, 2017-05-05 at 16:32 +, sare...@att.net wrote:
> Why doesn't Debian 8 Cinnamon notify when updates are ready to
> install after all these years Debian has existed? Don't tell me there
> is one, because after installing Debian I waited a long time to see
> if a notification would pop up. It never did. I know about doing apt-
> get update && apt-get upgrade,but why should we have to use a command
> line? It makes me wonder about Debian security. Would you please put
> an update notifier in all your versions of Debian.

You can also install the package pk-update-icon

This can be found in the jessie-backports repo.

Thanks
Matt

What On Earth Did I do? (was Boot Drives for older Systems)

[Martin McCormick]

This story has a good ending but I am mystified.

Until the new boot drives I ordered get here, I took an
old slow 10GB Maxtor drive and made a new installation of Debian
jessie and got it like I wanted it. It booted fine on the older
Dell system whose drive went to the ultimate bit bucket so I
decided to save the image via dd so as to dd it to other boot drives.

dd if=/dev/sdb of=systemname.bin

The image copied slowly but did appear to copy so I put
the drive that had been copied back in to the system being
repaired and booted up again.  There was that sickening beep-beep
one hears when the game is over before it starts.  I checked the
jumper and it was okay for being the master boot drive.

I tried it on a known good system and no luck there. Did
I accidentally reverse the if and of names?  No because had I
does so, the target would have been trashed. It is also 7 times
bigger than the source so it would have been a bust all round and
the system I had used for the copy was still up and running when
all was done.  I could mount the drive I had copied and read it.
Fdisk showed all the partitions were still there so I decided to
check the boot flag. It obviously had been working at first but
could have gotten modified.

/dev/sda1 is the primary partition with sd5 being swap
off of sd2 which is an extended partition. fdisk told me that the
boot flag defaults to sda5 so I told it to set the flag and
re-wrote the table. A re-running of fdisk confirmed that the *
was now on sda5 so it was time to try to boot again.

It boots again on the old system.  The only event between
the last time it worked and now was the total dd copy.

Any better suggestions as to how the boot flag got
changed are quite welcome. This probably means that the boot flag
in the copy I made is also corrupt and will need to be set when
applied to a new disk. I have used dd many times and never had it
write any changes to the input so I am confused.

Thanks and so far, it is back like it was.

Martin McCormick

Re: suspend/resume device

[Charles Kroeger]

> That "apt-listchanges" package comes in handy

thanks for that tip, I have it installed now.

-- 
CK


pgp0IIh2byNkp.pgp
Description: OpenPGP digital signature

Re: /tmp/.X0-lock

[Charles Kroeger]

> Does the PID in the lock file correspond to a running process?
> 
> ps -f `cat /tmp/.X0-lock`

I get nothing from that command

> Are there any running instances of an X server?
> 
> ps -fC Xorg

UIDPID  PPID  C STIME TTY  TIME CMD
root  2994  2812  0 17:36 tty7 00:01:23 /usr/lib/xorg/Xorg :0 -seat
seat0 -auth /var/run/lightdm/root/:0 -nolist

that would be the one I'm using. I will try that command after stopping the
X-server

after stopping the X-server I ran: ps --fC Xorg
UID PID PPID C STIME TTY TIME CMD

on running startx (as user) the X server failed to start with these error
messages:

(EE) could not create lock file in /tmp/.tX0-lock

Xinit: unable to connect to X server: connection refused

Xauth: error in locking authority file /home/charles/.Xauthority

the contents of this file is some machine language symbols and some
english -MIT-MAGIC-COOKIE-1   (and) mundo 0  -MIT-MAGIC-COOKIE-1
(and that is all)

thanks for being patient,

--
CK



pgpt6yEc6GH2R.pgp
Description: OpenPGP digital signature

Re: /tmp/.X0-lock

[Ben Caradoc-Davies]

On 06/05/17 12:09, Charles Kroeger wrote:

not that I know of how do you tell if there's another X server running. I mean
there is after I do a sysvinit boot (from the grub advanced menu) but on a
reboot of course the X server obviously shuts down (or does it?)


Does the PID in the lock file correspond to a running process?

ps -f `cat /tmp/.X0-lock`

Are there any running instances of an X server?

ps -fC Xorg

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: suspend/resume device [SOLVED]

[Charles Kroeger]

thank you Cindy-Sue, I did have both of those files but the one with RESUME in
it and it did list a mysterious UUID device number (I don't know where it got
that as this is a desktop but it does get a  lot of dist-upgrades I'll admit)
so that's the one I removed and added 'none' in its place.

the other file /etc/initramfs-tools/initramfs.conf didn't mention the resume
device, so it had its own file. (maybe I should just remove that file?)

anyway, well done you and all the best.

-- 
CK


pgpujxbhJDiQS.pgp
Description: OpenPGP digital signature

Re: Live Fille System Backup

[Henrique de Moraes Holschuh]

On Fri, 05 May 2017, John Conover wrote:
> Also be advised if "dest/" is a FAT formatted SD card, there is a file
> size limit of 4GB, (and the -aAXv argument to rsync(1) may not be
> viable to restore the permission/ACL of files/directories.)

Using rsync on non-POSIX filesystems is a Bad Idea, it is going to
mangle a lot of metadata.

> If "dest/" is archival, (i.e., must be recoverable for a long period
> of time,) saving the MD5/SHA* hash values of files in "source/" is
> advisable for verification that a file is not corrupt sometime in the
> future.

In that case, using tar+lzip (*not* xz) and adding par2 ECC blocks might
be in order.  Refer to the lzip/plzip and par2 packages.

-- 
  Henrique Holschuh

Re: /tmp/.X0-lock

[Charles Kroeger]

>ls -ld /tmp

drwxrwxrwt 10 root root 20480 May  5 18:58 /tmp

(looks good)

>ls -l /tmp/.S0-lock

-r--r--r-- 1 root root 11 May  5 17:36 /tmp/.X0-lock

>df /tmp

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdc1  245996848 42724396 203256068  18% /

> If /tmp/.X0-lock already exists, is there another instance of the X 
> server running (with that PID? Or did a previous instance crash without 
> removing it?> 

not that I know of how do you tell if there's another X server running. I mean
there is after I do a sysvinit boot (from the grub advanced menu) but on a
reboot of course the X server obviously shuts down (or does it?)

-- 
CK


pgpTvuzSQSKrH.pgp
Description: OpenPGP digital signature

Re: suspend/resume device

[Cindy-Sue Causey]

On 5/5/17, Charles Kroeger  wrote:
> on a normal boot I get a long wait (30 seconds +-) whilst the cursor winks
> then
> the message: waiting on suspend/resume device, before resuming the steps to
> boot to a login prompt.


Your words, "boot", "wait", and "30 seconds" there triggered this
response. Did you do any upgrades in last couple days? This may not
affect others but on Stretch, I received the following
"apt-listchanges" auto-generated message that I knew was one of those
"keeper" kind of things:

 BEGIN apt-listchanges: News MESSAGE 

initramfs-tools (0.129) unstable; urgency=medium

  * Some systems that do not support suspend-to-disk (hibernation) will
require a configuration change to explicitly disable this.

From version 0.128, the boot code waits for a suspend/resume device
to appear, rather than checking just once.  If the configured or
automatically selected resume device is not available at boot time,
this results in a roughly 30 second delay.

You should set the RESUME variable in
/etc/initramfs-tools/conf.d/resume or
/etc/initramfs-tools/initramfs.conf to one of:

- auto - select the resume device automatically
- none - disable use of a resume device
- UUID= - use a specific resume device (by UUID)
- /dev/ - use a specific resume device (by kernel name)

 -- Ben Hutchings   Thu, 20 Apr 2017 23:21:32
+0100

 END apt-listchanges: News MESSAGE 

That "apt-listchanges" package comes in handy for putting that type of
information right in your face during upgrades.

Hope that helps someone somewhere some day... :)

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with plastic sporks *

systemd-fstab-generator failed to create mount

[Charles Kroeger]

the whole error message is: systemd-fstab-generator failed to create mount unit
five /run/systemd/generator/-.mount   as it already exit possible duplicate
entry in /etc/fstab? I've enclosed my fstab file:

#
proc/proc   procdefaults0   0

#ata-Hitachi /dev/sdb1
UUID=8c502a23-b2ab-4670-b4e8-86d79b595aa5/  ext4errors=remount-ro
0  0

#ata-Hitachi /dev/sdb2  "BACKUP"
UUID=71e15b9e-e549-4157-a9dc-1288c4a5a20e/   ext4errors=remount-ro
0  0

#ata-Crucial /dev/sdc1 
UUID=81183740-7329-4088-b467-4c24c4345f67/  ext4 errors=remount-ro
0  0

/dev/sr0   /media/cdrom0   udf,iso9660 user,noauto 0   0


if systemd-fstab-generator is now making its own fstab file, should we delete
our old one?

-- 
CK


pgpxxhYq2AKrr.pgp
Description: OpenPGP digital signature

suspend/resume device

[Charles Kroeger]

on a normal boot I get a long wait (30 seconds +-) whilst the cursor winks then
the message: waiting on suspend/resume device, before resuming the steps to
boot to a login prompt.

-- 
CK


pgpPyMPjo4Wft.pgp
Description: OpenPGP digital signature

Re: Live Fille System Backup

[John Conover]

Henrique de Moraes Holschuh writes:
> On Fri, 05 May 2017, Sergei G wrote:
> > I am not convinced that rsync can handle all device type files, all types
> > of links and other attributes I don't even know about.  I am not convinced
> > that anyone actually restored file system using rsync.  Does it really work?
> 
> Yes, it does.  Been there, done that.  But it takes a lot of command
> line options, just a plain "rsync source/ dest/" usually won't be
> enough.
> 
> The caveats about quiescing anything that might modify data while rsync
> is running do apply.
>

Also be advised if "dest/" is a FAT formatted SD card, there is a file
size limit of 4GB, (and the -aAXv argument to rsync(1) may not be
viable to restore the permission/ACL of files/directories.)

If "dest/" is archival, (i.e., must be recoverable for a long period
of time,) saving the MD5/SHA* hash values of files in "source/" is
advisable for verification that a file is not corrupt sometime in the
future.

John

-- 

John Conover, cono...@rahul.net, http://www.johncon.com/

Re: /tmp/.X0-lock

[Ben Caradoc-Davies]

On 06/05/17 11:06, Charles Kroeger wrote:

running freshly upgraded kernel image 4.9.0.3 on normal boot with startx
command but getting the following error message from (X server) xorg: could not
create lock file in /tmp/.X0-lock (the contents of, are the numbers 2994)
unable to connect to the X server: connection refused


Check permissions and free space:

ls -ld /tmp
ls -l /tmp/.X0-lock
df /tmp

If /tmp/.X0-lock already exists, is there another instance of the X 
server running (with that PID? Or did a previous instance crash without 
removing it?


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

/tmp/.X0-lock

[Charles Kroeger]

running freshly upgraded kernel image 4.9.0.3 on normal boot with startx
command but getting the following error message from (X server) xorg: could not
create lock file in /tmp/.X0-lock (the contents of, are the numbers 2994)
unable to connect to the X server: connection refused

there's a lot about this problem on the Internet but the information is
quite old and nothing applies to my present problem, it would seem. 

happily and also the reason I'm writing this letter (et.al) is that I can still
use the sysvinit boot option that presents a graphical login and after that
starts the X server. (I then have to run 'service network restart' to connect
to the Internet and there is complaining about that being deprecated but good
thing something works.

there's more error messages I've decided to keep as separate post, in the spirit
of helping others down the line. 

-- 
CK


pgpwSVAEELYnJ.pgp
Description: OpenPGP digital signature

debian-installer preseeding over https

[Mario Abajo]

Hello,
Playing with unattended deployments of debian using foreman (
https://theforeman.org/) i found out that debian-installer doesn't support
loading the preseeding file from a https server. It do it well from a http
url but using ssl never works. I have found an old question in
stackoverflow about this (
https://serverfault.com/questions/320019/how-to-use-debug-debian-preseed-with-ssl-using-startssl-certs)
explaining that the problem comes from the wget in busybox not compiled
with SSL support, it's old, but it's still true with the actual stable and
testing releases. I would like to know how to fill a bug (wishlist) for
this, also, i would like to hear some opinions about it; other distros have
this support even with the fact that it's not perfect (because you trust
all certificates, and that's not good) but at least you avoid simple
sniffers for tacking your installation data (and hash passwords).

Thanks in advance,
  Mario Abajo

Re: Live Fille System Backup

[Bob Weber]

On 5/4/17 7:17 PM, Sergei G wrote:
> I am running Raspberry PI and I would like to dump full file system without
> shutting down the system.  One machine runs nginx and another runs
> PostgreSQL.  I have had a good success with FreeBSD and dump software, because
> it is part of the OS and core team maintains it.  
>
> However, dump utility is no longer maintained by the original developer and is
> effectively getting too old.  I am no longer sure what is a dump-like solution
> that's easy to work with at a file system level.
>
> I would like a backup tool that does not bring a million dependencies with MBs
> of files.  Something that works on server without X Windows and can send
> backup to an externally attached USB drive.  Nothing fancy.   No network
> infrastructure.  Incremental backups would be greatly appreciated.  Ability to
> pipe to a compression program is a plus, just like I did with dump.
>
> I'd like to be able to apply a similar solution on actual Debian and Ubuntu
> VMs.  When I go to Ubuntu I might have to deal with newer ext file systems. 
> Not sure what is supported there.
>
> If there is no good live backup solution, I am willing to take the system down
> and back it up using another system.  It is not ideal, but it would work.
>
> Any advice would be greatly appreciated.
>
> P.S. All mentioned systems are Debian based and I feel that it is appropriate
> to ask on Debian user list.
>
>
> Thank you
I use rsnapshot to live backup my root partition (home is mounted on another
partition) to a directory under home.  rsnapshot uses rsync with the appropriate
options (I do add some extras) to do a backup.  I do this before I do an "apt
upgrade"  so that if things don't work well after the upgrade I can restore what
was there before.  I have used this "backup" several times to take my system
back to before the upgrade and have not had any problems.  I am not backing up
databases so those remarks here about that sort of backup apply.  To restore I
boot a copy of  SystemRescueCd, mount the source and destination partitions and
run a script that runs rsync with similar options to restore the root back to a
working state.  The rsnapshot backup is an exact copy (uncompressed) of the root
so you can go get a single file easily if you need to.

I also have several VM's of different Debian installs (unstable and testing)
that I upgrade every few days to follow any problems that arise but since the
VM's can't duplicate my main system's xorg setup they don't catch everything.  I
use rsnapshot on these VM's also and have restored the rsnapshot backup several
times.  I have tried btrfs on these vm's but I always ended up running out of
free space during an upgrade so I would have to delete some older snapshots to
free up some space and run the upgrade again.  These vm's are running on 20 to
30 GB virtual hard drives so there is not a lot of free space for the btrfs
snapshots.

Grub can also handle booting an iso of SystemRescueCd so I don't even have to
find a cd with SystemRescueCd on it.  Just select the grub menu option for
SystemRescueCd.

For a daily backup I use backuppc to backup all my local systems and a remote vm
at digital ocean.  These backups are all on live systems and would have the
problems with live databases as described by others.  You just need an ssh login
using rsa key pairs so you don't have to supply a password to backuppc. 
Postgresql has ways to backup databases and is made very easy by using a program
like "pgadmin III" (in Debian as pgadmin3/testing,unstable,now 1.22.2-1 amd64). 
You might have to stop database updates while you backup though.  Individual
tables or the whole database can be backuped.

...bob

Re: Live Fille System Backup

[Henrique de Moraes Holschuh]

On Fri, 05 May 2017, Sergei G wrote:
> I am not convinced that rsync can handle all device type files, all types
> of links and other attributes I don't even know about.  I am not convinced
> that anyone actually restored file system using rsync.  Does it really work?

Yes, it does.  Been there, done that.  But it takes a lot of command
line options, just a plain "rsync source/ dest/" usually won't be
enough.

The caveats about quiescing anything that might modify data while rsync
is running do apply.

-- 
  Henrique Holschuh

Re: Live Fille System Backup

[Henrique de Moraes Holschuh]

On Fri, 05 May 2017, Sergei G wrote:
> it would be naive at best to think that busy files can be handled at
> application level.   No, rsync cannot handle the problem of entire file
> system dump.  Neither it is safe to handle all special file cases.  I am
> thinking about sparse files (if Linux has those).

Yes, Linux has sparse files.  And yes, rsync can deal with sparse files,
check its documentation.  It can also deal with many "special files",
extended attributes and ACLs properly, if directed to do so.

Also, shortcut "file/inode changed" detection can break on Debian
*system* directories.  *You have been warned*.  Either always do a full
backup of those, or use something that actually _always_ checksums the
contents (such as rsync -c), when doing dedup or incremental backups.

As for live data such as running database backends, or active logs, you
have to snapshot/quiece such applications for a rsync backup just like
you'd have to do for filesystem or device snapshotting, or any other
non-application-level backup.

-- 
  Henrique Holschuh

attempt to read or write outside of disk 'hd0'

[Joe]

I've just done the first upgrades for months on a netbook and a USB
hard drive, both containing sid installations. Yes, I know that's
risky, but the longer you leave it, the riskier it gets...

The netbook was fine. The hard drive installation completed an apt-get
update and apt-get upgrade while booted on a two-year-old laptop. I
thought I'd reboot before the dist-upgrade, as I usually do this, and
lo and behold, I'm dropped to a grub rescue> prompt after the message
in the subject line...

I can list the (hd0,1)/boot/ directory, but insmod normal gives the
illegal access message again.

The Net mostly reckons this is due to using too large a drive on an old
BIOS, but since this very drive has booted on this very computer many
dozens of times, without change in the partition structure, that is not
the case here.

I plugged it into the netbook, where it has also worked many times,
with the same result. I booted the netbook itself, chrooted, did an
update-grub followed by a grub-install to the *correct* drive, no
errors found, no change in boot behaviour. As far as I can tell from
fdisk, the partition table looks right, or at least not wildly
incorrect as it would need to be to cause this.

I'm assuming this is not a kernel issue, as grub is failing to read its
own modules from partition 1 correctly, and has not come close to
displaying its kernel menu. Am I right? There is a new kernel, 4.7, and
that and later kernels certainly have issues on my main workstation.
It's an i386 installation, though I can't see that being relevant,
apt-get really shouldn't have put in any 64-bit-only stuff.

This is not a particularly valuable installation, it's no big deal to
reinstall, but that seems a very Windows thing to do. I'd like to fix
it, if anyone has any ideas.

-- 
Joe

Re: Live Fille System Backup

[Sergei G]

I just realized that busy files are pretty much impossible to deal with no
matter what.  If DB is in the middle of the transaction, then a "snapshot"
based backup will work (we simply loose that transaction data as it is
equivalent to crash).  Other busy files might be corrupted if those files
don't use transaction model.

I am not convinced that rsync can handle all device type files, all types
of links and other attributes I don't even know about.  I am not convinced
that anyone actually restored file system using rsync.  Does it really work?

I personally use rsync to synchronize data for application deployment and
it works great.  But I usually have no special files to worry about.

On Fri, May 5, 2017 at 1:35 PM, Sergei G  wrote:

> it would be naive at best to think that busy files can be handled at
> application level.   No, rsync cannot handle the problem of entire file
> system dump.  Neither it is safe to handle all special file cases.  I am
> thinking about sparse files (if Linux has those).
>
> On Thu, May 4, 2017 at 11:52 PM, Dejan Jocic  wrote:
>
>> On 04-05-17, Sergei G wrote:
>> > That's good to know.
>> >
>> >
>> > Thank you
>> >
>> >
>> > On 5/4/17 6:46 PM, Anders Andersson wrote:
>> > > On Fri, May 5, 2017 at 1:17 AM, Sergei G 
>> wrote:
>> > > > I would like a backup tool that does not bring a million
>> dependencies with
>> > > > MBs of files.  Something that works on server without X Windows and
>> can send
>> > > > backup to an externally attached USB drive.  Nothing fancy.   No
>> network
>> > > > infrastructure.  Incremental backups would be greatly appreciated.
>> Ability
>> > > > to pipe to a compression program is a plus, just like I did with
>> dump.
>> > > > [...]
>> > > > Any advice would be greatly appreciated.
>> > > You won't like my solution, and it doesn't work with your current
>> > > setup because it requires a specific file system: btrfs[1]. I'm
>> > > posting it here for two reasons:
>> > >   1) You might consider using btrfs on new installs
>> > >   2) Someone else may search and find the thread
>> > >
>> > > After switching to btrfs I can now take instant snapshots of selected
>> > > filesystems, transfer these to remote servers for backup, and most
>> > > important: btrfs can track the *exact difference* between two
>> > > snapshots taken over time, and only transfer the changes. All of this
>> > > is very quick, because the filesystem already knows exactly what
>> > > changed: Permission bits, file sizes, deleted files, changed data,
>> > > whatever, all is already kept in a log. It also means that nothing
>> > > will be missed, for example ACL bits etc.
>> > >
>> > > The delta is just a simple stream of data that can be compressed if
>> > > necessary. Typically it is transmitted to a backup server where it is
>> > > "replayed" so that you have a full clone of the original system.[2]
>> > >
>> > > In debian I use the little tool, btrbk[3], to automate all of this.
>> > > You can simply do it manually if you want.
>> > >
>> > > [1] https://btrfs.wiki.kernel.org/index.php/Main_Page
>> > > [2] https://btrfs.wiki.kernel.org/index.php/Incremental_Backup
>> > > [3] https://github.com/digint/btrbk
>> > >
>> >
>>
>> Perhaps rsync can do the job for you?
>>
>>
>

Re: Live Fille System Backup

[Sergei G]

it would be naive at best to think that busy files can be handled at
application level.   No, rsync cannot handle the problem of entire file
system dump.  Neither it is safe to handle all special file cases.  I am
thinking about sparse files (if Linux has those).

On Thu, May 4, 2017 at 11:52 PM, Dejan Jocic  wrote:

> On 04-05-17, Sergei G wrote:
> > That's good to know.
> >
> >
> > Thank you
> >
> >
> > On 5/4/17 6:46 PM, Anders Andersson wrote:
> > > On Fri, May 5, 2017 at 1:17 AM, Sergei G 
> wrote:
> > > > I would like a backup tool that does not bring a million
> dependencies with
> > > > MBs of files.  Something that works on server without X Windows and
> can send
> > > > backup to an externally attached USB drive.  Nothing fancy.   No
> network
> > > > infrastructure.  Incremental backups would be greatly appreciated.
> Ability
> > > > to pipe to a compression program is a plus, just like I did with
> dump.
> > > > [...]
> > > > Any advice would be greatly appreciated.
> > > You won't like my solution, and it doesn't work with your current
> > > setup because it requires a specific file system: btrfs[1]. I'm
> > > posting it here for two reasons:
> > >   1) You might consider using btrfs on new installs
> > >   2) Someone else may search and find the thread
> > >
> > > After switching to btrfs I can now take instant snapshots of selected
> > > filesystems, transfer these to remote servers for backup, and most
> > > important: btrfs can track the *exact difference* between two
> > > snapshots taken over time, and only transfer the changes. All of this
> > > is very quick, because the filesystem already knows exactly what
> > > changed: Permission bits, file sizes, deleted files, changed data,
> > > whatever, all is already kept in a log. It also means that nothing
> > > will be missed, for example ACL bits etc.
> > >
> > > The delta is just a simple stream of data that can be compressed if
> > > necessary. Typically it is transmitted to a backup server where it is
> > > "replayed" so that you have a full clone of the original system.[2]
> > >
> > > In debian I use the little tool, btrbk[3], to automate all of this.
> > > You can simply do it manually if you want.
> > >
> > > [1] https://btrfs.wiki.kernel.org/index.php/Main_Page
> > > [2] https://btrfs.wiki.kernel.org/index.php/Incremental_Backup
> > > [3] https://github.com/digint/btrbk
> > >
> >
>
> Perhaps rsync can do the job for you?
>
>

Re: Installation Input required

[Pascal Hambourg]

Le 05/05/2017 à 11:16, to...@tuxteam.de a écrit :


On Fri, May 05, 2017 at 02:26:44PM +0530, Ashok Inder wrote:


During the entire setup screen, the debian installer did not asked me
for the 2nd or 3rd DVD. Also many a places its mentioned that the DVD is
a set of 12 DVD but I only found 3 set DVD.

Support pages mention that installer will ask for other part of the DVD
as an option. It never asked, only driver cd/dvd was asked.

Just wondering that did I missed something?


The Debian installer does not know how many CDs or DVD there are nor 
what they contain.


I remember that, after scanning the first installation disk, the Debian 
installer used to ask whether I wanted to scan other disks. I have not 
seen that option for a long time. Maybe it is available only when 
booting from a real optical disk instead of a USB drive.



Also I installed with Sudo option (no root account), will this be of any
disadvantage at anytime in future over Sudo considering I'm not a power
user.


Yes. It will be a disadvantage if you need to log in directly as root to 
fix things when log in as a normal user does not work any more (e.g. 
/home filesystem full or mounted read-only or could not be mounted, or 
corrupted user profile).



There is just one downside I know of: if the system panics on boot,
e.g. because it can't mount the root file system (say, because it's
corrupted), it will ask you for the root password before giving you
a root shell


Of course not. If the initramfs cannot mount the root filesystem, it 
cannot read /etc/shadow and check the root password. It just drops a 
root shell.


The root password is asked when booting in emergency mode, either when 
selecting a "rescue" entry in the boot loader or when something went 
wrong during the init phase, e.g. a filesystem listed in /etc/fstab 
could not be mounted.

Need help with Pidgin

[Dennis Wicks]

I installed Pidgin from the repository but I can't get it to
work.


I have setup my user id, and that seems to work. But when I
enable that user

it never connects. Everything I try indicates that it is not
making connection
with the chat server. Does anybody have any ideas? I have
searched for firewall
and other problems associated with Pidgin but nothing found.

BTW, I am trying to use Yahoo Messenger if that makes a
difference.


TIA & TNX!
Dennis

Re: Booting a CF or SD card from an internal card reader

[David Wright]

On Fri 05 May 2017 at 13:53:00 (-0400), Stefan Monnier wrote:
> >> Of course it all depends on what you mean by "booting from".  AFAICT in
> >> Leandro's situation, he's loading Grub from some other disk (probably
> >> the main HDD or SSD), so he's already "not booting from the SD card" in
> >> this sense.
> > By "booting from" I mean everything which is needed to bring the OS up
> > is located on the SD or CF card.
> 
> AFAIK in his case, Grub itself is already on another device because the
> BIOS can't boot directly from the SD card.  So, he can't "boot from" his
> SD card using your definition.
> 
> > In essence, the card can be transferred to to another machine and will
> > still boot. What you describe below I'd refer to as "booting into the
> > OS" ; it cannoot be done without the assistance of software on the
> > machine itself.  I hope this is not an artificial distinction.
> 
> I fully agree: I myself tried to setup a "rescue USB key" that could
> boot everywhere, but that simply can't work on those machines whose
> BIOS simply doesn't know how to boot from USB.
> 
> > In principle this is a viable booting method but there are issues to be
> > aware of.
> 
> Oh, yes.
> 
> > The kernel on the main HDD or SSD is unlikely to be the Tails
> > kernel so a third device would be needed to hold such a kernel;
> 
> You don't need a third device.  You need to consciously/carefully save
> your Tails kernel and initrd somewhere on the HDD/SSD.  You can use
> a separate "TAILS-BOOT" partition on that HDD/SSD for that, or you can
> place them in "the normal partition" but under a special name like
> "vmlinuz-tails" and "inird.img-tails".

I'm using a third device here for a different reason: what I'm booting
is the netinst d-i, so the files on the hard drive will be blown away.

I've booted From the pre-existing Grub2 on the hard drive, but Into
the netinst.iso file on a FAT USB stick by loop-mounting it (Brian's
terminology).

That works fine until the d-i tries to read the "CD-ROM", but then
it's simply a matter of pulling the FAT stick, inserting another one
where netinst.iso has been copied to /dev/sdX itself (not to a FAT
filesystem) and pressing Continue.

> > The OP in the original thread actually booted in this way from the hard
> > disk, but (as it fortuitously happened) kernel, initrd and OS on hard
> > disk and SD card were identical.
> 
> That must have been "beginner's luck", indeed.

Actually, I think it was more because they used a sole Debian DVD for
installing both the hard drive's system and the one on the SD. The
OP in the original thread is probably one of the most experienced
d-i installers on this list.

Cheers,
David.

Re: Booting a CF or SD card from an internal card reader

[Brian]

On Fri 05 May 2017 at 13:53:00 -0400, Stefan Monnier wrote:

> >> Of course it all depends on what you mean by "booting from".  AFAICT in
> >> Leandro's situation, he's loading Grub from some other disk (probably
> >> the main HDD or SSD), so he's already "not booting from the SD card" in
> >> this sense.
> > By "booting from" I mean everything which is needed to bring the OS up
> > is located on the SD or CF card.
> 
> AFAIK in his case, Grub itself is already on another device because the
> BIOS can't boot directly from the SD card.  So, he can't "boot from" his
> SD card using your definition.

Indeed. I thought I had highlighted that a few times, but maybe not.
GRUB doesn't see a card reader on a PCI bus.
> 
> > In essence, the card can be transferred to to another machine and will
> > still boot. What you describe below I'd refer to as "booting into the
> > OS" ; it cannoot be done without the assistance of software on the
> > machine itself.  I hope this is not an artificial distinction.
> 
> I fully agree: I myself tried to setup a "rescue USB key" that could
> boot everywhere, but that simply can't work on those machines whose
> BIOS simply doesn't know how to boot from USB.

GRUB's nativedisk could help with this. It does on my machines which
don't know how to boot from USB.

> > In principle this is a viable booting method but there are issues to be
> > aware of.
> 
> Oh, yes.
> 
> > The kernel on the main HDD or SSD is unlikely to be the Tails
> > kernel so a third device would be needed to hold such a kernel;
> 
> You don't need a third device.  You need to consciously/carefully save
> your Tails kernel and initrd somewhere on the HDD/SSD.  You can use
> a separate "TAILS-BOOT" partition on that HDD/SSD for that, or you can
> place them in "the normal partition" but under a special name like
> "vmlinuz-tails" and "inird.img-tails".

Fair enough.
 
> > The OP in the original thread actually booted in this way from the hard
> > disk, but (as it fortuitously happened) kernel, initrd and OS on hard
> > disk and SD card were identical.
> 
> That must have been "beginner's luck", indeed.

I've done the same myself. It works. Great! Then I've discovered the
special circumstances in which the procedure was carried out. Usually
when something goes wrong.

(Totally off-topic: I use the dialog utility with a gauge widget. After
many years the script using it stopped working. I read the manual. It
has "integer" in it for the section on gauge. One word made all the
difference between a working and non-working script. The new input I
have now has no integer values. No wonder the script didn't work).

Aren't Debian computers wonderful? :)

-- 
Brian.

Re: is there a firewall which blocks the connection

[Abdelkader Belahcene]

Thanks for reply
I solved the problem


it was blocked by a  firewall enabled by default in linuxlite.
I just disabled by usibg   ufw .
thanks again

Re: Migration 32 bits vers 64 bits gros problème avec dpkg testing

[Étienne Mollier]

Bonjour Philippe,

Philippe Merlin, le 2017-05-04 à 14:53:16 CEST :
> Sur ce poste est installé la Debian testing à jour et j'ai
> essayé de migrer d'une version 32 bits vers  64 bits en suivant
> la doc
>
>   https://wiki.debian.org/CrossGrading

Intéressante manipulation, j'ai essayé dans une machine
virtuelle.  Le moins qu'on puisse dire, c'est que c'est délicat.
Ma configuration était une machine en Testing avec uniquement les
composants de base, donc je suis probablement passé à côté des
problèmes de configuration.

Avant toute chose, j'espère que tu as une copie de sauvegarde des
donnée de ta machine et de sa configuration et que tu sais
comment la restaurer.

Les liens en bas de la page du wiki CrossGrading renvoient sur
d'autres retours d'expérience. Il ne faut pas hésiter à les
consulter également pour voir leurs approches.  En particulier,
j'ai trouvé de l'inspiration dans l'article suivant :


http://blog.zugschlus.de/archives/972-How-to-amd64-an-i386-Debian-installation-with-multiarch.html

Ce n'est pas mentionné dans ton courriel, mais je pars du
principe que tu as pu installer tes commandes tar, dpkg et apt en
version 64bits :

$ file $(which tar)
/bin/tar: ELF 64-bit LSB shared object, ...
$ file $(which dpkg)
/usr/bin/dpkg: ELF 64-bit LSB shared object, ...
$ file $(which apt-get)
/usr/bin/apt-get: ELF 64-bit LSB shared object, ...

Si ce n'est pas le cas et que quelque chose a cassé, les
manipulations à base de `ar' et de `busybox tar' mentionnée dans
les retours d'expérience peuvent éventuellement te sauver la
mise.

> Tout a très bien marché, j'ai bien migré vers une version 64
> bits de la testing  qui fonctionne très bien avec un noyau AMD
> 64 et des librairies 32 bits Merci Multi-Arch , mais il y a un
> mais Si je veux migrer tous les paquets  installés de 32
> bits à 64 bits par la commande :
>
>   dpkg --get-selections|grep  :i386 |sed -e s/:i386/:amd64/ | dpkg 
> --set-selections
>
> J'obtiens une liste de warning  :
>
>   package not in status nor available database a line xxx : :amd64
>
> une ligne par paquet répondant à dpkg --get-selections
> On dirait que les paquets amd64 sont ignorés.

Les paquets amd64 sont effectivement ignorés.  L'erreur se
produit dans mon cas d'utilisation aussi.  Un gourou de dpkg aura
sans doute la solution pour résoudre ce problème proprement.
Pour ma part, je suis passé par un fichier temporaire `packages`
pour pouvoir travailler dedans avec un éditeur de texte :

dpkg --get-selections\
| grep :i386 \
| sed -e s/:i386/:amd64/ \
| awk '{print $1}'   \
> packages

Le fichier `packages` contient une liste des paquets, un par
ligne, sans le champ d'état d'installation.  Je le réutilise pour
une première tentative d'installation des paquets en 64bits :

apt-get install $(xargs < packages)

À la première passe, `apt` sort des erreurs sur des paquets
introuvable.  Il faut les retirer de la liste.  Typiquement les
images linux 686 sont en cause, mais éventuellement certaines
versions de paquets devenus obsolètes, si des mises à jour sont
passées pendant la crossgrade.  C'est souvent le cas des paquets
qui ont leur numéro de version dans leur nom, pour faciliter
l'installation de versions différentes sur un même système.

En relançant la commande sans les erreurs sur les paquets
indisponibles, l'installation démarre.  Étant donné les
composants de cœur en 32bits qui nécessiteront un
désinstallation, il est vraisemblable qu'apt demande de confirmer
l'opération par la saisie au clavier d'une locution: "Yes, do as
I say!" sur une machine localisée en en_US.  La désinstallation
de perl-base:i386 dans mon cas a été la cause du message.  Si
l'opération plante, passer un coup `apt-get -f install` avant de
recommencer avec la liste complète des paquets.

Il est probable que certain services récalcitrants bloquent le
gestionnaire de paquet.  Dans ce cas j'ai eu la chance de pouvoir
désinstaller manuellement le composant, puis le réinstaller après
coup dans sa nouvelle architecture.  En l'occurrence, il
s'agissait du passage de acpid:i386 à acpid:amd64.

Quand une tentative d'installation de l'ensemble des paquets
termine en disant que tout est bien installé et qu'aucune
opération n'est à effectuer, alors la partie 64bits du système
est normalement complète.  Les paquets en 32bits peuvent être
enlevés :

dpkg --get-selections \
| grep  :i386 \
| awk '{print $1}'\
> packages.i386

apt-get remove $(xargs < packages.i386)

À ce stade, le système ne doit plus comporter de binaire 32bits
sur disque et être capable de tourner juste avec les paquets
amd64.  Reste à redémarrer la machine pour arrêter les processus
32bits encore en cours d'exécution, tel l'init.

Si la machine est capable de redémarrer correctement avec ses
services opérationnels après ce traitement, alors la bouteille

Re: Booting a CF or SD card from an internal card reader

[Stefan Monnier]

>> Of course it all depends on what you mean by "booting from".  AFAICT in
>> Leandro's situation, he's loading Grub from some other disk (probably
>> the main HDD or SSD), so he's already "not booting from the SD card" in
>> this sense.
> By "booting from" I mean everything which is needed to bring the OS up
> is located on the SD or CF card.

AFAIK in his case, Grub itself is already on another device because the
BIOS can't boot directly from the SD card.  So, he can't "boot from" his
SD card using your definition.

> In essence, the card can be transferred to to another machine and will
> still boot. What you describe below I'd refer to as "booting into the
> OS" ; it cannoot be done without the assistance of software on the
> machine itself.  I hope this is not an artificial distinction.

I fully agree: I myself tried to setup a "rescue USB key" that could
boot everywhere, but that simply can't work on those machines whose
BIOS simply doesn't know how to boot from USB.

> In principle this is a viable booting method but there are issues to be
> aware of.

Oh, yes.

> The kernel on the main HDD or SSD is unlikely to be the Tails
> kernel so a third device would be needed to hold such a kernel;

You don't need a third device.  You need to consciously/carefully save
your Tails kernel and initrd somewhere on the HDD/SSD.  You can use
a separate "TAILS-BOOT" partition on that HDD/SSD for that, or you can
place them in "the normal partition" but under a special name like
"vmlinuz-tails" and "inird.img-tails".

> The OP in the original thread actually booted in this way from the hard
> disk, but (as it fortuitously happened) kernel, initrd and OS on hard
> disk and SD card were identical.

That must have been "beginner's luck", indeed.


Stefan

Re: Installation Input required

[Stefan Monnier]

> That eases problems for Debian servers, I don't see an advantage to me.

Given that there is an advantage (for Debian servers), the question
isn't if there's an advantage to you, but instead if there's
a *dis*advantage to you (or others).


Stefan

Re: 3 écrans

[Thierry Bugier Pineau]

Bonjour
C'est intéressant, il faudrait que je voie comment ça se passe avec
deux GPUs de fabricant différent.
Il m'est arrivé dans diverses situations (matérielles) d'avoir des
modifications de disposition après un changement de résolution d'un
écran. Comme ce n'est pas quelque chose qu'on change souvent, je me
suis toujours contenté de réajuster la disposition logique des écrans.
Si deux écrans ont une résolution différente, l'un ayant plus de lignes
que l'autre, la souris peut "buter" contre la limite de l'écran ayant
le plus de hauteur si l'autre écran à côté ne prolonge pas l'affichage
à l'endroit précis de la souris. Pour moi c'est logique pour éviter de
perdre la souris dans une zone non affichée.
Quand on a plusieurs écrans, il faut veiller à ce que la disposition
logique (connue du système) reflète la réalité, sinon en passant la
souris d'un écran à l'autre, elle va "sauter" à un endroit inattendu. 
Si dans vote cas vous avez réussi à avoir vos 3 écrans avec une seule
carte graphique, c'est parfait. Utiliser les préférences d'affichage de
votre environnement graphique pour configurer la disposition des écrans
les uns par rapport aux autres, en reflétant la réalité. Ce sera
parfait. Je suis sour XFCE et avec le menu Whisker j'ai juste à taper
"affichage" pour avoir accès au programme qui va bien.
Pour ceux qui ne coonnaissent pas Whisker c'est un plugin pour XFCE,
disponible dans les dépôts qui donne au menu plus de richesse. Ca
ressemble d'assez près au menu démarrer d'un système pas libre du tout
en version 7. Mais c'est bien pratique pur lancer rapidement  son
programme favori. Un article au hasard, mais en français: https://la-va
che-libre.org/tag/whisker-menu/ pour avoir un aperçu.
Pour finir mes 4 écrans sont disposés en une matrice 2x2 : 2 lignes et
2 colonnes. A l'horizontal ça ne me parait pas confortable, il faudrait
2 bureaux et le champ de vision humain est plus proche du 16/10 que du
64/10 :)
Le vendredi 05 mai 2017 à 14:28 +0200, Eric Bernard a écrit :
> re,
> 
>   j'ai réussi en laissant faire le système à avoir mes 3 écrans (
> 1
>   sur la prise VGA de la carte interne Intel et 2 sur la Nvidia
> (DVI
>   et HDMI).
> 
>   Je rencontre 2 problèmes :
> 
>    - si je dépasse la résolution 1440x900, mes écrans ne sont
> plus à
>   la suite l'un de l'autre (1+1+1) mais se décalent vers le haut
>   comme si "l'espace bureau" n'était pas assez grand en largeur
> pour
>   des résolutions supérieures (1680x1050 ou 1920x1080)
> 
>   - l'écran "principale" des menus et de la barre des raccourcis
> est
>   sur l'écran de gauche alors que l'écran marqué comme principal
> est
>   bien celui du centre.
> 
>   
> 
>   Vos 4 écrans sont en superposition (2+2) ou alignés (1+1+1+1) ?
> 
>   
> 
>   merci de votre aide !!! 
> 
>   
> 
>   
> 
>   Le 05/05/2017 à 09:00, Thierry Bugier Pineau a écrit :
> 
> 
> 
> >   
> >   Bonjour
> >   
> > 
> >   
> >   Ce sont 2 écrans d'un modèle 27 pouces, 2 écrans d'un autre
> > modèle 24 pouces. Ils partagent tous la même résolution. 
> >   
> > 
> >   
> >   Je joins mon xorg.conf car il est nécéssaire d'en créer un
> > avec une telle configuration matérielle.
> >   
> > 
> >   
> >   Si vous l'utilisez, il faudra adapter le busID des GPUs, le
> > nom des sorties vidéo (HDMI, DVI, ...) et peut être aussi
> > la
> > position des écrans les uns par rapport aux autres.
> >   
> > 
> >   
> >   Le vendredi 05 mai 2017 à 08:12 +0200, Eric Bernard a écrit :
> >   
> > > Bonjour,
> > > 
> > >   4 écrans identiques (résolution etc..) ?
> > > 
> > >   
> > > 
> > >   
> > > 
> > >   
> > > 
> > >   Le 03/05/2017 à 14:39, Thierry Bugier Pineau a écrit :
> > > 
> > > 
> > > 
> > > >   Bonjour
> > > >   
> > > > 
> > > >   
> > > >   Je suis sur une configuration avec 4 écrans répartis
> > > > sur
> > > > 2 cartes graphiques. 
> > > >   
> > > > 
> > > >   
> > > >   Historiquement j'avais une carte NVidia de faible
> > > > puissance, juste pour mes activités type
> > > > bureautique. J'ai
> > > > récemment évolué vers 4 écrans an acquérant une
> > > > seconde
> > > > carte identique à la première.
> > > >   
> > > > 
> > > >   
> > > >   Cela a été un peu difficile: Nouveau plante quand
> > > > j'ai 2
> > > > GPUs. Attention, des cartes graphiques avec 2 GPU
> > > > existent,
> > > > et de ce que j'ai lu, c'est exactement comme avoir
> > > > 2 cartes
> > > > graphiques avec 1 GPU.
> > > >   
> > > > 
> > > >   
> > > >   J'ai dû utiliser contre mon gré le pilote Nvidia, et
> > > > utiliser un mode dit "Zaphod" (voir H2G2) pour
> > > > 

Re: Booting a CF or SD card from an internal card reader

[Brian]

On Fri 05 May 2017 at 08:44:48 -0400, Stefan Monnier wrote:

> > This is the 4-in-1 card reader; the one you want you are trying to boot
> > from. As indicted by /dev/mmcblk0p1 it is on the PCI bus. 'lspci' should
> > display the chip used; one from Ricoh?
> >
> > GRUB doesn't see anything on this bus (it has no drivers for the device),
> > so booting from it is not possible.
> 
> Of course it all depends on what you mean by "booting from".  AFAICT in
> Leandro's situation, he's loading Grub from some other disk (probably
> the main HDD or SSD), so he's already "not booting from the SD card" in
> this sense.

By "booting from" I mean everything which is needed to bring the OS up
is located on the SD or CF card. In essence, the card can be transferred
to to another machine and will still boot. What you describe below I'd
refer to as "booting into the OS" ; it cannoot be done without the
assistance of software on the machine itself. I hope this is not an
artificial distinction.

> Based on what I see above, his normal boot has 3 steps (ignoring the
> earlier BIOS/UEFI booting itself):
> 1- load/start Grub
> 2- load/start vmlinuz+initrd
> 3- load/start /sbin/init from the LABEL=TAILS partition
> 
> All 3 parts can be stored at different places.  My guess is that step
> 1 fetches its data (Grub's code as well as grub.cfg) from some HDD or
> SSD.  Apparently step 2 can't fetch its data from the SD card.
> 
> But step 3 can definitely fetch its data from the SD card.  So all you
> need is to put your vmlinuz+initrd onto a disk that Grub can see
> (e.g. alongside Grub rather than in the LABEL=TAILS partition).

In principle this is a viable booting method but there are issues to be
aware of. The kernel on the main HDD or SSD is unlikely to be the Tails
kernel so a third device would be needed to hold such a kernel; any old
kernel will not do. Then there is the initrd. The Tails one might not
contain the drivers for the card reader, so that will have be attended
to. Updates to any kernel or GRUB could lead to a failed boot.

The OP in the original thread actually booted in this way from the hard
disk, but (as it fortuitously happened) kernel, initrd and OS on hard
disk and SD card were identical.

Nice as it is to use the hardware built into a machine the acquisition
of an external USB card reader could make life simpler when it comes to
booting from an SD card.

-- 
Brian.

Re: Update Notifier

[Dominik George]

> Why doesn't Debian 8 Cinnamon notify when updates are ready to install
> after all these years Debian has existed? Don't tell me there is one,
> because after installing Debian I waited a long time to see if a
> notification would pop up. It never did. I know about doing apt-get
> update && apt-get upgrade,but why should we have to use a command
> line? It makes me wonder about Debian security. Would you please put
> an update notifier in all your versions of Debian.

$ apt install gnome-packagekit

If you think it should be part of the desktop task or
cinnamon-desktop-environment, please file a wishlist bug (in a more
helpful tone).

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Phone: +49 228 92934581 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature

Update Notifier

[sarez45]

Why doesn't Debian 8 Cinnamon notify when updates are ready to install after 
all these years Debian has existed? Don't tell me there is one, because after 
installing Debian I waited a long time to see if a notification would pop up. 
It never did. I know about doing apt-get update && apt-get upgrade,but why 
should we have to use a command line? It makes me wonder about Debian security. 
Would you please put an update notifier in all your versions of Debian.

Re: 4K problemen

[Paul van der Vlis]

Op 27-04-17 om 23:20 schreef Heiko Noordhof:

> In de tekst van de link die je hierboven noemt, staat dat de schrijver
> versie 1:7.6.1-1 van het
> "xserver-xorg-video-radeon" package geinstalleerd heeft. In Debian
> Jessie zit een oudere versie, nl: 1:7.5.0-1.
> 
> In stretch en jessie-backports zit inmiddels al weer nieuwere versie.
> Heb jij gewoon de Jessie versie gebruikt? Dan zou ik aanraden de
> backports in je apt-sources opnemen, en misschien ook een kernel daaruit
> te installeren (als die niet al vanzelf meekomt als depdency).

Het lijkt er op dat juist de nieuwere versie het niet goed doet!

Met Debian 8 geen problemen (op andere machine met dezelfde videokaart)
Met Debian 9 en Debian 8 met jessie-backports kernel zie ik wel
problemen op deze machine.

Pfff.

Groet,
Paul


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: testing, mhwaveedit, anyone else having problem saving files?

[songbird]

Victor A. Stoichita wrote:
...
> Hi songbird. Mhwaveedit works as usual here. I have 1.4.23 from testing
> repo. Just tried it on a flac file. Open -> edit -> save -> reopen = no 
> problem.
>
> Mhwaveedit is very useful for me too as it is blazing fast for basic
> audio file editing.
>
> Did you try "save as…" and "save selection as…" as well ?

Victor, 

  yes, i did, thank you for the test!

  that at least let's me know it is something on this end.  :)


  songbird

Re: Installation Input required

[David Wright]

On Fri 05 May 2017 at 08:17:34 (-0500), Richard Owlett wrote:
> On 05/05/2017 04:49 AM, Thomas Schmitt wrote:
> >[snip]
> >This question was asked often enough to cause the existence of
> >  https://www.debian.org/CD/faq/#not-all-images
> >which says
> >  "We don't store/serve the full set of ISO images for all
> >architectures, to reduce the amount of space taken up on the mirrors.
> >You can use the jigdo tool to recreate the missing ISO images
> >instead."
> >
> >
> >The advantage of Jigdo for the DVD mirror servers is that the bulk
> >of data can be fetched from Debian servers which provide packages.
> >Jigdo loads a compressed ISO image with lots of holes and then loads
> >all the package files which fit exactly into the holes.
> 
> That eases problems for Debian servers, I don't see an advantage to me.

That's because you're only thinking about your own space/bandwidth
consumption. However, if there are fewer servers, then those ones
will be busier, and download speeds suffer.

On dial-up, you pay for that speed reduction. In fact, when I used
dial-up at home, there were sites (like washington.edu, remember
Pine?) where it was worth telephoning my office machine (on broadband)
to start downloads there, then telephoning an hour later and
transferring the downloaded files (if they were ready) directly from
office to home, with no pausing. This was faster/cheaper than using the
ISP to download those files directly across the Atlantic.

Cheers,
David.

Re: testing, mhwaveedit, anyone else having problem saving files?

[Victor A. Stoichita]

Le 05 May 2017, songbird  a écrit :

>   i haven't had to use this program in a while, but today
> was trying to fix an audio file and when i go to save it
> the program gives error message:
>
>   Failed to open '/home/me/smb/tmp1.flac'!
>
>   which is also annoying because it opens the file without
> any problem, but then it also erases it so there's nothing
> left.
>
>   luckily i do have backups so the file is recoverable.
>
>   it's a simple program that is useful, but perhaps nobody
> else ever uses it?
>
>   p.s. doesn't matter what i try to call the file or
> extension...
>
>
>   songbird

Hi songbird. Mhwaveedit works as usual here. I have 1.4.23 from testing
repo. Just tried it on a flac file. Open -> edit -> save -> reopen = no problem.

Mhwaveedit is very useful for me too as it is blazing fast for basic
audio file editing.

Did you try "save as…" and "save selection as…" as well ?

Victor

Re: Booting a CF or SD card from an internal card reader

[David Wright]

On Fri 05 May 2017 at 07:58:06 (-0500), Richard Owlett wrote:
> On 05/05/2017 04:28 AM, Brian wrote:
> >On Fri 05 May 2017 at 05:34:13 +0200, Leandro Noferini wrote:
> >
> >>Brian  writes:
> >>
> >>>1. This HOWTO is a result of the discussion on debian-user beginning at
> >
> >It should be stressed that the HOWTO is applicable only to devices on
> >the USB bus.
> >
> >>Thanks a lot for this document because it hits a problem I found many
> >>months ago without solution for me. I would like to use my internal card
> >>reader (Lenovo X240) to boot in tails (https://tails.boum.org)
> >
> >I rarely dabble in hardware-related things, so a mistake or two could
> >creep into what follows.
> >
> >>My reader appears this way:
> >>
> >>
> >>~ $ lsusb
> >>Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
> >>
> >
> >The Lenovo X240 has a Smart Card reader and a 4-in-1 card reader (MMC,
> >SD, SDHC, SDXC). The Smart Card reader is on the USB bus. I have never
> >used one but it appears to have something to do with identity cards.
> >GRUB does not detect it with nativedisk so booting from it is not
> >possible.
> >
> >>The sd card with tails on appears this way:
> >>
> >>
> >>leandro@tricheco:~$ sudo fdisk /dev/mmcblk0
> >>
> >>Welcome to fdisk (util-linux 2.29.2).
> >>Changes will remain in memory only, until you decide to write them.
> >>Be careful before using the write command.
> >>
> >>Command (m for help): p
> >>Disk /dev/mmcblk0: 7,4 GiB, 7969177600 bytes, 15564800 sectors
> >>Units: sectors of 1 * 512 = 512 bytes
> >>Sector size (logical/physical): 512 bytes / 512 bytes
> >>I/O size (minimum/optimal): 512 bytes / 512 bytes
> >>Disklabel type: gpt
> >>Disk identifier: F12D15CF-2FC3-4852-8226-9D4F7E625B29
> >>
> >>Device Start End Sectors  Size Type
> >>/dev/mmcblk0p1  2048 5122047 512  2,5G EFI System
> >>
> >
> >This is the 4-in-1 card reader; the one you want you are trying to boot
> >from. As indicted by /dev/mmcblk0p1 it is on the PCI bus. 'lspci' should
> >display the chip used; one from Ricoh?
> >
> >GRUB doesn't see anything on this bus (it has no drivers for the device),
> >so booting from it is not possible.
> >
> >>Following your document I edited /etc/grub.d/40_custom adding these
> >>lines:
> >>
> >>
> >>menuentry 'Tails on CF card' {
> >>insmod part_msdos
> >>insmod ext2
> >>echo "Running nativedisk command. Please wait."
> >>nativedisk
> >>search --label --set=root TAILS
> >>linux /vmlinuz root=LABEL=TAILS ro
> >>initrd /initrd.img
> >>}
> >>
> >>
> >>But it is not working.
> >>
> >>If I give the "nativedisk" command in grub command line I get only
> >>
> >>
> >>(ahci0)
> >>
> >>
> >>Where am I wrong?
> >
> >I think you have possibly not appreciated the distinction between a card
> >reader on a USB bus and one on a PCI bus. The first should be visible to
> >GRUB and nativedisk (but, as you have seen, isn't always). The second is
> >never visible to GRUB.
> >
> 
> Not true.
> On my Lenovo T510 laptop I have
> 
> root@march-9-Jessie:/home/richard# ls /dev/mm*
> /dev/mmcblk0  /dev/mmcblk0p1  /dev/mmcblk0p2  /dev/mmcblk0p5
> 
> Although my BIOS will not boot from /dev/mmcblk0, the GRUB resident
> on /dev/sda1 has no trouble finding Debian on /dev/mmcblk0p1.

Which Grub are you talking about? Just to clarify, Grub running in
Linux (lspci, lsusb, etc given to a $ or # prompt) may have no
trouble; it's got a full set of drivers available. What we're
interested in is Grub running at boot time where it gives this
prompt:

grub>

This can still be part of "GRUB resident on" /dev/sda, if not
/dev/sda1, but the Linux OS's drivers are absent.

Looking back at this and the preceding thread, you posted:

> On 04/12/2017 12:13 PM, Pascal Hambourg wrote:
>> - while the SD card is inserted, in the GRUB menu press "c" to enter a
>> GRUB shell and report the result of the "ls" command.
>
>Did not see any way to capture the output. So made manual copy. The
>following appeared on a single line.
>
>(hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6)
>(hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1)

I see nothing here corresponding to /dev/mmcblk0p1.

> My notes are:
>
> with no usb devices present, I get
> (ahci) (ahci0,msdosXX) (ahci1)
> where XX maches the partions on my "hard disk" {it is actually a
> solid state drive which was manufactured to be a plugin 

testing, mhwaveedit, anyone else having problem saving files?

[songbird]

  i haven't had to use this program in a while, but today
was trying to fix an audio file and when i go to save it
the program gives error message:

  Failed to open '/home/me/smb/tmp1.flac'!

  which is also annoying because it opens the file without
any problem, but then it also erases it so there's nothing
left.

  luckily i do have backups so the file is recoverable.

  it's a simple program that is useful, but perhaps nobody
else ever uses it?

  p.s. doesn't matter what i try to call the file or 
extension...


  songbird

Re: Installation Input required

[Thomas Schmitt]

Hi,

i wrote:
> > The advantage of Jigdo for the DVD mirror servers is that the bulk
> > of data can be fetched from Debian servers which provide packages.

Richard Owlett wrote:
> That eases problems for Debian servers, I don't see an advantage to me.

The advantage for those who need them is that there are full DVD sets
for free. Which other distro still offers this ?

One may question the ergonomic quality of a set of 13 DVDs as on:
  https://cdimage.debian.org/debian-cd/8.7.1/amd64/jigdo-dvd/
But for example volume 1 of the 3 ISOs on
  https://cdimage.debian.org/debian-cd/8.7.1/amd64/jigdo-bd/
gives you the equivalent of 5 DVDs on one medium.
To be put on BD medium or on e.g. a 32 GB USB stick.


Have a nice day :)

Thomas

[Off-Topic]_hack-us legally

[Pyroteus]

https://www.welivesecurity.com/2017/04/27/hack-us-air-force-make-cash-legally/
Good Luck !

use non-US email accounts
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

Re: Booting a CF or SD card from an internal card reader

[Brian]

On Fri 05 May 2017 at 07:58:06 -0500, Richard Owlett wrote:

> On 05/05/2017 04:28 AM, Brian wrote:
> >
> >I think you have possibly not appreciated the distinction between a card
> >reader on a USB bus and one on a PCI bus. The first should be visible to
> >GRUB and nativedisk (but, as you have seen, isn't always). The second is
> >never visible to GRUB.
> 
> Not true.
> On my Lenovo T510 laptop I have
> 
> root@march-9-Jessie:/home/richard# ls /dev/mm*
> /dev/mmcblk0  /dev/mmcblk0p1  /dev/mmcblk0p2  /dev/mmcblk0p5
> 
> Although my BIOS will not boot from /dev/mmcblk0, the GRUB resident on
> /dev/sda1 has no trouble finding Debian on /dev/mmcblk0p1.

What I said is true. What you say above is also true. Of course, we are
talking about different things. :)

-- 
Brian.

Re: Installation Input required

[Henrique de Moraes Holschuh]

On Fri, 05 May 2017, Richard Owlett wrote:
> >The advantage of Jigdo for the DVD mirror servers is that the bulk
> >of data can be fetched from Debian servers which provide packages.
> >Jigdo loads a compressed ISO image with lots of holes and then loads
> >all the package files which fit exactly into the holes.
> 
> That eases problems for Debian servers, I don't see an advantage to me.

Correct when your issue is low-bandwidth or bandwidth cap.  Jigdo cannot
help, there... but a direct image download wouldn't, either: buying a
DVD/BD set makes more sense.

Jigdo is indeed a direct advantage for the Debian mirror network, and an
indirect advantage to users that would download the image sets from the
mirrors: we would [likely] not be able to provide the larger images *at
all* nowadays on most mirrors.  Jigdo solves that *important* issue.

Jigdo can also be a direct advantage (as in: it will be much faster) for
an user that has a close (or even local) mirror that does not carry the
full DVD/BD images, though:  it will download >95% of the data from the
close mirror, and rsync whatever is missing from the (relatively few)
mirrors that have the full images.

Evidently, when the mirror closer to you also happens to mirror the full
DVD/BD images, downloading those directly makes sense.

-- 
  Henrique Holschuh

Re: 3 écrans

[Eric Bernard]

re,
j'ai réussi en laissant faire le système à avoir mes 3 écrans ( 1 sur la 
prise VGA de la carte interne Intel et 2 sur la Nvidia (DVI et HDMI).

Je rencontre 2 problèmes :
 - si je dépasse la résolution 1440x900, mes écrans ne sont plus à la 
suite l'un de l'autre (1+1+1) mais se décalent vers le haut comme si 
"l'espace bureau" n'était pas assez grand en largeur pour des 
résolutions supérieures (1680x1050 ou 1920x1080)
- l'écran "principale" des menus et de la barre des raccourcis est sur 
l'écran de gauche alors que l'écran marqué comme principal est bien 
celui du centre.


Vos 4 écrans sont en superposition (2+2) ou alignés (1+1+1+1) ?

merci de votre aide !!!


Le 05/05/2017 à 09:00, Thierry Bugier Pineau a écrit :

Bonjour

Ce sont 2 écrans d'un modèle 27 pouces, 2 écrans d'un autre modèle 24 
pouces. Ils partagent tous la même résolution.


Je joins mon xorg.conf car il est nécéssaire d'en créer un avec une 
telle configuration matérielle.


Si vous l'utilisez, il faudra adapter le busID des GPUs, le nom des 
sorties vidéo (HDMI, DVI, ...) et peut être aussi la position des 
écrans les uns par rapport aux autres.


Le vendredi 05 mai 2017 à 08:12 +0200, Eric Bernard a écrit :

Bonjour,
4 écrans identiques (résolution etc..) ?



Le 03/05/2017 à 14:39, Thierry Bugier Pineau a écrit :

Bonjour

Je suis sur une configuration avec 4 écrans répartis sur 2 cartes 
graphiques.


Historiquement j'avais une carte NVidia de faible puissance, juste 
pour mes activités type bureautique. J'ai récemment évolué vers 4 
écrans an acquérant une seconde carte identique à la première.


Cela a été un peu difficile: Nouveau plante quand j'ai 2 GPUs. 
Attention, des cartes graphiques avec 2 GPU existent, et de ce que 
j'ai lu, c'est exactement comme avoir 2 cartes graphiques avec 1 GPU.


J'ai dû utiliser contre mon gré le pilote Nvidia, et utiliser un 
mode dit "Zaphod" (voir H2G2) pour utilsier mes 4 écrans. On perd un 
peu en fonctionnalités : un menu contextuel pouvant se trouver 
réparti entre plusieurs affichages, et xrandr ne "voit" qu'un écran. 
Cela m'empêche aussi d'utiliser le logiciel Redshift (sauf à 
accepter son effet sur un seul écran).


C'est assez difficile de configurer X11 avec une telle 
configuration. Si vous avez besoins de passer à 2 GPUs NVidia, je 
peux donner mon Xorg.conf.


Je pense qu'il faut d'abord expérimenter en trouvant des cartes 
diverses. Je n'ai pas trouvé de cartes graphiques discrètes avec un 
GPU Intel, ce qui aurait été l'idéal pour leur prise en charge par 
l'Open Source. Il me reste à expérimenter si je peux une telle 
configuration avec des cartes ATI/AMD.


Avec 3 écrans, je pense qu'une carte graphique peut suffire, mais 
attention, certains ont plus de 2 sorties, mais ne supportent à 
priori que 2 écrans en même temps.


Voilà grosso modo les infos que j'ai pu glaner / expérimenter pour 
arriver à faire marcher mon système.


Au fait : je suis sous SID, ça peut avoir son importance.

Le mercredi 03 mai 2017 à 08:23 +0200, Eric Bernard a écrit :


Bonjour,

Je recherche des infos et/ou retour d'expérience sur l'utilisation 
de 3 écrans "indépendant" (pas de clonage).



Merci de vos réponses


Eric

Re: Installation Input required

[Richard Owlett]

On 05/05/2017 04:49 AM, Thomas Schmitt wrote:

[snip]
This question was asked often enough to cause the existence of
  https://www.debian.org/CD/faq/#not-all-images
which says
  "We don't store/serve the full set of ISO images for all
architectures, to reduce the amount of space taken up on the mirrors.
You can use the jigdo tool to recreate the missing ISO images
instead."


The advantage of Jigdo for the DVD mirror servers is that the bulk
of data can be fetched from Debian servers which provide packages.
Jigdo loads a compressed ISO image with lots of holes and then loads
all the package files which fit exactly into the holes.


That eases problems for Debian servers, I don't see an advantage to me.

Re: Installation Input required

[Richard Owlett]

On 05/05/2017 03:56 AM, Ashok Inder wrote:

Hi,

Fairly new to Debian environment. I downloaded the 3 DVD
(debian-8.7.1-amd64-DVD-1.iso, debian-8.7.1-amd64-DVD-2.iso,
debian-8.7.1-amd64-DVD-3.iso). The reason for downloading all setup were:
1) Speed internet available in my office and allowed to download and
take it on usb flash drive.
2) Slow speed net in home (were I'm supposed to install debian) and
hence no netinst iso.
[SNIP]


I was on dialup when first installing Squeeze. I found {and still find} 
it convenient to purchase complete DVD sets 
(https://www.debian.org/CD/vendors/). My vendor charges $35 for the 13 
DVD set and $3 for a single CD/DVD {Live CDs, utility discs, etc}. I now 
have high speed access but with a minimal data cap.

Re: Booting a CF or SD card from an internal card reader

[Richard Owlett]

On 05/05/2017 04:28 AM, Brian wrote:

On Fri 05 May 2017 at 05:34:13 +0200, Leandro Noferini wrote:


Brian  writes:


1. This HOWTO is a result of the discussion on debian-user beginning at


It should be stressed that the HOWTO is applicable only to devices on
the USB bus.


Thanks a lot for this document because it hits a problem I found many
months ago without solution for me. I would like to use my internal card
reader (Lenovo X240) to boot in tails (https://tails.boum.org)


I rarely dabble in hardware-related things, so a mistake or two could
creep into what follows.


My reader appears this way:


~ $ lsusb
Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader



The Lenovo X240 has a Smart Card reader and a 4-in-1 card reader (MMC,
SD, SDHC, SDXC). The Smart Card reader is on the USB bus. I have never
used one but it appears to have something to do with identity cards.
GRUB does not detect it with nativedisk so booting from it is not
possible.


The sd card with tails on appears this way:


leandro@tricheco:~$ sudo fdisk /dev/mmcblk0

Welcome to fdisk (util-linux 2.29.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p
Disk /dev/mmcblk0: 7,4 GiB, 7969177600 bytes, 15564800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F12D15CF-2FC3-4852-8226-9D4F7E625B29

Device Start End Sectors  Size Type
/dev/mmcblk0p1  2048 5122047 512  2,5G EFI System



This is the 4-in-1 card reader; the one you want you are trying to boot
from. As indicted by /dev/mmcblk0p1 it is on the PCI bus. 'lspci' should
display the chip used; one from Ricoh?

GRUB doesn't see anything on this bus (it has no drivers for the device),
so booting from it is not possible.


Following your document I edited /etc/grub.d/40_custom adding these
lines:


menuentry 'Tails on CF card' {
insmod part_msdos
insmod ext2
echo "Running nativedisk command. Please wait."
nativedisk
search --label --set=root TAILS
linux /vmlinuz root=LABEL=TAILS ro
initrd /initrd.img
}


But it is not working.

If I give the "nativedisk" command in grub command line I get only


(ahci0)


Where am I wrong?


I think you have possibly not appreciated the distinction between a card
reader on a USB bus and one on a PCI bus. The first should be visible to
GRUB and nativedisk (but, as you have seen, isn't always). The second is
never visible to GRUB.



Not true.
On my Lenovo T510 laptop I have

root@march-9-Jessie:/home/richard# ls /dev/mm*
/dev/mmcblk0  /dev/mmcblk0p1  /dev/mmcblk0p2  /dev/mmcblk0p5

Although my BIOS will not boot from /dev/mmcblk0, the GRUB resident on 
/dev/sda1 has no trouble finding Debian on /dev/mmcblk0p1.


root@march-9-Jessie:/home/richard# lspci -tv
-+-[:ff]-+-00.0  Intel Corporation Core Processor QuickPath 
Architecture Generic Non-core Registers
 |   +-00.1  Intel Corporation Core Processor QuickPath 
Architecture System Address Decoder

 |   +-02.0  Intel Corporation Core Processor QPI Link 0
 |   +-02.1  Intel Corporation 1st Generation Core Processor 
QPI Physical 0
 |   +-02.2  Intel Corporation 1st Generation Core Processor 
Reserved
 |   \-02.3  Intel Corporation 1st Generation Core Processor 
Reserved

 \-[:00]-+-00.0  Intel Corporation Core Processor DRAM Controller
 +-02.0  Intel Corporation Core Processor Integrated 
Graphics Controller
 +-16.0  Intel Corporation 5 Series/3400 Series Chipset 
HECI Controller

 +-19.0  Intel Corporation 82577LM Gigabit Network Connection
 +-1a.0  Intel Corporation 5 Series/3400 Series Chipset 
USB2 Enhanced Host Controller
 +-1b.0  Intel Corporation 5 Series/3400 Series Chipset 
High Definition Audio

 +-1c.0-[02]--
 +-1c.1-[03]00.0  Intel Corporation Centrino Advanced-N 
6200
 +-1c.3-[05-0c]00.0  Renesas Technology Corp. uPD720202 
USB 3.0 Host Controller

 +-1c.4-[0d]--+-00.0  Ricoh Co Ltd MMC/SD Host Controller
 |+-00.1  Ricoh Co Ltd R5U2xx (R5U230 / R5U231 
/ R5U241) [Memory Stick Host Controller]
 |\-00.3  Ricoh Co 

Re: Only root can write on USB disk

[Stefan Monnier]

> I have a very annoying problem. I can't write to my usb drives (fat32,
> ntfs, etc.) without root permissions. How can I fix this?

How did you mount it?  I usually mount those with `pmount`.


Stefan

Re: Booting a CF or SD card from an internal card reader

[Stefan Monnier]

> This is the 4-in-1 card reader; the one you want you are trying to boot
> from. As indicted by /dev/mmcblk0p1 it is on the PCI bus. 'lspci' should
> display the chip used; one from Ricoh?
>
> GRUB doesn't see anything on this bus (it has no drivers for the device),
> so booting from it is not possible.

Of course it all depends on what you mean by "booting from".  AFAICT in
Leandro's situation, he's loading Grub from some other disk (probably
the main HDD or SSD), so he's already "not booting from the SD card" in
this sense.


Based on what I see above, his normal boot has 3 steps (ignoring the
earlier BIOS/UEFI booting itself):
1- load/start Grub
2- load/start vmlinuz+initrd
3- load/start /sbin/init from the LABEL=TAILS partition

All 3 parts can be stored at different places.  My guess is that step
1 fetches its data (Grub's code as well as grub.cfg) from some HDD or
SSD.  Apparently step 2 can't fetch its data from the SD card.

But step 3 can definitely fetch its data from the SD card.  So all you
need is to put your vmlinuz+initrd onto a disk that Grub can see
(e.g. alongside Grub rather than in the LABEL=TAILS partition).


Stefan

Re: Only root can write on USB disk

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 05, 2017 at 10:55:58AM +, Curt wrote:
> On 2017-05-05,   wrote:
> >
> > On Fri, May 05, 2017 at 09:17:51AM +, Curt wrote:
> >> On 2017-05-02, Greg Wooledge  wrote:
> >> > On Tue, May 02, 2017 at 07:16:57PM +0430, Mostafa Shahverdy wrote:
> >> >> I have a very annoying problem. I can't write to my usb drives (fat32,
> >> >> ntfs, etc.) without root permissions. How can I fix this?
> >> >
> >> > Mount the file system with "-o uid=youruser" to have the files presented
> >> > by the kernel as being "owned" by that user.
> >> >
> >> >
> >> 
> >> I don't understand that advice entirely.
> >> 
> >> Isn't there a difference between mounting the device as a regular user
> >> and writing to the device as a regular user (which you might be
> >> prevented from doing if the filesystem had root-only write permissions,
> >> thus Brian's ls -l suggestion to eliminate that possibility)?
> >
> > There is a difference. The "-o=foo" advice is betting on the file system
> > being one without ownership info (i.e. a lower life form ;-)
> 
> The OP does mention FAT32, and FAT32 doesn't have permissions, I hear,
> so in the case of a FAT32 file system on a usb stick any user at all
> should be able to write to it (given the appropriate mount options)?

There is an option "umask" (and specifically "dmask" and "fmask" for
directories and files) which has the usual umask semantics. It defaults
to the "current process's umask", so no, typically you won't get 0777.

The mountpoint permissions should be irrelevant (except that you might
fail traversing the path if you haven't read access to it or one of
its parents).

Look at this little session

  # Make empty disk, 4M:
  tomas@rasputin:~$ dd if=/dev/zero of=dose bs=4096 count=1024
  1024+0 records in
  1024+0 records out
  4194304 bytes (4.2 MB) copied, 0.0153837 s, 273 MB/s

  # Put vfat file system on that:
  tomas@rasputin:~$ /sbin/mkfs.vfat dose
  mkfs.fat 3.0.27 (2014-11-12)


  # Mount. Gotta be boss for that (usually):
  tomas@rasputin:~$ sudo mount dose /mnt
  [sudo] password for tomas: 

  # Empty. Mere mortals seem to have read access:
  tomas@rasputin:~$ ls -l /mnt
  total 0

  # but no write access:
  tomas@rasputin:~$ touch /mnt/file
  touch: cannot touch ‘/mnt/file’: Permission denied

  # Boss can do:
  tomas@rasputin:~$ sudo touch /mnt/file
  tomas@rasputin:~$ ls -l /mnt
  total 0
  -rwxr-xr-x 1 root root 0 May  5 13:29 file

  # A-hah. Boss umask seems to be 022 by default

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkMYyQACgkQBcgs9XrR2kbOowCeIm95XUsgC0rPpu+lXOLH93o5
+xcAnA1stptuhdJLVDvKfzHPzIKhWq0l
=Kj4q
-END PGP SIGNATURE-

Re: Only root can write on USB disk

[Curt]

On 2017-05-05,   wrote:
>
> On Fri, May 05, 2017 at 09:17:51AM +, Curt wrote:
>> On 2017-05-02, Greg Wooledge  wrote:
>> > On Tue, May 02, 2017 at 07:16:57PM +0430, Mostafa Shahverdy wrote:
>> >> I have a very annoying problem. I can't write to my usb drives (fat32,
>> >> ntfs, etc.) without root permissions. How can I fix this?
>> >
>> > Mount the file system with "-o uid=youruser" to have the files presented
>> > by the kernel as being "owned" by that user.
>> >
>> >
>> 
>> I don't understand that advice entirely.
>> 
>> Isn't there a difference between mounting the device as a regular user
>> and writing to the device as a regular user (which you might be
>> prevented from doing if the filesystem had root-only write permissions,
>> thus Brian's ls -l suggestion to eliminate that possibility)?
>
> There is a difference. The "-o=foo" advice is betting on the file system
> being one without ownership info (i.e. a lower life form ;-)

The OP does mention FAT32, and FAT32 doesn't have permissions, I hear,
so in the case of a FAT32 file system on a usb stick any user at all
should be able to write to it (given the appropriate mount options)?

However, ntfs does have some sort of permission system, I believe.

What about the permissions on the directory under which the mount is
eventually made? That could affect the right to write, right? 

> Once mounted, the operating system just "assumes" some ownership and
> permission info. The "user=" and "group=" options give you some say
> in it.
>
> The option "user" on the fstab just allows a regular user to activate
> a mount according to said entry (however perms & ownership of the "end
> result" might look like).
>
> The two things are (somewhat) orthogonal (if I understood your question
> correctly).

I think you did, thanks.

> cheers
> - -- t
>
>


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: Installation Input required

[Thomas Schmitt]

Hi,

Ashok Inder wrote:
> During the entire setup screen, the debian installer did not asked me
> for the 2nd or 3rd DVD.

Can it be you only asked for installing stuff which is on DVD 1 ?

If the lack of requesting other DVDs led to a system which does not
contain what you asked for, then this would be a topic for the debian-cd
list.
If all seems well, then you probably only needed DVD 1.


> Also many a places its mentioned that the DVD is
> a set of 12 DVD but I only found 3 set DVD.

This question was asked often enough to cause the existence of
  https://www.debian.org/CD/faq/#not-all-images
which says
  "We don't store/serve the full set of ISO images for all architectures,
   to reduce the amount of space taken up on the mirrors. You can use the
   jigdo tool to recreate the missing ISO images instead."


The advantage of Jigdo for the DVD mirror servers is that the bulk
of data can be fetched from Debian servers which provide packages.
Jigdo loads a compressed ISO image with lots of holes and then loads
all the package files which fit exactly into the holes.

Here is a nice illustration from the times when disc images were still
made of wood ;-)
  
https://s-media-cache-ak0.pinimg.com/originals/e7/22/0c/e7220c2e4ed04fbd2d2e233e1b7cb90f.jpg


Have a nice day :)

Thomas

Re: CD Ripper

[Sébastien NOBILI]

Bonjour,

Le jeudi 04 mai 2017 à 21:11, Jean-Marc a écrit :
> Un conseil pour un ripper efficace dans ceux dispo dans les dépôts Debian ?
> 
> Je rippe en FLAC.

J’utilise « morituri » depuis plusieurs années, ça permet de simplifier
grandement le processus :
— j’insère le CD,
— je lance la commande,
— quand le CD est éjecté, c’est prêt !

Sinon pour la partie tags, j’utilise « pytags ».

Enfin, j’utilise « replaygain » pour harmoniser les niveaux.

Sébastien

Connexion wifi dans un hôtel Brit avec Unbound - Réglage DNS

[G2PC]

Bonjour.
Brit Hotel.
Linux Mint Sarah avec Unbound.

/etc/resolv.conf
affiche :
nameserver 127.0.0.1
search lan

route
affiche :
Table de routage IP du noyau
Destination Passerelle Genmask Indic Metric Ref Use Iface
default 172.16.1.1 0.0.0.0 UG 0 0 0 wlp60s0
default 172.16.1.1 0.0.0.0 UG 600 0 0 wlp60s0
link-local * 255.255.0.0 U 1000 0 0 wlp60s0
172.16.1.0 * 255.255.255.0 U 600 0 0 wlp60s0

Décidément, je ne comprend pas, mais, j'arrive bien à avoir une page
d'accueil sous windows, qui me demande un mail de connexion . puis
me donne accès au web . ( de l'hotel ) 

Mais, pas moyen, avec Linux Sarah, surement à cause de Unbound et de mon
réglage.

Comment feriez vous sous Debian pour avancer sur ce problème pour
arriver à obtenir la page d'accueil de l'hotel ?

Je suppose que "le soucis" vient de l'ip 172.16.1.1
J'obtient une erreur de connexion avec cette ip lorsque je tente
d'accéder à google :
https://zs3.noodo-wifi.com/wifi-access/prod/login/?gw_address=172.16.1.1_port=2060_id=401=E4:A4:71:71:69:25=http%3A//www.google.fr/

Re: Only root can write on USB disk

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 05, 2017 at 09:17:51AM +, Curt wrote:
> On 2017-05-02, Greg Wooledge  wrote:
> > On Tue, May 02, 2017 at 07:16:57PM +0430, Mostafa Shahverdy wrote:
> >> I have a very annoying problem. I can't write to my usb drives (fat32,
> >> ntfs, etc.) without root permissions. How can I fix this?
> >
> > Mount the file system with "-o uid=youruser" to have the files presented
> > by the kernel as being "owned" by that user.
> >
> >
> 
> I don't understand that advice entirely.
> 
> Isn't there a difference between mounting the device as a regular user
> and writing to the device as a regular user (which you might be
> prevented from doing if the filesystem had root-only write permissions,
> thus Brian's ls -l suggestion to eliminate that possibility)?

There is a difference. The "-o=foo" advice is betting on the file system
being one without ownership info (i.e. a lower life form ;-)

Once mounted, the operating system just "assumes" some ownership and
permission info. The "user=" and "group=" options give you some say
in it.

The option "user" on the fstab just allows a regular user to activate
a mount according to said entry (however perms & ownership of the "end
result" might look like).

The two things are (somewhat) orthogonal (if I understood your question
correctly).

cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkMRzQACgkQBcgs9XrR2kZ5LgCfVD5r7m+3e53QYAxNoUmk9aty
MKIAnjCpqgVIHB8Z48BWTFD5hVpWt2Ji
=eP+p
-END PGP SIGNATURE-

Re: Re : CD Ripper

[maderios]

On 05/05/2017 08:45 AM, nicolas.patr...@gmail.com wrote:

Le 05/05/2017 08:36:16, Bernard Siorat a écrit :


Asunder ?


Grip (s’il existe encore) ou XCFA ?


XCFA est très bien mais il ne permet pas de renommer les pistes.

--
Maderios

Re: Booting a CF or SD card from an internal card reader

[Brian]

On Fri 05 May 2017 at 05:34:13 +0200, Leandro Noferini wrote:

> Brian  writes:
> 
> > 1. This HOWTO is a result of the discussion on debian-user beginning at

It should be stressed that the HOWTO is applicable only to devices on
the USB bus.

> Thanks a lot for this document because it hits a problem I found many
> months ago without solution for me. I would like to use my internal card
> reader (Lenovo X240) to boot in tails (https://tails.boum.org)

I rarely dabble in hardware-related things, so a mistake or two could
creep into what follows.

> My reader appears this way:
> 
> 
> ~ $ lsusb
> Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
> 

The Lenovo X240 has a Smart Card reader and a 4-in-1 card reader (MMC,
SD, SDHC, SDXC). The Smart Card reader is on the USB bus. I have never
used one but it appears to have something to do with identity cards.
GRUB does not detect it with nativedisk so booting from it is not
possible.

> The sd card with tails on appears this way:
> 
> 
> leandro@tricheco:~$ sudo fdisk /dev/mmcblk0
> 
> Welcome to fdisk (util-linux 2.29.2).
> Changes will remain in memory only, until you decide to write them.
> Be careful before using the write command.
> 
> Command (m for help): p
> Disk /dev/mmcblk0: 7,4 GiB, 7969177600 bytes, 15564800 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: F12D15CF-2FC3-4852-8226-9D4F7E625B29
> 
> Device Start End Sectors  Size Type
> /dev/mmcblk0p1  2048 5122047 512  2,5G EFI System
> 

This is the 4-in-1 card reader; the one you want you are trying to boot
from. As indicted by /dev/mmcblk0p1 it is on the PCI bus. 'lspci' should
display the chip used; one from Ricoh?

GRUB doesn't see anything on this bus (it has no drivers for the device),
so booting from it is not possible.

> Following your document I edited /etc/grub.d/40_custom adding these
> lines:
> 
> 
> menuentry 'Tails on CF card' {
>   insmod part_msdos
> insmod ext2
> echo "Running nativedisk command. Please wait."
> nativedisk
> search --label --set=root TAILS
> linux /vmlinuz root=LABEL=TAILS ro
> initrd /initrd.img
> }
> 
> 
> But it is not working.
> 
> If I give the "nativedisk" command in grub command line I get only
> 
> 
> (ahci0)
> 
> 
> Where am I wrong?

I think you have possibly not appreciated the distinction between a card
reader on a USB bus and one on a PCI bus. The first should be visible to
GRUB and nativedisk (but, as you have seen, isn't always). The second is
never visible to GRUB.

-- 
Brian.

Re: Live patching du kernel

[C. Mourad Jaber]

Le 04/05/2017 à 20:28, Pascal Hambourg a écrit :

Le 04/05/2017 à 10:27, C. Mourad Jaber a écrit :

Bonjour,

J'ai vu plusieurs post parlant du livepatching (patcher les noyaux sans
redémarrage) natif des noyaux 4.x...

Est-ce debian propose ce type de possibilité pour les noyaux de la
future stable ?


Ksplice était disponible dans Wheezy et Jessie, Kpatch est disponible dans 
Stretch.

Merci pour cette information, y'a-t-il un service de debian qui fournit les patchs comme 
canonical live patch ?


++

Mourad

Re: Only root can write on USB disk

[Curt]

On 2017-05-02, Greg Wooledge  wrote:
> On Tue, May 02, 2017 at 07:16:57PM +0430, Mostafa Shahverdy wrote:
>> I have a very annoying problem. I can't write to my usb drives (fat32,
>> ntfs, etc.) without root permissions. How can I fix this?
>
> Mount the file system with "-o uid=youruser" to have the files presented
> by the kernel as being "owned" by that user.
>
>

I don't understand that advice entirely.

Isn't there a difference between mounting the device as a regular user
and writing to the device as a regular user (which you might be
prevented from doing if the filesystem had root-only write permissions,
thus Brian's ls -l suggestion to eliminate that possibility)?


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: Installation Input required

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 05, 2017 at 02:26:44PM +0530, Ashok Inder wrote:
> Hi,

[...]

> During the entire setup screen, the debian installer did not asked me
> for the 2nd or 3rd DVD. Also many a places its mentioned that the DVD is
> a set of 12 DVD but I only found 3 set DVD.
> 
> Support pages mention that installer will ask for other part of the DVD
> as an option. It never asked, only driver cd/dvd was asked.
> 
> Just wondering that did I missed something?

I don't know for sure, but I think this is a testament to the CD
team: they work very hard to have the most-used things in the first
DVD. Seems to have worked, kudos to them :-)

> Also I installed with Sudo option (no root account), will this be of any
> disadvantage at anytime in future over Sudo considering I'm not a power
> user.

There is just one downside I know of: if the system panics on boot,
e.g. because it can't mount the root file system (say, because it's
corrupted), it will ask you for the root password before giving you
a root shell, for you to analyse and possibly fix the situation. I've
been in that position once, having drunk the Kool Aid to the bottom
of the glass. Very frustrating, believe me :)

I'm still a fan of sudo, but have learnt since then to leave a bit
in the glass and actually have a root password.

Nothing, of course, which can't be fixed by having around a rescue
disk.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkMQtEACgkQBcgs9XrR2kaRKwCfeYQg29vP7sFUcPcr5GzV+qGJ
tiQAn2n6s6y3tXT5JY2oOKuMSJWsonak
=IGrO
-END PGP SIGNATURE-

Installation Input required

[Ashok Inder]

Hi,

Fairly new to Debian environment. I downloaded the 3 DVD
(debian-8.7.1-amd64-DVD-1.iso, debian-8.7.1-amd64-DVD-2.iso,
debian-8.7.1-amd64-DVD-3.iso). The reason for downloading all setup were:
1) Speed internet available in my office and allowed to download and
take it on usb flash drive.
2) Slow speed net in home (were I'm supposed to install debian) and
hence no netinst iso.
3) Setup would have all software that I would need, and a good
probability that some would have been on DVD2 or DVD3. This would have
ensured that I never had to use apt-get update && apt-get upgrade

During the entire setup screen, the debian installer did not asked me
for the 2nd or 3rd DVD. Also many a places its mentioned that the DVD is
a set of 12 DVD but I only found 3 set DVD.

Support pages mention that installer will ask for other part of the DVD
as an option. It never asked, only driver cd/dvd was asked.

Just wondering that did I missed something?

Also I installed with Sudo option (no root account), will this be of any
disadvantage at anytime in future over Sudo considering I'm not a power
user.

Regards,
Ashok Kumar



signature.asc
Description: OpenPGP digital signature

how to add a remote login to XDMCP Chooser in the login window

[Abdelkader Belahcene]

Hi,

I want to log in a remote server using xdmcp from my local machine,
unfortunately there is no chooser in my local login (I use lightdm).
How to add a remote connexion to the list in local login window?
I remember 8 or 9 years ago, in the login window (may be with  xdm) there
was a remote login in the list.

thank

Re: 3 écrans

[Thierry Bugier Pineau]

Bonjour
Ce sont 2 écrans d'un modèle 27 pouces, 2 écrans d'un autre modèle 24
pouces. Ils partagent tous la même résolution. 
Je joins mon xorg.conf car il est nécéssaire d'en créer un avec une
telle configuration matérielle.
Si vous l'utilisez, il faudra adapter le busID des GPUs, le nom des
sorties vidéo (HDMI, DVI, ...) et peut être aussi la position des
écrans les uns par rapport aux autres.
Le vendredi 05 mai 2017 à 08:12 +0200, Eric Bernard a écrit :
> Bonjour,
> 
>   4 écrans identiques (résolution etc..) ?
> 
>   
> 
>   
> 
>   
> 
>   Le 03/05/2017 à 14:39, Thierry Bugier Pineau a écrit :
> 
> 
> 
> >   
> >   Bonjour
> >   
> > 
> >   
> >   Je suis sur une configuration avec 4 écrans répartis sur 2
> > cartes graphiques. 
> >   
> > 
> >   
> >   Historiquement j'avais une carte NVidia de faible puissance,
> > juste pour mes activités type bureautique. J'ai récemment
> > évolué
> > vers 4 écrans an acquérant une seconde carte identique à la
> > première.
> >   
> > 
> >   
> >   Cela a été un peu difficile: Nouveau plante quand j'ai 2
> > GPUs. Attention, des cartes graphiques avec 2 GPU existent,
> > et
> > de ce que j'ai lu, c'est exactement comme avoir 2 cartes
> > graphiques avec 1 GPU.
> >   
> > 
> >   
> >   J'ai dû utiliser contre mon gré le pilote Nvidia, et utiliser
> > un mode dit "Zaphod" (voir H2G2) pour utilsier mes 4
> > écrans. On
> > perd un peu en fonctionnalités : un menu contextuel pouvant
> > se
> > trouver réparti entre plusieurs affichages, et xrandr ne
> > "voit"
> > qu'un écran. Cela m'empêche aussi d'utiliser le logiciel
> > Redshift (sauf à accepter son effet sur un seul écran).
> >   
> > 
> >   
> >   C'est assez difficile de configurer X11 avec une telle
> > configuration. Si vous avez besoins de passer à 2 GPUs
> > NVidia,
> > je peux donner mon Xorg.conf. 
> >   
> > 
> >   
> >   Je pense qu'il faut d'abord expérimenter en trouvant des
> > cartes diverses. Je n'ai pas trouvé de cartes graphiques
> > discrètes avec un GPU Intel, ce qui aurait été l'idéal pour
> > leur
> > prise en charge par l'Open Source. Il me reste à
> > expérimenter si
> > je peux une telle configuration avec des cartes ATI/AMD. 
> >   
> > 
> >   
> >   Avec 3 écrans, je pense qu'une carte graphique peut suffire,
> > mais attention, certains ont plus de 2 sorties, mais ne
> > supportent à priori que 2 écrans en même temps.
> >   
> > 
> >   
> >   Voilà grosso modo les infos que j'ai pu glaner / expérimenter
> > pour arriver à faire marcher mon système.
> >   
> > 
> >   
> >   Au fait : je suis sous SID, ça peut avoir son importance.
> >   
> > 
> >   
> >   Le mercredi 03 mai 2017 à 08:23 +0200, Eric Bernard a écrit :
> >   
> > > Bonjour,
> > > Je recherche des infos et/ou retour d'expérience sur
> > >   l'utilisation de 3 écrans "indépendant" (pas de
> > > clonage).
> > > 
> > > 
> > > 
> > > Merci de vos réponses
> > > 
> > > 
> > > 
> > > Eric
> > > 
> > > 
> > >   
> > 
> > 
> 
> 
> 
> 
>   
> Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0" 0 0
Screen  1  "Screen1" RightOf "Screen0"
Screen  2  "Screen2" Below "Screen0"
Screen  3  "Screen3" Below "Screen1"
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
Option "Xinerama" "on"
Option "Clone" "off"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
Identifier"Monitor0"
VendorName"Vendor"
ModelName "Model"
Option"DPMS"
EndSection

Section "Monitor"
Identifier"Monitor1"
VendorName"Vendor"
ModelName "Model"
Option"DPMS"
EndSection

Section "Monitor"
Identifier"Monitor2"
VendorName"Vendor"
ModelName "Model"
Option"DPMS"
EndSection

Section "Monitor"
Identifier"Monitor3"
VendorName"Vendor"
ModelName "Model"
Option"DPMS"
EndSection

Section "Device"
# Actual PCI location of first card/gpu
# Actual connector - as reported by /sys/class/drm/card0-xx
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "GeForce GT 710"
BusID  "PCI:4:0:0"
Option 

Re: Live Fille System Backup

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, May 04, 2017 at 04:17:46PM -0700, Sergei G wrote:
> I am running Raspberry PI and I would like to dump full file system without
> shutting down the system.  One machine runs nginx and another runs
> PostgreSQL.  I have had a good success with FreeBSD and dump software,
> because it is part of the OS and core team maintains it.

Rsync. Hands down.

That said...

there are some thigs you might want to take into account.

 - A solution like rsync alone won't ever solve the "skew" problem
   (i.e. the file system moves while the backup is being taken).
   Depending on how sensitive your "world" is to that, this might
   be a problem or not. "Typically" (famous last words, I know)
   it ain't for me, especially if I take care of taking a "second
   rsync", which will be very fast. If that isn't enough, you might
   like to "snapshot" with LVM or overlayfs and back-up your
   "frozen" (and thus consistent) snapshot, while life throbs on
   on your "real" file system branch.

 - PostgreSQL. Conventional wisdom says you shouldn't back up a
   running database. Nevertheless, you can do that with PostgreSQL,
   if you take care of orchestrating pg_start_backup, pg_stop_backup
   and the right copying of WALs [1]. This sounds complicated, is
   not: your (homegrown or acquired) backup scripts just have to
   provide a "before" and an "after" hook (if they don't, claim your
   money back :) where to enlist the scripts to steer your database(s).

   Having an old-fashioned pg_dump around which isn't too old won't
   hurt, especially if you want to be able to restore to a significantly
   different architecture/ PostgreSQL version.

Things rsync won't be very good at:

  - huge backups (several terabytes or more; millions of files)
My current backup is around 48 GB and 650K files (not much),
and the rsync approach (organic, homegrown :) doesn't break
a sweat, with fairly modest hardware. YMMV. I've seen a photo
archive (~20TB) where the buildup of the file list would have
taken rsync short of two days -- that won't work, obviously
(to be fair, rsync has gotten better in this department as
of late, and the shop in question has a faible for "seasoned"
software versions).

 - whatever I forgot: please chime in!

regards

[1] 
https://www.postgresql.org/docs/current/static/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkMJqgACgkQBcgs9XrR2kZaWQCfY7/XyU5LJJR5Oz3h4W6afU0u
kLUAn0H/ewNQMYkEv/LbTjwwtxOnzDxo
=H0lN
-END PGP SIGNATURE-

Re: CD Ripper

[Jean Louis Giraud Desrondiers]

On Thu, 4 May 2017 21:11:02 +0200
Jean-Marc  wrote:

> salut la liste,
bonjour
> 
> Je suis en train de ripper mes CDs.
> 
> La dernière version de Sound Juicer que j'utilise ne me permet plus de 
> choisir le nom des pistes comme j'aimerai qu'ils soient.
> 
> Un conseil pour un ripper efficace dans ceux dispo dans les dépôts Debian ?
> 
je crois qu'ABCDE fait ça mais tout en ligne de commande (donc il faut
aussi maîtriser un éditeur de texte) mais sinon quand on a la patience
de lire le man en entier il est configurable à l'infini
et sinon je crois que ripperx peut faire ça mais j'ai un doute. 

-- 
Cordialement, 

Jean Louis Giraud Desrondiers 

Re: Live Fille System Backup

[Dejan Jocic]

On 04-05-17, Sergei G wrote:
> That's good to know.
> 
> 
> Thank you
> 
> 
> On 5/4/17 6:46 PM, Anders Andersson wrote:
> > On Fri, May 5, 2017 at 1:17 AM, Sergei G  wrote:
> > > I would like a backup tool that does not bring a million dependencies with
> > > MBs of files.  Something that works on server without X Windows and can 
> > > send
> > > backup to an externally attached USB drive.  Nothing fancy.   No network
> > > infrastructure.  Incremental backups would be greatly appreciated.  
> > > Ability
> > > to pipe to a compression program is a plus, just like I did with dump.
> > > [...]
> > > Any advice would be greatly appreciated.
> > You won't like my solution, and it doesn't work with your current
> > setup because it requires a specific file system: btrfs[1]. I'm
> > posting it here for two reasons:
> >   1) You might consider using btrfs on new installs
> >   2) Someone else may search and find the thread
> > 
> > After switching to btrfs I can now take instant snapshots of selected
> > filesystems, transfer these to remote servers for backup, and most
> > important: btrfs can track the *exact difference* between two
> > snapshots taken over time, and only transfer the changes. All of this
> > is very quick, because the filesystem already knows exactly what
> > changed: Permission bits, file sizes, deleted files, changed data,
> > whatever, all is already kept in a log. It also means that nothing
> > will be missed, for example ACL bits etc.
> > 
> > The delta is just a simple stream of data that can be compressed if
> > necessary. Typically it is transmitted to a backup server where it is
> > "replayed" so that you have a full clone of the original system.[2]
> > 
> > In debian I use the little tool, btrbk[3], to automate all of this.
> > You can simply do it manually if you want.
> > 
> > [1] https://btrfs.wiki.kernel.org/index.php/Main_Page
> > [2] https://btrfs.wiki.kernel.org/index.php/Incremental_Backup
> > [3] https://github.com/digint/btrbk
> > 
> 

Perhaps rsync can do the job for you?

Re : CD Ripper

[nicolas . patrois]

Le 05/05/2017 08:36:16, Bernard Siorat a écrit :

> Asunder ?

Grip (s’il existe encore) ou XCFA ?

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des 
humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Re: CD Ripper

[Bernard Siorat]

Asunder ?

Le 04/05/2017 à 21:11, Jean-Marc a écrit :
> salut la liste,
> 
> Je suis en train de ripper mes CDs.
> 
> La dernière version de Sound Juicer que j'utilise ne me permet plus de 
> choisir le nom des pistes comme j'aimerai qu'ils soient.
> 
> Un conseil pour un ripper efficace dans ceux dispo dans les dépôts Debian ?
> 
> Je rippe en FLAC.
> 
> Et je suis en Debian Stretch.
> 
> Bonne soireé à tous.
> 
> Jean-Marc 
> 

-- 
Cordialement,
Bernardo.

Labourage et pâturage sont les deux mamelles dont la France est
alimentée, et les vraies mines et trésors du Pérou.
-+- Sully (1559-1641) -+-