On Tue, 22 Jun 1999, Enrico Zini wrote:

> Hello!
> 
> I've come up with a bunch of practical questions around the Debian Slink
> distribution:

Well, i'll answer the ones i can figure out...

>  1) There isn't a group 'shutdown' to whom add people allowed to shutdown,
>     while I often find a need for it in many environments: is there
>     another way (i.e. "The Debian Right Way") to do it?

Well, anyone who has access to the console can shutdown with the
Ctrl-Alt-Del, if you add their names to /etc/shutdown.allow (or possibly
anyone, depends if shutdown has the -a option in inittab)

If you wanted to make a shutdown group, i guess you _could_ chmod the
shutdown binary to 550, owned by root.shutdown, and make it suid root? Not
sure of the security implications here, though.

>  3) make-kpkg rebuilds all of the kernel after every single change: if
>     I just compiled a kernel and wanted to add, say, a module,
>     everything gets recompiled instead of just the few required files:
>     is there a clean way to allow this? Can I just set do_clean := NO in
>     debian/rules?

Looks like do_clean := NO will do it for you.

>  6) SSH came with unencrypted communcation disabled at compile time; I
>     run a network in a secure environment and want to use ssh for its
>     cryptographical authentication, but allow it to operate unencrypted
>     when connecting to local hosts, since there's no risk of network
>     snooping and I want to avoid unnecessary computation. Couldn't the
>     option be disallowed by default in a system wide configuration file
>     instead of compile time? This isn't an important issue, however,
>     because one can suppose that if I'm smart enough to tell when an
>     environment is secure, then I'm smart enough to download the source
>     package and recompile it. I just wanted to point it out.

Couldn't you just plain telnet if the connection is secure?

>  8) I've never been able to use the multi_cd access method of dselect:
>     I always happen to see only the contents of the first cd, while with
>     apt I need every cd mounted to see them both. For the former, I know
>     it's my fault, for the latter I understood I have to wait for potato
>     to be able to use apt with multiple cd: am I right? And for
>     multi_cd, what's the right way of operation? I have never been asked
>     for the second CD.

You don't have to wait for potato, i hear netgod has slink-ized debs of
the latest apt.

As for using CDs, i can't help because i've done everything over the net,
even the initial install...

> 10) Debian is a beautiful thing.

I agree, although that's technically not a question... ;)

Reply via email to