Differences between revisions 32 and 33
Revision 32 as of 2002-01-16 00:38:31
Size: 4282
Editor: user-uini6l7
Comment:
Revision 33 as of 2002-01-16 00:43:29
Size: 4315
Editor: user-uini6l7
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * Add [http://www.personaltelco.net/download/warez/debian-ap-20011210.img.bz2 image] (requires a 340mb drive).  * The dd [http://www.personaltelco.net/download/warez/debian-ap-20011210.img.bz2 image] (requires a 340mb drive).
Line 12: Line 12:
This is a pre-built disk image/tarball for getting the fujisu 1000 running as an AP. It has nocatauth, NAT, firewalls, and dhcp support right out of the box. Cool features: It looks like it has ipv6 support, ext3 for fast(er) reboots (well, it still takes 5 min with 40mb of ram in the system, but hey..). We are currently really looking for bugs with this system. If you find any see DebianApImageBugs. This is a pre-built disk image/tarball for getting the FujitsuSytlistic1000 running as an AccessPOint. It has NoCatAuth, NAT, firewalls, and DHCP support right out of the box.

Cool features: It looks like it has IPv6 support, EXT3 for fast(er) reboots (well, it still takes 5 min with 40mb of ram in the system, but hey..). We are currently really looking for bugs with this system. If you find any see DebianApImageBugs.
Line 21: Line 23:
 * Be VERY careful with the next command. If you use the wrong drive (if the 340 meg PCMCIA drive is not hde), you WILL fsck your other drive. This took up about 15 miuntes on a 166 MHz Toshiba Notebook {{{
# bunzip2 -dc ImageFileName.bz2 | dd of=/dev/hde
 * Be VERY careful with the next command. If you use the wrong drive (if the 340 meg PCMCIA drive is not hde), you WILL fsck your other drive. This took up about 15 miuntes on a 166 MHz Toshiba Notebook
 
{{{# bunzip2 -dc ImageFileName.bz2 | dd of=/dev/hde
Line 24: Line 26:
666144+0 records out
#
}}}
666144+0 records out}}}
Line 29: Line 29:
Line 31: Line 30:
Line 89: Line 87:
 * exit out of the chroot'd env  * Exit out of the chroot'd environment and run

This document goes hand in hand with the DebianLinuxAccessPoint page. Once your image is created this shows you how to load the image onto a FujitsuStylistic1000. You can download it in two formats:

If you think that you've found a bug in the image please report it on the DebianApImageBugs page, make sure you include enough information for me to duplicate it. -- AdamShand

See also: DebianAp, DebianApImageBugs, HostApMode

Info

This is a pre-built disk image/tarball for getting the FujitsuSytlistic1000 running as an AccessPOint. It has NoCatAuth, NAT, firewalls, and DHCP support right out of the box.

Cool features: It looks like it has IPv6 support, EXT3 for fast(er) reboots (well, it still takes 5 min with 40mb of ram in the system, but hey..). We are currently really looking for bugs with this system. If you find any see DebianApImageBugs.

  • Q. What happens if you use a DD image on a larger drive?

  • A. It won't work because DD is a bit level copy so it copies all the formatting information which is reliant on disk geometry. That being said I've actually never tried it, it's possible that it will just format your larger disk to the smaller size. Try it and report back ;) -- AdamShand

Using the dd image

  1. Put drive in laptop, it should show up as /dev/hde (if it doesn't you'll need to adjust the rest of the document accordingly).
  2. Be VERY careful with the next command. If you use the wrong drive (if the 340 meg PCMCIA drive is not hde), you WILL fsck your other drive. This took up about 15 miuntes on a 166 MHz Toshiba Notebook

    {{{# bunzip2 -dc ImageFileName.bz2 | dd of=/dev/hde

666144+0 records in 666144+0 records out}}}

--JayPrimePositve, EricJohanson

  • Things that you may need to change:
    • The password for root
    • /etc/network/interfaces
      • If you aren't using DHCP for eth0 put in IP, subnet, gateway, etc.
      • Check the channel setting for wlan0
    • /etc/dhcpd.conf
      • Make sure it knows the correct information for your eth0 subnet (Is this necessary?)
    • /etc/resolv.conf
      • Set the correct name servers for your connection
    • /etc/hostname
      • Name the machine what you like

--MichaelCodanti

Using the tar ball

  1. Put drive in laptop, it should show up as /dev/hde (if it doesn't you'll need to adjust the rest of the document accordingly).
  2. Format the disk (if you don't have cfdisk, normal fdisk will do just fine):

    # cfdisk /dev/hde I set my partition table up like this and it seems to work fairly well. {{{hde1 Boot Primary Linux 299.93

hde2 Primary Linux swap 41.15}}}

  • Format the filesystem (we'll upgrade to EXT3 later):

    # mke2fs /dev/hde1

  • Mount the drive:

    # mount /dev/hde1 /mnt

  • Untar the image onto the drive (note the image is compressed with bzip2 so it will require a recent version of tar and the bunzip2 utility), on my laptop this takes 2 or 3 minutes:

    # tar Ixvf /mnt/debian-ap-image-yyyymmdd.tar.bz2 -C /mnt

  • Chroot into the mount point so that you can

    # chroot /mnt

  • Update the filesystem to support EXT3:

    # tune2fs -j /dev/hde1

  • Exit out of the chroot'd environment and run
  • cp /mnt/etc/lilo.conf.install /mnt/etc/lilo.conf

  • Modify /mnt/etc/lilo.conf so the top section reflects the current device name of the drive
  • Make the image bootable with lilo (first # exit out of the chroot'ed environment):

    # lilo -r /mnt -C /etc/lilo.conf

  • Boot the drive up in the Stylistic and then install grub (do this on the Stylistic):

    # grub-install 


[CategoryHowto]

DebianApImage (last edited 2012-03-11 02:31:15 by RussellSenior)