nvy == Nikita V Youshchenko [EMAIL PROTECTED] writes:
nvy The thing I really don't like in debian-cd is the requirement
nvy to have a local mirror. I prefer to use apt-get (+apt-proxy)
nvy to fetch packages while building CD. I have a (currently
nvy ugly) script to do so; if
Christoph Berg wrote:
The problem that one doesn't want things like .bash_completion read
there is easily solved by
# check whether we run interactively
[ $PS1 ] || return
(Something like that exists in Debian's /etc/skel/.bash_profile.)
Uh, no. You are thinking of
Re: Re: [custom] Some issues for custom debian distributions [Bob Proulx
[EMAIL PROTECTED], Sun, Jul 27, 2003 at 11:10:40PM -0600, [EMAIL PROTECTED]]
# check whether we run interactively
[ $PS1 ] || return
(Something like that exists in Debian's /etc/skel/.bash_profile.)
Uh
Nikita V. Youshchenko [EMAIL PROTECTED] wrote:
[...]
Another thing is replacing #!/bin/sh by #!/bin/bash --login in
/etc/kde3/kdm/Xsession (and other dm's Xsession files). This is the only
way I know to make login shell startup files evaluated during X logins.
This issue is known for ages,
Re: Re: [custom] Some issues for custom debian distributions [Nikita V.
Youshchenko [EMAIL PROTECTED], Sun, Jul 27, 2003 at 08:30:33AM +0400,
[EMAIL PROTECTED]]
if [ -r $HOME/.profile ] ; then
. $HOME/.profile
fi
Sterictly saying, this is broken.
/etc/profile, ~/.profile
On Fri, Jul 25, 2003 at 05:58:31PM +0200, Petter Reinholdtsen wrote:
- Preconfigure the packages we install
Using two different approaches: (1) Load answers into the debconf
database before the packages are installed using some home-make
scripts, and (2) rewrite/replace
It's really good news that someone is writing on this. Since Debian is
somewhat hard to install and configure for unexperienced user, but
otherwise Debian is The Best :), I guess many people are doing custom
Debain installation tools.
- Preconfigure the packages we install
Using two
Quoting Tore Anderson ([EMAIL PROTECTED]):
well), as I've seen far too many packages which ask Debconf questions
way out of proportion, carelessly ignore policy 11.7.3 (cf. the manage
with Debconf madness thread), etc. So even though it is possible to
I hope you didn't forgot to file bugs
Nikita V. Youshchenko wrote:
E.g. in a distribution (better to say - custom installation CD) I maintain
here I expect users to use kppp to connect to their ISPs. To make this work
by default, I have to comment out whole contents of /etc/ppp/options during
the last stage of the installation. I
Nikita V. Youshchenko [EMAIL PROTECTED] wrote:
[...]
Another thing is replacing #!/bin/sh by #!/bin/bash --login in
/etc/kde3/kdm/Xsession (and other dm's Xsession files). This is the only
way I know to make login shell startup files evaluated during X logins.
This issue is known for ages, but
On Sat, Jul 26, 2003 at 05:51:35PM +0200, Andreas Metzler wrote:
cat EOF /etc/X11/Xsession.d/60local_userenvironment
if [ -r /etc/profile ] ;then
. /etc/profile
fi
if [ -r $HOME/.profile ] ; then
. $HOME/.profile
fi
EOF
This'll work for all display-managers that use
Javier Fernández-Sanguino Peña [EMAIL PROTECTED] wrote:
[...]
Introducing an ~/.environment which would be evaluated by pam_env would
really be nice.
Isn't /etc/environment read too? Because that is what base-config modifies
IIRC.
Yes or no ;-) Currently pam_env does read /etc/environment
On Sat, Jul 26, 2003 at 09:24:55PM +0200, Andreas Metzler wrote:
Javier Fern?ndez-Sanguino Pe?a [EMAIL PROTECTED] wrote:
[somebody broke attributions here]
Introducing an ~/.environment which would be evaluated by pam_env would
really be nice.
Isn't /etc/environment read too? Because that
Andreas Metzler wrote:
Nikita V. Youshchenko [EMAIL PROTECTED] wrote:
[...]
Another thing is replacing #!/bin/sh by #!/bin/bash --login in
/etc/kde3/kdm/Xsession (and other dm's Xsession files). This is the only
way I know to make login shell startup files evaluated during X logins.
This
As discussed during debcamp in Oslo, all the groups/projects making
debian based custom distributions should join together to find common
solutions to the common problems. This is a start, with a few of the
issues that Skolelinux had and solved.
- Automatic installation
Using the new
* Petter Reinholdtsen
- Preconfigure the packages we install
Using two different approaches: (1) Load answers into the debconf
database before the packages are installed using some home-make
scripts, and (2) rewrite/replace configuration files using
cfengine at
On Fri, 25 Jul 2003 18:28:27 +0200
Tore Anderson [EMAIL PROTECTED] wrote:
* Petter Reinholdtsen
- Preconfigure the packages we install
I believe the best option would be to extend all the packages
we use to make it possible to configure everything we need
using
[Tore Anderson]
God, No! There's far too many Debconf questions being asked by
various Debian packages already, IMNSHO.
There is no reason for you to get religious over this question.
The nice thing about debconf is that there is no _need_ to present all
options as questions. One can like
Hi
On Fri, Jul 25, 2003 at 05:58:31PM +0200, Petter Reinholdtsen wrote:
[...]
- Configure default language for all users
Using a custom script to rewrite config files to modify the
default language/locale.
Why not having multiple languages per user? I mean for example:
1) French
* Tore Anderson
God, No! There's far too many Debconf questions being asked by
various Debian packages already, IMNSHO.
* Petter Reinholdtsen
There is no reason for you to get religious over this question.
The nice thing about debconf is that there is no _need_ to present all
Petter Reinholdtsen wrote:
- Installing the list of package we want
Using meta-packages (ie packages consisting only of dependencies)
to install the packages we want. Used hooks in base-config to
get them installed during first time installation. Not too happy
about
21 matches
Mail list logo
