On Fri 21 Jul, bug1 wrote:
> So, on your strongarm you only have 4MB of permenant storage ?
> What sort of applications do you use on it?
That was just an example, but not an extreme one. This would be a
single-purpose unit with just a kernel and initrd on the flash disk/ROM
which get uncompress
Wookey wrote:
>
> Some of you may be aware that emdebian.org has been created to generate a
> debian-allied embedded linux distibution. My area of interest is ARM
> devices, and a lot of the potential platforms are handheld/embdedded
> devices (4Mb flash, 32Mb RAM, 100Mhz Strongarm, LCD+touchscre
I've just been catching up on my mailing lists and reading the
intersting discussion about future direction of the installer for woody
(ie sorry this response is less than timely). Some good points are being
made. I don't feel I know the process well enough to comment on the
specifics but there ar
Wookey wrote:
>
> On Sat 17 Jun, bug1 wrote:
>
> > I think Ben meant msdos partition *tables*, ie parted doesnt support
> > partitioning schemes that arent native to i386 architecture.
>
> > This got me wondering , exactly what other types of partition tables
> > would need to be supported by p
> > disadvantages:
> >ext3 isn't a real journalingfs or better: it hasen't the ful
> > power. Forget ext3.
>
> Do you mean "it doesn't do metadata-only journaling"? Perhaps you
> mean "it's not finished".
Yes; it was only the current state.
>
> >xfs is non-free stuff
>
> Pe
Hartmut Koptein <[EMAIL PROTECTED]> writes:
> disadvantages:
>ext3 isn't a real journalingfs or better: it hasen't the ful
> power. Forget ext3.
Do you mean "it doesn't do metadata-only journaling"? Perhaps you
mean "it's not finished".
>xfs is non-free stuff
Perhaps you are
On Sat 17 Jun, bug1 wrote:
> I think Ben meant msdos partition *tables*, ie parted doesnt support
> partitioning schemes that arent native to i386 architecture.
> This got me wondering , exactly what other types of partition tables
> would need to be supported by parted ?
I know that for ARM (e
Joey Hess wrote:
>
> bug1 wrote:
> > > What is the advantage to delaying partitioning, get it out of the way
> > > fast and you have the whole harddrive to play with.
> > >
> > If you get it out the way first, then you limit how powerfull it can be.
> >
> > If we delay partitioning till after the
bug1 wrote:
> > What is the advantage to delaying partitioning, get it out of the way
> > fast and you have the whole harddrive to play with.
> >
> If you get it out the way first, then you limit how powerfull it can be.
>
> If we delay partitioning till after the installer has accessed the
> de
On Tue, 20 Jun 2000, Erik Andersen wrote:
> On Tue Jun 20, 2000 at 03:37:17AM -0600, Bruce Sass wrote:
> > I think you are forgetting about something...
> > how is partitioning going to be accomplished without user interaction.
> >
> > I'm not aware of any tools that can take a description of a
On Tue, 20 Jun 2000, bug1 wrote:
> Bruce Sass wrote:
> > I think you are forgetting about something...
> > how is partitioning going to be accomplished without user interaction.
> >
> > I'm not aware of any tools that can take a description of a filesystem
> > then partition and setup a harddrive
On Tue Jun 20, 2000 at 03:37:17AM -0600, Bruce Sass wrote:
> No argument here.
>
> I think you are forgetting about something...
> how is partitioning going to be accomplished without user interaction.
>
> I'm not aware of any tools that can take a description of a filesystem
> then partition a
Bruce Sass wrote:
> I think you are forgetting about something...
> how is partitioning going to be accomplished without user interaction.
>
> I'm not aware of any tools that can take a description of a filesystem
> then partition and setup a harddrive(s) accordingly, that seems to be a
> task ne
On Tue, 20 Jun 2000, bug1 wrote:
> Bruce Sass wrote:
> > > Bruce Sass wrote:
> > > > On Sun, 18 Jun 2000, bug1 wrote:
> > > > > How and Interim filesystem might work (as i see it)
> > > >
> > > > Why have an interim fs?
> > >
> > > 1) To get around any space limitations presented by the boot mediu
> > And what about raiserfs or better jfs ?
> >
>
> I havent tried reiserfs yet, from what i know it save us a bit of space
> with small files wouldnt it, does it have nay other advantages ?
>
> Whats jfs?
jfs is the journaling-file-system from ibm -- the aix filesystem without
the LVM.
We h
Hartmut Koptein wrote:
>
> > > > How and Interim filesystem might work (as i see it)
> > >
> > > Why have an interim fs?
>
> And what about raiserfs or better jfs ?
>
I havent tried reiserfs yet, from what i know it save us a bit of space
with small files wouldnt it, does it have nay other adv
> > > How and Interim filesystem might work (as i see it)
> >
> > Why have an interim fs?
And what about raiserfs or better jfs ?
Hartmut
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bruce Sass wrote:
>
> On Mon, 19 Jun 2000, bug1 wrote:
> > Bruce Sass wrote:
> > > On Sun, 18 Jun 2000, bug1 wrote:
> > > > How and Interim filesystem might work (as i see it)
> > >
> > > Why have an interim fs?
> >
> > 1) To get around any space limitations presented by the boot medium, or
> > r
On Mon, 19 Jun 2000, bug1 wrote:
> Bruce Sass wrote:
> > On Sun, 18 Jun 2000, bug1 wrote:
> > > How and Interim filesystem might work (as i see it)
> >
> > Why have an interim fs?
>
> 1) To get around any space limitations presented by the boot medium, or
> ramdisk.
> It is delaying the pa
Bruce Sass wrote:
> > > onto an existing Debian system. The boot-floppies .deb is not useful to
> > > the average user, but it can still be installed; debinst .debs would be
> > > installed for the same reasons that someone would want to install the
> > > boot-floppies .deb.
> >
> > Ok, but we'
On Sun, 18 Jun 2000, Joey Hess wrote:
> Bruce Sass wrote:
> > It would be very confusing to have .debs that could not be installed
> > onto an existing Debian system. The boot-floppies .deb is not useful to
> > the average user, but it can still be installed; debinst .debs would be
> > installed
Bruce Sass wrote:
>
> On Sun, 18 Jun 2000, bug1 wrote:
> > How and Interim filesystem might work (as i see it)
>
> Why have an interim fs?
>
> - Bruce
1) To get around any space limitations presented by the boot medium, or
ramdisk.
It is delaying the partitioning process till later on
Esben Haabendal Soerensen wrote:
> Ok, I see I have to look into debconf before arguing much more about
> this.
Joey Hess wrote:
> Let me summarize the features of debconf that seem to apply to
> using in in an installer:
> * Debconf reduces user interaction to a series of questions and
> ans
Esben Haabendal Soerensen wrote:
> Ok, I see I have to look into debconf before arguing much more about
> this.
Let me summarize the features of debconf that seem to apply to using in
in an installer:
* Debconf reduces user interaction to a series of questions and
answers.
* The questions are
> "Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> Esben Haabendal Soerensen wrote:
>> I think it is a good idea to turn this design up-side down.
>>
>> The basic design component should not be the UI. I suggest that
>> the basic design for the woody installer is based in the actual
>>
On Sun, 18 Jun 2000, Joey Hess wrote:
> Bruce Sass wrote:
<...>
> > <...description of a dpkg based installation system...>
> > > I think this would require a minimum of 16 mb of disk space, and
> > > probably a bit more. Since with ramfs, disk space == memory, this
> > > would limit installations
Some very interesting ideas, the loop mounted raid is a neat trick.
bug1 wrote:
> Case 2 : TRADITIONAL : This is the traditional method used, it requires
> partitioning prior to setting up any nonram filesystems, if this method
> is taken there aren't really any advantages to an interim filesyste
Esben Haabendal Soerensen wrote:
> I think it is a good idea to turn this design up-side down.
>
> The basic design component should not be the UI. I suggest that the
> basic design for the woody installer is based in the actual
> installation proces, making the modularity concept even more
> po
Bruce Sass wrote:
> It would be very confusing to have .debs that could not be installed
> onto an existing Debian system. The boot-floppies .deb is not useful to
> the average user, but it can still be installed; debinst .debs would be
> installed for the same reasons that someone would want to
Bruce Sass wrote:
> > 1. Modularity.
> > 2. Do the absolute minimum in the installer, do as much as is possible
> >in the full debian install.
>
> A side effect of both these points is that the installation system
> should become scalable and get smaller...
You becha.
It should also be poss
On Sat, 17 Jun 2000, Joey Hess wrote:
<...>
> These wouldn't be .deb's that are policy complient, or that you'd want
> to install onto a real debian system. (They would in fact, probably have
> dependancies to prevent that.)
Policy is what you people make it, since .debs have never been used in
t
Steve Przepiora wrote:
> As long as your thinking of re-doing boot-floppies, why not take suggestions
> from users about what's important for them? Maybe set up some kind voting
> page or something.
>
Its a good idea to keep in touch with regular users, but i think timing
is important.
I think it
> "Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> The question of how the UI should work is the weak point of my
Joey> current proposal. I've been wrestling with really two orthagonal
Joey> issues:
Joey> 1. How should the UI work? I rather like most of our current UI,
Joey> but is it r
On Sat, 17 Jun 2000, Joey Hess wrote:
> The ideas I stress are important are:
>
> 1. Modularity.
> 2. Do the absolute minimum in the installer, do as much as is possible
>in the full debian install.
A side effect of both these points is that the installation system
should become scalable and
Joey Hess wrote:
> I think this would require a minimum of 16 mb of disk space, and
> probably a bit more. Since with ramfs, disk space == memory, this
> would limit installations to systems with around 20-32 mb of memory.
> I don't think that's very acceptable.
>
> I don't see how you could use
Hi, A little background first, so you all know were I'm coming from...
I am not a debian developer, but I follow quite a few developer related lists
for debian, and have been for quite some time. I have been using debian since
slink was listed as unstable, so am pretty familiar with debian, and w
Karl mentioned something on this in another post, there are lots of
ideas floating around, maybe we do need something other than emails and
cvs to keep track of everything.
What about a web page or something?
I guess the issue is, would the benefits of maintaining a web page for
the development
Karl M. Hegbloom wrote:
> We'll have to put that "on the board" for this project. Who will act
> as secretary? The list software?
>
> Joey Hess is obviously very busy and should not be expected to manage
> the `debinst' whiteboard himself.
I've seen a lot of ideas thrown out in this thread
I had meant to not have this discussion until potato was released,
so as to not distract from the more important work on getting
potato boot-floppies polished, but we're probably close enough.
bug1 wrote:
> > http://kitenet.net/cgi-bin/cvsweb/joey-cvs/public/packages/debinst>
> >
> > (Joey? P
Red Hat's `libfdisk' contains a partition editor with a `newt'
> > > > > interface. It might be possible to port it to our system and hook
> > > > > that into our Woody `debinst' `dbootstrap'.
> > > > >
> > > > Wh
On Sat, Jun 17, 2000 at 02:30:39AM -0700, Karl M. Hegbloom wrote:
> > "Ben" == Ben Collins <[EMAIL PROTECTED]> writes:
>
> Ben> On Sat, Jun 17, 2000 at 02:22:10PM +1000, bug1 wrote:
> >> Ben Collins wrote:
> >>
> >> >
> >> > Also, I'm looking into a program on freshmeat
27;s `libfdisk' contains a partition editor with a `newt'
interface. It might be possible to port it to our system and hook
that into our Woody `debinst' `dbootstrap'.
bug1> What about parted, it doesnt have much a of a GUI, but it wouldnt be
bug1> hard to do i
> "Erik" == Erik Andersen <[EMAIL PROTECTED]> writes:
Erik> Agreed re parted. I think a cool project would be hacking a GUI similar to
Erik> cfdisk into parted...
Yes, that would be a good thing to do. If we used Newt for the
interface, we'd have X for free, with `gnewt'.
Er
> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes:
Ben> On Fri, Jun 16, 2000 at 09:44:31PM -0600, Erik Andersen wrote:
>> On Sat Jun 17, 2000 at 01:29:43PM +1000, bug1 wrote:
>> > What about parted, it doesnt have much a of a GUI, but it wouldnt be
>> > hard to do i dont think
> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes:
Ben> On Sat, Jun 17, 2000 at 02:22:10PM +1000, bug1 wrote:
>> Ben Collins wrote:
>>
>> >
>> > Also, I'm looking into a program on freshmeat called genext2fs that can
>> > create ext2 images from a directory (and usin
#x27; contains a partition editor with a `newt'
> > > > > interface. It might be possible to port it to our system and hook
> > > > > that into our Woody `debinst' `dbootstrap'.
> > > > >
> > > > What about parted, it doesnt have much a
> > > interface. It might be possible to port it to our system and hook
> > > > that into our Woody `debinst' `dbootstrap'.
> > > >
> > > What about parted, it doesnt have much a of a GUI, but it wouldnt be
> > > hard to do i dont th
On Sat, Jun 17, 2000 at 02:22:10PM +1000, bug1 wrote:
> Ben Collins wrote:
>
> >
> > Also, I'm looking into a program on freshmeat called genext2fs that can
> > create ext2 images from a directory (and using an optional device list for
> > devices) as non-root. Would be very nice for woody boot-
"Karl M. Hegbloom" wrote:
> Karl> newtGrid's and whatnot. I'm going to start learning Newt, and see
> Karl> what I can come up with.
Karl, if you havent found this newt tutorial already, its at
http://oksid.ch/gnewt/tutorial.html
Glenn
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Ben Collins wrote:
>
> Also, I'm looking into a program on freshmeat called genext2fs that can
> create ext2 images from a directory (and using an optional device list for
> devices) as non-root. Would be very nice for woody boot-floppies, IMO.
> It's a single .c, so could go into utilities if i
On Fri, Jun 16, 2000 at 09:44:31PM -0600, Erik Andersen wrote:
> On Sat Jun 17, 2000 at 01:29:43PM +1000, bug1 wrote:
> > > Red Hat's `libfdisk' contains a partition editor with a `newt'
> > > interface. It might be possible to port it to our system and hook
On Sat Jun 17, 2000 at 01:29:43PM +1000, bug1 wrote:
> > Red Hat's `libfdisk' contains a partition editor with a `newt'
> > interface. It might be possible to port it to our system and hook
> > that into our Woody `debinst' `dbootstrap'.
> >
uration into debconf and the packages that relate
to it (even make up virtual packages), it makes the configuration
process more easily reusable for debian users.
> They have device detection codes worth haveing a look over also...
> so does Corel Linux.
>
Redhats hardware detection is cal
bbed Red Hat's `anaconda' package, which is their
installation system. It's worth haveing a look at. Most of it is
written in Python, with both a `newt' and `gtk' interface. I've not
yet seen it in operation. It looks like they have a `busybox' alike
thing, cal
54 matches
Mail list logo
