Bug#185261: di-utils-generic: mapdevfs do not handle LVM devices
Package: di-utils-generic Version: 0.18 Severity: grave When remapping LVM devices, it insertes NULL as the device name: % ./mapdevfs /dev/tjener_vg/usr_lv /dev/(null)3 % It should just pass on the LVM devpath without changing it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problème d'intallation
Hi, On Tue, Mar 18, 2003 at 08:45:16AM +0100, Mario Jeanmaire wrote: > Madame, Monsieur, > Jai une logiciel Linux Madrake qui fonctionne très bien sur lun de mes PC > mais je voudrais passer sur mon portable linstallation se passe bien sauf > au moment du re boot , la il démarre puis le code page de départ sarrête et > lécran reste noir et tout sarrête comme si la carte graphique se bloquais > pour votre information ce notebook. > Je viens de lacheter et c est un Fujitsu/siemens avec processeur AMD > Athlon 2200 la carte graphique Radeon igp 320m > Ma question est y a t il une solution et la quelle et comment pratiquer > pour que sa fonctionne > Dans lattente ,Veuillez agréer, Madame, Monsieur, l'expression de mes > sentiments distingués > M.jeanmaire This is not the right list to ask about Mandrake Linux on laptops; it's dedicated to Debian. Also a Linux-based OS, but quite different. Furthermore, this list's topic is the development of the new installer for Debian, and the language is English. You'll have more success asking somewhere else. Cheers, Emile. -- E-Advies - Emile van Bergen [EMAIL PROTECTED] tel. +31 (0)70 3906153 http://www.e-advies.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building d-i
On Tue, Mar 18, 2003 at 06:50:37AM +0800, [EMAIL PROTECTED] wrote: > On 17 Mar 2003, Tollef Fog Heen wrote: > > > obviously not, since you should ordinarily not build > > libdebian-installer yourself, you should just install it into your > > host system. libdebian-installer is a normal debian package, which is > > built like all normal debian packages. > > > > Please, please read all the stuff doc/*, the various README files > > lying around and the Developer's Reference. > > I had read the doc/* before I started. Obviously I had missed > build/README, but I have now read that, more than once, and the > information I need is not there. > > I have already pointed out one error in the documentation, and here's > another: > [EMAIL PROTECTED] summer]$ lynx -dump > http://people.debian.org/~tfheen/debian-installer/ > >Not Found > >The requested URL /~tfheen/debian-installer/ was not found on > this >server. > _ > > > Apache/1.3.26 Server at people.debian.org Port 80 > [EMAIL PROTECTED] summer]$ > > > Please, take the time to check that the documentation you want me to > read is correct, and has pointers to necessary supplementary material > such as relevant sections of the Developer's Reference. > > Also, check that you provide "complete source code" as described in the > GPL. I have the feeling that the files and /or scripts to make the > package is missing. I've been able to build the floppy 'net' image without any trouble only by installing the needed packages on the host system (and removing the bogl stuff from the floppy tree), so I guess everything's there to build the package. If you want an easy way to find what's missing, just try to run the build process by entering the 'build' directory and run "make TYPE=whateveryouwant build". Then you'll soon see which packages are missing. Install them on the host system, and re-run, it'll work fine. Stéphane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdebconf override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): cdebconf-gtk-udeb_0.34_i386.udeb: package says priority is standard, override says optional. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdebconf_0.34_i386.changes ACCEPTED
Accepted: cdebconf-gtk-udeb_0.34_i386.udeb to pool/main/c/cdebconf/cdebconf-gtk-udeb_0.34_i386.udeb cdebconf-newt-udeb_0.34_i386.udeb to pool/main/c/cdebconf/cdebconf-newt-udeb_0.34_i386.udeb cdebconf-slang-udeb_0.34_i386.udeb to pool/main/c/cdebconf/cdebconf-slang-udeb_0.34_i386.udeb cdebconf-udeb_0.34_i386.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.34_i386.udeb cdebconf_0.34.dsc to pool/main/c/cdebconf/cdebconf_0.34.dsc cdebconf_0.34.tar.gz to pool/main/c/cdebconf/cdebconf_0.34.tar.gz cdebconf_0.34_i386.deb to pool/main/c/cdebconf/cdebconf_0.34_i386.deb libdebconf1-dev_0.34_i386.deb to pool/main/c/cdebconf/libdebconf1-dev_0.34_i386.deb libdebconf1_0.34_i386.deb to pool/main/c/cdebconf/libdebconf1_0.34_i386.deb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d-i - Automated installs
This is a kickstart file I have used for Red Hat Linux 7.3.
Using this, I can install a RHL desktop on a Celeron (about) 900 in
under 15 minutes, with no interaction.
_
lang en_US
langsupport --default en_AU en_US
keyboard us
#Probe for Mouse
mouse
timezone Australia/Perth
rootpw client-password
reboot
bootloader --location=mbr --append='vga=6 apm=off'
clearpart --drives=hda --linux
install
#nfs --server 192.168.1.1 --dir /var/ftp/pub/linux/RedHat/7.3/ISO
url --url http://cc.computerdatasafe.com.au/RedHat/7.3u/dist
part /boot --fstype ext3 --size 25 --asprimary --ondisk hda
part / --fstype ext3 --size 1 --grow --ondisk hda
part swap --size 64 --ondisk hda
network --bootproto dhcp
text
#skipx
#xconfig --noprobe --resolution 1280x1024 --depth 16 --monitor
#xconfig --resolution 1280x1024 --depth 16 --hsync 31.5-56.5 --vsync 50.0-90.0
--startxonboot
xconfig --startxonboot
auth --useshadow --enablemd5
firewall --disabled
%packages
@Network Support
@Router / Firewall
@KDE
@GNOME
@Dialup Support
@Messaging and Web Tools
@Games and Entertainment
@Software Development
@Kernel Development
vim-enhanced
vim-X11
openssh
openssh-server
openssh-clients
procinfo
perl
pine
lsof
lynx
strace
pump
#=
%pre
# This didn't work
#set -ex
#dd if=/dev/null of=/var/swap count=65536 size=1024
#mkswap /var/swap
#swapon /var/swap
%post --nochroot
(
echo To: [EMAIL PROTECTED]
echo From: [EMAIL PROTECTED]
echo Subject: Installation of Red Hat Linux
set
set -x
cp /etc/resolv.conf /mnt/sysimage/etc
URL=$(echo ${ANACONDAARGS} | chroot /mnt/sysimage awk '{print $2}' )
BASEURL=$(chroot /mnt/sysimage dirname ${URL} )
chroot /mnt/sysimage wget -P /etc/init.d ${BASEURL}/ks/postinstall/ks.post
chmod +x /mnt/sysimage/etc/init.d/ks.post
chroot /mnt/sysimage chkconfig ks.post on
for p in dhcpcd lilo efax finger rsh talk mutt rsh-server telnet-server talk-server
postgresql-devel \
tux iptables-ipv6
do chroot /mnt/sysimage rpm --erase -v ${p}
done
REL=$(chroot /mnt/sysimage rpm -q redhat-release | sed -e 's=[-a-zA-Z]*==;s=-.*==')
RH=192.168.1.1
RDname=/var/ftp/pub/linux/RedHat/${REL}
NFSOPTS="user,soft,intr,noauto,exec"
echo ${RH}:${RDname}/mnt/nfsnfs ${NFSOPTS}
echo ${RH}:${RDname}/mnt/nfsnfs ${NFSOPTS} >>/mnt/sysimage/etc/fstab
mkdir /mnt/sysimage/mnt/nfs
ed <<. /mnt/sysimage/etc/sysctl.conf
H
/kernel.sysrq/s=0=1=
wq
.
/mnt/sysimage/bin/cp -a /tmp/ks.cfg /mnt/sysimage/tmp/
chroot /mnt/sysimage procinfo
ls -al /tmp
) 2>&1 | chroot /mnt/sysimage /usr/sbin/sendmail -t
_
You activate it at the syslinux boot prompt. I generally edit the
configuration so as to make the timeout=1, and the default (only)
selection the one I want.
The ks file can be on a floppy, on the CD, or accessible by http/ftp
etc. Since you can use http to get it, it could be generated in the fly
using CGI or similar.
Most of the ks file seems pretty simple to me. Packages can be named
individually, or chosen as a group - think tasksel. The at symbol
signifies a package name.
The %pre script I've not found much use for, but you _can_ use it to
partition the drive.
You can have more than one %post script, and they can execute chroot to
the target system or not, and you have choice in interpreter (anyone for
Perl?).
While my %post script erases some packages that were installed, it is
now possible (might have been then too) to exclude packages by preceding
their names with a minus sign:
-sendmail
--
Cheers
John Summerfield
Please, no off-list mail at all at all. This address accepts mail only from Debian
lists.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#185014: cdebconf mangles strings with consecutive spaces
On Mon, Mar 17, 2003 at 06:51:49PM +0100, Martin Sjögren wrote: [...] > I think it's quite reasonable to have a libdebconf1-dev for the > libdebconf1 package (which is still needed, no matter whether > you've got debconf or cdebconf installed). > > Perhaps it's an idea to split libdebconf in libdebconfclient and > libcdebconf? (note the c, since that package would only be used together > with cdebconf, to write frontends perhaps). You got it here, split libdebconf in libdebconfclient(-dev) and libcdebconf, then you will realize that libcdebconf is only needed by cdebconf and can be dropped (the package, not the library) as well as libcdebconf-dev. Then API changes will seldom occur. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building d-i
On Tue, 18 Mar 2003, Stephane Enten wrote: > On Tue, Mar 18, 2003 at 06:50:37AM +0800, [EMAIL PROTECTED] wrote: > > On 17 Mar 2003, Tollef Fog Heen wrote: > > > > > obviously not, since you should ordinarily not build > > > libdebian-installer yourself, you should just install it into your > > > host system. libdebian-installer is a normal debian package, which is > > > built like all normal debian packages. > > > > > > Please, please read all the stuff doc/*, the various README files > > > lying around and the Developer's Reference. > > > > I had read the doc/* before I started. Obviously I had missed > > build/README, but I have now read that, more than once, and the > > information I need is not there. > > > > I have already pointed out one error in the documentation, and here's > > another: > > [EMAIL PROTECTED] summer]$ lynx -dump > http://people.debian.org/~tfheen/debian-installer/ > > > >Not Found > > > >The requested URL /~tfheen/debian-installer/ was not found on > > this > >server. > > _ > > > > > > Apache/1.3.26 Server at people.debian.org Port 80 > > [EMAIL PROTECTED] summer]$ > > > > > > Please, take the time to check that the documentation you want me to > > read is correct, and has pointers to necessary supplementary material > > such as relevant sections of the Developer's Reference. > > > > Also, check that you provide "complete source code" as described in the > > GPL. I have the feeling that the files and /or scripts to make the > > package is missing. > > I've been able to build the floppy 'net' image without any trouble only > by installing the needed packages on the host system (and removing the > bogl stuff from the floppy tree), so I guess everything's there to build > the package. > > If you want an easy way to find what's missing, just try to run the > build process by entering the 'build' directory and run > "make TYPE=whateveryouwant build". > > Then you'll soon see which packages are missing. Install them on the > host system, and re-run, it'll work fine. It may well be that I am missing something incredibly obvious, and I will be delighted if someone can point it out. I have checked out debian-installer, and I have these main directories: chroot [EMAIL PROTECTED] tmp]# find debian-installer -type d -maxdepth 1 debian-installer debian-installer/CVS debian-installer/anna debian-installer/doc debian-installer/build debian-installer/kernel-image-di debian-installer/kernel-splitter debian-installer/libd-i debian-installer/libdebian-installer debian-installer/main-menu debian-installer/retriever debian-installer/rootskel debian-installer/tools debian-installer/utils chroot [EMAIL PROTECTED] tmp]# What I want to do is to build all these packages, and then go on to create bootable disks from the results. I expect at some point to have a set of udebs. Those directories come from a tarball I created from the checkout, which I did under another account name. Here are the commands I have used most recently: #!/bin/bash -xe cd /tmp rm -rf debian-installer ls -oh debian-installer.tar.bz2 tar xjf debian-installer.tar.bz2 cd debian-installer/libdebian-installer make all install cd ../build/ cp -p sources.list sources.list.local fakeroot make TYPE=net build This failed with these messages: Need to download : di-utils-shell rootskel anna main-menu cdebconf-udeb udpkg busybox-udeb dash-udeb kernel-image-2.4.20-386-udeb choose-mirror net-retriever netcfg-static netcfg-dhcp pump-udeb modutils-basic ethdetect nic-modules-shared-2.4.20-386-udeb socket-modules-2.4.20-386-udeb isa-pnp-modules-2.4.20-386-udeb nic-modules-2.4.20-386-udeb Reading Package Lists... Building Dependency Tree... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Sorry, but the following packages have unmet dependencies: anna: Depends: libdebian-installer3 (>= 0.10) but it is not installable ethdetect: Depends: libdebian-installer3 (>= 0.10) but it is not installable Depends: libdiscover1 but it is not installable main-menu: Depends: libdebian-installer3 (>= 0.10) but it is not installable netcfg-dhcp: Depends: libdebian-installer3 (>= 0.10) but it is not installable netcfg-static: Depends: libdebian-installer3 (>= 0.10) but it is not installable pump-udeb: Depends: libpopt0 (>= 1.6.4) but 1.6.2-7 is to be installed E: Sorry, broken packages make: *** [net-get_udebs-stamp] Error 100 chroot [EMAIL PROTECTED] root]# Now, I have actually built and installed libdebian-installer: chroot [EMAIL PROTECTED] tmp]# ls /usr/lib/libdebian-installer.* -rwxr-xr-x1 root root 9280 Mar
Re: How to handle non-ascii characters in templates?
On Mon, Mar 10, 2003 at 06:25:36PM +0100, Petter Reinholdtsen wrote: > [Denis Barbier] > >>> Maybe we could also add an en.po file to provide ISO-8859-1 > >> That is one option, but I believe it is better to specify that > >> templates should use UTF-8. I'm not sure how much must change to make > >> it happen. > > > > Gettext only accepts ASCII encoded msgids. > > OK. Then I guess an en.po is a better idea. But I am not sure > cdebconf will use 'en' as a fallback language. I believe it should. It would indeed work for d-i. But if cdebconf is used as a debconf replacement, only ASCII characters should be displayed when locale is POSIX. A better solution is to let languagechooser always append 'en' to LANGUAGE. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building d-i
On Tue, Mar 18, 2003 at 09:23:00PM +0800, [EMAIL PROTECTED] wrote: > On Tue, 18 Mar 2003, Stephane Enten wrote: > > > I've been able to build the floppy 'net' image without any trouble only > > by installing the needed packages on the host system (and removing the > > bogl stuff from the floppy tree), so I guess everything's there to build > > the package. > > > > If you want an easy way to find what's missing, just try to run the > > build process by entering the 'build' directory and run > > "make TYPE=whateveryouwant build". > > > > Then you'll soon see which packages are missing. Install them on the > > host system, and re-run, it'll work fine. > > It may well be that I am missing something incredibly obvious, and I > will be delighted if someone can point it out. > > I have checked out debian-installer, and I have these main directories: > chroot [EMAIL PROTECTED] tmp]# find debian-installer -type d -maxdepth 1 > debian-installer > debian-installer/CVS > debian-installer/anna > debian-installer/doc > debian-installer/build > debian-installer/kernel-image-di > debian-installer/kernel-splitter > debian-installer/libd-i > debian-installer/libdebian-installer > debian-installer/main-menu > debian-installer/retriever > debian-installer/rootskel > debian-installer/tools > debian-installer/utils > chroot [EMAIL PROTECTED] tmp]# > > What I want to do is to build all these packages, and then go on to > create bootable disks from the results. I expect at some point to have a > set of udebs. Yes, that's the idea. > Those directories come from a tarball I created from the checkout, which > I did under another account name. > > Here are the commands I have used most recently: > #!/bin/bash -xe > cd /tmp > rm -rf debian-installer > ls -oh debian-installer.tar.bz2 > tar xjf debian-installer.tar.bz2 > cd debian-installer/libdebian-installer > make all install > cd ../build/ > cp -p sources.list sources.list.local > fakeroot make TYPE=net build > > This failed with these messages: > Need to download : di-utils-shell rootskel anna main-menu cdebconf-udeb > udpkg busybox-udeb dash-udeb kernel-image-2.4.20-386-udeb choose-mirror > net-retriever netcfg-static netcfg-dhcp pump-udeb modutils-basic > ethdetect nic-modules-shared-2.4.20-386-udeb > socket-modules-2.4.20-386-udeb isa-pnp-modules-2.4.20-386-udeb > nic-modules-2.4.20-386-udeb > Reading Package Lists... > Building Dependency Tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > Sorry, but the following packages have unmet dependencies: > anna: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > ethdetect: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > Depends: libdiscover1 but it is not installable > main-menu: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > netcfg-dhcp: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > netcfg-static: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > pump-udeb: Depends: libpopt0 (>= 1.6.4) but 1.6.2-7 is to be installed > E: Sorry, broken packages > make: *** [net-get_udebs-stamp] Error 100 > chroot [EMAIL PROTECTED] root]# > > Now, I have actually built and installed libdebian-installer: > chroot [EMAIL PROTECTED] tmp]# ls /usr/lib/libdebian-installer.* > -rwxr-xr-x1 root root 9280 Mar 18 21:03 > /usr/lib/libdebian-installer.a > lrwxrwxrwx1 root root 28 Mar 18 21:03 > /usr/lib/libdebian-installer.so -> libdebian-installer.so.3.2.0 > lrwxrwxrwx1 root root 28 Mar 18 21:03 > /usr/lib/libdebian-installer.so.3 -> libdebian-installer.so.3.2.0 > -rwxr-xr-x1 root root15276 Mar 18 21:03 > /usr/lib/libdebian-installer.so.3.2.0 > chroot [EMAIL PROTECTED] tmp]# > > but because it didn't go through package manangement, it does not > satisfy the depenencies. You could change the apt-get command ran by the Makefile to get rid of the Dependancies check, but it would not be really clean. > While I could install the package from Sarge, it is actually the CVS > version I want to use and test, so it makes no sense to me to install > the older version. I did install the package from the sid repository. > I have not yet found any way to make any packages from this source, and > that is why I think something is missing. You can to to the "libdebian-installer" and run "dpkg-buildpackage" (you may need to install the dpkg-dev -from the sarge repository- package) and you should end with a .deb of libdebian-installer fresh from your CVS tree. Stéphane -- To UNSUBSCRIBE, emai
Re: Building d-i
[EMAIL PROTECTED] writes: > On Tue, 18 Mar 2003, Stephane Enten wrote: > >> On Tue, Mar 18, 2003 at 06:50:37AM +0800, [EMAIL PROTECTED] wrote: >> I've been able to build the floppy 'net' image without any trouble only >> by installing the needed packages on the host system (and removing the >> bogl stuff from the floppy tree), so I guess everything's there to build >> the package. >> >> If you want an easy way to find what's missing, just try to run the >> build process by entering the 'build' directory and run >> "make TYPE=whateveryouwant build". >> >> Then you'll soon see which packages are missing. Install them on the >> host system, and re-run, it'll work fine. > > It may well be that I am missing something incredibly obvious, and I > will be delighted if someone can point it out. > > I have checked out debian-installer, and I have these main directories: > chroot [EMAIL PROTECTED] tmp]# find debian-installer -type d -maxdepth 1 > debian-installer > debian-installer/CVS > debian-installer/anna > debian-installer/doc > debian-installer/build > debian-installer/kernel-image-di > debian-installer/kernel-splitter > debian-installer/libd-i > debian-installer/libdebian-installer > debian-installer/main-menu > debian-installer/retriever > debian-installer/rootskel > debian-installer/tools > debian-installer/utils > chroot [EMAIL PROTECTED] tmp]# > > What I want to do is to build all these packages, and then go on to > create bootable disks from the results. You do not need to do this. The whole idea of udeb packages is that they can reside in the archives, and you do not need to build them all individually, you can just download and install them into the build tree (actually, that is what build/Makefile does) > I expect at some point to have a set of udebs. If you really need to do this, you can build the individual udebs using dpkg-buildpackage, and copy them into build/localudebs/ All udebs which are found in that directory are not downloaded from the archives. Instead, the localudeb version is used. > Those directories come from a tarball I created from the checkout, which > I did under another account name. > > Here are the commands I have used most recently: > #!/bin/bash -xe > cd /tmp > rm -rf debian-installer > ls -oh debian-installer.tar.bz2 > tar xjf debian-installer.tar.bz2 > cd debian-installer/libdebian-installer > make all install > cd ../build/ > cp -p sources.list sources.list.local > fakeroot make TYPE=net build > > This failed with these messages: > Need to download : di-utils-shell rootskel anna main-menu cdebconf-udeb > udpkg busybox-udeb dash-udeb kernel-image-2.4.20-386-udeb choose-mirror > net-retriever netcfg-static netcfg-dhcp pump-udeb modutils-basic > ethdetect nic-modules-shared-2.4.20-386-udeb > socket-modules-2.4.20-386-udeb isa-pnp-modules-2.4.20-386-udeb > nic-modules-2.4.20-386-udeb > Reading Package Lists... > Building Dependency Tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > Sorry, but the following packages have unmet dependencies: > anna: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > ethdetect: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > Depends: libdiscover1 but it is not installable > main-menu: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > netcfg-dhcp: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > netcfg-static: Depends: libdebian-installer3 (>= 0.10) but it is not > installable > pump-udeb: Depends: libpopt0 (>= 1.6.4) but 1.6.2-7 is to be installed > E: Sorry, broken packages > make: *** [net-get_udebs-stamp] Error 100 > chroot [EMAIL PROTECTED] root]# > > Now, I have actually built and installed libdebian-installer: > chroot [EMAIL PROTECTED] tmp]# ls /usr/lib/libdebian-installer.* > -rwxr-xr-x1 root root 9280 Mar 18 21:03 > /usr/lib/libdebian-installer.a > lrwxrwxrwx1 root root 28 Mar 18 21:03 > /usr/lib/libdebian-installer.so -> libdebian-installer.so.3.2.0 > lrwxrwxrwx1 root root 28 Mar 18 21:03 > /usr/lib/libdebian-installer.so.3 -> libdebian-installer.so.3.2.0 > -rwxr-xr-x1 root root15276 Mar 18 21:03 > /usr/lib/libdebian-installer.so.3.2.0 > chroot [EMAIL PROTECTED] tmp]# > > but because it didn't go through package manangement, it does not > satisfy the depenencies. Exactly. If you know the reason already, why do you insist on doing the wrong thing? You should build libdebian-installer like this: cd debian-installer/libdebian-installer dpkg-buildpackage -rfakeroot dpkg -i ../libdebiaan-installer*.deb > While I could install the package from Sarge, it is actually the CVS > version I want to use an
Re: Building d-i
On Tue, Mar 18, 2003 at 02:55:41PM +0100, Stephane Enten wrote: > On Tue, Mar 18, 2003 at 09:23:00PM +0800, [EMAIL PROTECTED] wrote: > > > I have not yet found any way to make any packages from this source, and > > that is why I think something is missing. > > You can to to the "libdebian-installer" and run "dpkg-buildpackage" > (you may need to install the dpkg-dev -from the sarge repository- > package) and you should end with a .deb of libdebian-installer fresh > from your CVS tree. To clarify, that's the debian-installer/libdebian-installer source directory you had identified. The .deb will arrive in debian-installer, and you can use dpkg -i to install it so the package management system is aware of it. -- "The way the Romans made sure their bridges worked is what we should do with software engineers. They put the designer under the bridge, and then they marched over it." -- Lawrence Bernstein, Discover, Feb 2003 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[pcmcia-problem] kernel-image-2.4.20-bf2.4 -5
Hallo John, * John H. Robinson, IV [Sun, Mar 09 2003, 12:34:11AM]: > i have built the USB 2.0 modules in. i have also built the pcmcia > external modules. ... We have a problem: something is broken with the modules in the pcmcia-modules or with cardmgr. I think about reporting a grave bug against pcmcia-cs because of this: Mar 18 17:57:43 debian cardmgr[490]: executing: 'insmod /lib/modules/2.4.20-bf2. 4/pcmcia/orinoco_cs.o' Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_setup Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol hermes_struct_init Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_shutdown Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_reset Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_proc_dev_cleanup Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_interrupt Mar 18 17:57:43 debian cardmgr[490]: + /lib/modules/2.4.20-bf2.4/pcmcia/orinoco_ cs.o: unresolved symbol orinoco_proc_dev_init Mar 18 17:57:44 debian cardmgr[490]: insmod exited with status 1 Mar 18 17:57:45 debian cardmgr[490]: get dev info on socket 1 failed: Resource t I am not sure what to do know. I have just rebuilt the packages, same problem. I am running out of ideas, I checked the dependency chain detected by depmod and loaded the modules manually - cardmgr loads the modules in the correct order. This works as-is with 2.4.18-bf2.4 and fails with 2.4.20-bf2.4. Mar 11 02:00:50 debian cardmgr[2632]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter Mar 11 02:00:50 debian cardmgr[2632]: executing: 'modprobe hermes' Mar 11 02:00:51 debian kernel: hermes.c: 5 Apr 2002 David Gibson <[EMAIL PROTECTED] dropbear.id.au> Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco' Mar 11 02:00:51 debian kernel: orinoco.c 0.11b (David Gibson <[EMAIL PROTECTED] bear.id.au> and others) Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco_cs' Mar 11 02:00:51 debian kernel: orinoco_cs.c 0.11b (David Gibson <[EMAIL PROTECTED] ropbear.id.au> and others) vs. Mar 11 22:27:22 debian cardmgr[381]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter Mar 11 22:27:22 debian cardmgr[381]: executing: 'modprobe hermes' Mar 11 22:27:22 debian kernel: hermes.c: 4 Dec 2002 David Gibson <[EMAIL PROTECTED] dropbear.id.au> Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco' Mar 11 22:27:23 debian kernel: orinoco.c 0.13b (David Gibson <[EMAIL PROTECTED] bear.id.au> and others) Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco_cs' Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_shutdown Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_reset Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_proc_dev_cleanup Mar 11 22:27:24 debian cardmgr[381]: + /lib/modules/2.4.20-wolk4.0s-rc3/pcmcia/o rinoco_cs.o: unresolved symbol orinoco_proc_dev_init Gruss/Regards, Eduard. -- Es gibt einen neuen Aufkleber für die A-Klasse? "Ich bremse nicht für Elche!" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [pcmcia-problem] kernel-image-2.4.20-bf2.4 -5
Eduard Bloch <[EMAIL PROTECTED]> wrote: > We have a problem: something is broken with the modules in the > pcmcia-modules or with cardmgr. I think about reporting a grave bug > against pcmcia-cs because of this: The source of your problems is that there are two sets of modules named orinoco.o and hermes.o. Check under /lib/modules/2.4.20... You'll find that one resides under pcmcia, the other kernel/drivers/net/wireless. Unfortunately, modprobe is loading the wrong set of modules. Observe: > Mar 11 02:00:50 debian cardmgr[2632]: socket 1: Intersil PRISM2 11 Mbps ... > Mar 11 02:00:50 debian cardmgr[2632]: executing: 'modprobe hermes' > Mar 11 02:00:51 debian kernel: hermes.c: 5 Apr 2002 David Gibson ... > Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco' > Mar 11 02:00:51 debian kernel: orinoco.c 0.11b (David Gibson ... > Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco_cs' > Mar 11 02:00:51 debian kernel: orinoco_cs.c 0.11b (David Gibson ... Same version numbers (0.11b = 0.11b): Success > Mar 11 22:27:22 debian cardmgr[381]: socket 1: Intersil PRISM2 11 Mbps ... > Mar 11 22:27:22 debian cardmgr[381]: executing: 'modprobe hermes' > Mar 11 22:27:22 debian kernel: hermes.c: 4 Dec 2002 David Gibson ... > Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco' > Mar 11 22:27:23 debian kernel: orinoco.c 0.13b (David Gibson ... > Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco_cs' Different version numbers (0.13b != 0.11b): Failure The orinoco_cs module is version 0.11b, whereas the orinoco module is version 0.13b. Obviously, the kernel orinoco driver is being loaded instead of the driver from pcmcia-cs. The 2.4.20 kernel source (in the kernel-source package) has version 0.11b (I think that 2.4.18 also has this version), which is why this problem doesn't appear more frequently. What patches did you apply to this kernel? Where did the newer driver come from? One way to fix this would be to use insmod to explicitly load the correct drivers, or to delete the orinoco and hermes drivers under the kernel subdirectory and run depmod. The real problem is that there should not be two modules with the same name. - Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Kernel panic: No init found
On Tue, 18 Mar 2003, kuppermanfred wrote: Hi, i'm installing debian the third time now on my laptop from cd: cause of bad video-card i had to restart four times. cd boot prompt: bf24 vga=791 apm=on ended in a fading colormonitor and system hangs up: tried rescue cd boot prompt: rescbf24 vga=791 apm=on it starts penguin is drawn in all colors screen is prompted with messages and ends in Kernel panic: No init found That message is a result of some other error, typically because it was unable to mount the root filesystem. This in turn could arise because the kernel can't find your CD drive - note that the kernel itself is read in using BIOS calls. We need more of the preceding messages. -- Cheers John Summerfield Hello John i tried again with rescbf24 vga=791 apm=on root=/dev/hda1 it went trough up to the login prompt,. but i didn't even came so far to create teh root user. i' m still up to the install debian. i came so far to make the system bootable. I tried different install parameters, but only bf24 vga=791 apm=on worked, but ever time i like to make my laptop bootable it come to that the screen was black and startet to illuminating via different colors to white. input was not possible just reboot. can you see where there is a possibilty to install debian at all? cheers manfred -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Update floppy bug
Processing commands for [EMAIL PROTECTED]: > tags 184994 + pending Bug#184994: di-utils-generic: Floppy device is /dev/(null) There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#185014: cdebconf mangles strings with consecutive spaces
On Mon, Mar 17, 2003 at 10:09:44PM +0100, Martin Sjögren wrote: > mån 2003-03-17 klockan 21.20 skrev Denis Barbier: > > > Are they? db_subst foo/bar NAME "..." Will that be gobbled? > > > > With current implementation, yes. > > Then I think that should be changed too! A workaround is to replace spaces by 0xC2 0xA0 (no break space character in UTF-8 encoding). Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
CPQ ML530 + Smart Array 431
hey hey hey I am valiantly struggling with getting debian 3.0r1 onto a Compaq ML530 server which has a Smart Array 431 RAID controller (2+1) I have had Win2K and Redhat 7.x on this server in the past with no problems, but I would prefer to go with Debian if possible. I am currently running RH7.2 on an identical box. I have tried both the "vanilla" and "compact" boot CD's with similar results. After trawling the net I have learnt that the '431 uses CPQARRAY.O, which should already be compiled into the kernel. Unfortunately, the controller doesn't appear to be recognised, and I subsequently get a "No hard disk!" error when attempting to partition the drive. I have searched high and low for a driver disk but could only find Red Hat flavoured ones. I tried one of these but it wasn't recognised as a valid driver disk by Debian. SYSTEM DETAILS Compaq ProLiant ML530 1 x PIII XEON 1Ghz 1Gb RAM Compaq Smart Array 431 configured with 3 x 18.2Gb SCSI HDDs (RAID5) IDE CD-ROM Best regards Brett Glasson Salient Networks Pty Ltd Level 2, 4-10 Bridge Street Pymble NSW 2073 Phone (02) 9144 2622 Mobile(0412) 022982 Fax (02) 9144 7266 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CPQ ML530 + Smart Array 431
Hi, On Wed, Mar 19, 2003 at 10:35:25AM +1100, Brett Glasson wrote: > I have tried both the "vanilla" and "compact" boot CD's with similar > results. After trawling the net I have learnt that the '431 uses > CPQARRAY.O, which should already be compiled into the kernel. > > Unfortunately, the controller doesn't appear to be recognised, and I > subsequently get a "No hard disk!" error when attempting to partition > the drive. Try the bf2.4 flavour; it contains a 2.4 kernel that to my knowledge contains cpqarray.o. Cheers, Emile. -- E-Advies - Emile van Bergen [EMAIL PROTECTED] tel. +31 (0)70 3906153 http://www.e-advies.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building d-i
On Tue, 18 Mar 2003, Stephane Enten wrote: > > You could change the apt-get command ran by the Makefile to get rid of > the Dependancies check, but it would not be really clean. I'm not yet that desperate;-) > > While I could install the package from Sarge, it is actually the CVS > > version I want to use and test, so it makes no sense to me to install > > the older version. > > I did install the package from the sid repository. > > > I have not yet found any way to make any packages from this source, and > > that is why I think something is missing. > > You can to to the "libdebian-installer" and run "dpkg-buildpackage" > (you may need to install the dpkg-dev -from the sarge repository- > package) and you should end with a .deb of libdebian-installer fresh > from your CVS tree. Ah. This is one of the missing links. I have done these things: 1. Cloned my Woody chroot environment, cp -a woody sarge, and in Sarge 2. Edited /etc/apt/sources.list to point to a Sarge mirror 3. apt-get update 4. apt-get dist-upgrade 5. Fixed a problem that's NYB, but caused some grief;-(. 6. apt-get -y install d-shlibs I can now build libdebian-installer3. Thankyou Stephane. I now get some more build deps of which apt-get install can't find libdebconf1. I can find the relevant debs (actually two versions) on a convient mirror, but what's the proper incantation to get it? In source.list I have: deb http://cc.computerdatasafe.com.au/debian-sarge/ sarge main deb http://ftp.wa.au.debian.org/debian/ sarge main deb http://non-us.debian.org/debian-non-US sarge/non-US main deb-src http://non-us.debian.org/debian-non-US sarge/non-US main deb http://security.debian.org/ sarge/updates main deb-src http://ftp.wa.au.debian.org/debian/ unstable main deb-src http://ftp.wa.au.debian.org/debian/ stable main -- Cheers John Summerfield Please, no off-list mail at all at all. This address accepts mail only from Debian lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building d-i
On Tue, 18 Mar 2003, Chris Tillman wrote: > On Tue, Mar 18, 2003 at 02:55:41PM +0100, Stephane Enten wrote: > > On Tue, Mar 18, 2003 at 09:23:00PM +0800, [EMAIL PROTECTED] wrote: > > > > > I have not yet found any way to make any packages from this source, and > > > that is why I think something is missing. > > > > You can to to the "libdebian-installer" and run "dpkg-buildpackage" > > (you may need to install the dpkg-dev -from the sarge repository- > > package) and you should end with a .deb of libdebian-installer fresh > > from your CVS tree. > > To clarify, that's the debian-installer/libdebian-installer > source directory you had identified. The .deb will arrive in > debian-installer, and you can use dpkg -i to install it so > the package management system is aware of it. Thanks Chris. I feel I'm making progress now. -- Cheers John Summerfield Please, no off-list mail at all at all. This address accepts mail only from Debian lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building d-i
On Tue, 18 Mar 2003, Mario Lang wrote: > > What I want to do is to build all these packages, and then go on to > > create bootable disks from the results. > > You do not need to do this. The whole idea of udeb packages > is that they can reside in the archives, and you do not need to build > them all individually, you can just download and install them into > the build tree (actually, that is what build/Makefile does) What I want to do is test the latest version of d-i. Downloading udebs defeats that purpose. I can get the source from cvs as soon as someone's checked in a change, and that is what I want to do, maybe more than once a day at times. > > I expect at some point to have a set of udebs. > > If you really need to do this, you can build the individual > udebs using dpkg-buildpackage, and copy them into > build/localudebs/ > > All udebs which are found in that directory are not downloaded > from the archives. Instead, the localudeb version is used. > > > > > but because it didn't go through package manangement, it does not > > satisfy the depenencies. > Exactly. If you know the reason already, why do you insist on doing > the wrong thing? I have been taking all the advice offered that made any sense at all. Some, such as "Install the package from ..." seemed wrong and so I queried it. I suspected that would not work, the easiest clarification was to try it. In the case of "Install the package from ...," the advice seemed to me likely to be actually harmful to my objectives, so I didn't try it. > > You should build libdebian-installer like this: > > cd debian-installer/libdebian-installer > dpkg-buildpackage -rfakeroot > dpkg -i ../libdebiaan-installer*.deb Thanks for that. I've already accomplished that, following Stephane's advice. > > While I could install the package from Sarge, it is actually the CVS > > version I want to use and test, so it makes no sense to me to install > > the older version. > > So build the package, and dpkg -i that. > > > I have not yet found any way to make any packages from this source, and > > that is why I think something is missing. > > This is why Tollef asked you to read the Developers reference. That is like answering the question, "Tell me about Lazarus?" with "Read the Bible." How much more quickly would you find about Lazarus if the answer was, "The story is in John 11?" I know there's a lot in The Developers Reference that's not relevant to my immediate needs, and I don't know enough to know what to look for. I do know that I've been reading computer manuals for over thirty years, I've read them by the tonne. I also know they're often not the best way of learning stuff;-). Tollef, don't take any offense. I know from my own experience, giving useful advice can be difficult, and this has been very frustrating. -- Cheers John Summerfield Please, no off-list mail at all at all. This address accepts mail only from Debian lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CPQ ML530 + Smart Array 431
On Wed, 19 Mar 2003, Emile van Bergen wrote: > Hi, > > On Wed, Mar 19, 2003 at 10:35:25AM +1100, Brett Glasson wrote: > > > I have tried both the "vanilla" and "compact" boot CD's with similar > > results. After trawling the net I have learnt that the '431 uses > > CPQARRAY.O, which should already be compiled into the kernel. > > > > Unfortunately, the controller doesn't appear to be recognised, and I > > subsequently get a "No hard disk!" error when attempting to partition > > the drive. > > Try the bf2.4 flavour; it contains a 2.4 kernel that to my knowledge > contains cpqarray.o. And take care that you actually get a 2.4 kernel installed too. I have just done an install using bf24 and discovered I got a 2.2.20 kernel installed. *I* would have a boot disk made on RHL to hand "just in case," and maybe a rescue CD (you can get a good one from ftp.redhat.de) as well. -- Cheers John Summerfield Please, no off-list mail at all at all. This address accepts mail only from Debian lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
