On Lu, 04 aug 14, 23:12:41, The Wanderer wrote:
>
> However, I'm using radeon (or related non-proprietary driver) on a
> different system, and I still get the same 80x25 behavior. I do notice
> an error message about being unable to load fglrx on that system, so
> possibly it's still listed in som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/04/2014 04:44 PM, Andrei POPESCU wrote:
> On Lu, 04 aug 14, 11:20:38, Bob Proulx wrote:
>
>> Or it is also possible that the hardware differences is the source
>> of the difference. Your graphics display hardware may decide to
>> use the 25
On Lu, 04 aug 14, 11:20:38, Bob Proulx wrote:
>
> Or it is also possible that the hardware differences is the source of
> the difference. Your graphics display hardware may decide to use the
> 25 line terminal while mine chooses a 48 line terminal.
I'm guessing it's due to fglrx, which is blackl
Am 04.08.2014 20:14, schrieb Rob Owens:
> You could try installing bootlogd. I just tried it on my jessie system
> (running systemd) and it didn't log anything. But I recall using it on
> Wheezy and I think it logged all the services starting/stopping/failing.
Don't use bootlogd. That's a hack
- Original Message -
> From: "Mark Carroll"
>
> Curt writes:
>
> > On 2014-07-25, Brian wrote:
> >>
> >> With sysvinit the default at booting is for the screen messages to fly
> >> past at a bewildering speed and then for the screen to be cleared by
> >> agetty. Nobody particularily
The Wanderer wrote:
> Maybe it's got something to do with the way I install Debian? I don't
> quite follow the normal installer defaults 100%; I do partitioning
> manually, and I disable all tasks except for the base system, then
> install everything I need (including X) separately afterwards.
I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/03/2014 10:27 PM, Bob Proulx wrote:
> The Wanderer wrote:
>
>> Bob Proulx wrote:
>>> I must have a higher resolution monitor than you. (shrug) I have
>>> 44 lines of console boot messages. The monitor is an older
>>> 1280x1024 monitor. Th
The Wanderer wrote:
> Bob Proulx wrote:
> > I must have a higher resolution monitor than you. (shrug) I have 44
> > lines of console boot messages. The monitor is an older 1280x1024
> > monitor. The default console size is 48 lines and annoyingly doesn't
> > use the bottom third of the screen.
Hi Tom,
Tom H wrote:
> Bob Proulx wrote:
> > kill -1 1 # Tell init to re-read the inittab file.
>
> You can use "telinit q" instead of "kill -1 1".
It is the same thing. Six of one or a half dozen of the other. Use
whichever one you prefer. I prefer sending SIGHUP. Among other
thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/03/2014 04:50 PM, Bob Proulx wrote:
> The Wanderer wrote:
>
>> Bob Proulx wrote:
>>> Note that Squeeze 6 /sbin/getting does not support --noclear so
>>> don't set this on Squeeze systems. But for Wheezy 7 and later
>>> this snippet will mak
On Sun, Aug 3, 2014 at 2:12 PM, Bob Proulx wrote:
>
> if [ -f /etc/inittab ]; then
> if grep -q '^1:2345:respawn:/sbin/getty 38400 tty' /etc/inittab; then
> log "Fixing getty --noclear in /etc/inittab"
> sed --in-place '/^1/s/getty 38400/getty --noclear 38400/' /etc/initt
The Wanderer wrote:
> Bob Proulx wrote:
> > The Wanderer wrote:
> >> Where do you set this, exactly? /etc/inittab ?
> >
> > Note that Squeeze 6 /sbin/getting does not support --noclear so don't
> > set this on Squeeze systems. But for Wheezy 7 and later this
> > snippet will make automate the cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/03/2014 02:12 PM, Bob Proulx wrote:
> The Wanderer wrote:
>
>> Brian wrote:
>>> Upstream for agetty responded to concerns about security from
>>> users, some of whom apparently had the compliance police
>>> breathing down their necks. My vie
The Wanderer wrote:
> Brian wrote:
> > Bob Proulx wrote:
> >> Just for the record I complain about that behavior. I don't like
> >> the fancy tty colors and always disable them. I don't like the
> >> screen clearing those away and so I always set the getty --noclear
> >> option. The problem is th
On Sun 03 Aug 2014 at 12:39:50 +1000, Zenaan Harkness wrote:
> On 8/3/14, Brian wrote:
> >
> > Upstream for agetty responded to concerns about security from users,
> > some of whom apparently had the compliance police breathing down their
> > necks. My view on such idiocy is probably not for this
On 2014-08-03 09:16 +0200, Tom H wrote:
> On Sat, Aug 2, 2014 at 8:53 PM, The Wanderer wrote:
>> On 08/02/2014 03:15 PM, Brian wrote:
>>> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
Brian wrote:
>
> With sysvinit the default at booting is for the screen messages
> to
On Sat, Aug 2, 2014 at 8:53 PM, The Wanderer wrote:
> On 08/02/2014 03:15 PM, Brian wrote:
>> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
>>> Brian wrote:
With sysvinit the default at booting is for the screen messages
to fly past at a bewildering speed and then for the
On 8/3/14, Brian wrote:
> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
>> Brian wrote:
>> > With sysvinit the default at booting is for the screen messages to fly
>> > past at a bewildering speed and then for the screen to be cleared by
>> > agetty. Nobody particularily complains about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/02/2014 03:15 PM, Brian wrote:
> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
>
>> Brian wrote:
>
>>> With sysvinit the default at booting is for the screen messages
>>> to fly past at a bewildering speed and then for the screen t
On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
> Brian wrote:
> > With sysvinit the default at booting is for the screen messages to fly
> > past at a bewildering speed and then for the screen to be cleared by
> > agetty. Nobody particularily complains about this behaviour. Unless
> > you
Brian wrote:
> With sysvinit the default at booting is for the screen messages to fly
> past at a bewildering speed and then for the screen to be cleared by
> agetty. Nobody particularily complains about this behaviour. Unless
> you have an excellent visual memory you are in the dark as regards wha
On Mon, Jul 28, 2014 at 11:52:51PM +0300, Andrei POPESCU wrote:
> On Lu, 28 iul 14, 08:41:39, Chris Bannister wrote:
> > On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
> > >
> > > You are aware of course that:
> > > - it's also possible to scroll *back* (surprise, surprise)
> >
>
On Lu, 28 iul 14, 08:41:39, Chris Bannister wrote:
> On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
> >
> > You are aware of course that:
> > - it's also possible to scroll *back* (surprise, surprise)
>
> Can you still? It used to be , (which didn't work last
> time I tried) have
On Lu, 28 iul 14, 11:22:30, Zenaan Harkness wrote:
>
> 3) disable scrolling (I think Andrei said this is possible),
No, I said stopped (Ctrl-S / Ctrl-Q).
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth
On 7/28/14, Chris Bannister wrote:
> On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
>> On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
>> > I've thought for years, and noted in my "fix unix" notes that
>> > boot messages ought be written starting at the top of the
>> > screen,
On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
> On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
> > I've thought for years, and noted in my "fix unix" notes that
> > boot messages ought be written starting at the top of the
> > screen, then when they get to the bottom, rather t
On Du, 27 iul 14, 09:59:21, Mark Carroll wrote:
>
> This is the problem with what the current wheezy default seems to be of
> the screen clearing when the login prompt is reached. Before agetty
> started doing that, I could usefully scroll back, now it seems to wipe
> out anything much after check
Andrei POPESCU writes:
> On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
>> On 7/26/14, Brian wrote:
>>
>> > With sysvinit the default at booting is for the screen messages to fly
>> > past at a bewildering speed and then for the screen to be cleared by
>> > agetty.
>>
>> I've thought for y
On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
> On 7/26/14, Brian wrote:
>
> > With sysvinit the default at booting is for the screen messages to fly
> > past at a bewildering speed and then for the screen to be cleared by
> > agetty.
>
> I've thought for years, and noted in my "fix unix" n
On 7/26/14, Brian wrote:
> On Fri 25 Jul 2014 at 16:02:18 -0400, The Wanderer wrote:
>> On 07/25/2014 03:33 PM, Michael Biebl wrote:
>> > Hi,
>> > Am 25.07.2014 20:27, schrieb Steven Post:
>> >> I'm running Jessie (lagging about 5 days behind with the updates)
>> >> and use systemd-sysv. Today I n
On Sun, 27 Jul 2014, Michael Biebl wrote:
> Am 27.07.2014 00:26, schrieb Rick Thomas:
> > On Jul 25, 2014, at 12:33 PM, Michael Biebl wrote:
> >> So a future update of systemd will slightly change this behaviour:
> >> whenever there is a service that failed or takes longer then a certain
> >> thre
Am 27.07.2014 00:26, schrieb Rick Thomas:
>
> On Jul 25, 2014, at 12:33 PM, Michael Biebl wrote:
>
>> So a future update of systemd will slightly change this behaviour:
>> whenever there is a service that failed or takes longer then a certain
>> threshold (iirc it's something like 5 secs), syste
On Jul 25, 2014, at 12:33 PM, Michael Biebl wrote:
> So a future update of systemd will slightly change this behaviour:
> whenever there is a service that failed or takes longer then a certain
> threshold (iirc it's something like 5 secs), systemd will automatically
> switch into verbose mode
W
On 2014-07-26, Michael Biebl wrote:
>
> You can use the journal for that. It captures everything.
> Try journalctl -alb
>
I tried as both a regular user and as root to no avail. I searched for
it with apt-cache with equally disappointing results (I am still using
squeeze).
I now understand tha
Am 26.07.2014 12:03, schrieb Mark Carroll:
> Curt writes:
>
>> On 2014-07-25, Brian wrote:
>>>
>>> With sysvinit the default at booting is for the screen messages to fly
>>> past at a bewildering speed and then for the screen to be cleared by
>>> agetty. Nobody particularily complains about this
Curt writes:
> On 2014-07-25, Brian wrote:
>>
>> With sysvinit the default at booting is for the screen messages to fly
>> past at a bewildering speed and then for the screen to be cleared by
>> agetty. Nobody particularily complains about this behaviour. Unless
>> you have an excellent visual m
Hi Michael,
On Fri, 2014-07-25 at 21:33 +0200, Michael Biebl wrote:
> Hi,
>
> Am 25.07.2014 20:27, schrieb Steven Post:
>
> > I'm running Jessie (lagging about 5 days behind with the updates) and
> > use systemd-sysv. Today I noticed that there is no visual feedback from
> > fsck when checking a
On 2014-07-25, Brian wrote:
>
> With sysvinit the default at booting is for the screen messages to fly
> past at a bewildering speed and then for the screen to be cleared by
> agetty. Nobody particularily complains about this behaviour. Unless
> you have an excellent visual memory you are in the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
(Sorry if this turns out to be a resend; there's been a hiccup on my
end, and due to the usual variable lag before I receive messages I send
to the Debian lists, I don't know if it got sent before or not.)
On 07/25/2014 04:21 PM, Michael Biebl wrote
On Fri 25 Jul 2014 at 16:02:18 -0400, The Wanderer wrote:
> On 07/25/2014 03:33 PM, Michael Biebl wrote:
>
> > Hi,
> >
> > Am 25.07.2014 20:27, schrieb Steven Post:
> >
> >> I'm running Jessie (lagging about 5 days behind with the updates)
> >> and use systemd-sysv. Today I noticed that there i
Am 25.07.2014 22:21, schrieb Michael Biebl:
> Am 25.07.2014 22:02, schrieb The Wanderer:
>> Is there any plan to do either of these things in the Debian-default
>> configuration (and possibly update existing installs to match, if
>> unmodified)?
>
> No, there is no such plan.
What I do plan to d
Am 25.07.2014 22:02, schrieb The Wanderer:
> On 07/25/2014 03:33 PM, Michael Biebl wrote:
>
>> Hi,
>
>> Am 25.07.2014 20:27, schrieb Steven Post:
>
>>> I'm running Jessie (lagging about 5 days behind with the updates)
>>> and use systemd-sysv. Today I noticed that there is no visual
>>> feedback
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/25/2014 03:33 PM, Michael Biebl wrote:
> Hi,
>
> Am 25.07.2014 20:27, schrieb Steven Post:
>
>> I'm running Jessie (lagging about 5 days behind with the updates)
>> and use systemd-sysv. Today I noticed that there is no visual
>> feedback fr
Hi,
Am 25.07.2014 20:27, schrieb Steven Post:
> I'm running Jessie (lagging about 5 days behind with the updates) and
> use systemd-sysv. Today I noticed that there is no visual feedback from
> fsck when checking an ext4 filesystem at boot time. Since it appears the
> system is stuck (apart from
Hello list,
I'm running Jessie (lagging about 5 days behind with the updates) and
use systemd-sysv. Today I noticed that there is no visual feedback from
fsck when checking an ext4 filesystem at boot time. Since it appears the
system is stuck (apart from the HDD LED) I would consdider this a bug.
45 matches
Mail list logo
