| 00:08.53 | *** join/##pxe mick__ (n=mick@teksup41.lnk.telstra.net) |
| 00:09.32 | *** join/##pxe map7work (n=mick@teksup41.lnk.telstra.net) |
| 00:09.59 | map7work | Is it possible to get a WIFI device which can PXE-boot? |
| 02:25.09 | *** join/##pxe map7work (n=mick@teksup41.lnk.telstra.net) |
| 05:05.13 | ScytheBlade1 | map7work, nope |
| 05:06.03 | ScytheBlade1 | map7work, realize this: with wifi, you have to setup the link layer.. specify which AP to connect to, encryption, the works |
| 05:06.13 | ScytheBlade1 | ethernet, you just plug it in and the link layer is configured |
| 05:06.34 | map7work | so the BIOs is not smart enough to do this operation? |
| 05:07.04 | ScytheBlade1 | Nope |
| 05:08.14 | map7work | So you would have to run an OS just so you can create that link, then connect to the server? |
| 05:08.24 | ScytheBlade1 | yup |
| 05:11.18 | map7work | Are there any boot loaders such as GRUB which could create this link? |
| 05:11.25 | ScytheBlade1 | Nope |
| 05:11.26 | ScytheBlade1 | None |
| 05:11.39 | ScytheBlade1 | further, PXE downloads and runs a boot loader |
| 05:11.49 | ScytheBlade1 | You'd have to store this in some physical medium on the computer first |
| 05:13.03 | map7work | Hmmm, I've been doing some research and sometimes I've seen people use PXE-LINUX chips instead of PXEBOOT chips, what's the difference? |
| 05:13.59 | ScytheBlade1 | I've never heard of pxelinux chips |
| 08:23.21 | *** join/##pxe Norky (n=dan@milton.ocsl.co.uk) |
| 09:47.16 | *** join/##pxe deny__ (n=andy@adsl-69-210-244-25.dsl.chcgil.ameritech.net) |
| 09:55.16 | *** join/##pxe deny_ (n=andy@adsl-69-210-247-27.dsl.chcgil.ameritech.net) |
| 10:03.16 | *** join/##pxe deny__ (n=andy@adsl-69-211-0-143.dsl.chcgil.ameritech.net) |
| 10:18.00 | *** join/##pxe Norky_ (n=dan@milton.ocsl.co.uk) |
| 14:50.38 | *** join/##pxe PacketScan (n=PacketSc@ool-45763453.dyn.optonline.net) |
| 15:56.01 | *** join/##pxe SB1-Work (n=kylesb@about/pxe/ScytheBlade1) |