Adam Di Carlo wrote:
>
> Glenn McGrath <[EMAIL PROTECTED]> writes:
>
> > Adam Di Carlo wrote:
> > >
> > > Glenn McGrath <[EMAIL PROTECTED]> writes:
> > >
> > > > I just tested the 2.2.17-ide and 2.2.18-ide kernels and they bot
Joey Hess wrote:
>
> I've been thinking about how the kernel and kernel modules stuff could
> work.
>
> The requirements:
> * The modules will be split amoung a number of udebs, and some of them
> might be on a remote mirror and be downloaded during the installation
> process.
Just to clar
Adam Di Carlo wrote:
>
> Maybe you guys could clue me in on the partitioner you are going to
> use. You talk about using libparted or libfdisk. Does the libfdisk
> mean the libfdisk in the boot-floppies CVS area? Does that mean it
> has to be packaged separately?
>
> I'm curious because there
Adam Di Carlo wrote:
>
> Glenn McGrath <[EMAIL PROTECTED]> writes:
>
> > I just tested the 2.2.17-ide and 2.2.18-ide kernels and they both detect
> > a HPT370 chip
>
> Where does this lead us? Are you saying the HPT370 problems should be
> fixed as of 2.2.1
Joey Hess wrote:
>
> In particular, cdebconf, ddetect, netcfg, and maybe pcidetect seem to be
> fairly far along, and are not in the archive. If anyone needs a sponsor,
> I would be glad to help.
>
Im not sure about the future of pcidetect, ddetect looks to do a better
job, isa cards will have
I just tested the 2.2.17-ide and 2.2.18-ide kernels and they both detect
a HPT370 chip
Glenn
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Karl Hammar wrote:
>
> Understood and agreed.
> So we won't file bug reports about it?
>
> Regards,
> /Karl
>
I assume the next release will use the kernel-image-2.2.18-ide image
(rather than pre18), maybe you could check if this image recognises your
card.
Im not sure how to check which patc
Adam Di Carlo wrote:
>
> Karl Hammar <[EMAIL PROTECTED]> writes:
>
> > I assume you have two ordinary ide controllers on your motherboard.
> > In that case you can:
> > connect disc on std. ide
> > install debian
> > download lk-2.2.18 and latest ide-patches
> > roll your own kernel and inst
Adam Di Carlo wrote:
>
> > This patch should be right i hope
>
> Ok -- I think you should go ahead and apply this in CVS, ok?
>
Patch has been committed.
Glenn
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > Actually looks like i was wrong... i did a search a found a snippit of
> > code that refered to a default 1/2 physical memory limit, but looks like
> > the patch wasnt applied.
> > I just made a ramdisk and did dd if=
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > Well, if we need more than 4MB of space in /usr then it will mean that
> > we can only install to machines with more than 8MB, which effictively
> > means you need 16MB to install debian.
>
> BTW, where is the 1/2 o
Anthony Towns wrote:
>
> On Thu, Jan 11, 2001 at 11:19:35AM +1100, Glenn McGrath wrote:
> > Well, if we need more than 4MB of space in /usr then it will mean that
> > we can only install to machines with more than 8MB, which effictively
> > means you need 16MB to instal
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > c) udebs get installer to /usr/local, which can be mounted on a seperate
> > area that has no limiting space constraints, loopfs would be ideal.
> > /usr/local can be unmounted and remounted without killing the system
>
&
Adam Di Carlo wrote:
>
> Glenn McGrath <[EMAIL PROTECTED]> writes:
>
> > I am unsure about the priority with solaris partitions so i just put
> > them at the end, i guess i really should have checked the linux kernel
> > source, as i dont have any other info o
First a disclamer, this idea popped into my head 5 minutes ago so maybe
im overlooking something.
There is a bit of a catch-22 at work here.
1) We want to have as few core components as possible, to minimise space
requirements
2) The more non-core components we have the more temperary space we
David Whedon wrote:
>
> > I haven't been able to do concrete work yet. But I'm still interested in it,
> > so we can work together.
> great.
>
> >
> > > I've also seen conflicting info on how it should probably be done. I've seen
> > > libparted and libfdisk suggested, I'm not sure that people
Just to create more email traffic, heres a better diff
diff -r -d -U 3 ./boot-floppies.orig/utilities/libfdisk/partbl_msdos.c
./boot-floppies/utilities/libfdisk/partbl_msdos.c
--- ./boot-floppies.orig/utilities/libfdisk/partbl_msdos.c Sat May 6 01:44:26
2000
+++ ./boot-floppies/utilities/
I forgot the patch on the previous email
diff -r -U 3 boot-floppies/utilities/libfdisk/partbl_msdos.c
boot-floppies.orig/utilities/libfdisk/partbl_msdos.c
--- boot-floppies/utilities/libfdisk/partbl_msdos.c Wed Jan 10 19:33:43 2001
+++ boot-floppies.orig/utilities/libfdisk/partbl_msdos.c
Attached is a patch that changes libfdisk's behaviour.
Currently libfdisk adds extended partitions as they are found.
e.g. if hda1 contains an extended partition, be that a normal exteneded
partition a BSD partition or a SOLARIS extended partition then whatever
type it is it will appear before h
Joey Hess wrote:
>
> Anthony Towns wrote:
> > * devices stuff. difficult. would go away with devfs on b-f's :)
>
> Maybe MAKEDEV should be required to make that stuff on installation if
> it doesn't exist? Or does it need to exist earlier?
>
I made up a libmakedev a few weeks back when i
This is the code i have so far that works out a list of used and unused
partitions, the heirarchy thing is working but only to two levels.
I made a md0 array comprised of /dev/hdd1 /dev/hdd2 /dev/hdd3 /dev/hdd4
(silly i know), and it recognised that md0, hdd1 - hdd4 were taken, but
it didnt reco
David Whedon wrote:
>
> >
> > sounds nice. btw, is there any standard here on the data structures?
> > would it be possible to agree on this since we're using C, and data
> > structure codes tend to be replicated over and over again? i'd be
>
> I'm not sure what you mean by standard for data str
David Whedon wrote:
>
> I've started to look into doing the disk partitioner.
>
> Looking through the boot archives it looks like Eray indicated some interest, I
> don't want to step on toes, Eray, let me know if you are still working on it, we
> can work together, o ryou can have it, just let m
"C. Paul" wrote:
>
> Hi, ...
> one moment - please.
Do you understand what i think the problem is, that libfdisk can see
that your hda2 contains 4 internal partitions, and lists then starting
at hda5, then your extended partitions from hda9 - hda15. Your kernel
doesnt understand that hda2 contai
Adam Di Carlo wrote:
>
> Glenn McGrath <[EMAIL PROTECTED]> writes:
>
> > What i really need you to do is compile a kernel with BSD partition
> > support,
>
> Better yet, use the kernel-image-2.2.18pre21 in Potato, which is also
> the kernel used in the van
> debbi:/usr/src/boot-floppies/utilities/libfdisk# ./testing
> /dev/hda: /dev/hda1, /dev/hda2, /dev/hda5, /dev/hda6, /dev/hda7, /dev/hda8,
>/dev/hda3, /dev/hda4, >/dev/hda9, /dev/hda10, /dev/hda11, /dev/hda12, /dev/hda13,
>/dev/hda14, /dev/hda15,
> /dev/hda1 (DOS 16-bit FAT >=32M), /dev/hda2 (BS
"Kenneth G. Kastella" wrote:
>
> I am trying to install Debian Linux on an old 33 MHz, 486 Gateway,
> 16 MB RAM, ATAPI cd-rom. I got Linux version 2.2 on 3 cd-roms
> from Linux Central. I copied rescue.bin, root.bin, driver-1.bin, driver-
> 2.bin, driver-3.bin and driver-4.bin to 5 1/4" floppie
Chris Paul wrote:
>
> Hi Adam,
> it took me quite a few days to `find ..` your "flavours" in a path requiring 70
>chars ... ;-)
>
> There was no vanilla, but the test results of the rest looks really interesting.
>
> > ... I need to know what "flavor" you were booting from...
> So sit down, ..
Thom May wrote:
>
> Folks.
> Much of this is probably repeating what has already been said,
> but here goes.
> I, either on line or in real life, continually say to people who
> ask me which distribution of linux to use, "use debian". and
> they, routinely, say "but the installer is terrifying, a
im starting to get into the partitioning side of of things.
Ive started with this small routine that parses /proc/mounts into
debconf. I figure ill do one that parses /proc/partitions and then one
to get known filesystems. With those three lots of information in
debconf format and mount functions
Attached is some new memdetect code, it uses cdebconf, it doesnt use
libdetect or anything as its pretty simple to detect memory.
Its only a few KB, so its probably best to roll this code in with
something else.
We will need to detect memory to determine how much space we have for
ramfs, or ramd
Erik Andersen wrote:
>
> Having carefully looked over nano-tiny ('apt-get install nano-tiny' for the
> curious) I propose we immediately throw ae out of the boot-floppies and use
> nano-tiny instead. It is already linked vs slang so there are no library
> problems. It _is slightly_ bigger. On
Yea, i think thats the way to go.
Important ddetect modules
ethdetect
mdmdetect
diskdetect
cddetect
cpudetect and memdetect can be done in a few lines of code seperately,
so they probably dont warrant doing via libdetect.
Also if we do a seperate libisapnp it may be smaller that i stated below
Adam Di Carlo wrote:
>
> Glenn, you sent this followup to the wrong place. Resending.
>
> Glenn McGrath <[EMAIL PROTECTED]> writes:
>
> > Acording to www.linux-ide.org hpt370 should be supported under the 2.2
> > series fo kernels, the first patch i s
Anthony Towns wrote:
>
> On Sat, Dec 23, 2000 at 09:25:17AM -0800, Joey Hess wrote:
> > Gergely Risko wrote:
> > > I made an udeb for lilo. You can find the patch for the unstable lilo
> > > in bug 80390.
> > Why do we need a lilo udeb?
>
> We need lilo on a rescue disk, at least...
>
> Cheers,
Randolph Chung wrote:
>
> > 2. Look at this pretty failure mode. Looks like it
> >doesn't work if not run in / -- should be easy to fix of course.
> > # pwd
> > /usr/lib/debian-installer/retriever
> > # /usr/share/debconf/frontend wget-retriever
> > Cannot load database module
Jon Branch wrote:
>
> Hi Alexander
>
> Sorry no solution from me. I'm faced with a near identical problem using the HPT 370
>on-board controller with a 2theMax BX7 +100 motherboard (actually with five of them).
>So I'll be interested to see the solution if/when you get one.
>
> Regards
>
I
Debian Bug Tracking System wrote:
>
> Processing commands for [EMAIL PROTECTED]:
>
> > reassign 79459 boot-floppies
> Bug#79459: UDMA66/HPT370 boot problem
> Bug reassigned from package `disks-i386' to `boot-floppies'.
>
> > --
> Stopping processing here.
>
> Please contact me if you need assi
Daniel Jacobowitz wrote:
>
> I've begun designing a BOGL based frontend for cdebconf. I've not actually
> got anything useful yet, but I plan to take the project home with me over
> break; I'll see how it goes.
>
> In order to do this, though, I need to separate BOGL out from boot-floppies.
> B
Joey Hess wrote:
>
> Tollef Fog Heen wrote:
> > Another possibility which imho is the best is to use ramfs.
>
> Thanks for reminding me -- the docs were just out of date, Glenn pointed
> ramfs out to me a while ago, and it does seem to be the best choice.
> Only concern is it makes us dependant
Gergely Risko wrote:
>
> Hello!
>
> > - {lilo,grub} installer [UNCLAIMED]
> > Not started. Sets up {lilo,grub}.
> I can claim this one. I wrote a letter before about a nice boot manager,
> but nobody replied :(
> But I can wrote the debconf things for lilo (and grub, and
"Eray Ozkural (exa)" wrote:
>
> Hi,
>
> I'd like to take the disk partitioner UI. How should I proceed?
> (I still don't have a debian account since my AM is kind of busy
> and I'm at tasks & skills step)
>
> Thanks,
>
I think what we need for a disk partitioner is to have some code that
Linked against static libisapnp.a
20k cddetect
20k cpudetect
20k diskdetect
20k ethdetect
28k mdmdetect
20k memdetect
128ktotal
Linked agianst a libisapnp.so i hacked together.
8.0kcddetect
4.0kcpudetect
4.0kdiskdetect
8.0kethdetect
12k mdmdetect
4
Erik Andersen wrote:
>
> On Thu Dec 07, 2000 at 01:02:26PM -0800, Joey Hess wrote:
> > > Log message:
> > > busybox breaks udpkg
> >
> > An update to that, I thought the busybox .udeb was breaking udpkg, but
> > it was actually that udpkg does not work with busybox ar, which was in
> > my path.
>
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > If all the users hardware is supported by the kernel, then it doesnt
> > need any drivers to support the hardware, hardware detection programs
> > will still show what kernel modules are needed to support the hardware,
Anthony Towns wrote:
>
> On Tue, Nov 28, 2000 at 03:39:23PM +1100, Glenn McGrath wrote:
> > Not as easy as it should be, i thought another goal was going to be
> > elimination of base.tar.gz, but we arent allowed to use normal debs to
> > build the base,
>
> I th
Anthony Towns wrote:
>
> On Mon, Nov 27, 2000 at 07:55:59PM -0800, Joey Hess wrote:
>
> (Some comments, take them how you like)
>
> > We need a retreiver controller, but it does *not* need to look like apt.
> > I'm mostly concerned that we don't know how the retreiver controller is
> > supposed
Randolph Chung wrote:
>
> I was wondering if anyone is interested in arranging a time to hold a
> debian-installer design brainstorming session or such on irc
> (#debian-boot on irc.debian.org). If we do something like Dec12 midnight UTC
> will people find this useful?
>
> randolph
yea, i think
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > The way i see it, a key feature of the new installer is that packaging
> > is much more tightly integrated.
> >
> > There are really 3 levels of abstraction for package managment(ignoring
> > debconf), dpkg-deb
Randolph Chung wrote:
>
> > Ive been working on a uapt-get.
> >
> > Currently status is that it can process //etc/apt/source.list and fetch
> > the Packages.gz and Source.gz files by calling wget, then to merge the
> > package files i am calling "dpkg --merge-avail " to
> > generate a correct //v
Ive been working on a uapt-get.
Currently status is that it can process //etc/apt/source.list and fetch
the Packages.gz and Source.gz files by calling wget, then to merge the
package files i am calling "dpkg --merge-avail " to
generate a correct //var/lib/dpkg/available file.
To do the equivvale
If all the users hardware is supported by the kernel, then it doesnt
need any drivers to support the hardware, hardware detection programs
will still show what kernel modules are needed to support the hardware,
information which is useless in this case.
We could just try and fetch and load the mo
Im a bit hazzy about the role and requirements of a shell in the
installer.
My understanding is that shell commands may be needed by some core
components,
udpkg calls ar, tar, gz (and rm if my patch gets reversed), and also
needs to be able to handle postinsts.
Postinst area bit of a grey area
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > Ive been thinking about hardware detection. I think hardware detection
> > should be a dependency on the fetch method it applies to.
> >
> > e.g. the http/ftp/nfs retriever should depend on network and modem
> >
Joey Hess wrote:
> Glenn McGrath wrote:
> > I guess the card names are handy for the user if all doesnt go to plan,
> > i just left them out because the program didnt _need_ them, and they
> > take the most space.
>
> That's true, it is nice to be able to look at
cdebconf will be a core component of the woody installer, and if
cdebconf works the same way as debconf then it needs shell scripts to
work from.
So the way it is looking we will need a shell to be a core component
wont we ?
Glenn
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Glenn McGrath wrote:
>
> This may be slightly offtopic, but anyway..
>
> The linux kernel has internal code to do gunzip, if there was a kernel
> module that could provide access to the internal gunzip code from
> userland then it would provide an almost free gunzip as f
This may be slightly offtopic, but anyway..
The linux kernel has internal code to do gunzip, if there was a kernel
module that could provide access to the internal gunzip code from
userland then it would provide an almost free gunzip as far as space
goes.
Is this a good/bad idea ?
Glenn
--
T
David Whedon wrote:
>
> Hi,
>
> I made a new version of ddetect with a few changes, even if we don't
> go the libdetect way it was instructive to figure out how to make
> multiple .udebs conviennently.
>
> I'm now generating 2 udebs which each provide the virtual package
> [sound|ethernet]-card
David Whedon wrote:
>
> > Splitting detection up like this seems to me to be the most space
> > efficient way of doing it as well.
> agreed.
>
> >
> > Yesterday i started hacking together a small program that uses libpci to
> > detect the required ethernet kernel modules, it is attached.
>
> I
How are multiple retrievers going to be handled ?
I think he default/initial retriever should be the same medium as was
booted from.
e.g. if you boot from a floppy, then the floppy should come with a
working floppy retriever, if you boot from cd it should have enough to
retrieve from cd.
This wa
Claudio Gamberini wrote:
>
> hi, I'm Claudio from Italy,
> I have as problem for installing Linux, the boot don't found hard disk,
> my hard disk is an EIDE IBM 30 Gb ATA100.
> Also the Bios don't found it but windows run correctly.
> How i have to do for installing Linux in the system ( found th
Robert Young wrote:
>
> Hi,
> Corel has created a modular detection system which detects
> system
> hardware by probing what the kernel has found and by looking for
> hardware itself. We are in the finishing stage and will be releasing it
> to the open source community shortly.
>
>
David Whedon wrote:
> >
> > Yesterday i started hacking together a small program that uses libpci to
> > detect the required ethernet kernel modules, it is attached.
>
> I spent some time on a similar program that uses lib detect It can be
> found at (still alpha, meant to generate discussion):
>
Ive been thinking about hardware detection. I think hardware detection
should be a dependency on the fetch method it applies to.
e.g. the http/ftp/nfs retriever should depend on network and modem
hardware detection.
This way, if a network retriever is to be used, the hardware detection
component
Junichi Uekawa wrote:
>
> In Sun, 05 Nov 2000 23:14:16 +1100 Glenn McGrath <[EMAIL PROTECTED]> cum
>veritate scripsit :
>
> > > > I understand how msdos partition tables work now, its just a bunch of
> > > > ugly hacks to make use o
Goswin Brederlow wrote:
>
> Glenn McGrath <[EMAIL PROTECTED]> writes:
>
> > I understand how msdos partition tables work now, its just a bunch of
> > ugly hacks to make use of legacy structures that are long obsolete.
> >
> > msdos partitions need
Vaidhyanathan Mayilrangam wrote:
>
> On Wed, Nov 01, 2000 at 10:30:33PM -0800, Joey Hess wrote:
> > Vaidhyanathan Mayilrangam wrote:
> > > > - kernel module udebs [UNCLAIMED]
> > > > Not started. We will need various sets of kernel modules;
> > > > one such set is NIC driver
David Whedon wrote:
>
> newlib is a replacement for libc used on embedded systems. Perhpas the
> small footprint would be good for the installer. I searched the
> archive for references to using cygnus's newlib for the installer and
> didn't find anything. Either it hasn't been considered, or t
> - retreiver control program [UNCLAIMED]
> Not started. Sort of like apt, except tons dumber, this
> uses retreiver(s) to download Packages files and then udebs,
> and calls udpkg to install them.
> - http retreiver [UNCLAMED]
>
Daniel Jacobowitz wrote:
>
> On Wed, Nov 01, 2000 at 08:11:52PM -0800, Joey Hess wrote:
> > - disk partitioner [UNCLAIMED]
> > Not started. Some kind of a UI to let the user partition their
> > disks and decide what the partitions are used for.
>
> I'd kind of
Bastien CAZENAVE wrote:
>
> Hi,
> Maybe you guys from debian-boot could know about this...
>
> While trying to make a CompactFlash IDE SanDisk SDCFB 48 bootable, I
> experienced a problem with fdisk:
> when I wrote the new partition table to disk, erasing the old DOS/FAT16
> one shipped with the
I understand how msdos partition tables work now, its just a bunch of
ugly hacks to make use of legacy structures that are long obsolete.
msdos partitions need to be supported for machines that need microsoft
compatability (and other OS's ?), but i think that we should provided
users the ability
Adam Di Carlo wrote:
>
> "Antonio-M. Corbi Bellot" <[EMAIL PROTECTED]> writes:
>
> > I have to install Debian 2.2 on an ASUS A7V motherboard 'loaded' with an
> > UDMA100 Promise chip and a hard-disk attached to it, no other hard disk.
> >
> > I read somewhere that UDMA100 was backward compatible
Joey Hess wrote:
> Or don't use ".udeb" as the filename extention for debian-installer
> modules. Which doogie says he will flame me for, so please go ahead
> doogie and tell me why just using ".deb" is such a terrible idea.
>
What about having a subsection for installer modules, that way it wo
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > My personal opinion is that Joey is trying to make a compromise by
> > having a seperate area for installer packages, but as far as i know the
> > installer team has no idea whatsoever if or when there will be a
> >
Roland Bauerschmidt wrote:
>
> On Mon, Oct 23, 2000 at 10:35:37PM -0700, Joey Hess wrote:
> > The binary packages (installer modules) will not be going into
> > the main/binary-foo directories, and will not be in the Packages files or
> > anything, so we are going to feel free to ignore policy in
tommorow, i guess i will put it
in /debian-installer/tools
Glenn
#!/bin/sh
# Partitial implementation of debians apt-get command
# GPL Glenn McGrath
# Shell commands used
#
# BUGS/LIMITATIONS
# update: always fetches rather than checking if the file to download is newer
# doesnt fetch
"Karl M. Hegbloom" wrote:
>
> What exists in the way of shared calendars we can utilize to help
> co-ordinate our efforts? Work schedules, IRC meetings, video phone
> conferences, whatever we decide?
>
What about plain old ICQ. could be usefull for some situations
I am bug1 UIN 3210560
"Karl M. Hegbloom" wrote:
>
> > "Adam" == Adam Di Carlo <[EMAIL PROTECTED]> writes:
>
> Adam> Joey Hess <[EMAIL PROTECTED]> writes:
> >> [ ... ]
> >> all the disgusting stuff basedisks.sh has to do in the boot-floppies to
> >> create a debian base system. A lot of packages ne
Erik Andersen wrote:
>
> On Fri Oct 20, 2000 at 02:21:34PM -0700, Karl M. Hegbloom wrote:
> > > "Erik" == Erik Andersen <[EMAIL PROTECTED]> writes:
> >
> > Erik> It will fit. Oh, yes. It will. ;-)
> >
> > Erik> I'm sure it can be done. Though we may need to switch to libc5 or
>uc
"Karl M. Hegbloom" wrote:
>
> > "Goswin" == Goswin Brederlow <[EMAIL PROTECTED]>
>writes:
>
> Goswin> Hartmut Koptein <[EMAIL PROTECTED]> writes:
> >> > Let's add one more bullet point for the new installer--namely,
> >> > alternative root filesystem support. I and my colleague
Im currently working on a shell script to do provide some basic apt-get
functionality. I have it so it can do an apt-get update, am working on
apt-get install.
It uses wget to do download, and will just call dpkg to do the actual
install.
I will upload something to CVS in a day or so.
Glenn
Antti-Juhani Kaijanaho wrote:
>
> On 20001018T134523+1100, Glenn McGrath wrote:
> > A busybox package was previously rejected because it was uninstable on
> > an existing system.
>
> This is not the whole story. The package did not contain several
> important file
Timshel Knoll wrote:
> > Ive had a look at partitioning with parted, i made a small program that
> > showed partition and drive details, and chopped up libparted manually to
> > only include functions needed, and that was relatively only 20 KB or so,
> > but when i started adding extra functionali
Randolph Chung wrote:
>
> > * udebconf ??
>
> I was hoping to have gotten some code feedback and/or volunteers to help
> me work on this :-) i will continue to work on this as time permits,
> though i am spread kinda thin atm.
>
I had a superficial look at it, but didnt really come to grips wi
Joey Hess wrote:
>
> Daniel Jacobowitz wrote:
> > For network installs, we could theoretically dispense with IDE and SCSI
> > entirely. This is probably not generally useful, though, since we'd
> > still need to support installing off CD and hard disk.
>
> Nah -- see, once the network is up, sp
Joey Hess wrote:
> * main-menu is 90% done, and will be finished by the end of this week
> * udpkg is 97% done
> * udebconf ??
Randolph has started this,
http://auric.debian.org/~tausq/cdebconf-0.10.tgz
> * modules to set up network, partition hard disk, download modules, set
> up swap, form
Joey Hess wrote:
>
> Glenn McGrath wrote:
> > For the installer we could share information of detected hardware via
> > debconf, but i guess it should be stored on the filesystem somewhere.
>
> Why? I don't see anything wrong with just storing it in the debconf
I would like to see the busybox package in the main debian archive.
Busxybox is a multicall binary that is targeted at embedded systems, it
is the basis of the debian installer.
A busybox package was previously rejected because it was uninstable on
an existing system. This was because busybox wou
I am a little worried about how we are going to handle all the kernel
modules required for installing.
Where are all the ide, scsi and net drivers going to reisde ?
The user will need drivers to suit the fetch method on the actual boot
media, that way they can fetch other install or kernel modul
Vaidhyanathan Mayilrangam wrote:
>
> Hi All,
>
> I met with joeyh during ALS and offered to work on kernel for the boot floppies.
> I got the kernel down to 355 KB.. From what I understood from joeyh, the new
> installer will be just the kernel and the network drivers.. However, one of the
> iss
Vaidhyanathan Mayilrangam wrote:
>
> Hi ,
>
> I wonder if we would be having bzip2 or gzip on the boot floppies.. All the
> network modules compiled takes about 1.3M, but compresssed with bzip2 , needs
> only 435K.. The size of bzip2 + libbz2.so is about 85K.. We can probably do the
> same with
Vaidhyanathan Mayilrangam wrote:
>
> Hi All,
>
> I met with joeyh during ALS and offered to work on kernel for the boot floppies.
> I got the kernel down to 355 KB.. From what I understood from joeyh, the new
> installer will be just the kernel and the network drivers.. However, one of the
> iss
Adam Di Carlo wrote:
>
> Erik Andersen <[EMAIL PROTECTED]> writes:
>
> > I would prefer using a busybox package. Otherwise, I will again end
> > up with the painful task of keeping two CVS trees in sync... The
> > busybox package has been ready to upload for months, but thus far
> > noone has
Adam Di Carlo wrote:
>
> [I'm re-sending this due to the subject line damage -- this is a very
> important issue.]
>
> Talking to the release manager, Anthony Towns, in IRC, I learned it is
> his current plan to freeze woody early in January 2001.
>
> I think this is a laudable goal, but unfor
Randolph Chung wrote:
>
> > nl is from textutils, it isnt in busybox, but it wouldnt be hard to do
> > all it does is number the text lines so head and tail work, there is
>
> ah, you can also do cat file | grep -n "" -
>
> > I dont have cvs upload access at debian, i could upload it to busyb
Randolph Chung wrote:
>
> In reference to a message from Glenn McGrath, dated Oct 05:
> > Attached is a little shell script i wrote that does most of what the
> > real dpkg-deb does.
>
> very cool!
>
> a few questions:
> what's control and nl? does it w
I was just looking at parted, and it does some automatic hardware
detection of storage devices, looks like there could end up being a few
different hardware detection programs used for differetn things in
woody.
For the installer we could share information of detected hardware via
debconf, but i
Attached is a little shell script i wrote that does most of what the
real dpkg-deb does.
Glenn
#!/bin/sh
# Shell commands used, ar, tar, zcat, head, tail, cut, nl, sed
#
# TODO
# -I unsupported
# clean it up
# BUGS
# -f option displays an extra space at the start
packageName=$2
arg3=$3
arFi
201 - 300 of 334 matches
Mail list logo
