On 01/13/2018 04:43 AM, Curt wrote:
On 2018-01-11, The Wanderer wrote:
Googling on that error message (with the presumed typo corrected) leads
me to http://forums.debian.net/viewtopic.php?f=3D5&t=3D133578 as a first
hit.
That's funny; I am led here first-hit wise:
https://lists.debian.org/
On 2018-01-11, The Wanderer wrote:
>
> Googling on that error message (with the presumed typo corrected) leads
> me to http://forums.debian.net/viewtopic.php?f=3D5&t=3D133578 as a first
> hit.
>
That's funny; I am led here first-hit wise:
https://lists.debian.org/debian-kernel/2017/04/msg00192.h
On 01/12/2018 09:29 AM, David Wright wrote:
On Fri 12 Jan 2018 at 06:19:57 (-0600), Richard Owlett wrote:
[snip]
Not sure. Noticed it recently after fixing a long standing problem
involving a bad UUID for the swap partition.
Perhaps it's no coincidence then that the Wanderer's earlier
forum r
On 01/12/2018 09:29 AM, David Wright wrote:
On Fri 12 Jan 2018 at 06:19:57 (-0600), Richard Owlett wrote:
On 01/11/2018 01:43 PM, David Wright wrote:
On Thu 11 Jan 2018 at 11:10:33 (-0600), Richard Owlett wrote:
I multi-boot several varieties of Debian.
When booting one specific install, it di
On 01/11/2018 11:38 AM, The Wanderer wrote:
[snip]
On my system (stable+testing, though with sysvinit rather than systemd):
$ dlocate scripts/local-block
mdadm: /usr/share/initramfs-tools/scripts/local-block
mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm
lvm2: /usr/share/initramfs-
On 01/11/2018 11:22 AM, bw wrote:
On Thu, 11 Jan 2018, Richard Owlett wrote:
[snip]
journalctl -xb > jan11test
The string of interest not present.
/usr/share/initramfs-tools/ does not exist
/etc/initramfs-tools/scripts has 10 empty folders
Doesn't sound right.
[snip]
Something is lookin
On Fri 12 Jan 2018 at 06:19:57 (-0600), Richard Owlett wrote:
> On 01/11/2018 01:43 PM, David Wright wrote:
> >On Thu 11 Jan 2018 at 11:10:33 (-0600), Richard Owlett wrote:
> >>I multi-boot several varieties of Debian.
> >>When booting one specific install, it displays many repetitions of:
> Be
On 2018-01-11 at 12:45, bw wrote:
> On Thu, 11 Jan 2018, The Wanderer wrote:
>
>> On 2018-01-11 at 12:35, bw wrote:
>>
>> > On stretch local_block is a function in a script named local, maybe using
>> > a stretch tool on jessie has things confused? or the initramfs-tools pkg
>> > is hosed on
On 01/11/2018 01:43 PM, David Wright wrote:
On Thu 11 Jan 2018 at 11:10:33 (-0600), Richard Owlett wrote:
I multi-boot several varieties of Debian.
When booting one specific install, it displays many repetitions of:
Begin: Running /scripts/local-block ... done.
It then proceeds to bring up a
On 01/11/2018 01:28 PM, bw wrote:
On Thu, 11 Jan 2018, Richard Owlett wrote:
On 01/11/2018 11:35 AM, bw wrote:
[snip]
Sounds complicated, one version of grub but
separate boot partitions always gets me confused too.
Not sure best solution.
But I'm used to it and have not discovered any pot
On Thu 11 Jan 2018 at 11:10:33 (-0600), Richard Owlett wrote:
> I multi-boot several varieties of Debian.
> When booting one specific install, it displays many repetitions of:
> >>Begin: Running /scripts/local-block ... done.
> It then proceeds to bring up an apparently normal system.
[…]
> sda8 -
On 01/11/2018 11:35 AM, bw wrote:
[snip]
Sounds complicated, one version of grub but
separate boot partitions always gets me confused too.
Not sure best solution.
But I'm used to it and have not discovered any potholes. YET ;/
I've had it that way since Squeeze in order to force update-grub to
On 2018-01-11 at 12:35, bw wrote:
> On Thu, 11 Jan 2018, The Wanderer wrote:
>
>> On 2018-01-11 at 12:10, Richard Owlett wrote:
>>
>> > I multi-boot several varieties of Debian.
>> > When booting one specific install, it displays many repetitions of:
>> >>> Begin: Running /scripts/local-block ..
On 2018-01-11 10:44 -0500, The Wanderer wrote:
> On 2018-01-11 at 10:35, Greg Wooledge wrote:
>
>> wooledg:~$ ls -l /sbin/init
>> lrwxrwxrwx 1 root root 20 Jul 5 2017 /sbin/init -> /lib/systemd/systemd
>> wooledg:~$ cat /proc/1/comm
>> systemd
>
> So it's smart enough to bypass the name of the s
On Thu, 11 Jan 2018, Richard Owlett wrote:
> I multi-boot several varieties of Debian.
> When booting one specific install, it displays many repetitions of:
> > > Begin: Running /scripts/local-block ... done.
>
> It then proceeds to bring up an apparently normal system.
> Would this be logged s
On 2018-01-11 at 12:10, Richard Owlett wrote:
> I multi-boot several varieties of Debian.
> When booting one specific install, it displays many repetitions of:
>>> Begin: Running /scripts/local-block ... done.
>
> It then proceeds to bring up an apparently normal system.
> Suggested diagnostics
I multi-boot several varieties of Debian.
When booting one specific install, it displays many repetitions of:
Begin: Running /scripts/local-block ... done.
It then proceeds to bring up an apparently normal system.
Would this be logged somewhere?
Where?
Specifics:
sda1 - Always has the latest v
On 2018-01-11 at 10:35, Greg Wooledge wrote:
> On Thu, Jan 11, 2018 at 10:27:33AM -0500, The Wanderer wrote:
>
>> On 2018-01-11 at 10:23, Brian wrote:
>>> Guaranteed: 'cat /proc/1/comm'.
>>
>> On my system:
>>
>> $ dlocate /sbin/init
>> sysvinit-core: /sbin/init
>> $ cat /proc/1/comm
>> init
>>
On Thu, Jan 11, 2018 at 10:27:33AM -0500, The Wanderer wrote:
> On 2018-01-11 at 10:23, Brian wrote:
>
> > On Thu 11 Jan 2018 at 09:45:35 -0500, The Wanderer wrote:
> >
> >> What init system are you running?
> >>
> >> Usually, this can be determined by 'dlocate /sbin/init', but I can't
> >> guar
On 2018-01-11 at 10:23, Brian wrote:
> On Thu 11 Jan 2018 at 09:45:35 -0500, The Wanderer wrote:
>
>> What init system are you running?
>>
>> Usually, this can be determined by 'dlocate /sbin/init', but I can't
>> guarantee that that will hold for all systems.
>
> Guaranteed: 'cat /proc/1/comm'
On Thu 11 Jan 2018 at 09:45:35 -0500, The Wanderer wrote:
> What init system are you running?
>
> Usually, this can be determined by 'dlocate /sbin/init', but I can't
> guarantee that that will hold for all systems.
Guaranteed: 'cat /proc/1/comm'.
--
Brian.
On 2018-01-11 at 09:36, Richard Owlett wrote:
> On 01/11/2018 07:26 AM, rhkra...@gmail.com wrote:
>
>> On Thursday, January 11, 2018 05:29:42 AM Richard Owlett wrote:
>>
>>> OOPS, typos and awkward phrasing. It should have read:
>>> When booting one specific install, it displays many repetitions o
On 01/11/2018 07:26 AM, rhkra...@gmail.com wrote:
On Thursday, January 11, 2018 05:29:42 AM Richard Owlett wrote:
OOPS, typos and awkward phrasing. It should have read:
When booting one specific install, it displays many repetitions of the
line to the effect that it is beginning a specific scrip
On Thursday, January 11, 2018 05:29:42 AM Richard Owlett wrote:
> OOPS, typos and awkward phrasing. It should have read:
> When booting one specific install, it displays many repetitions of the
> line to the effect that it is beginning a specific script.
>
Did it give you the name of the specific
On 01/11/2018 02:32 AM, Jeroen Mathon wrote:
Hey Richard,
Perhaps it is just me but i am having trouble deciphering this
sentence:
"When booting one specific install I many repetitions to the effect
that it is beginning a specific script." could you please elaborate
upon it?
OOPS, typos and a
Hey Richard,
Perhaps it is just me but i am having trouble deciphering this sentence:
"When booting one specific install I many repetitions to the effect that
it is beginning a specific script." could you please elaborate upon it?
On 01/10/2018 03:22 PM, Richard Owlett wrote:
> I multi-boot sev
On Wed, Jan 10, 2018 at 08:22:51AM -0600, Richard Owlett wrote:
I multi-boot several varieties of Debian.
When booting one specific install I many repetitions to the effect
that it is beginning a specific script.
It then proceeds to bring up an apparently normal system.
Would this be logged s
On Wed 10 Jan 2018 at 08:22:51 (-0600), Richard Owlett wrote:
> I multi-boot several varieties of Debian.
> When booting one specific install I many repetitions to the effect
> that it is beginning a specific script.
>
> It then proceeds to bring up an apparently normal system.
>
> Would this be
I multi-boot several varieties of Debian.
When booting one specific install I many repetitions to the effect that
it is beginning a specific script.
It then proceeds to bring up an apparently normal system.
Would this be logged somewhere?
Where?
TIA
29 matches
Mail list logo
