10:28 p.m.
I have a Pogoplug e02 sitting waiting to be used, and now I am ready to
set it up. I have been using Fedora on my notebooks and Centos on my
servers for a lot of years, so want to stay with what I know. I see that
F18 for ARM was released in Feb:
http://lists.fedoraproject.org/pipermail/arm/2013-February/005314.html
However the instructions I am finding are for the F18 beta. I started with:
http://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
which has both F17 and F18 instructions. At this point, why start with
F17 and have one less year before having to upgrade? But this page
points to:
http://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image
which talks about F18-beta. So what do I have to do to build a F18
production image and is there anything else I need to do?
Oh, the primary use of this system will be as a backup/archive server.
11:23 p.m.
On 04/15/2013 10:28 PM, Robert Moskowitz wrote:
I have a Pogoplug e02 sitting waiting to be used, and now I am ready
to set it up. I have been using Fedora on my notebooks and Centos on
my servers for a lot of years, so want to stay with what I know. I see
that F18 for ARM was released in Feb:
http://lists.fedoraproject.org/pipermail/arm/2013-February/005314.html
However the instructions I am finding are for the F18 beta. I started
with:
http://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
which has both F17 and F18 instructions. At this point, why start
with F17 and have one less year before having to upgrade? But this
page points to:
http://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image
which talks about F18-beta. So what do I have to do to build a F18
production image and is there anything else I need to do?
I don't know about the PogoPlug, but there is an F18 Kirkwood release
image that was tested on GuruPlug:
http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug#Writing_the_...
so maybe that could replace the "Kirkwood#Writing_the_Image" part of the
instructions.
Oh, the primary use of this system will be as a backup/archive server.
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
5:08 a.m.
On 04/16/2013 12:23 AM, David A. Marlin wrote:
On 04/15/2013 10:28 PM, Robert Moskowitz wrote:
> I have a Pogoplug e02 sitting waiting to be used, and now I am ready
> to set it up. I have been using Fedora on my notebooks and Centos on
> my servers for a lot of years, so want to stay with what I know. I
> see that F18 for ARM was released in Feb:
>
> http://lists.fedoraproject.org/pipermail/arm/2013-February/005314.html
>
> However the instructions I am finding are for the F18 beta. I
> started with:
>
> http://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
>
> which has both F17 and F18 instructions. At this point, why start
> with F17 and have one less year before having to upgrade? But this
> page points to:
>
> http://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image
>
>
> which talks about F18-beta. So what do I have to do to build a F18
> production image and is there anything else I need to do?
I don't know about the PogoPlug, but there is an F18 Kirkwood release
image that was tested on GuruPlug:
http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug#Writing_the_...
so maybe that could replace the "Kirkwood#Writing_the_Image" part of
the instructions.
Thanks the instructions for the Pogoplug say it uses the same image as
the Guruplug, only slightly different steps to get it working.
>
> Oh, the primary use of this system will be as a backup/archive server.
>
>
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
4:24 p.m.
New subject: Problems with a pogoplug v02
I have been trying to follow:
http://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
Point of difference, mine is a black pogoplug v02, not a pink or grey...
I built a F18 USB drive on a 8Gb drive following:
http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
I did this from a F18 notebook. When I mount this drive back in to the
notebook, it does not see anything, and disk manager sees the drive as
one partition of unknown linux type.
I then followed the Pogoplug instructions for F18 and rebooted. Of
course there is no reboot command, and no power cycle switch, so the
only way I can see to reboot is unplug and plug back in.
After this power cycle, I attempted to ssh in, and instead of the Fedora
root password,it was the password I assigned via the pogoplug.com enable
SSH setting. And I ended up in bash.
I am looking at the instructions at
http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
And am I suppose to be using a serial port during this first boot? I do
have a USB serial device, but I would need that on my linux notebook for
a serial port. Oh, wait, I have an old XP notebook with a serial
port... If this USB serial device works, do I use a 'regular' serial
cable (whatever that is these days) and what port settings do I use?
At what point do I restart this install process?
thank you.
Oh 'free' on bash is showing 256Mb of memory?
On 04/16/2013 06:08 AM, Robert Moskowitz wrote:
On 04/16/2013 12:23 AM, David A. Marlin wrote:
> On 04/15/2013 10:28 PM, Robert Moskowitz wrote:
>> I have a Pogoplug e02 sitting waiting to be used, and now I am ready
>> to set it up. I have been using Fedora on my notebooks and Centos
>> on my servers for a lot of years, so want to stay with what I know.
>> I see that F18 for ARM was released in Feb:
>>
>> http://lists.fedoraproject.org/pipermail/arm/2013-February/005314.html
>>
>> However the instructions I am finding are for the F18 beta. I
>> started with:
>>
>> http://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
>>
>> which has both F17 and F18 instructions. At this point, why start
>> with F17 and have one less year before having to upgrade? But this
>> page points to:
>>
>> http://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image
>>
>>
>> which talks about F18-beta. So what do I have to do to build a F18
>> production image and is there anything else I need to do?
>
> I don't know about the PogoPlug, but there is an F18 Kirkwood release
> image that was tested on GuruPlug:
>
> http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug#Writing_the_...
>
>
> so maybe that could replace the "Kirkwood#Writing_the_Image" part of
> the instructions.
Thanks the instructions for the Pogoplug say it uses the same image as
the Guruplug, only slightly different steps to get it working.
>
>
>>
>> Oh, the primary use of this system will be as a backup/archive server.
>>
>>
>> _______________________________________________
>> arm mailing list
>> arm(a)lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/arm
>
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
4:40 p.m.
New subject: Problems with a pogoplug v02
On 04/16/2013 05:24 PM, Robert Moskowitz wrote:
I have been trying to follow:
http://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
Point of difference, mine is a black pogoplug v02, not a pink or grey...
I know they had done black casings, but not personally seen any of the
V2s in Black.
I built a F18 USB drive on a 8Gb drive following:
http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
I did this from a F18 notebook. When I mount this drive back in to the
notebook, it does not see anything, and disk manager sees the drive as
one partition of unknown linux type.
I then followed the Pogoplug instructions for F18 and rebooted. Of
course there is no reboot command, and no power cycle switch, so the
only way I can see to reboot is unplug and plug back in.
I do recall the reboot command being missing, but there was a way to
reboot it, I think 'init 6' still works. But it's been about a half year
since I touched mine.
There have been a fair bit of changes since I did a major update of
those instructions for early F17. I'll try to look them over tonight
with one of my Pogoplugs.
After this power cycle, I attempted to ssh in, and instead of the
Fedora
root password,it was the password I assigned via the pogoplug.com enable
SSH setting. And I ended up in bash.
So it did not boot to fedora, your still in the PogoPlug's native linux.
I am looking at the instructions at
http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
And am I suppose to be using a serial port during this first boot? I do
have a USB serial device, but I would need that on my linux notebook for
a serial port. Oh, wait, I have an old XP notebook with a serial
port... If this USB serial device works, do I use a 'regular' serial
cable (whatever that is these days) and what port settings do I use?
/!\ Do Not Use a normal serial adapter/port! The logic levels will be at
12volts and will fry your pogoplugs UART.
The pogoplus expects 3.3V logic level.
I personally use one these https://www.sparkfun.com/products/9873
At what point do I restart this install process?
thank you.
Oh 'free' on bash is showing 256Mb of memory?
Yes, those Pogoplugs only came 256Mb.
--
Scott Sullivan
4:53 p.m.
New subject: Problems with a pogoplug v02
On 04/16/2013 05:40 PM, Scott Sullivan wrote:
On 04/16/2013 05:24 PM, Robert Moskowitz wrote:
> I have been trying to follow:
>
> http://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
>
> Point of difference, mine is a black pogoplug v02, not a pink or grey...
I know they had done black casings, but not personally seen any of the
V2s in Black.
> I built a F18 USB drive on a 8Gb drive following:
>
> http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
>
> I did this from a F18 notebook. When I mount this drive back in to the
> notebook, it does not see anything, and disk manager sees the drive as
> one partition of unknown linux type.
>
> I then followed the Pogoplug instructions for F18 and rebooted. Of
> course there is no reboot command, and no power cycle switch, so the
> only way I can see to reboot is unplug and plug back in.
I do recall the reboot command being missing, but there was a way to
reboot it, I think 'init 6' still works. But it's been about a half
year since I touched mine.
There have been a fair bit of changes since I did a major update of
those instructions for early F17. I'll try to look them over tonight
with one of my Pogoplugs.
I can wait until tonight. This has been on my todo list since I picked
up this pogoplug back in the fall.
After this power cycle, I attempted to ssh in, and instead of the
Fedora
> root password,it was the password I assigned via the pogoplug.com enable
> SSH setting. And I ended up in bash.
So it did not boot to fedora, your still in the PogoPlug's native linux.
So it seems.
> I am looking at the instructions at
>
> http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
>
> And am I suppose to be using a serial port during this first boot? I do
> have a USB serial device, but I would need that on my linux notebook for
> a serial port. Oh, wait, I have an old XP notebook with a serial
> port... If this USB serial device works, do I use a 'regular' serial
> cable (whatever that is these days) and what port settings do I use?
/!\ Do Not Use a normal serial adapter/port! The logic levels will be
at 12volts and will fry your pogoplugs UART.
The pogoplus expects 3.3V logic level.
I personally use one these https://www.sparkfun.com/products/9873
We are talking about 2 different things. I thought the instructions
meant I use on of the USB-to-serial dongles like one of these:
http://www.iogear.com/product/GUC232A/
> At what point do I restart this install process?
>
> thank you.
>
> Oh 'free' on bash is showing 256Mb of memory?
Yes, those Pogoplugs only came 256Mb.
Well all I really want it for is a backup server running rsyncd. Thought
samba stuff would be nice but not necessary.
5:58 p.m.
New subject: Problems with a pogoplug v02
On 04/16/2013 05:40 PM, Scott Sullivan wrote:
On 04/16/2013 05:24 PM, Robert Moskowitz wrote: I am looking at the
instructions at
>
> http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
>
> And am I suppose to be using a serial port during this first boot? I do
> have a USB serial device, but I would need that on my linux notebook for
> a serial port. Oh, wait, I have an old XP notebook with a serial
> port... If this USB serial device works, do I use a 'regular' serial
> cable (whatever that is these days) and what port settings do I use?
/!\ Do Not Use a normal serial adapter/port! The logic levels will be
at 12volts and will fry your pogoplugs UART.
The pogoplus expects 3.3V logic level.
I personally use one these https://www.sparkfun.com/products/9873
Where does this get plugged into? Do I break open the case? All I see
on the outside is power, LAN, and 4 USB ports.
7:58 p.m.
New subject: Problems with a pogoplug v02
On 04/16/2013 06:58 PM, Robert Moskowitz wrote:
On 04/16/2013 05:40 PM, Scott Sullivan wrote:
> On 04/16/2013 05:24 PM, Robert Moskowitz wrote: I am looking at the
> instructions at
>>
>> http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
>>
>> And am I suppose to be using a serial port during this first boot? I do
>> have a USB serial device, but I would need that on my linux notebook for
>> a serial port. Oh, wait, I have an old XP notebook with a serial
>> port... If this USB serial device works, do I use a 'regular' serial
>> cable (whatever that is these days) and what port settings do I use?
>
> /!\ Do Not Use a normal serial adapter/port! The logic levels will be
> at 12volts and will fry your pogoplugs UART.
>
> The pogoplus expects 3.3V logic level.
> I personally use one these https://www.sparkfun.com/products/9873
Where does this get plugged into? Do I break open the case? All I see
on the outside is power, LAN, and 4 USB ports.
Internal Header, this is a good photo.
http://www.hack247.co.uk/hack247/wp-content/uploads/serialport.jpg
I've got a little adapter cable I built to go from the JST connector for
the serial to the correct pins on that USB to 3.3v Serial adapter.
You'll find the vast majority of arm devices do not have proper 12v
RS232. Instead they have a UART which is serial with only the TX, RX and
GND lines. The usually operate at the core logic voltage of the SoC and
if you apply the wrong voltage you'll fry the UART.
Most of my devices have had 3.3v serial UARTs including the openWRT
capable routers I experiment with, so I invested in that adapter. It's
served me rather well as I can easily us jumper wires for custom adapter
cables for each board.
--
Scott Sullivan
8:26 p.m.
New subject: Problems with a pogoplug v02
On 04/16/2013 08:58 PM, Scott Sullivan wrote:
On 04/16/2013 06:58 PM, Robert Moskowitz wrote:
>
> On 04/16/2013 05:40 PM, Scott Sullivan wrote:
>> On 04/16/2013 05:24 PM, Robert Moskowitz wrote: I am looking at the
>> instructions at
>>>
>>> http://fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
>>>
>>> And am I suppose to be using a serial port during this first boot?
>>> I do
>>> have a USB serial device, but I would need that on my linux
>>> notebook for
>>> a serial port. Oh, wait, I have an old XP notebook with a serial
>>> port... If this USB serial device works, do I use a 'regular'
serial
>>> cable (whatever that is these days) and what port settings do I use?
>>
>> /!\ Do Not Use a normal serial adapter/port! The logic levels will be
>> at 12volts and will fry your pogoplugs UART.
>>
>> The pogoplus expects 3.3V logic level.
>> I personally use one these https://www.sparkfun.com/products/9873
>
> Where does this get plugged into? Do I break open the case? All I see
> on the outside is power, LAN, and 4 USB ports.
Internal Header, this is a good photo.
http://www.hack247.co.uk/hack247/wp-content/uploads/serialport.jpg
I've got a little adapter cable I built to go from the JST connector
for the serial to the correct pins on that USB to 3.3v Serial adapter.
OK. I don't get this. I am not a hardware hacker. Or rather I stopped
that 20 years ago or so.
You'll find the vast majority of arm devices do not have proper 12v
RS232. Instead they have a UART which is serial with only the TX, RX
and GND lines. The usually operate at the core logic voltage of the
SoC and if you apply the wrong voltage you'll fry the UART.
Yet there are the USB to serial devices that work off the 5v USB just
fine. Or fine enough to connect to a serial port on a firewall, switch
or router.
If I plug mine in to the USB, will it be recognized during the boot? Or
does it need Linux running, so it can't be used as a boot monitor?
Most of my devices have had 3.3v serial UARTs including the openWRT
capable routers I experiment with, so I invested in that adapter. It's
served me rather well as I can easily us jumper wires for custom
adapter cables for each board.
So to do this, I am going to have to invest in some hardware. :(
8:53 p.m.
New subject: Problems with a pogoplug v02
On 04/16/2013 09:26 PM, Robert Moskowitz wrote:
On 04/16/2013 08:58 PM, Scott Sullivan wrote:
> You'll find the vast majority of arm devices do not have proper 12v
> RS232. Instead they have a UART which is serial with only the TX, RX
> and GND lines. The usually operate at the core logic voltage of the
> SoC and if you apply the wrong voltage you'll fry the UART.
Yet there are the USB to serial devices that work off the 5v USB just
fine. Or fine enough to connect to a serial port on a firewall, switch
or router.
The serial adapter you linked to is a 'proper'* 12V RS232 adapter. What
it's doing is converting the 5V from the USB power up to the 12V need
for the serial. The USB adapter I have for the pogoplug down converts to
3.3V which is what the UART on the PogoPlug.
Serial signaling is done using voltage changes to indicate logical 1 or
0. http://en.wikipedia.org/wiki/RS-232#Voltage_levels
If you try to use a serial adapter that is the wrong voltage you get
problems ranging from 'doesn't work' becasue the voltage is to low to
register as logical HIGH, all the way to 'doesn't work' because you
applied more voltage then the UART is designed to tolerate.
If I plug mine in to the USB, will it be recognized during the boot?
Or
does it need Linux running, so it can't be used as a boot monitor?
Ah! I get you, your hoping the PogoPlug will see the USB adapter during
boot and auto-configure it as it's console and talk to you. No dice. No
one builds a distro with that much smarts. The serial all the tutorials
are refering to is the UART inside the case where the linux and uboot
consoles are configured to talk on.
>
> Most of my devices have had 3.3v serial UARTs including the openWRT
> capable routers I experiment with, so I invested in that adapter. It's
> served me rather well as I can easily us jumper wires for custom
> adapter cables for each board.
So to do this, I am going to have to invest in some hardware. :(
To use the serial UART console on the pogoplug, yes. But the
instructions on the wiki we're made with the goal that you should not
have to use the serial console.
I've got a USB stick being prepared right now and I've already gone
through the uboot upgrade on one of the few virgin model Pogo-E02 's I have.
I'll post my notes when I'm done.
--
Scott Sullivan
9:31 p.m.
New subject: Problems with a pogoplug v02
On 04/16/2013 09:53 PM, Scott Sullivan wrote:
To use the serial UART console on the pogoplug, yes. But the
instructions on the wiki we're made with the goal that you should not
have to use the serial console.
I've got a USB stick being prepared right now and I've already gone
through the uboot upgrade on one of the few virgin model Pogo-E02 's I
have.
I'll post my notes when I'm done.
So the short of it is that I had no issues following the steps provided
on the wiki. They are actually a lot cleaner then when I did them.
My Notes:
http://revident.net/projects/pogoplug/fedora-18-install/
shell.history
^ This is what I did at the command line. Of note is that I did this at
the serial console because I couldn't get my pogoplug to register to
enable SSH. There should be no applicable difference between doing it
here vs ssh as I've done it from SSH when setting up Fedora 17.
There is a little extra in there from my mounting a spare USB drive to
get the files off as scp didn't work for some reason.
uboot.afterupdate
^ fw_printenv of the uboot settings after I applied the updated uboot.
uboot.fedorachanges
^ fw_printenv of the uboot settings after I applied the fedora 18
specific fw_setenv commands.
All of the above was done and taken from within side the pogoplug linux
environment.
Other things I noticed.
1) I did have the reboot command in the pogoplug linux and it worked as
expected.
2) The loading of the uInitrd took on the order of a minute, but that
might be the microSD+adapter I'm using for the OS image.
3) The fedora instance rebooted itself once after seemingly to finish
booting. It came up fine after that. I had to be patienent for SSH to
come up, was maybe 2-3 minuets.
Compare your uboot environment to what I posted, see if anything is a miss.
--
Scott Sullivan
11:26 a.m.
New subject: Problems with a pogoplug v02
Reboot in process see below.
On 04/16/2013 10:31 PM, Scott Sullivan wrote:
On 04/16/2013 09:53 PM, Scott Sullivan wrote:
> To use the serial UART console on the pogoplug, yes. But the
> instructions on the wiki we're made with the goal that you should not
> have to use the serial console.
>
> I've got a USB stick being prepared right now and I've already gone
> through the uboot upgrade on one of the few virgin model Pogo-E02 's I
> have.
>
> I'll post my notes when I'm done.
>
So the short of it is that I had no issues following the steps
provided on the wiki. They are actually a lot cleaner then when I did
them.
My Notes:
http://revident.net/projects/pogoplug/fedora-18-install/
shell.history
^ This is what I did at the command line. Of note is that I did this
at the serial console because I couldn't get my pogoplug to register
to enable SSH. There should be no applicable difference between doing
it here vs ssh as I've done it from SSH when setting up Fedora 17.
There is a little extra in there from my mounting a spare USB drive to
get the files off as scp didn't work for some reason.
uboot.afterupdate
^ fw_printenv of the uboot settings after I applied the updated uboot.
fw_printenv was not in my path. I had to add /usr/sbin/
I also could not get scp working, and had to mount a usb drive to
capture my work. I DID ssh into the system.
uboot.fedorachanges
^ fw_printenv of the uboot settings after I applied the fedora 18
specific fw_setenv commands.
All of the above was done and taken from within side the pogoplug
linux environment.
Other things I noticed.
1) I did have the reboot command in the pogoplug linux and it worked
as expected.
/sbin/reboot Again not in my path.
I rebooted and am still in the pogo linux bash.
2) The loading of the uInitrd took on the order of a minute, but that
might be the microSD+adapter I'm using for the OS image.
3) The fedora instance rebooted itself once after seemingly to finish
booting. It came up fine after that. I had to be patienent for SSH to
come up, was maybe 2-3 minuets.
One thing I noticed different in your picture than mine, I have the
fedora usb drive in the back top USB port. I did this as a 'safer'
location for it, as well as allowing me to use the front port easily if
needed for a drive. Does this impact line 17 or 22 of your history
output? If so, you need to tell in your notes which USB port to place
the drive in!
Compare your uboot environment to what I posted, see if anything is a
miss.
You will find my files at medon.htt-consult.com/~rgm/pogo
12:09 p.m.
On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:
which talks about F18-beta. So what do I have to do to build a F18
production image and is there anything else I need to do?
Oh, the primary use of this system will be as a backup/archive server.
AFAIK it will not be supported anymore starting with Fedora 19,
therefore you might consider setting up a different distribution.
Regards
Till
12:52 p.m.
On Wed, Apr 17, 2013 at 6:09 PM, Till Maas <opensource(a)till.name> wrote:
On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:
> which talks about F18-beta. So what do I have to do to build a F18
> production image and is there anything else I need to do?
>
> Oh, the primary use of this system will be as a backup/archive server.
AFAIK it will not be supported anymore starting with Fedora 19,
therefore you might consider setting up a different distribution.
That's correct, F-18 will be the last supported armv5tel release. It
will be supported for the entire mainline support cycle so until a
month after the release of Fedora 20.
Peter
1:47 p.m.
On 04/17/2013 01:52 PM, Peter Robinson wrote:
On Wed, Apr 17, 2013 at 6:09 PM, Till Maas
<opensource(a)till.name> wrote:
> On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:
>
>> which talks about F18-beta. So what do I have to do to build a F18
>> production image and is there anything else I need to do?
>>
>> Oh, the primary use of this system will be as a backup/archive server.
> AFAIK it will not be supported anymore starting with Fedora 19,
> therefore you might consider setting up a different distribution.
That's correct, F-18 will be the last supported armv5tel release. It
will be supported for the entire mainline support cycle so until a
month after the release of Fedora 20.
Facinating.
Any writeups as to why Fedora is exiting what will be a major part of
the computing landscape in coming years?
What other options are there out there?
2 p.m.
On 04/17/2013 02:47 PM, Robert Moskowitz wrote:
On 04/17/2013 01:52 PM, Peter Robinson wrote:
> On Wed, Apr 17, 2013 at 6:09 PM, Till Maas <opensource(a)till.name> wrote:
>> On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:
>>
>>> which talks about F18-beta. So what do I have to do to build a F18
>>> production image and is there anything else I need to do?
>>>
>>> Oh, the primary use of this system will be as a backup/archive server.
>> AFAIK it will not be supported anymore starting with Fedora 19,
>> therefore you might consider setting up a different distribution.
> That's correct, F-18 will be the last supported armv5tel release. It
> will be supported for the entire mainline support cycle so until a
> month after the release of Fedora 20.
Facinating.
Any writeups as to why Fedora is exiting what will be a major part of
the computing landscape in coming years?
What other options are there out there?
Their only referring to the armv5tel architecture which the Marvel
Kirkwood is built on. The arm7hfp and aarch64 architecture will continue
and be the primary focus for ARM hardware going forward.
A very bad analogy is like dropping i286 support and only focusing on
i686 and x86_64.
--
Scott Sullivan
2:54 p.m.
On 04/17/2013 03:00 PM, Scott Sullivan wrote:
On 04/17/2013 02:47 PM, Robert Moskowitz wrote:
>
> On 04/17/2013 01:52 PM, Peter Robinson wrote:
>> On Wed, Apr 17, 2013 at 6:09 PM, Till Maas <opensource(a)till.name>
>> wrote:
>>> On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:
>>>
>>>> which talks about F18-beta. So what do I have to do to build a F18
>>>> production image and is there anything else I need to do?
>>>>
>>>> Oh, the primary use of this system will be as a backup/archive
>>>> server.
>>> AFAIK it will not be supported anymore starting with Fedora 19,
>>> therefore you might consider setting up a different distribution.
>> That's correct, F-18 will be the last supported armv5tel release. It
>> will be supported for the entire mainline support cycle so until a
>> month after the release of Fedora 20.
>
> Facinating.
>
> Any writeups as to why Fedora is exiting what will be a major part of
> the computing landscape in coming years?
>
> What other options are there out there?
Their only referring to the armv5tel architecture which the Marvel
Kirkwood is built on. The arm7hfp and aarch64 architecture will
continue and be the primary focus for ARM hardware going forward.
Oh, yes. Now I see. So in perhaps a year, I will have to see what is
hitting ebay with these chips.
A very bad analogy is like dropping i286 support and only focusing on
i686 and x86_64.
Ah, yes I remember well..... I was on a Comdex breakfast panel in '87?
On why to abandon your i286 for the i386. The panel was David House of
Intel, Gates of .... (well you know), Cheryl Curid of General Foods (?
I think I remember), and me of Chrysler. They say my point on the
simplified memory map to support large spreadsheets and word documents
(though it was not Word at that time!) was the 'winning' point.
Particularly to this young guy who was seated at my table: Michael Dell...
Yes, OS/2 2.0 was a GREAT operating system! :)' Long live LU6.2 SNA!
2:21 p.m.
On Wed, Apr 17, 2013 at 7:47 PM, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
On 04/17/2013 01:52 PM, Peter Robinson wrote:
>
> On Wed, Apr 17, 2013 at 6:09 PM, Till Maas <opensource(a)till.name> wrote:
>>
>> On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:
>>
>>> which talks about F18-beta. So what do I have to do to build a F18
>>> production image and is there anything else I need to do?
>>>
>>> Oh, the primary use of this system will be as a backup/archive server.
>>
>> AFAIK it will not be supported anymore starting with Fedora 19,
>> therefore you might consider setting up a different distribution.
>
> That's correct, F-18 will be the last supported armv5tel release. It
> will be supported for the entire mainline support cycle so until a
> month after the release of Fedora 20.
Facinating.
Any writeups as to why Fedora is exiting what will be a major part of the
computing landscape in coming years?
We're not exiting the ARM landscape, we're discontinuing support for
older ARM chipsets based on the ARMv5 designs. We're doing this
because there was only every very few devices that were workable with
Fedora (256Mb+ RAM and some other bits) and ARM has discontinued the
ARMv5 platforms because they've been replaced with equivalent
cost/feature/power equivalents in the ARMv7 Cortex-Ax series of
processors. They also are dependent on older HW like DDR1 RAM which is
also getting more expensive.
What other options are there out there?
ARMv7 hardware such as a BeagleBone, PandaBoard, a number of different
Marvell devices based on the Armada chipset.
There's also the upcoming aarch64 platforms.
Peter
3:04 p.m.
On 04/17/2013 03:21 PM, Peter Robinson wrote:
On Wed, Apr 17, 2013 at 7:47 PM, Robert Moskowitz
<rgm(a)htt-consult.com> wrote:
> On 04/17/2013 01:52 PM, Peter Robinson wrote:
>> On Wed, Apr 17, 2013 at 6:09 PM, Till Maas <opensource(a)till.name> wrote:
>>> On Mon, Apr 15, 2013 at 11:28:12PM -0400, Robert Moskowitz wrote:
>>>
>>>> which talks about F18-beta. So what do I have to do to build a F18
>>>> production image and is there anything else I need to do?
>>>>
>>>> Oh, the primary use of this system will be as a backup/archive server.
>>> AFAIK it will not be supported anymore starting with Fedora 19,
>>> therefore you might consider setting up a different distribution.
>> That's correct, F-18 will be the last supported armv5tel release. It
>> will be supported for the entire mainline support cycle so until a
>> month after the release of Fedora 20.
>
> Facinating.
>
> Any writeups as to why Fedora is exiting what will be a major part of the
> computing landscape in coming years?
We're not exiting the ARM landscape, we're discontinuing support for
older ARM chipsets based on the ARMv5 designs. We're doing this
because there was only every very few devices that were workable with
Fedora (256Mb+ RAM and some other bits) and ARM has discontinued the
ARMv5 platforms because they've been replaced with equivalent
cost/feature/power equivalents in the ARMv7 Cortex-Ax series of
processors. They also are dependent on older HW like DDR1 RAM which is
also getting more expensive.
> What other options are there out there?
ARMv7 hardware such as a BeagleBone, PandaBoard, a number of different
Marvell devices based on the Armada chipset.
There's also the upcoming aarch64 platforms.
I meant distros :)
But with this information, I will be staying with Fedora, but Redsleeve
looks interesting (I run a number of Centos boxes here and just brought
up my 1st ClearOS box). But with only two developers and everything
still 'by hand', it reminds me too much of my Whitehat days.
I looked at OpenWRT for pogoplug and got scared off. I am not a role
your own kernel kind of person.
So I will be looking at alternative boxes probably the end of the year.
I still have too much to upgrade here. But I would be interested in
some router/firewalls that I could run something like Shorewall on. Or
something with a GUI. Build on Fedora. 3 boxes. One with 3 interfaces
(one to my ISP and two to the others) and the others with at least 6
interfaces. 100Mb is fast enough. My single Juniper SSG5 is becoming a
problem.
4032
days inactive
4033
days old
18 comments
5 participants
participants (5)
-
d.marlin -
Peter Robinson -
Robert Moskowitz -
Scott Sullivan -
Till Maas