-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I let your opinion settle into my mind over night.
I agree that a single config is enough (config-default).
But for the patches folder I would prefer kernel specific names, as they
differ in files and line numbers.
Maddes
On 03.02.2010 12:29, Imre Ka
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I mainly get seg faults when restarting the network via
"/etc/init.d/network restart" or sometimes when installing stuff via opkg.
LAN is set to 10.0.0.0/24 and router is .254, WAN is accessed via PPPoE
(DSL) and WLAN/Wifi is 11ng, country is DE, chann
Hello Maddes,
On Wed, 03 Feb 2010 15:48:48 +0100, Matthias Buecher / Germany
wrote:
Imre, thanks for your fast reply.
I find it more comfortable to have separate configs and patch folders.
So while trying to get a new kernel running (like 2.6.32, which
currently gives me seg faults), you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Imre, thanks for your fast reply.
I find it more comfortable to have separate configs and patch folders.
So while trying to get a new kernel running (like 2.6.32, which
currently gives me seg faults), you can easily switch back to the
current stable k
Hello,
NAK. Although some people love to name the config files that way if the
differences
don't conflict, it makes no sense -- it's easier to keep the same config and
add the
extra symbols to it for the newer kernel. Also, if 2.6.32 is working, there's
no reason
to keep .30 around.
Imre
O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
please execute the following svn commands inside trunk to correct the
names of the orion config file and patches folder:
svn mv target/linux/orion/config-default target/linux/orion/config-2.6.30
svn mv target/linux/orion/patches/ target/l
