From: Glyn Millington on
Mike Jones <Not(a)Arizona.Bay> writes:

> Responding to Glyn Millington:
>>
>> Well has that happened yet? The major tool is a text editor - we have
>> lots on the dvd. There seem to be lots of .*rc files around and
>> /etc/rc.d seems to be the sunny playground it always was :-) All that
>> has happened is that the KDE version has taken a major bump up.
>>
>>> The prosecution rests at this time.
>>
>> And you have a *good* case - I just don't think it helps if it is
>> overstated :-) The sky isn't about to fall down.
>>
>
>
> Wellllllll....
>
> Back to that /dev/??? thing. Back on Slack 9 I had a dir full of devs.
> Now I don't, and have udev\HAL to deal with. Sure I can nuke HAL and even
> udev, but then what?
>
> See how those bridged get burned behind you while you're not watching?


Well its a long time since I did it, but I think I recall that if you
switch off udev then the /dev/ gets populated in the good old fashoined
way.

Damn - then I remember this from the Slackware RELEASENOTES


I would not suggest trying to run without udev. Consider it the
userspace portion of the kernel. It *is* possible, but if you must
do that you'll have to tweak a couple things here and there. The
specifics are left as an exercise for the advanced user. Wait, an
advanced user would just use udev. Really, it works and makes things
a lot easier.


This is true!!

Good guide here ...........


http://www.reactivated.net/writing_udev_rules.html


:-)


atb

Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.org/ The Official Source :-)
STFW http://groups.google.com/groups?hl=en&group=alt.os.linux.slackware
JFGI http://jfgi.us/
From: Loki Harfagr on
Fri, 11 Sep 2009 10:43:24 -0400, Michael Black did cat :

> On Fri, 11 Sep 2009, Peter Chant wrote:
>
>> dae3 wrote:
>>
>>> Mike Jones <Not(a)Arizona.Bay> wrote:
>>>
>>>> Whats wrong with RXVT?
>>>>
>>>> If you want extended function, MRXVT?
>>>
>>>
>>> For that matter, I wonder what's wrong with xterm...
>>>
>>>
>>>
>> ...or connecting a teletype to your serial port...
>>
> What's a serial port?

a bit like a parallel port but 'cuter' ;-)

> This about 2001 computer has only one, which I find a problem at times.
> But I assume later computers have even less in the way of serial ports.

maybe not, my last personal desktop still has one and any server
I've met until now still had it, even the ones that are natively
equipped with ILO devices, seems the possibility to plug
a 'cisco' cyan cord still can be of some interest ;-)

Now, that's far from being an equivalent to Konsole or Eterm/screen or
whatever and event rxvt seems to lack the "screen" idea, I really
like the ability to get back to my 'at work' sessions in a simple
-RR pinch or eq. instead of clicketyclicking all over again and again ,-)

Though, I admit that in case you just need some consoles in X
to work locally I don't really care about having transparency or
giggling borders or jellying backgrounds and most of the time
I simply use Ctrl-Alt-PF[1-6] for local chores.
From: notbob on
On 2009-09-11, Glyn Millington <wistanswick(a)linuxmail.org> wrote:

> is that the KDE version has taken a major bump up.

Define "up".

nb
From: Mike Jones on
Responding to Glyn Millington:

> Mike Jones <Not(a)Arizona.Bay> writes:
>
>> Responding to Glyn Millington:
>>>
>>> Well has that happened yet? The major tool is a text editor - we have
>>> lots on the dvd. There seem to be lots of .*rc files around and
>>> /etc/rc.d seems to be the sunny playground it always was :-) All that
>>> has happened is that the KDE version has taken a major bump up.
>>>
>>>> The prosecution rests at this time.
>>>
>>> And you have a *good* case - I just don't think it helps if it is
>>> overstated :-) The sky isn't about to fall down.
>>>
>>>
>>
>> Wellllllll....
>>
>> Back to that /dev/??? thing. Back on Slack 9 I had a dir full of devs.
>> Now I don't, and have udev\HAL to deal with. Sure I can nuke HAL and
>> even udev, but then what?
>>
>> See how those bridged get burned behind you while you're not watching?
>
>
> Well its a long time since I did it, but I think I recall that if you
> switch off udev then the /dev/ gets populated in the good old fashoined
> way.
>
> Damn - then I remember this from the Slackware RELEASENOTES
>
>
> I would not suggest trying to run without udev. Consider it the
> userspace portion of the kernel. It *is* possible, but if you must
> do that you'll have to tweak a couple things here and there. The
> specifics are left as an exercise for the advanced user. Wait, an
> advanced user would just use udev. Really, it works and makes things
> a lot easier.
>


Once again, the case for the prosecution rests.

--
*===( http://www.400monkeys.com/God/
*===( http://principiadiscordia.com/
*===( http://www.slackware.com/
From: Jim Diamond on
On 2009-09-11 at 12:42 ADT, Mike Jones <Not(a)Arizona.Bay> wrote:
> Responding to Jim Diamond:
>
>> On 2009-09-11 at 05:57 ADT, Mike Jones <Not(a)Arizona.Bay> wrote:
>>> Responding to dae3:
>>>
>>>> Mike Jones <Not(a)Arizona.Bay> wrote:
>>>>
>>>>> Whats wrong with RXVT?
>>>>>
>>>>> If you want extended function, MRXVT?
>>>>
>>>>
>>>> For that matter, I wonder what's wrong with xterm...
>>>
>>>
>>> A good point, seeing as RXVT's key strength is that is it lighter than
>>> xterm, and these days thats not even going to cause a ripple on today's
>>> hardware.
>>>
>>> MRXVT does do multiple tabs though, and all the fancy stuff if you want
>>> it.
>>
>> I think it is still lacking utf8 support, which is a bit of a nuisance
>> in some circumstances. Also, it doesn't use X resources, which IMHO is
>> a Bad Thing. Other than that, it's not a bad terminal emulator.

> A console that doesn't require X resources? Isn't that a /good/ thing?

At the risk of being pedantic, this sub-thread concerns terminal
emulators, not consoles. Since these terminal emulators run under
the X window system, they have functionality which could be controlled
via X window resources, rather than via config files.

I don't get why you think not requiring X resources would be a good thing.
Do tell.

Jim