Hello,
FYI, http://floppy.slitaz.org/builder/index.php can build boot floppy sets
with a 15Mb kernel.
Shell standalone version: http://floppy.slitaz.org/builder/bootloader.
-pascal
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
Your message dated Mon, 13 Sep 2010 19:31:27 +0200
with message-id <20100913173127.gf3...@mykerinos.kheops.frmug.org>
and subject line No more floppies...no more bug
has caused the Debian Bug report #252426,
regarding no oldworld mac boot floppies
to be marked as done.
This means that you
h problems
--- Begin Message ---
Package: installation-reports
In addition to the already noted problems with 2.4 PowerPC boot
floppies, I have two requests for modules to be included on the
root or root-2:
1) The "change installation priority" menu item should be available
*very* early in
trator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: boot-floppies
Version: N/A - current CVS
Severity: wishlist
I'm working on fixes for base-config, and in the process I thought it
is smart to change dbootstrap to be able to us the lang->msgcat
content the same way a
Hi Geert,
booting into the etch installer works very well this way. Thus I have the
laptop now up with a
topsi:~# uname -a
Linux topsi 2.6.17-2-486 #1 Wed Sep 13 15:56:30 UTC 2006 i686 GNU/Linux
topsi:~#
kernel from the debian installer for etch. The laptop has etch installed, but
grub/lilo a
The solution to the devmapper issue was simple:
modprobe dm-mod
(that might have helped even with the sarge install discs).
For the poor owners of laptops with usbfloppies and without bootable cdrom,
the pxe-on-a-disk method will help a lot to get etch installed. Can that be
documented in the
quot; will have
a hard time how to get boot floppies of RC1 for VAIO laptop.
Please reply below the text!
Geert Stappers
in another plea to bottom post
--
http://www.catb.org/~esr/jargon/html/B/bottom-post.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
Doug,
I run
silverboxy:/home/rd# dd if=grub-0.97-i486-pc.ext2fs of=/dev/fd0 bs=512
conv=sync ; sync
2880+0 records in
2880+0 records out
1474560 bytes transferred in 96.615515 seconds (15262 bytes/sec)
silverboxy:/home/rd#
but the floppy did *not* boot. Is that one in etch broken, or did I do
Op 02-12-2006 om 18:36 schreef Rainer Dorsch:
>
> Hmmgood point, but I would be surprised, if booting from an usb stick
> would work. It explicitly says in the BIOS floppy, there is no usb stick
> option. I would be surprised, if an usb stick and a floppy image look
> identical for the lapt
On Sun, Dec 03, 2006 at 12:40:48AM +0100, Rainer Dorsch wrote:
>
> > Can it boot a grub-disk floppy?
> >
> > Can you burn a CD? Or, on that nice hdd, make a 256 MB (or 1 GB if its
> > a large disk) partition. Put the hd-media and the netinst.iso there
> > following the long-way instructions for
Am Samstag, 2. Dezember 2006 19:09 schrieb Frans Pop:
> On Saturday 02 December 2006 18:36, Rainer Dorsch wrote:
> > Just wondering, if there is a way to work around this. Somehow people
> > doing an update from sarge to etch must see the same issue. How does it
> > work there?
>
> Can you free up
Am Samstag, 2. Dezember 2006 20:40 schrieb Holger Wansing:
> On Sat, 2 Dec 2006 18:36:13 +0100 Rainer Dorsch wrote:
> > Hmmgood point, but I would be surprised, if booting from an usb stick
> > would work. It explicitly says in the BIOS floppy, there is no usb stick
> > option. I would be surpr
Am Samstag, 2. Dezember 2006 22:24 schrieb Douglas Tutty:
> On Sat, Dec 02, 2006 at 06:36:13PM +0100, Rainer Dorsch wrote:
> > Am Samstag, 2. Dezember 2006 15:47 schrieb Douglas Tutty:
> > > On Sat, Dec 02, 2006 at 01:03:15PM +0100, Rainer Dorsch wrote:
> > > > Am Samstag, 2. Dezember 2006 10:40 sc
On Sat, Dec 02, 2006 at 06:36:13PM +0100, Rainer Dorsch wrote:
> Am Samstag, 2. Dezember 2006 15:47 schrieb Douglas Tutty:
> > On Sat, Dec 02, 2006 at 01:03:15PM +0100, Rainer Dorsch wrote:
> > > Am Samstag, 2. Dezember 2006 10:40 schrieben Sie:
> > > > On Friday 01 December 2006 23:05, Rainer Dors
On Sat, 2 Dec 2006 18:36:13 +0100 Rainer Dorsch wrote:
> Hmmgood point, but I would be surprised, if booting from an usb stick
> would work. It explicitly says in the BIOS floppy, there is no usb stick
> option. I would be surprised, if an usb stick and a floppy image look
> identical for th
On Saturday 02 December 2006 18:36, Rainer Dorsch wrote:
> Just wondering, if there is a way to work around this. Somehow people
> doing an update from sarge to etch must see the same issue. How does it
> work there?
Can you free up enough space on your harddisk using the Sarge installer
for say
vaio laptop (z505je) with the etch boot
> > > > floppies. While it worked well with sarge floppies, I get with the
> > > > RC1 boot floppy (the same with the latest daily build):
> > >
> > > The problem is that the 2.6.18 kernel is so big that we canno
On Sat, Dec 02, 2006 at 01:03:15PM +0100, Rainer Dorsch wrote:
> Am Samstag, 2. Dezember 2006 10:40 schrieben Sie:
> > On Friday 01 December 2006 23:05, Rainer Dorsch wrote:
> > > I just tried to boot a vaio laptop (z505je) with the etch boot
> > > floppies. Whil
(No need to CC me. I read the list!)
On Saturday 02 December 2006 13:03, Rainer Dorsch wrote:
> Is it easy enough to create my own boot/root floppies and throw away
> stuff which I don't need for example (e.g. CD-ROM support)?
Not really as your problem is the boot floppy and that already does no
Am Samstag, 2. Dezember 2006 10:40 schrieben Sie:
> On Friday 01 December 2006 23:05, Rainer Dorsch wrote:
> > I just tried to boot a vaio laptop (z505je) with the etch boot
> > floppies. While it worked well with sarge floppies, I get with the RC1
> > boot floppy (the same
On Friday 01 December 2006 23:05, Rainer Dorsch wrote:
> I just tried to boot a vaio laptop (z505je) with the etch boot
> floppies. While it worked well with sarge floppies, I get with the RC1
> boot floppy (the same with the latest daily build):
>
> Floppy drive(s): fd0 is 1.44
Hello,
I just tried to boot a vaio laptop (z505je) with the etch boot floppies. While
it worked well with sarge floppies, I get with the RC1 boot floppy (the same
with the latest daily build):
Floppy drive(s): fd0 is 1.44 M
floppy0: no floppy controllers found
Cannot load floppy module
Giving
@lists.debian.org
> Subject: Re: Bug#126208: boot-floppies: First choose DHCP-Configure, then
> change to static
> Date: 31 Dec 2001 13:24:45 -0700
>
> On Sun Dec 30, 2001 at 10:52:59PM -0500, Colin Walters wrote:
> > On Sun, 2001-12-30 at 19:01, Erik Andersen wrote:
> > &
On Sat, Apr 08, 2006 at 10:42:58AM -0700, Brad Boyer wrote:
> On Fri, Apr 07, 2006 at 06:50:54AM -0500, Colin Watson wrote:
> > On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> > > On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > > > So, my questions would be:
> > > > - w
On Fri, Apr 07, 2006 at 06:50:54AM -0500, Colin Watson wrote:
> On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> > On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > > So, my questions would be:
> > > - which driver is actually needed in the case of #345467
> >
> > swim3.k
On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > So, my questions would be:
> > - which driver is actually needed in the case of #345467
>
> swim3.ko
>
> > - is this driver available on the root floppy (built in or module
On Tue, Mar 07, 2006 at 06:41:47AM -0600, vinai wrote:
> I made a few small changes to the interrupt call routines so the driver
> would compile and work, but was informed that those changes were not
> SMP-clean. Then I got lost in work ...
I certainly understand. I haven't had time to do anythin
On Mon, 6 Mar 2006, Brad Boyer wrote:
On Sun, Mar 05, 2006 at 02:01:23AM +0100, Marco d'Itri wrote:
[EMAIL PROTECTED] wrote:
I guess we are using udev, but with a devfs-like naming scheme on
top, right ? I strongly believe that swim3.ko is not hotplug
friendly, or that udev has some trouble
On Sun, Mar 05, 2006 at 02:01:23AM +0100, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
> >I guess we are using udev, but with a devfs-like naming scheme on top, right
> >?
> >I strongly believe that swim3.ko is not hotplug friendly, or that udev has
> >some trouble with builtin modules, but i wo
On Sun, Mar 05, 2006 at 11:35:55PM +0100, Marco d'Itri wrote:
> On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
>
> > I believe it would be best for all involved if we maintained a list of such
> > cases, and had proper workaround in either udev or a separate package, and
> > then, actively sear
On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> I believe it would be best for all involved if we maintained a list of such
> cases, and had proper workaround in either udev or a separate package, and
> then, actively search to get those cases fixed in the kernel, either by doing
> the develop
On Sun, Mar 05, 2006 at 08:39:28PM +0100, Marco d'Itri wrote:
> On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> > So, on one hand you say you have no plan to oppose workarounds, but on the
> > other hand you clearly oppose such workarounds ?
> No, I oppose attempts to require me to maintain the
On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> Well, i remember some issues with the firewire module in the sarge timeframe,
> and how you actively discouraged a workaround for this.
It's hard to be specific since I do not remember the details either, but
IIRC I suggested a solution to be im
On Sun, Mar 05, 2006 at 04:25:01PM +0100, Marco d'Itri wrote:
> On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
>
> > > By saying that these obsolete drivers should be supported anyway you are
> > > basically requesting other people to spend their time maintaining
> > > workarounds in their own
On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> > By saying that these obsolete drivers should be supported anyway you are
> > basically requesting other people to spend their time maintaining
> > workarounds in their own packages.
> Well, we have done this for sarge in a much more extensive w
On Sun, Mar 05, 2006 at 11:19:04AM +0100, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
>
> >I think that this is not a position acceptable in debian right now, who aims
> >to support many less-supported-arches/subarches, who still struggle to get
> >their main patches into mainline. So i believe
On Sun, Mar 05, 2006 at 02:01:23AM +0100, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
>
> >I guess we are using udev, but with a devfs-like naming scheme on top, right
> >?
> >I strongly believe that swim3.ko is not hotplug friendly, or that udev has
> >some trouble with builtin modules, but i
On Mar 05 2006, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
> >I guess we are using udev, but with a devfs-like naming scheme on
> >top, right ? I strongly believe that swim3.ko is not hotplug
> >friendly, or that udev has some trouble with builtin modules, but i
> >would go for the first case.
On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > So, my questions would be:
> > - which driver is actually needed in the case of #345467
>
> swim3.ko
>
> > - is this driver available on the root floppy (built in or module
On Fri, Mar 03, 2006 at 11:50:38PM +0100, Frans Pop wrote:
> On Friday 03 March 2006 23:30, Brad Boyer wrote:
> > Are we still using devfs, or have we moved on to using udev?
>
> The installer uses udev for current 2.6 kernels.
Then the likely explanation is that udev doesn't like devices
that ar
On Friday 03 March 2006 23:30, Brad Boyer wrote:
> Are we still using devfs, or have we moved on to using udev?
The installer uses udev for current 2.6 kernels.
pgpcgUt6C1aSt.pgp
Description: PGP signature
On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> So, my questions would be:
> - which driver is actually needed in the case of #345467
swim3.ko
> - is this driver available on the root floppy (built in or module)
> - if it's modular, is it being loaded
No idea. Haven't looked. Based
On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> On Sunday 26 February 2006 17:00, Brad Boyer wrote:
> > This problem seems pretty simple. The driver floppy.ko is for normal PC
> > style floppy controllers. Apple never did use such a beast in a Mac.
> > The swim3 driver should handle th
On Sunday 26 February 2006 17:00, Brad Boyer wrote:
> This problem seems pretty simple. The driver floppy.ko is for normal PC
> style floppy controllers. Apple never did use such a beast in a Mac.
> The swim3 driver should handle the floppy drives for all PCI Macs that
> have internal floppy drives
Sven Luther wrote:
On Sun, Feb 26, 2006 at 08:00:34AM -0800, Brad Boyer wrote:
On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
I've been trying to coax the floppy images from
http://people.debian.org/~luther/d
On Sun, Feb 26, 2006 at 08:00:34AM -0800, Brad Boyer wrote:
> On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
> > On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
> > > I've been trying to coax the floppy images from
> > > http://people.debian.org/~luther/d-i/images/d
Brad Boyer wrote:
On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
I've been trying to coax the floppy images from
http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/
(where daily = 25/2/2006) to boot
On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
> On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
> > I've been trying to coax the floppy images from
> > http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/
> > (where daily = 25/2/2006) to boot on a 7200
On Sun, Feb 26, 2006 at 10:00:23PM +0800, Tomasz Grzegurzko wrote:
> Just a quick update Sven; I got the bugger working. It looks like your root
> disk
> is missing a *whole* bunch of stuff from /dev such as /dev/floppy/0 etc and
> after a few mknod commands, I was in business. That at least got m
On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
> Hi Sven,
>
> I've been trying to coax the floppy images from
> http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/
> (where daily = 25/2/2006) to boot on a 7200/75 I've picked up. The
> system boots of the disks fi
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.5
> retitle 246443 boot-floppies: Fails to advise admin of kernel vulnerabilities
Bug#246443: boot-floppies: There is no indice *bf kernel has security issues
Changed Bug title.
&g
Processing commands for [EMAIL PROTECTED]:
> reassign 290239 boot-floppies
Bug#290239: annoying IDE2 interrupt error text every 3 seconds when I try to
boot and configure the new installation
Warning: Unknown package 'installer'
Bug reassigned from package `installer' to `boot
On Wed, Dec 29, 2004 at 04:14:14PM +0100, Ludovic Drolez wrote:
> No news for 2 years...
>
> Hope it's been fixed for Sarge !
Certainly has, there's a pcmcia-cs-udeb which hw-detect uses.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMA
No news for 2 years...
Hope it's been fixed for Sarge !
Ludo.
--
www.palmopensource.com - The PalmOS open source portal
www.drolez.com - Personal site
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Dec 09, 2004 at 02:31:59AM -0600, John and Holly Klug wrote:
> On my machine, my NIC is not recognized by the boot floppies CD image.
>
> When I try to manually install it per SysKonnect directions I get a
> device or resource busy message.
>
> lspci says it is from
On my machine, my NIC is not recognized by the boot floppies CD image.
When I try to manually install it per SysKonnect directions I get a
device or resource busy message.
lspci says it is from Galileo Technology Ltd. The support from
Syskonnect says it is a Marvell Yukon chipset. I found a
On Thu, Apr 29, 2004 at 04:56:04AM +0200, Jan Minar wrote:
> Package: boot-floppies
> Version: N/A; reported 2004-04-29
> Severity: critical
> Justification: root security hole
> Tags: security
>
> Hi.
>
> I've just installed Debian @ my friend's, and I
On Nov 10, 2004, at 5:25 PM, Sven Luther wrote:
On Wed, Nov 10, 2004 at 01:35:04PM -0700, Wade Berrier wrote:
I did have one idea: if you can boot a coff image from an hfs
partition, couldn't you have an hfs /boot partition on the harddrive
and
boot directly from open firmware? If I understand
On Wed, Nov 10, 2004 at 01:35:04PM -0700, Wade Berrier wrote:
> Thanks again for the help. I'm up and running. The CMOS battery fixed
> my boot problems, and I did have to use the quik "quirk" settings for my
> powerpc 6400 (load-base=10, output-device=ttya).
>
> I also was also able to boot
Thanks again for the help. I'm up and running. The CMOS battery fixed
my boot problems, and I did have to use the quik "quirk" settings for my
powerpc 6400 (load-base=10, output-device=ttya).
I also was also able to boot the 2.4 debian installer floppies from
daily builds.
It's been an inte
On Nov 9, 2004, at 3:45 AM, Wade Berrier wrote:
One last thing I'm going to try is to replace the cmos battery. When I
boot into the woody install, the time is set to 1956. I'll set it, and
even still, the next reboot is 1956. I friend at work tipped me on
this
one. Maybe this will make it so
On Tue, Nov 09, 2004 at 01:45:35AM -0700, Wade Berrier wrote:
> Thanks for all the feedback I've gotten from y'all.
>
> Here's a quick log about my situation:
>
> First, started out as I installed woody from the boot-floppy-hfs.img,
> install went ok. On reboot, I get claim failed.
>
> I've tri
Thanks for all the feedback I've gotten from y'all.
Here's a quick log about my situation:
First, started out as I installed woody from the boot-floppy-hfs.img,
install went ok. On reboot, I get claim failed.
I've tried all the settings from the quik quirks page without any
success. (http://www
;.
>
> Unfortunately, I'm not close to my 4400 at the moment, so I can't help
> (and I have no experience with the woody boot floppies).
>
> The boot.img for the 2.4 kernel booted for me (but had problems reading
> the root.img, which might be model-specific to a few 4400
y
> to no avail. I'll usually get back can't LOAD.
>
> And really, the main problem with my woody install is that when I
> reboot, I get "CLAIM FAILED".
Unfortunately, I'm not close to my 4400 at the moment, so I can't help
(and I have no experience with th
On Mon, Nov 08, 2004 at 12:01:38PM -0700, Wade Berrier wrote:
> Thanks for the reply,.
>
> So how do I actually get the boot.img to boot?
>
> I've set up open firmware (version 2.0) to have the display as output
> and the keyboard as input, and auto-boot to false.
>
> But, I've tried what seems
Thanks for the reply,.
So how do I actually get the boot.img to boot?
I've set up open firmware (version 2.0) to have the display as output
and the keyboard as input, and auto-boot to false.
But, I've tried what seems every combination of boot fd or boot floppy
to no avail. I'll usually get bac
On Mon, Nov 08, 2004 at 09:19:12AM -0700, Wade Berrier wrote:
> Hi Malte,
>
> I found a message in the debian mailing lists about a 4400/200:
>
> http://lists.debian.org/debian-boot/2004/03/msg05918.html
>
> You said that boot.img booted for you.
>
> How do you get this to boot? The only thing
Hi Malte,
I found a message in the debian mailing lists about a 4400/200:
http://lists.debian.org/debian-boot/2004/03/msg05918.html
You said that boot.img booted for you.
How do you get this to boot? The only thing I've been able to boot on
mine is the hfs-only image from woody.
My install go
On Friday 01 October 2004 9:40, Roman Zippel wrote:
> Rick Thomas wrote:
> > When one mounts an hfs filesystem under 2.4, there are a bunch of
> > pseudo-directories with names beginning with a "." that give you access
> > to the finder info and the resource forks of all the files.
>
> You can acce
Hi,
Rick Thomas wrote:
When one mounts an hfs filesystem under 2.4, there are a bunch of
pseudo-directories with names beginning with a "." that give you access
to the finder info and the resource forks of all the files.
You can access the resource via /rsrc. I have a patch to export
some other
Your message dated Fri, 1 Oct 2004 15:32:52 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#272890: boot-floppies: Error in debootstrap Sarge-rc1 NetInstall
(chroot segmentation fault) vmware I
has caused the attached Bug report to be marked as done.
This means that you clai
On Fri, Oct 01, 2004 at 11:07:18AM +0200, Sven Luther wrote:
> Thanks for the info. Keep in mind i am w total neophyte about HFS filesystems.
> I suppose we would need to bring the HFS driver in 2.6 upto speed, or create
> an HFS+ filesystem instead.
I can understand. Apple has always been a littl
Processing commands for [EMAIL PROTECTED]:
> reassign 272890 installation-reports
Bug#272890: boot-floppies: Error in debootstrap Sarge-rc1 NetInstall (chroot
segmentation fault) vmware I
Bug reassigned from package `installation-reports' to `installation-reports'.
> thanks,
Sto
reassign 272890 installation-reports
thanks,
On Wed, Sep 22, 2004 at 01:19:14PM -0300, Oper wrote:
> Package: boot-floppies
> Version: N/A; reported 2004-09-22
> Severity: critical
> Justification: breaks the whole system
>
> Debian Sarge-rc1 CD installation image (the o
On Fri, 1 Oct 2004, Sven Luther wrote:
> Geert, you can probably help us here, the current scenario is :
>
> - 2.4 floppies, either work fine, the frambuffer takes over and we see the
> kernel boot info, or fail because of miboot problems, and we see a red
> cross over the miboot stuff.
On Fri, Oct 01, 2004 at 09:56:37AM +0200, Geert Uytterhoeven wrote:
> On Thu, 30 Sep 2004, Rick_Thomas wrote:
> > On Thu, 2004-09-30 at 05:18, Sven Luther wrote:
> > > On Wed, Sep 29, 2004 at 11:11:49PM -0400, Rick Thomas wrote:
> > > > Now, is the loss under 2.6 of the HFS ".finderinfo" and ".reso
On Thu, 30 Sep 2004, Rick_Thomas wrote:
> On Thu, 2004-09-30 at 05:18, Sven Luther wrote:
> > On Wed, Sep 29, 2004 at 11:11:49PM -0400, Rick Thomas wrote:
> > > Now, is the loss under 2.6 of the HFS ".finderinfo" and ".resource"
> > > pseudo-directories a bug, or a feature?
> >
> > You probably n
On Thu, Sep 30, 2004 at 04:33:47PM -0400, Rick_Thomas wrote:
> On Thu, 2004-09-30 at 05:18, Sven Luther wrote:
> > On Wed, Sep 29, 2004 at 11:11:49PM -0400, Rick Thomas wrote:
>
> > > Now, is the loss under 2.6 of the HFS ".finderinfo" and ".resource"
> > > pseudo-directories a bug, or a feature?
On Thu, 2004-09-30 at 05:18, Sven Luther wrote:
> On Wed, Sep 29, 2004 at 11:11:49PM -0400, Rick Thomas wrote:
> > Now, is the loss under 2.6 of the HFS ".finderinfo" and ".resource"
> > pseudo-directories a bug, or a feature?
>
> You probably need to load the hfs+ driver ?
>
> If that doesn't
On Wed, Sep 29, 2004 at 11:11:49PM -0400, Rick Thomas wrote:
>
> On Wednesday, September 29, 2004, at 01:30 PM, Holger Levsen wrote:
>
> >Hi,
> >
> >>>However... There is one important thing missing from the boot
> >>>disks. Specifically, the "System" file is zero length. This is
> >>>true of b
On Wed, Sep 29, 2004 at 11:11:49PM -0400, Rick Thomas wrote:
> I think I've just discovered a major difference between the "hfs"
> implementation in 2.4 and that in 2.6.
>
> When one mounts an hfs filesystem under 2.4, there are a bunch of
> pseudo-directories with names beginning with a "." tha
On Wednesday, September 29, 2004, at 01:30 PM, Holger Levsen wrote:
Hi,
However... There is one important thing missing from the boot
disks. Specifically, the "System" file is zero length. This is
true of both boot and ofonlyboot for both 2.4 and 2.6. It won't
boot that way.
Arg, again. I have t
Hi,
> > However... There is one important thing missing from the boot
> > disks. Specifically, the "System" file is zero length. This is
> > true of both boot and ofonlyboot for both 2.4 and 2.6. It won't
> > boot that way.
> Arg, again. I have to checkup and see what is missing in the build pr
On Wed, Sep 29, 2004 at 01:25:22AM -0400, Rick Thomas wrote:
>
> On Saturday, September 25, 2004, at 04:49 PM, Colin Watson wrote:
>
> >After my changes,
> >there's *loads* of room left for things. We were just being
> >inefficient,
> >that's all.
>
> Well,
>
> I just took a look at the latest
On Saturday, September 25, 2004, at 04:49 PM, Colin Watson wrote:
After my changes,
there's *loads* of room left for things. We were just being
inefficient,
that's all.
Well,
I just took a look at the latest floppy images. It looks like
everything that's there fits with room to spare -- in some
On Saturday, September 25, 2004, at 04:49 PM, Colin Watson wrote:
Bringing things back into sync with other architectures is worth it on
its own, and reducing the number of floppies required for an
installation was one of the original goals of d-i. After my changes,
there's *loads* of room left for
On Sat, Sep 25, 2004 at 03:19:20PM -0400, Rick Thomas wrote:
> On Saturday, September 25, 2004, at 04:13 AM, Colin Watson wrote:
> >On Fri, Sep 24, 2004 at 01:50:34AM -0400, Rick Thomas wrote:
> >>ROOT-2) The "root-2" floppy is a bunch of "udeb"s for all the
> >>components that wouldn't fit on "roo
On Saturday, September 25, 2004, at 04:13 AM, Colin Watson wrote:
On Fri, Sep 24, 2004 at 01:50:34AM -0400, Rick Thomas wrote:
ROOT-2) The "root-2" floppy is a bunch of "udeb"s for all the
components that wouldn't fit on "root". [This is a good design,
but it requires that "root" have everything n
On Fri, Sep 24, 2004 at 01:50:34AM -0400, Rick Thomas wrote:
> ROOT-2) The "root-2" floppy is a bunch of "udeb"s for all the
> components that wouldn't fit on "root". [This is a good design,
> but it requires that "root" have everything needed to install a
> udeb, making the "root" floppy even
Oper wrote:
> Debian Sarge-rc1 CD installation image (the one downloader from
> http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/sarge-i386-netinst.iso)
> have problems during installation of 'linux26'
>
> When the "install base system" phase starts, I get a red screen tailling t
On Fri, Sep 24, 2004 at 01:50:34AM -0400, Rick Thomas wrote:
>
> On Thursday, September 23, 2004, at 06:45 PM, Sven Luther wrote:
>
> >On Thu, Sep 23, 2004 at 06:30:48PM -0400, Rick Thomas wrote:
> >>
> >>On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote:
> >>
> I understand the
Hi,
Rick Thomas writes:
> Actually, it's quite useful -- for writing to mac-formatted (HFS)
> floppy disks... as in for saving the log files for later debugging
> when all else has failed.
For that kind of thing, I wouldn't bother with filesystems, and just
dd or tar to the raw medium.
Regards,
On Fri, 24 Sep 2004, Rick Thomas wrote:
> On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote:
> > I wrote:
> > > I understand the size constraints. But isn't that the reason why
> > > we added the "root-2" floppy? Would adding hfs and/or hfsplus kick
> > > us over the edge into "root
On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote:
I wrote:
I understand the size constraints. But isn't that the reason why
we added the "root-2" floppy? Would adding hfs and/or hfsplus kick
us over the edge into "root-3" land?
We could indeed add it to root-2, but i would prefer t
On Thursday, September 23, 2004, at 06:45 PM, Sven Luther wrote:
On Thu, Sep 23, 2004 at 06:30:48PM -0400, Rick Thomas wrote:
On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote:
I understand the size constraints. But isn't that the reason why
we added the "root-2" floppy? Would addin
On Thu, Sep 23, 2004 at 06:30:48PM -0400, Rick Thomas wrote:
>
> On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote:
>
> >>I understand the size constraints. But isn't that the reason why
> >>we added the "root-2" floppy? Would adding hfs and/or hfsplus kick
> >>us over the edge in
On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote:
I understand the size constraints. But isn't that the reason why
we added the "root-2" floppy? Would adding hfs and/or hfsplus kick
us over the edge into "root-3" land?
We could indeed add it to root-2, but i would prefer to get the
ion to the already noted problems with 2.4 PowerPC boot
> >>floppies, I have two requests for modules to be included on the
> >>root or root-2:
> >
> >Ok, actually following up on this from Oldenbourg with an oldworld
> >box on
> >hand.
>
> Glad yo
On Thursday, September 23, 2004, at 11:02 AM, Sven Luther wrote:
On Mon, Sep 20, 2004 at 05:05:58PM -0400, Rick Thomas wrote:
Package: installation-reports
In addition to the already noted problems with 2.4 PowerPC boot
floppies, I have two requests for modules to be included on the
root or root-2
1 - 100 of 7537 matches
Mail list logo
