On 03/08/2012 05:29 AM, Andrei POPESCU wrote:
On Mi, 07 mar 12, 14:52:19, Wayne Topa wrote:
UPDATE
Fount the problem. Even though dpkg -l bootlogd said it was installed.
some how back in January the bootlogd executable had been removed.
Aptitude was able to purge/install the package and the l
On Mi, 07 mar 12, 14:52:19, Wayne Topa wrote:
>
> UPDATE
>
> Fount the problem. Even though dpkg -l bootlogd said it was installed.
> some how back in January the bootlogd executable had been removed.
> Aptitude was able to purge/install the package and the log is now
> working in wheezy
>
> Th
On 07/03/2012 21:52, Wayne Topa wrote:
On 03/07/2012 11:34 AM, Wayne Topa wrote:
On 03/07/2012 09:13 AM, hvw59601 wrote:
Johan Scheepers wrote:
On 07/03/2012 14:51, Camaleón wrote:
On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
On wheezy testing how can the screen output be logg
On 03/07/2012 11:34 AM, Wayne Topa wrote:
On 03/07/2012 09:13 AM, hvw59601 wrote:
Johan Scheepers wrote:
On 07/03/2012 14:51, Camaleón wrote:
On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
On wheezy testing how can the screen output be logged.
There seem to to be a bit problem w
On Wed, 07 Mar 2012 20:31:02 +0200, Johan Scheepers wrote:
> On 07/03/2012 16:34, Camaleón wrote:
>> On Wed, 07 Mar 2012 08:13:50 -0600, hvw59601 wrote:
>>
>>> Johan Scheepers wrote:
On 07/03/2012 14:51, Camaleón wrote:
> On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
>
On 07/03/2012 16:34, Camaleón wrote:
On Wed, 07 Mar 2012 08:13:50 -0600, hvw59601 wrote:
Johan Scheepers wrote:
On 07/03/2012 14:51, Camaleón wrote:
On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
On wheezy testing how can the screen output be logged.
There seem to to be a bi
On 03/07/2012 09:13 AM, hvw59601 wrote:
Johan Scheepers wrote:
On 07/03/2012 14:51, Camaleón wrote:
On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
On wheezy testing how can the screen output be logged.
There seem to to be a bit problem with some missing modules. Too fast
can not
On Wed, 07 Mar 2012 08:13:50 -0600, hvw59601 wrote:
> Johan Scheepers wrote:
>> On 07/03/2012 14:51, Camaleón wrote:
>>> On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
>>>
On wheezy testing how can the screen output be logged.
There seem to to be a bit problem with som
Johan Scheepers wrote:
On 07/03/2012 14:51, Camaleón wrote:
On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
On wheezy testing how can the screen output be logged.
There seem to to be a bit problem with some missing modules. Too fast
can not read it.
(...)
Boot logs go under "/v
On 07/03/2012 14:51, Camaleón wrote:
On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
On wheezy testing how can the screen output be logged.
There seem to to be a bit problem with some missing modules. Too fast
can not read it.
(...)
Boot logs go under "/var/log/messages" and "/var
On Wed, 07 Mar 2012 14:38:24 +0200, Johan Scheepers wrote:
> On wheezy testing how can the screen output be logged.
>
> There seem to to be a bit problem with some missing modules. Too fast
> can not read it.
(...)
Boot logs go under "/var/log/messages" and "/var/log/boot" (should
bootlodg has
Good day,
On wheezy testing how can the screen output be logged.
There seem to to be a bit problem with some missing modules.
Too fast can not read it.
The OS is running fine.
I am actually impressed. My samsung scx-4624f was installed in seconds
after switch on and connected to PC. On other O
12 matches
Mail list logo
