2 gig should be enough assuming you aren't running a lot of BGP peers. Cheers, Robert.
Michael Steinhart wrote: > Thanks, > > The system has 2GB ram. Will that be sufficient? > By looking at the operational system I was able to see > that unionfs was running. I have tested it manually and it > is working. I will be adding the lines to the fstab. > > > The configuration of the system is. > > System: 1U Supermicro 5015M-MF+ > Processor: P4 Dual-Core at 1.8GHz, 800MHz FSB, 1MB L2 > NIC: Onboard Intel 82573L PCI-e Gigabit LAN > Onboard Intel 82573V PCI-e Gigabit LAN > PCI-X Intel Pro 1000 > RAM: 2GB > Disk – System: IDE to CF adapter – DMA support > 2GB CF Speed 266X > Disk – Config: 1 2GB USB Flash memory disk - Internal > 1 2GB USB Flash memory disk – external / Backup > > > On Mon, 26 Nov 2007 13:19:31 -0800 > Robert Bays <[EMAIL PROTECTED]> wrote: >> Both tmpfs and unionfs are available in vc3. >> >> I wouldn't put all of var under tmpfs unless you never >> plan on using >> packages upgrades of any sort. However to change >> /var/log and /tmp to >> tmpfs file systems you should edit your /etc/fstab to >> add something like >> the following lines... >> >> Make sure you have enough r >> tmpfs /tmp tmpfs nosuid,nodev 0 0 >> tmpfs /var/log tmpfs nosuid,nodev 0 0 >> >> This is safe enough. Obviously, make sure you have >> enough RAM to handle >> your log files... >> >> The more complicated solution would be to install the >> system to boot >> using a union. In order to do that you would need to >> boot the livecd. >> Next create a partition and an ext3 file system on a >> local disk using >> parted or fdisk and mke2fs. Then mount the new >> partition and copy >> /live_media/ to the partition. Finally you will have to >> setup grub by >> hand on that partition. Create your >> <partition>/boot/grub/menu.lst file >> and run grub-install. These are not exact the exact >> steps, but the >> outline should provide enough pointers to get you going. >> this will >> create the root union using tmpfs. You can make >> writable union >> partitions by editing the fstab on the installed system >> after the first >> boot. >> >> Cheers, >> Robert. >> >> James Chapman wrote: >>> Michael Steinhart wrote: >>>> Thanks for a good starting point. tmpfs / unionfs looks >>>> promising. Is tmpfs available on this distribution? >>> Both are in the standard kernel.org sources, though I >>> don't have VC3 to >>> hand right now to check if they're configured in the >>> Vyatta kernels. >>> Even if they were enabled in the Vyatta kernel, startup >>> scripts would >>> need to be modified so you'd need to build the OFR from >>> scratch to do this. >>> >>>> While >>>> doing research on this issue I stumbled across aufs >>>> witch >>>> looks like the proper way to go. Can aufs be implemented >>>> with Vyatta? >>> aufs is still in development. For sure, you could patch >>> the Vyatta >>> kernel with it, but I think unionfs would be fine for >>> /tmp, /var. >>> >>>> On Sun, 25 Nov 2007 17:02:53 +0000 >>>> James Chapman <[EMAIL PROTECTED]> wrote: >>>>> [EMAIL PROTECTED] wrote: >>>>>> I am putting together a new router using VC3 to replace >>>>>> a >>>>>> Cisco 7507. We no longer need the advanced routing of >>>>>> the >>>>>> 7507 so I am putting together a basic / high performance >>>>>> router. >>>>>> >>>>>> I have installed VC3 to a CF card as the boot device. my >>>>>> thought was that the system would install to a ram disk >>>>>> on >>>>>> boot-up. This dos not appear to be the case. It looks >>>>>> like >>>>>> the CF is being accesses after the load. If it were >>>>>> assessed in read only mode there would be no concern but >>>>>> it seems that the log files are being written to the >>>>>> disk. >>>>>> This is an issue due to the limited number of >>>>>> erase/write >>>>>> cycles such devices have before failure. Flash memory >>>>>> specifications generally allow 10,000 to 1,000,000 write >>>>>> cycles >>>>> The internal wear leveling of SD will increase the life >>>>> of the flash to >>>>> many more than 1,000,000 writes. However, I agree that >>>>> writing log files >>>>> and temporary files to flash will shorten flash life. >>>>> >>>>> Many Embedded Linux products put /var, /tmp, /dev and >>>>> sometimes /etc in >>>>> RAM using tmpfs / unionfs in order to minimize or >>>>> eliminate flash writes >>>>> during normal operation. Files written under those >>>>> directories would of >>>>> course be lost on reboot. But remote syslog could be >>>>> used to store the >>>>> router's log files on a remote server. Would configuring >>>>> remote syslog >>>>> eliminate most flash writes? >>>>> >>>>> An install-time option to put /var, /dev and /tmp into >>>>> RAM would be ideal. >>>>> >>>>> -- >>>>> James Chapman >>>>> Katalix Systems Ltd >>>>> http://www.katalix.com >>>>> Catalysts for your Embedded Linux software development >>>>> >>>> _______________________________________________ >>>> Vyatta-users mailing list >>>> Vyatta-users@mailman.vyatta.com >>>> http://mailman.vyatta.com/mailman/listinfo/vyatta-users >>>> > > _______________________________________________ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
