Here is a crazy little script that I intend to include with the
block-extroot package. I'm putting it here for reasonable comments.
Please, however, keep in mind that I don't intend to write a full-blown
bulletproof application for my mother, just an aid for those who want to
use an external root
Hi Peter,
Le jeudi 25 février 2010 à 03:30 +0100, Peter Wagner a écrit :
> applied in r19855
Thanks.
> please send the patch next time as file...
OK. I always included them inline and had no complaint, but will do next
time.
> i also fixed a typo:
>
> -> + umount /proc/fs/nsfd
> +> +
applied in r19855
please send the patch next time as file...
i also fixed a typo:
-> +umount /proc/fs/nsfd
+> +umount /proc/fs/nfsd
thanks
Am Donnerstag 25 Februar 2010 01:01:03 schrieb Benjamin Cama:
> Hi,
>
> While trying to run the kernel nfs server, I stumbled upon t
Hi,
I noticed, that the boost package is broken. There is a wrong '\' at
end of a line. Patch is attached.
Editing the boost package, I changed the config style for the libraries
to build to a Config.in interface and added some other libs someone
maybe need and also python bindings. Patch is attac
Hi,
While trying to run the kernel nfs server, I stumbled upon two bugs :
- /proc/fs/nfsd is not mounted anywhere, and this is absolutely needed
not to have strange "Stale NFS file handle" errors on the client (it
took me a while to figure that out). I am also wondering is the sunrpc
mount in /va
> As such I think it would be very useful to have a minimum build (just
> enough to bring up interfaces and install additional packages)
Agreed.
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/ma
This patch adds a missing dependency of the hifn_795x module from
CONFIG_HW_RANDOM in the kernel config. It cures the error:
hifn_795x: Unknown symbol hwrng_unregister
hifn_795x: Unknown symbol hwrng_register
on module load.
see https://forum.openwrt.org/viewtopic.php?pid=102774#p102774
Signed-
On Wed, Feb 24, 2010 at 9:48 PM, Steve Brown wrote:
> On 2/24/2010 11:34 AM, Kövesdi György wrote:
>>>
>>> You could start with providing some more informations.
>>> like: dmesg output, lsmod output, /proc/bus/pci, logread and whatever
>>> else seems useful.
>>>
>>
>> The boot log and the director
>
> Indeed. The only difference is that there is no predefined config for
> such small targets, so you have to manually select the part of busybox
> you want to strip, and similarly for the kernel config.
> You should be able to get pretty close to DD-WRT's config, while still
> benefitting from
On Wed, 2010-02-24 at 15:27 -0500, Stefan Monnier wrote:
> Indeed. The only difference is that there is no predefined config for
> such small targets, so you have to manually select the part of busybox
> you want to strip, and similarly for the kernel config.
> You should be able to get pretty clo
On 2/24/2010 11:34 AM, Kövesdi György wrote:
You could start with providing some more informations.
like: dmesg output, lsmod output, /proc/bus/pci, logread and whatever
else seems useful.
The boot log and the directory contents of /sys/bus/pci/ are attached. The
command lspci says nothing
> config mount
> option 'uuid' 'some-uuid-here'
> option 'label' 'fs-label'
> option 'device' '/dev/device'
> option 'target' '/usb'
> option 'fstype' 'ext3'
> option 'enabled' '1'
> option 'enabled_fsck' '1'
> option 'is_rootfs' '1'
Why
On Wed, 24 Feb 2010, Stefan Monnier wrote:
The Asus WL520GC I just bought is running Linux. It has 2MB of flash.
Wow, I assumed that out of the box, these devices with a small amount of
flash did not run Linux. That was true in the past at least. Things have
changed since I last checked...
obv
>> Still, you need jffs2 there (both the jffs2 partition and the jffs2
>> modules). That's a lot of flash space for something that's not
>> actually needed. And of course, it's also an added step when
>> installing upgrading the firmware.
> Having a fallback jffs2 is something most people have sa
>>> The Asus WL520GC I just bought is running Linux. It has 2MB of flash.
>> Wow, I assumed that out of the box, these devices with a small amount of
>> flash did not run Linux. That was true in the past at least. Things have
>> changed since I last checked...
> obviously. DD-WRT micro images also
> You could start with providing some more informations.
> like: dmesg output, lsmod output, /proc/bus/pci, logread and whatever
> else seems useful.
The boot log and the directory contents of /sys/bus/pci/ are attached. The
command lspci says nothing. Maybe problems with pci? The 'Support for PCI
Hi again,
>> i also think brcm47xx is ready for 2.6.32.8 update .. so please update it too
>> i added it as separate patch
> maybe you want to dig deeper into this, the Image with 2.6.32.8 works on
> my Asus WL500G-Premium v1 but not on the v2 Version.
please ignore this stupid brainfart, I screwd
On Wed, 2010-02-24 at 13:45 +0100, Hans Mustermann wrote:
> Do I have to apply all the patches?
Only the ones in the most recent email. But if you want external root
you need all the patches in that email.
Regards,
Daniel
--
And that's my crabbing done for the day. Got it out of the way earl
On 2010-02-24 4:05 PM, yann lopez wrote:
> Hi,
>
> I'm trying to setup a multiple wifi virtual interface (vifs)
> configuration, one running as an access point and the other as a
> station on an AR7240/AR9285 board using the ath9k driver.
>
> I'm facing the following issue : the two interfaces a
Hi,
I'm trying to setup a multiple wifi virtual interface (vifs) configuration,
one running as an access point and the other as a station on an
AR7240/AR9285 board using the ath9k driver.
I'm facing the following issue : the two interfaces are up but the ap
interface does not send any beacon fr
Do I have to apply all the patches?
2010/2/24, Daniel Dickinson :
> With the patches this time
>
> On Tue, 2010-02-23 at 21:46 -0500, Daniel Dickinson wrote:
>> Based on discussion, for block-mount:
>>
>> * I have changed the references to /etc/fstab to point to /tmp/fstab
>> (which is what is cur
21 matches
Mail list logo
