Re: about installer (anaconda from local CD)
On Mon, 2004-09-06 at 10:57, belahcene abdelkader wrote: > Hi jeff, me again, > since you have created a booter with anaconda ( for > sarge at least the 3 or 4 first Cd) from local CD, > You 'll probably help us if you put it on site for > downloading???!!! So far, our CDs have consisted entirely of DFSG-free software, so we of course have no problem with people mirroring or redistributing them. Anyone distributing them should keep an eye on platform.progeny.com and probably the cl-workers mailing list (see platform.progeny.com for details on the list). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with cups (cupsd and admin.cgi hang)
[Please don't send user-specific problems to debian-devel.] On Mon, 2002-05-13 at 11:46, Michael Schwind wrote: > i have Problems when i want to add a Printer, the command line tool and the > web > interface will not work. After pressing the button where you can choose the > printer, > the admin.cgi hangs with about 30% CPU-Time and cupsd needs about 60% > CPU-Time. Are you doing this from a remote machine? The default configuration for CUPS is set to refuse to allow remote access of any kind. Please read the System Administrator's Manual to learn how to enable remote access; it should be accessible by clicking "Help" in the top linkbar on the CUPS server's start page. If you aren't using a remote machine, then something is wrong. I would suggest, in this case, that you purge and reinstall the cupsys package, and try from there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recognizing Kernel Update to 2.4.12
On Tue, Oct 30, 2001 at 01:10:40AM -0500, eDoc wrote: > > - cd /usr/src/linux-2.4.13 > > > > - Configure the kernel. This isn't Debian-specific. Some people > >like "make menuconfig", others "make xconfig", others just plain > >"make config". One handy tip: Debian kernel packages store their > >configs in /boot/config-X.Y.Z, so you can start with a good kernel > >config and go from there. If you do that and just want to be asked > >the questions that are new since that kernel version, run "make > >oldconfig". > > > > - Pick a Debian package revision for your kernel stuff. I generally > >pick something that describes the purpose of the kernel and a > >version, such as "laptop.1". > > > > - Run "make-kpkg clean". > > Ooops! Missed this step. The first time you build, you *may* be able to get away with skipping this step. > > - Run "make-kpkg --revision= kernel_image". > > Uh oh. I just ran "make-kpkg" since i have frequently been told to do that. > > (All of my hacking around seems to have "accidently" resulted in > make-kpkg "deciding" to respond!) Here's where you've gone wrong this time around. I'm not sure what "make-kpkg" does by itself, but I know that it isn't what you need. > The hundreds of choices are, as usual, poorly documented internally > so I guessed on the few for which I did not accept the default. > > CONFIG_HOTPLUG Y > PCMCIA/CardBus Y > CardBus Support Y Good so far... > i82365 comp. bridge N (this may have been the default) Generally, if you can compile something as a module, it's better to do so than to disable it. In the 2.4.x tree, though, they've had some places where the code just doesn't compile with certain configs, so it's prudent to just disable things you don't need. You can always turn them off and try again if the compile fails. i82365 support may be necessary even for some newer laptops to get PCMCIA working. I have a Toshiba that's only about a year and a half old that needs it. > ParallelPort (CONFIG_PARPORT) Y > PC-Style hardware (CONFIG_PARPORT_PC) Y > Support for PCMCIA Mgmt. for PC-style Ports > (CONFIG_PARPORT_PC_PCMCIA) Y > PCMCIA Network (CONFIG_NET_PCMCIA) Y > 3com 589 Y > Ham Radio Y > PCMCIA Serial devices (CONFIG_PCMCIA_SERIAL_CS) M > ***I was thinking this may be necessary for my PCMCIA modem*** Yup. > Video for Linux Y > ***Was hoping this might help to get my Nogatech USB video > adapter/dongle to interface with my cancorder or other video device*** It might. I'm not sure. It shouldn't hurt anything, though. > > - If that succeeds, run "make-kpkg modules_image". > > Did this ... tons of code scrolled by. > > > - If you think you may need to compile other modules for this kernel > >after you've built other kernels with this source tree, run > >"make-kpkg kernel_headers". > > Did this ... tons of code scrolled by. Good. > > - cd /usr/src > > OK. > > > - ls -l *deb > > HOORAY! kernel-headers-2.4.12_100.Custom_i386.deb is there! > Also, from a while back, is modutils_2.4.10-3_i386.deb > > It is something more than before ... though I am not sure it is what I need. > > Is it? Nope. That line you didn't type before, where you just did "make-kpkg"? That's what builds the "kernel-image" package which contains your kernel. The first thing you need to do is uninstall the kernel-headers package you just installed. Do that with "dpkg --remove kernel-headers-2.4.12". Just for safety's sake, go ahead and "rm /usr/src/*deb" as well, so you don't accidentally install an old package that might screw up everything else. Now, back up to the "make-kpkg clean" part and do it all again, and this time follow the directions exactly as I typed them. It might help to print out the directions so you can refer to them exactly. You definitely don't need the modutils package, and downgrading to that version may introduce bugs that have been fixed. The next chance you get, run "apt-get update" and "apt-get dist-upgrade". That should restore the modutils version you had before, and install a bunch of other upgrades as well. > > You should now have a list of Debian packages on your screen, > > corresponding to the kernel packages you just built (and maybe some > > older ones, if you've been building kernels before). Run a "dpkg -i" > > on them, and you're all set. > > I tried "dpkg -i kernel-headers-2.4.12_100.Custom_i386.deb" but it > spit-up ... > > So I tried "dpkg -i *.deb" > > It downgraded modutils from 2.4.10-4 to 2.4.10-3 and then setup > kernel_headers and modutils. > > Nothing new in /boot > > What now, please? See above. > > I *highly* suggest your installing at least the libncurses5-dev package > > glen > > "find -name libncurses5-dev" says nada. > "apropos libncurses5-dev" says nada. > > Ran "apt-get install libncurses5-dev" seemed to go OK. Yup. That's what was needed. Now, "make menuconfig" should work. If you need to reconfigure the kernel, it will be a lot eas
Re: Recognizing Kernel Update to 2.4.12
On Mon, Oct 29, 2001 at 12:11:58PM -0500, eDoc wrote:
> > you need to, as in the documentation, run make-kpkg from the top-level
> kernel
> > directory, which will depend on where you put your kernel source. This is
> typically
> > either /usr/src/linux or /usr/src/kernel-source-
> > glen
>
> kernel-source? You mean "linux-2.4.12.tar.gz?
>
> Or do you mean "linux-2.4.12.gz"?
>
> "linux-2.4.12.tar.gz" is in /usr/src and I tried to run "make-kpkg" there.
> No go.
I'll take you through my complete set of steps for building kernel
packages from pristine kernel.org source.
- Download whatever it is you're getting. I tend to grab a tarball
at one point and then grab the successive patches for a while until
the point where I get tired of typing "patch -p1". You might also
want to verify the kernel sources with the signatures distributed
from that site if you know how to use gpg.
- cd /usr/src
- Untar the source tarball from kernel.org. It should get unpacked
to a "linux" directory in /usr/src.
- Apply any patches I need.
- Move the kernel dir so the dir name contains a version, such as
"linux-2.4.13". (I'll assume I'm building 2.4.13 from here on
out.) So, something like "mv /usr/src/linux /usr/src/linux-2.4.13"
should do the trick. I do this so I can keep track of exactly what
version of the kernel source I have handy.
- Grab the source for any other modules you think you may need.
Debian packages module source as packages that you can install;
look for packages with names that end in "-source". ("dpkg --list
'*-source'" should give you a nice list.) Once you have package
names, just apt-get them.
- The source packages unpack their source as tarballs in /usr/src.
Unpack each one with:
cd /usr/src
(b)zcat foo.tar.(gz|bz2) | tar xvf -
Something like this should unpack them all:
cd /usr/src
for file in *.tar.gz; do zcat $file | tar xvf -; done
for file in *.tar.bz2; do bzcat $file | tar xvf -; done
It's important to be in /usr/src when you unpack the tarball, as
it's set up to unpack to just the right place for make-kpkg to find
it.
- cd /usr/src/linux-2.4.13
- Configure the kernel. This isn't Debian-specific. Some people
like "make menuconfig", others "make xconfig", others just plain
"make config". One handy tip: Debian kernel packages store their
configs in /boot/config-X.Y.Z, so you can start with a good kernel
config and go from there. If you do that and just want to be asked
the questions that are new since that kernel version, run "make
oldconfig".
- Pick a Debian package revision for your kernel stuff. I generally
pick something that describes the purpose of the kernel and a
version, such as "laptop.1".
- Run "make-kpkg clean".
- Run "make-kpkg --revision= kernel_image".
- If that succeeds, run "make-kpkg modules_image".
- If you think you may need to compile other modules for this kernel
after you've built other kernels with this source tree, run
"make-kpkg kernel_headers".
- cd /usr/src
- ls -l *deb
You should now have a list of Debian packages on your screen,
corresponding to the kernel packages you just built (and maybe some
older ones, if you've been building kernels before). Run a "dpkg -i"
on them, and you're all set.
Re: Progeny Debian 1.0 released
On Mon, Apr 09, 2001 at 05:53:14PM +0200, Wichert Akkerman wrote: > Previously Branden Robinson wrote: > > Media Contact: > > Aaron Stenhoff > > Progeny Linux Systems, Inc. > > (317) 833-0313 (ext. 137) > > [EMAIL PROTECTED] > > So, do we get $1k for posting an advertisement now? We thought that this would be something that Debian people generally would be interested in, which is why we posted it. If you would rather not, then that's fine; we won't bother you all on the lists anymore. We've already donated some resources to Debian, and plan to donate more; we financed the development of the XFree86 4.0 packages, and we're working on a very well-connected Debian mirror (as two instances). Perhaps we could take a $1000 credit for "services rendered" or "services to be rendered"? :-)
