Prev: Akonadi and Slackware 13.1
Next: Kernel Panic: Slackware 13.1 64-bit
From: Res on 1 Jun 2010 21:01
On Tue, 01 Jun 2010 13:14:32 +0000, Douglas Mayne wrote:


> Ack! IME, wicd is sufficient and doesn't require editing config files.
> It transparently handles all of the parameters that had previously
> required manual loading of wpa_supplicant, etc. And the wicd-curses
> program gives a similar interface to CLI-only interfaces.
>


+1

It does it all, well, be nicer if it also did HSPA and PPP, they have
been "coming" for too many years now for me to give a damn waiting, just
use hand written scripts that work just as well, but for newbies, they'd
be screwed.



> To the OP: Because wicd is in the "extra" package group, that makes it

and I think once they sort out the above mentioned (and once they get PPP
in it, all the hard work has been done to also include HSPA) , I think
I'd like to see it moved from extra into n/ and used by default.








--
"If a man is in need of rescue, an airplane can come in and throw flowers
on him, and that's just about all. But a helicopter could come in and
save his life." - Igor I. Sikorsky
From: Martin on 2 Jun 2010 06:08
Chris Vine wrote:

> I don't think your approach is right. The README in the wicd extras
> directory tells you to remove any set-up in /etc/rc.inet1.conf and in
> my experience if that is done wicd is foolproof. It can also handle
> wired ethernet as well as wireless, and any necessary dhcp requests.

I remember having problems getting it to work, but thanks to the feedback of
yours and others I shall look into it again.

Cheers

Martin
From: Jim Diamond on 2 Jun 2010 10:58
On 2010-06-01 at 19:18 ADT, Mike Jones <luck(a)dasteem.invalid> wrote:
> Responding to Jim Diamond:
>
> [...]
>> I just put Slack64 13.1 on my laptop. Besides my hardware for which I
>> use proprietary drivers (nvidia graphics card), I add a lot of packages
>> which I need to d/l and compile myself. Is it a big deal? Well, not in
>> the sense that it is a major difficulty. But it took me about a day to
>> get everything set up, and if those packages came with Slackware
>> already, I'd be about a day ahead.

> I have a scripted files\slackpkg collection that I run on a fresh install.
>
> Everything done, including customised user accounts, in 7 minutes.
>
> Pre-use reboot optional.

I also have one, although I tend not to let it run automatically the
first time I use it on a new version of Slackware, in case something
significant has changed.

Even then, downloading and compiling just the slackbuilds.org packages
I add to Slackware takes way more than 7 minutes, and would do so even
if I had a gigabit network connection and 32 processors. I think it
takes my laptop (2 GHz Core 2 duo) more than 7 minutes just to compile
inkscape. :-(

What's a "reboot" ? :-)

Jim
From: Mike Jones on 2 Jun 2010 16:14
Responding to Jim Diamond:

> On 2010-06-01 at 19:18 ADT, Mike Jones <luck(a)dasteem.invalid> wrote:
>> Responding to Jim Diamond:
>>
>> [...]
>>> I just put Slack64 13.1 on my laptop. Besides my hardware for which I
>>> use proprietary drivers (nvidia graphics card), I add a lot of
>>> packages which I need to d/l and compile myself. Is it a big deal?
>>> Well, not in the sense that it is a major difficulty. But it took me
>>> about a day to get everything set up, and if those packages came with
>>> Slackware already, I'd be about a day ahead.
>
>> I have a scripted files\slackpkg collection that I run on a fresh
>> install.
>>
>> Everything done, including customised user accounts, in 7 minutes.
>>
>> Pre-use reboot optional.
>
> I also have one, although I tend not to let it run automatically the
> first time I use it on a new version of Slackware, in case something
> significant has changed.
>
> Even then, downloading and compiling just the slackbuilds.org packages I
> add to Slackware takes way more than 7 minutes, and would do so even if
> I had a gigabit network connection and 32 processors. I think it takes
> my laptop (2 GHz Core 2 duo) more than 7 minutes just to compile
> inkscape. :-(
>
> What's a "reboot" ? :-)
>
> Jim


I discluded final compiles as most extra stuff is in *tgz form.

As for "reboot", RTFM! ;)

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: Akonadi and Slackware 13.1
Next: Kernel Panic: Slackware 13.1 64-bit