Huge Log files

This forum is for all other ARMv5 devices

Re: Huge Log files

Postby slycat » Thu Jun 09, 2011 8:30 pm

Sorry bout that WHSE. Here's my info
$this->bbcode_second_pass_code('', '[root@Arch Linux ARM install ~]# pacman -Q udev
udev 171-1
[root@Arch Linux ARM install ~]# uname -a
Linux Arch Linux ARM install 2.6.31.6_SMP_820 #101 SMP Tue Apr 12 20:34:36 UTC 2011 armv6l ARMv6-compatible processor rev 5 (v6l) Oxsemi NAS GNU/Linux')
Currently syslog-ng is off and udevd was rebooted, running constant 7-9%cpu

ALSO I had to shutoff hd-idle as it kept crashing my plug when it tried to sleep the USB HDD. Not sure what's causing it or if it is related to this issue, but it never did it before.
Pogoplug Pro w/ Wireless User -> decomm.
Cubox-i4pro User
4TB eSATA HDD (8g/3700+ Sw/Storage)
Kodi / Transmission / Minidlna / Samba / Batch-audio-conversions / Lighttpd
------------------------------
Rollback Machine - Thanks to impatt
slycat
 
Posts: 169
Joined: Wed Feb 09, 2011 3:07 am
Location: Miami, FL

Re: Huge Log files

Postby kmihelich » Fri Jun 10, 2011 5:26 am

udev bumped to 171-2 today, does that help at all?
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: Huge Log files

Postby slycat » Fri Jun 10, 2011 5:42 am

$this->bbcode_second_pass_quote('kmihelich', 'u')dev bumped to 171-2 today, does that help at all?

Backing up my drive (hopefully migrate to sata connection drive soon), once done I'll test this out.

EDIT: rebooted with syslog-ng and udevd enabled after updates. No log barfing. udevd fluxes between 6-10%cpu, but no logging to daemon.log.

$this->bbcode_second_pass_code('', ' PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
361 root 20 0 2112 836 544 S 7 0.7 4:02.07 udevd

# du -h /var/log/*.log
0 /var/log/auth.log
120K /var/log/crond.log
0 /var/log/daemon.log
16K /var/log/dmesg.log
0 /var/log/errors.log
0 /var/log/everything.log
40K /var/log/hd-idle.log
540K /var/log/kernel.log
8.0K /var/log/lpr.log
0 /var/log/messages.log
4.0K /var/log/minidlna.log
200K /var/log/pacman.log
16K /var/log/syslog.log
4.0K /var/log/user.log')

Even mounted a drive in /media, disabled automounting (pesky bastard), and no power-hogging or log-barfing. Guess we'll see what happens to everyone else :)
Last edited by slycat on Fri Jun 10, 2011 7:13 am, edited 1 time in total.
Pogoplug Pro w/ Wireless User -> decomm.
Cubox-i4pro User
4TB eSATA HDD (8g/3700+ Sw/Storage)
Kodi / Transmission / Minidlna / Samba / Batch-audio-conversions / Lighttpd
------------------------------
Rollback Machine - Thanks to impatt
slycat
 
Posts: 169
Joined: Wed Feb 09, 2011 3:07 am
Location: Miami, FL

Re: Huge Log files

Postby ohthanks » Fri Jun 10, 2011 6:39 am

been having the same issues on a new pink plug I bought during the buy.com sale.

updating to 171-2 didn't seem to resolve anything for me. Commenting out $this->bbcode_second_pass_code('', '/sbin/udevadm settle --quiet --timeout=${UDEV_TIMEOUT:-30}') from rc.sysitit allows it to boot without any of the logging issues, so it does seem to be related to the settle command.

I'm unable to get it to boot with any usb drives attached though, just a flashing green until I pull the drives out and restart it. Then no problems. Plugging them back in with udevd running is fine and it detects/mounts them with no trouble. I assumed this was related to udevd being weird, but I'm not really sure now, any suggestions would be appreciated.
ohthanks
 
Posts: 1
Joined: Fri Jun 10, 2011 5:40 am

Re: Huge Log files

Postby pepedog » Fri Jun 10, 2011 7:53 am

I have a dockstar which I always leave updates lagging, so comparing rc.sysinit (old one date 3rd April) produced a staggering amount of changes, but that entry was-
/sbin/udevadm settle

Here is my old rc.sysinit
$this->bbcode_second_pass_code('', '#!/bin/bash
#
# /etc/rc.sysinit
#

. /etc/rc.conf
. /etc/rc.d/functions

echo " "
printhl "Arch Linux ARM Linux\n"
printhl "${C_H2}http://www.Arch Linux ARM.com"
printhl "Copyright 2009-2011 Mike Staszel"
printhl "Distributed under the GNU General Public License (GPL)"
printsep

run_hook sysinit_start

# mount /proc, /sys and our RAM /dev
if ! /bin/mountpoint -q /proc; then
/bin/mount -n -t proc none /proc
fi
if ! /bin/mountpoint -q /sys; then
/bin/mount -n -t sysfs none /sys
fi
if ! /bin/mountpoint -q /dev; then
if grep -q devtmpfs /proc/filesystems 2>/dev/null; then
/bin/mount -n -t devtmpfs udev /dev -o mode=0755,size=10M,nosuid
else
/bin/mount -n -t tmpfs udev /dev -o mode=0755,size=10M,nosuid
fi
fi

# Copy static device nodes to /dev
/bin/cp -a /lib/udev/devices/* /dev/

# start up our mini logger until syslog takes over
/sbin/minilogd

# anything more serious than KERN_WARNING goes to the console
# 'verbose' cmdline parameter enables more messages
if /bin/grep -q " verbose" /proc/cmdline; then
/bin/dmesg -n 8
else
/bin/dmesg -n 3
fi

HWCLOCK_PARAMS="--hctosys"
if [ "$HARDWARECLOCK" = "UTC" ]; then
HWCLOCK_PARAMS="$HWCLOCK_PARAMS --utc"
elif [ "$HARDWARECLOCK" = "localtime" ]; then
HWCLOCK_PARAMS="$HWCLOCK_PARAMS --localtime"
else
HWCLOCK_PARAMS=""
fi

if [ -n "$HWCLOCK_PARAMS" ]; then
# enable rtc access
/sbin/modprobe -q rtc-cmos
# some custom kernels use rtc/genrtc, try to load those too
/sbin/modprobe -q rtc
/sbin/modprobe -q genrtc
# If devtmpfs is used, the required RTC device already exists now
# Otherwise, create whatever device is available
if [ ! -c /dev/rtc -a ! -c /dev/rtc0 ]; then
if [ -f /sys/class/rtc/rtc0/dev ]; then
IFS=: read -r major minor < /sys/class/rtc/rtc0/dev
/bin/mknod /dev/rtc0 c $major $minor
elif [ -f /sys/class/misc/rtc/dev ]; then
IFS=: read -r major minor < /sys/class/misc/rtc/dev
/bin/mknod /dev/rtc c $major $minor
fi
fi

# Do a clock set here for a few reasons:
# 1. Make creation time on udev nodes sane (FS#8665)
# 2. Filesystem checks can depend on system time
# 3. This will set the clock, if using non-UTC, off the last known
# configured timezone. Any new timezone put in rc.conf is copied over at
# a later time.
# This does *NOT* take into account a time adjustment file as /var may not be
# mounted yet. A second set occurs later to match rc.conf.
if [ -f /etc/localtime ]; then
/sbin/hwclock $HWCLOCK_PARAMS --noadjfile
fi
fi

echo > /proc/sys/kernel/hotplug

stat_busy "Starting UDev Daemon"
/sbin/udevd --daemon
stat_done

run_hook sysinit_udevlaunched

# Trigger udev uevents
if /bin/pidof -o %PPID /sbin/udevd >/dev/null; then
stat_busy "Triggering UDev uevents"
/sbin/udevadm control --property=STARTUP=1
/sbin/udevadm trigger --action=add
stat_done
fi

# Load modules from the MODULES array defined in rc.conf
if ! [ "$load_modules" = "off" ]; then
if [ -f /proc/modules ]; then
stat_busy "Loading Modules"
for mod in "${MODULES[@]}"; do
if [ "$mod" = "${mod#!}" ]; then
/sbin/modprobe $mod
fi
done
stat_done
fi
fi

# Wait for udev uevents
if /bin/pidof -o %PPID /sbin/udevd >/dev/null; then
stat_busy "Waiting for UDev uevents to be processed"
/sbin/udevadm settle
/sbin/udevadm control --property=STARTUP=
stat_done
fi

run_hook sysinit_udevsettled

# bring up the loopback interface
if [ -d /sys/class/net/lo ]; then
stat_busy "Bringing up loopback interface"
/sbin/ifconfig lo 127.0.0.1 up
if [ $? -ne 0 ]; then
stat_fail
else
stat_done
fi
fi

# If necessary, find md devices and manually assemble RAID arrays
if [ -f /etc/mdadm.conf -a "$(/bin/grep ^ARRAY /etc/mdadm.conf 2>/dev/null)" ]; then
status "Activating RAID arrays" /sbin/mdadm --assemble --scan
fi

if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then
if [ -x /sbin/lvm -a -d /sys/block ]; then
# Kernel 2.6.x, LVM2 groups
/sbin/modprobe -q dm-mod 2>/dev/null
stat_busy "Activating LVM2 groups"
/sbin/lvm vgchange --ignorelockingfailure -a y >/dev/null
if [ $? -ne 0 ]; then
stat_fail
else
stat_done
fi
fi
fi

# Set up non-root encrypted partition mappings
if [ -f /etc/crypttab -a -n "$(/bin/grep -v ^# /etc/crypttab | /bin/grep -v ^$)" ]; then
/sbin/modprobe -q dm-mod 2>/dev/null
stat_busy "Unlocking encrypted volumes:"
csfailed=0
# Arch cryptsetup packages traditionally contained the binaries
# /usr/sbin/cryptsetup
# /sbin/cryptsetup.static
# By default, initscripts used the /sbin/cryptsetup.static.
# Newer packages will only have /sbin/cryptsetup and no static binary
# This ensures maximal compatibility with the old and new layout
if [ -x /sbin/cryptsetup ]; then
CS=/sbin/cryptsetup
elif [ -x /usr/sbin/cryptsetup ]; then
CS=/usr/sbin/cryptsetup
else
CS=/sbin/cryptsetup.static
fi
do_crypt() {
if [ $# -ge 3 ]; then
cname="$1"
csrc="$2"
cpass="$3"
shift 3
copts="$*"
stat_append "${cname}.."
# For some fun reason, the parameter ordering varies for
# LUKS and non-LUKS devices. Joy.
if [ "${cpass}" = "SWAP" ]; then
# This is DANGEROUS! The only possible safety check
# is to not proceed in case we find a LUKS device
# This may cause dataloss if it is not used carefully
if $CS isLuks $csrc 2>/dev/null; then
false
else
$CS -d /dev/urandom $copts create $cname $csrc >/dev/null
if [ $? -eq 0 ]; then
stat_append "creating swapspace.."
/sbin/mkswap -f -L $cname /dev/mapper/$cname >/dev/null
fi
fi
elif [ "${cpass}" = "ASK" ]; then
printf "\nOpening '${cname}' volume:\n"

if $CS isLuks $csrc 2>/dev/null; then
$CS $copts luksOpen $csrc $cname < /dev/console
else
$CS $copts create $cname $csrc < /dev/console
fi
elif [ "${cpass:0:1}" != "/" ]; then
if $CS isLuks $csrc 2>/dev/null; then
echo "$cpass" | $CS $copts luksOpen $csrc $cname >/dev/null
else
echo "$cpass" | $CS $copts create $cname $csrc >/dev/null
fi
else
if $CS isLuks $csrc 2>/dev/null; then
$CS -d $cpass $copts luksOpen $csrc $cname >/dev/null
else
$CS -d $cpass $copts create $cname $csrc >/dev/null
fi
fi
if [ $? -ne 0 ]; then
csfailed=1
stat_append "failed "
else
stat_append "ok "
fi
fi
}
while read line; do
eval do_crypt "$line"
done </etc/crypttab
if [ $csfailed -eq 0 ]; then
stat_done
else
stat_fail
fi
# Maybe someone has LVM on an encrypted block device
if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then
if [ -x /sbin/lvm -a -d /sys/block ]; then
/sbin/lvm vgchange --ignorelockingfailure -a y >/dev/null
fi
fi
fi

status "Mounting Root Read-only" /bin/mount -n -o remount,ro /

FORCEFSCK=
[ -f /forcefsck ] && FORCEFSCK="-- -f"
NETFS="nonfs,nonfs4,nosmbfs,nocifs,nocodafs,noncpfs,nosysfs,noshfs,nofuse,nofuseblk,noglusterfs"

fsck_reboot() {
echo "Automatic reboot in progress..."
/bin/umount -a
/bin/mount -n -o remount,ro /
/sbin/reboot -f
exit 0
}

if [ -x /sbin/fsck ]; then
stat_busy "Checking Filesystems"
FSCK_OUT=/dev/stdout
FSCK_ERR=/dev/stdout
FSCK_FD=
run_hook sysinit_prefsck
/sbin/fsck -A -T -C$FSCK_FD -a -t "$NETFS,noopts=_netdev" $FORCEFSCK >$FSCK_OUT 2>$FSCK_ERR
fsckret=$?
if [ ${fsckret} -gt 1 ]; then
stat_fail
fi
run_hook sysinit_postfsck
if [ $((${fsckret}&2)) -eq 2 ]; then
echo
echo "********************** REBOOT REQUIRED *********************"
echo "* *"
echo "* The system will be rebooted automatically in 15 seconds. *"
echo "* *"
echo "************************************************************"
echo
/bin/sleep 15
fsck_reboot
fi
if [ ${fsckret} -gt 1 -a ${fsckret} -ne 32 ]; then
echo
echo "***************** FILESYSTEM CHECK FAILED ****************"
echo "* *"
echo "* Please repair manually and reboot. Note that the root *"
echo "* file system is currently mounted read-only. To remount *"
echo "* it read-write type: mount -n -o remount,rw / *"
echo "* When you exit the maintenance shell the system will *"
echo "* reboot automatically. *"
echo "* *"
echo "************************************************************"
echo
/sbin/sulogin -p
fsck_reboot
fi
stat_done
fi

stat_busy "Mounting Local Filesystems"
/bin/mount -n -o remount,rw /
if [ -x /bin/findmnt -a -e /proc/self/mountinfo ]; then
/bin/findmnt -rnu -o SOURCE,TARGET,FSTYPE,OPTIONS >| /etc/mtab
else
cat /proc/mounts >| /etc/mtab
fi
run_hook sysinit_premount
# now mount all the local filesystems
/bin/mount -a -t $NETFS -O no_netdev
stat_done

status "Activating Swap" /sbin/swapon -a

stat_busy "Configuring System Clock"
if [ "$TIMEZONE" != "" -a -e "/usr/share/zoneinfo/$TIMEZONE" ]; then
/bin/rm -f /etc/localtime
/bin/cp "/usr/share/zoneinfo/$TIMEZONE" /etc/localtime
fi

clock_pid=""
if [ -n "$HWCLOCK_PARAMS" ]; then
# This time, we set the clock for real. Use the adjustment file now that
# /var will definitely be available, and then set the system clock once
# the hardware clock has been adjusted accordingly. The backgrounding magic
# is due to the fact that the second call to hwclock will almost always
# take ~1 second because of the clock granularity, and we might as well
# stay busy.
(
/sbin/hwclock --adjust
/sbin/hwclock $HWCLOCK_PARAMS
) &
clock_pid=$!
fi
stat_done

RANDOM_SEED=/var/lib/misc/random-seed
if [ -f $RANDOM_SEED ]; then
stat_busy "Initializing Random Seed"
/bin/cat $RANDOM_SEED > /dev/urandom
stat_done
fi

stat_busy "Removing Leftover Files"
/bin/rm -f /etc/nologin &>/dev/null
/bin/rm -f /etc/shutdownpid &>/dev/null
/bin/rm -f /var/lock/* &>/dev/null
/bin/rm -rf /tmp/* /tmp/.* &>/dev/null
/bin/rm -f /forcefsck &>/dev/null
(cd /var/run && /usr/bin/find . ! -type d -exec /bin/rm -f -- {} \; )
: >| /var/run/utmp
/bin/chmod 0664 /var/run/utmp
# Keep {x,k,g}dm happy with xorg
/bin/mkdir /tmp/.ICE-unix && /bin/chmod 1777 /tmp/.ICE-unix
/bin/mkdir /tmp/.X11-unix && /bin/chmod 1777 /tmp/.X11-unix
stat_done

#status "Updating Shared Library Links" /sbin/ldconfig

if [ "$HOSTNAME" != "" ]; then
status "Setting Hostname: $HOSTNAME" /bin/hostname $HOSTNAME
fi

# Set the NIS domain name, if necessary
[ -f /etc/conf.d/nisdomainname ] && . /etc/conf.d/nisdomainname
if [ "$NISDOMAINNAME" != "" ]; then
status "Setting NIS Domain Name: $NISDOMAINNAME" /bin/nisdomainname $NISDOMAINNAME
fi

status "Updating Module Dependencies" /sbin/depmod -A

# Flush old locale settings
: >| /etc/profile.d/locale.sh
/bin/chmod 755 /etc/profile.d/locale.sh
# Set user defined locale
[ -z "$LOCALE" ] && LOCALE="en_US"
stat_busy "Setting Locale: $LOCALE"
echo "export LANG=$LOCALE" >>/etc/profile.d/locale.sh
stat_done

if echo "$LOCALE" | /bin/grep -qi utf ; then
stat_busy "Setting Consoles to UTF-8 mode"
# UTF-8 consoles are default since 2.6.24 kernel
# this code is needed not only for older kernels,
# but also when user has set vt.default_utf8=0 but LOCALE is *.UTF-8.
for i in /dev/tty[0-9]*; do
/usr/bin/kbd_mode -u < ${i}
printf "\033%%G" > ${i}
done
# the $CONSOLE check helps us avoid this when running scripts from cron
echo 'if [ "$CONSOLE" = "" -a "$TERM" = "linux" -a -t 1 ]; then printf "\033%%G"; fi' >>/etc/profile.d/locale.sh
stat_done
[ -n "$KEYMAP" ] && status "Loading Keyboard Map: $KEYMAP" /bin/loadkeys -q -u $KEYMAP
else
stat_busy "Setting Consoles to legacy mode"
# make non-UTF-8 consoles work on 2.6.24 and newer kernels
for i in /dev/tty[0-9]*; do
/usr/bin/kbd_mode -a < ${i}
printf "\033%%@" > ${i}
done
# the $CONSOLE check helps us avoid this when running scripts from cron
echo 'if [ "$CONSOLE" = "" -a "$TERM" = "linux" -a -t 1 ]; then printf "\033%%@"; fi' >>/etc/profile.d/locale.sh
stat_done
[ -n "$KEYMAP" ] && status "Loading Keyboard Map: $KEYMAP" /bin/loadkeys -q $KEYMAP
fi

# Set console font if required
set_consolefont

# Adding persistent network/cdrom generated rules
if [ -f "/dev/.udev/tmp-rules--70-persistent-cd.rules" ]; then
stat_busy "Adding persistent cdrom udev rules"
/bin/cat /dev/.udev/tmp-rules--70-persistent-cd.rules >> /etc/udev/rules.d/70-persistent-cd.rules
stat_done
fi
if [ -f "/dev/.udev/tmp-rules--70-persistent-net.rules" ]; then
stat_busy "Adding persistent network udev rules"
/bin/cat /dev/.udev/tmp-rules--70-persistent-net.rules >> /etc/udev/rules.d/70-persistent-net.rules
stat_done
fi

/bin/dmesg >| /var/log/dmesg.log

# final hwclock setting needs to be done at this point
if [ -n "$clock_pid" ]; then
wait $clock_pid
fi

run_hook sysinit_end

# End of file
# vim: set ts=2 sw=2 noet:
')
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Huge Log files

Postby devr » Fri Jun 10, 2011 12:22 pm

This mornings udev update on my PogoPlug Pro did not help. When I ran the update, this is what updated:
$this->bbcode_second_pass_code('', '[2011-06-10 07:44] Running 'pacman -Su'
[2011-06-10 07:44] starting full system upgrade
[2011-06-10 07:45] upgraded glib2 (2.28.7-1 -> 2.28.8-1)
[2011-06-10 07:45] upgraded inputproto (2.0.1-1 -> 2.0.2-1)
[2011-06-10 07:45] upgraded net-tools (1.60-14 -> 1.60-16)
[2011-06-10 07:45] upgraded udev (171-1 -> 171-2)
[2011-06-10 07:45] upgraded udev-compat (171-1 -> 171-2)
')

After that I still have the same issue. And now my hostname isn't being set, "[root@(none) etc]". I did edit the /etc/rc.sysinit, to comment out the udev settle command, then later removed the comment.. so not sure if that is the cause...

Also on another thread it mentions how to get the kernel .config file. I do not seem to have the /proc/config.gz file... not sure if this is a symptom, or something unrelated.

Running a system update on my PogoPlug V2 Pink.... Hostname is not set (same as PogoPlug Pro), but udevd is not running out of control. Also it does have the /proc/config.gz file.
devr
 
Posts: 87
Joined: Wed May 11, 2011 12:22 am

Re: Huge Log files

Postby WarheadsSE » Fri Jun 10, 2011 12:31 pm

/proc/config.gz is a compile-time option for the kernel, which was not set at the time I compiled the running kernel for the OXNAS boards.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Huge Log files

Postby pepedog » Fri Jun 10, 2011 2:51 pm

I just updated my archlinux eee pc and saw udev update with a message, so I looked and there are some changes
from https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/udev/udev.install
$this->bbcode_second_pass_code('', ' if [ "$(vercmp $2 172)" -lt 0 ]; then
echo "ATTENTION UDEV:"
echo "---------------"
echo "Arch's custom blacklisting logic has been removed. MOD_AUTOLOAD and"
echo "blacklisting in MODULES no longer works."
echo "See 'man modprobe.conf' for a replacement to blacklisting."
echo "To disable a module mod1 on the kernel command line, use"
echo "mod1.disable=1"
echo "or"
echo "modprobe.blacklist=mod1"
echo " --"
echo "The following modules are no longer unconditionally loaded:"
echo " pcspkr irtty-sir analog lp ppdev ide-generic"
echo "Add them to MODULES in rc.conf if you need them."
echo "---------------"
fi
')
And I can't see this file on an earlier update
echo "Please read the instructions carefully before reboot."
echo "They are located in /etc/udev/readme-udev-arch.txt"
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Huge Log files

Postby Geoff » Wed Jun 15, 2011 2:31 am

For what it's worth, I have found that it's possible to boot up a Debian 2.6.32-5-versatile kernel using qemu-system-arm along with the root filesystem from ALARM-2011.06-oxnas-rootfs.tar.gz with the same modifications as done by oxnas-install.sh and additions from pack.oxnas.kernel.modules.tar.gz ... After a first-time boot with various module errors, I made a symbolic link in /lib/modules/ from 2.6.32-5-versatile to 2.6.31.6_SMP_820 and did a "depmod." Then after a reboot, everything went well, except (1) there was no eth0, (2) "s0" was respawning fast (easily fixed by commenting it out in /etc/inittab), and (3) the very same "udev" issue arose as described in this thread (taking up all CPU cycles until I killed it). There is no udev issue while using the native Debian root filesystem.

I mention all this as another possible tool to help diagnose the udev problem further. Naturally, I am tempted to see what might happen if I substitute the Debian "Versatile" root filesystem as /dev/sda1 on the Pogo Pro, while using the newly flashed 2.6.31.6_SMP_820 kernel. I imagine I might still have problems with eth0 and other devices, but just maybe the udev problem would go away. I must admit I still haven't quite had the nerve to install the Arch Linux ARM software directly onto my Pogo Pro, although I have successfully added and tested an eSATA connector with an external 2.5" drive powered by USB.
Last edited by Geoff on Wed Jun 15, 2011 6:14 am, edited 2 times in total.
Geoff
 
Posts: 231
Joined: Wed Mar 09, 2011 5:14 pm

Re: Huge Log files

Postby WarheadsSE » Wed Jun 15, 2011 3:04 am

directly as in installing the rootfs into the NAND?

Hell no, dont.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

PreviousNext

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 42 guests