Re: Log files: location and description

2017-10-09 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 09, 2017 at 09:02:12AM -0400, Greg Wooledge wrote: > On Sun, Oct 08, 2017 at 02:38:21PM +0200, to...@tuxteam.de wrote: > > It's a shell feature: if you do "set -x" in a shell script, all the > > commands in the current shell get transcribed

Re: Log files: location and description

2017-10-09 Thread Greg Wooledge
On Sun, Oct 08, 2017 at 02:38:21PM +0200, to...@tuxteam.de wrote: > It's a shell feature: if you do "set -x" in a shell script, all the > commands in the current shell get transcribed (to stdout, I think). To stderr by default, but bash lets you set the BASH_XTRACEFD variable to send it elsewhere.

Debian-installer writes /dev/ references in grub.cfg, was Re: Log files: location and description

2017-10-08 Thread David Wright
On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: > My current problem is finding the appropriate logs to document the > details behind my addendum to Bug 852323. Looking at the grub.cfg written by stretch's d-i RC3, it appears to write linux /boot/vmlinuz-4.9.0-2-686 root=

Re: Log files: location and description

2017-10-08 Thread David Wright
On Sun 08 Oct 2017 at 07:31:23 (-0500), Richard Owlett wrote: > On 10/07/2017 03:01 PM, David Wright wrote: > >On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: > >>[snip] > >> > >>I have a hypothesis, but I need to have facts to back it up. > >>Specifically: > >>1. During the installat

Re: Log files: location and description

2017-10-08 Thread Richard Owlett
On 10/08/2017 09:40 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 08:58:11AM -0500, Richard Owlett wrote: On 10/08/2017 07:38 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 07:31:23AM -0500,

Re: Log files: location and description

2017-10-08 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 08:58:11AM -0500, Richard Owlett wrote: > On 10/08/2017 07:38 AM, to...@tuxteam.de wrote: > >-BEGIN PGP SIGNED MESSAGE- > >Hash: SHA1 > > > >On Sun, Oct 08, 2017 at 07:31:23AM -0500, Richard Owlett wrote: [...] > >In a

Re: Log files: location and description

2017-10-08 Thread Richard Owlett
On 10/08/2017 07:38 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 07:31:23AM -0500, Richard Owlett wrote: On 10/07/2017 03:01 PM, David Wright wrote: On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: [...] No idea about the oth

Re: Log files: location and description

2017-10-08 Thread Richard Owlett
On 10/07/2017 03:01 PM, David Wright wrote: On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: [snip] I have a hypothesis, but I need to have facts to back it up. Specifically: 1. During the installation process I need to inventory when and "as what" various USB devices are recogn

Re: Log files: location and description

2017-10-08 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 07:31:23AM -0500, Richard Owlett wrote: > On 10/07/2017 03:01 PM, David Wright wrote: > >On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: [...] No idea about the other things, but: > I don't understand. > Accordi

Re: Log files: location and description

2017-10-08 Thread Richard Owlett
On 10/07/2017 03:01 PM, David Wright wrote: On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: [snip] I have a hypothesis, but I need to have facts to back it up. Specifically: 1. During the installation process I need to inventory when and "as what" various USB devices are recogn

Re: HD device name assignments (was: Log files: location and description)

2017-10-07 Thread Felix Miata
David Wright composed on 2017-10-07 15:01 (UTC-0500): > it might be worth pointing out that it has been reported here that > a USB3 stick inserted at boot can demote the internal disk to > /dev/sdb. It need not be v3 of USB, and it's one of the prime reasons alternatives to booting by device nam

Re: Log files: location and description

2017-10-07 Thread David Wright
On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: > I'm looking for a comprehensive catalog of log files giving > location, name, and one line description. I've Googled and found > bits and pieces that are too narrowly focused. To paraphrase my > situation, I'm not only not seeing the f

Log files: location and description

2017-10-07 Thread Richard Owlett
I'm looking for a comprehensive catalog of log files giving location, name, and one line description. I've Googled and found bits and pieces that are too narrowly focused. To paraphrase my situation, I'm not only not seeing the forest for the trees -- I'm also not seeing the forest for the leav