[OpenWrt-Devel] uclibc versions
which uClibc version are currently used? if i interpret toolchain/uClibc/Makefile correctly only 0.9.30-git 0.9.30.1 0.9.30.2 0.9.30.3 is this correct or are there still older version used elsewhere? thanks bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] broadcom sdhc package
hi jow, i just had time to double check the code you checked in. unfortunately you inserted the old version 2.0.2 from the originating web space. people will have problems with that version. please remove the Makefile and take the patch on https://dev.openwrt.org/ticket/6343 to add the package. in 2.0.3 there were some fixes you will find documented in the readme file. Also is the sourcecode included as it is not actively developed anymore by the author and nobody knows for how long the package will be available there. .. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] broadcom sdhc package
The patch attached to that ticket is for 2.0.2, please attach a patch for 2.0.3. Thanks Travis sorry for the confusion, actually i modified 2.0.1 into 2.0.2 .. obviously the original author also released an updated version in between. i was in contact with him and understood he would like it in buildroot but wouldn't have the time to bugfix and integrate and that he would like me to do it. i will clear matters up with him and report back. the package right now will work but lacks the root overlay feature i added. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] broadcom sdhc package
in my post for testers some people answered. Maybe somebody volunteers if you ask there or post a topic yourself? https://forum.openwrt.org/viewtopic.php?pid=100795 bud On 20.02.2010 20:25, Spudz76 wrote: I am also still working on the expanded version, as time permits, to support older cores (4702/4710/4712) without the direct register access (using the gpio calls via SB). It will all be configurable via module options, with the fastest access technique used by default. I may also add some core detection to auto-select the best mode that works, but that will require some test feedback from users with cores which I don't have on hand to test. I currently only have a 4702 board, and some newer ones which should work as-is with register access but I haven't installed a card slot yet. I'm not sure if I started with 2.0.3 or not, so once it is posted I'll bump my work over to the newest if I was working with 2.0.2 or older. Not sure on ETA for my patches to be complete - but once they are I will send the patches back to you (Bud) since you are the maintainer, and you can re-test on your hardware, then bump the version and submit. Mostly I don't want my GPIO access abstractions to slow it down any on the register access mode, especially since you spent a good amount of time optimizing it to generate the shortest/fastest assembly result. I would use compile-time selection but that seemed less user-friendly and more confusing than module options. -T On Sat, 2010-02-20 at 13:04 -0600, Travis Kemen wrote: On Sat, Feb 20, 2010 at 12:37 PM, bud.d...@suisse.org mailto:bud.d...@suisse.org wrote: hi jow, i just had time to double check the code you checked in. unfortunately you inserted the old version 2.0.2 from the originating web space. people will have problems with that version. please remove the Makefile and take the patch on https://dev.openwrt.org/ticket/6343 to add the package. in 2.0.3 there were some fixes you will find documented in the readme file. Also is the sourcecode included as it is not actively developed anymore by the author and nobody knows for how long the package will be available there. .. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel The patch attached to that ticket is for 2.0.2, please attach a patch for 2.0.3. Thanks Travis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] libupnp: fix parallel build and cleanup Makefile
On 15.02.2010 17:58, Raphaël HUCK wrote: +MAKE_ARGS += CCOPT=$(TARGET_CFLAGS) define Build/Compile/libupnp-sample $(MAKE) -C $(PKG_BUILD_DIR) \ - CCOPT=$(TARGET_CFLAGS) \ DESTDIR=$(PKG_INSTALL_DIR) \ check + $(MAKE) -C $(PKG_BUILD_DIR)/upnp/sample \ + upnp_tv_device upnp_tv_ctrlpt endef MAKE_ARGS is ignored, remember? Either CCOPT is not needed or you have to use MAKE_FLAGS .. But you have a Compile definition. Hence you have to add it manually to the make parameters. But you deleted the parameter with your patch. I guess the parameter is used during compiling and not with install. check include/package-defaults.mk .. it really clears up things. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hotplug.d/block/10-mount script
I use hotplugged swap. It is not a bad idea per se, as long as the administrator knows that the device can not be removed while the system is running. The reason I use hotplug in particular is that the USB subsystem is not initialized until after the fstab init script is run. or swapoff is used before removing the device, of course the script will do that on action 'remove' as well. Just in case. But it might be to late. Eventually: a feature for the advanced. Another reason to put it in swap-utils. See also issue 2 at [1] and the recently applied enhancement at [2] that adds swap support to the hotplug scripts. this is why I initially came to the idea. I don't like the idea to put every special case in one mount script. ..bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] hotplug mount usbstorage in kernel 2.4
while testing I found that the holplug.d/block scripts are not called for usbstorage devices on brcm-2.4 .. instead usb is called with just a few parameters, missing essentials like devicepath or such necessary for automount. is there a solution except from /sbin/usbstorage that is able to deal cleanly with multiple usbstorage devices? effectively I am thinking about rewriting /sbin/hotplug-call for 2.4 kernel to act on usbstorage device changes add/remove and check /dev/scsi* for changes and call hotplug.d/block scripts accordingly. The current list should be kept by uci state. ideas? comments? .. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] MAKE_ARGS not working?
are you referring to this ticket? https://dev.openwrt.org/ticket/6577 yes in connection to https://lists.openwrt.org/pipermail/openwrt-devel/2010-January/005722.html Yeah in fact the right way to do it is MAKE_FLAGS: MAKE_FLAGS += CFLAGS_O=$(TARGET_CFLAGS) nope, this does not work try it and check the resulting command during build. MAKE_FLAGS is ignored. I believe this is a bug, because MAKE_VARS does work. Other packages' Makefiles is my most reliable source of information :) and I was hoping you found actual documentation, would have been too nice .. nice finding still. I'll modify the upcoming fuse-2.8.2 accordingly. .. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] bump ntfs-3g to 2010.1.16
the attached patch bumps ntfs-3g to the latest version. menuconfig
integration has been slightly modified. Also new:
- package ntfs-3g now also contains the ntfs-3g.probe binary
- new subpackage called ntfs-3g-utils contains ntfs-3g.{usermap,secaudit}
Tested on brcm-2.4 and brcm-47xx.
.. bud
Index: feeds/packages/utils/ntfs-3g/patches/001-xattr_include.patch
===
--- feeds/packages/utils/ntfs-3g/patches/001-xattr_include.patch
(Revision 0)
+++ feeds/packages/utils/ntfs-3g/patches/001-xattr_include.patch
(Revision 0)
@@ -0,0 +1,14 @@
+--- ntfs-3g-2009.11.14/config.h.in.orig2009-12-16 23:51:30.58200
+0100
ntfs-3g-2009.11.14/config.h.in 2009-12-16 23:50:33.89000 +0100
+@@ -123,6 +123,11 @@
+ /* Define to 1 if you have the `setxattr' function. */
+ #undef HAVE_SETXATTR
+
++/* fix 'XATTR_REPLACE undeclared' compile errors */
++#ifndef HAVE_SETXATTR
++ #include linux/xattr.h
++#endif
++
+ /* Define to 1 if `stat' has the bug that it succeeds when given the
+zero-length file name argument. */
+ #undef HAVE_STAT_EMPTY_STRING_BUG
Index: feeds/packages/utils/ntfs-3g/Makefile
===
--- feeds/packages/utils/ntfs-3g/Makefile (Revision 19354)
+++ feeds/packages/utils/ntfs-3g/Makefile (Arbeitskopie)
@@ -1,5 +1,5 @@
#
-# Copyright (C) 2007-2008 OpenWrt.org
+# Copyright (C) 2007-2010 OpenWrt.org
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
@@ -8,23 +8,28 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=ntfs-3g
-PKG_VERSION:=2009.4.4
+PKG_VERSION:=2010.1.16
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tgz
-PKG_SOURCE_URL:=http://www.ntfs-3g.org/
-PKG_MD5SUM:=e0b5c170f088a8d82968f0a6b34d31da
+PKG_SOURCE_URL:=http://tuxera.com/opensource/
+PKG_MD5SUM:=e104c914e8d7d29ee83e63d46afbba25
include $(INCLUDE_DIR)/package.mk
define Package/ntfs-3g/common
- SECTION:=utils
- CATEGORY:=Utilities
- URL:=http://www.ntfs-3g.org
- SUBMENU:=Filesystem
- TITLE:=Stable Read/Write NTFS Driver (build options)
+ SECTION:=utils
+ CATEGORY:=Utilities
+ URL:=http://www.ntfs-3g.org
+ SUBMENU:=Filesystem
+ TITLE:=Stable Read/Write NTFS Driver (build options)
endef
+define Package/ntfs-3g
+ $(call Package/ntfs-3g/common)
+ DEPENDS:= +LINUX_2_4:kmod-fuse24 +libpthread +LINUX_2_6:kmod-fuse
+PACKAGE_NTFS-3G_USE_LIBFUSE:libfuse
+endef
+
define Package/ntfs-3g/description
ntfs-3g is an NTFS driver, which can create, remove, rename,
move files, directories, hard links, and streams; it can read
@@ -33,54 +38,46 @@
moreover it can also read transparently compressed files.
endef
-define Package/ntfs-3g
- $(call Package/ntfs-3g/common)
- DEPENDS+= +LINUX_2_4:kmod-fuse24 +libpthread +LINUX_2_6:kmod-fuse
- MENU:=1
+define Package/ntfs-3g/config
+config PACKAGE_NTFS-3G_USE_LIBFUSE
+ bool use external FUSE library (package libfuse)
+ depends PACKAGE_ntfs-3g
+ ---help---
+ Ntfs-3g by default uses a minimalized lite version of FUSE.
+ If libfuse is part of your filesystem anyway (because of sshfs, owfs
+ etc.) it makes sense to activate this option and save some kilobytes
+ of space.
endef
-define Package/externalFUSE
- $(call Package/ntfs-3g/common)
- TITLE:=use external FUSE library (package libfuse)
- DEFAULT:=n
- DEPENDS+=ntfs-3g +libfuse
+define Package/ntfs-3g-utils
+ $(call Package/ntfs-3g/common)
+ TITLE:=ntfs-3g utilities (ntfs-3g.secaudit, ntfs-3g.usermap)
+ DEFAULT:=n
+ DEPENDS+= +ntfs-3g
endef
-define Package/externalFUSE/description
- Ntfs-3g by default uses a lite version of FUSE for the ease
- of use and some special features. If you'd rather like to use
- the systemwide standard FUSE library activate this option [M|*].
+define Package/ntfs-3g-utils/description
+ Additional ntfs-3g utilities. Not included by default for size
+ considerations. All binaries except ntfs-3g, ntfs-3g.probe.
+ Currently:
+ - ntfs-3g.secaudit
+ - ntfs-3g.usermap
endef
CONFIGURE_ARGS += \
--enable-shared \
- --enable-static \
+ --enable-static
# insert config with external libfuse
-ifdef CONFIG_PACKAGE_externalFUSE
-CONFIGURE_ARGS += --with-fuse=external \
- CPPFLAGS=-I$(STAGING_DIR)/usr/include
-I$(STAGING_DIR)/include \
- LDFLAGS=-L$(STAGING_DIR)/usr/lib -L$(STAGING_DIR)/lib
-PKG_RELEASE:=$(PKG_RELEASE)-fuseext
+ifdef CONFIG_PACKAGE_NTFS-3G_USE_LIBFUSE
+ CONFIGURE_ARGS += --with-fuse=external
+ PKG_RELEASE:=$(PKG_RELEASE)-fuseext
else
-CONFIGURE_ARGS += --with-fuse=internal
-PKG_RELEASE:=$(PKG_RELEASE)-fuseint
+ CONFIGURE_ARGS += --with-fuse=internal
+ TARGET_CPPFLAGS:=-I../include/fuse-lite $(TARGET_CPPFLAGS)
+
[OpenWrt-Devel] hotplug.d/block/10-mount script
I want to split this into 3 scripts. 10-mount 11-mount_ntfs-3g 20-mount_swap the ntfs-3g and swap script will be part of the corresponding packages (swap-utils,ntfs-3g), hence will not be there if the package is not installed. All scripts check if a device was already mounted before. Swap comes last because I plan to enable swapfile support, which rely on the filesystem to be mounted first. Any idea for a swapfile name? /swapfile, /swap.swp ... Any comments? .. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] fuse24, fuse, ntfs-3g, sshfs in 8.09
What do I have to do to get these updated packages into the stable kamikaze branch? Fuse on brcm-2.4 and brcm-47xx is broken without the DCACHE BUG patch in trunk. thanks bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Fwd: broadcom-mmc replacement broadcom-sdhc package
Just a reminder. As usual :'( see bottom of the message I understand you guys are busy, but the lack of feedback in the list can be frustrating to contributors. It definitely is sometimes for me ;) Is there a list of open patches? Wouldn't it make sense to have one listed by priority, by which they also get overlooked by someone dedicated? Something like Recent List of patches and actions Prio, What High 1 release 8.09.3 2 patch security issue foo 3 patch something important Medium 1 patch bump version of package x, maillist link 2 patch missing config file package xy, maillist link Low 1 feature request x, ticketno 3456 2 feature request y, ticketno 1234 Of course this has to be moderated. But one dedicated moderator and one developer working the list could be a start. .. bud Original Message Subject: [OpenWrt-Devel] broadcom-mmc replacement broadcom-sdhc package Date: Fri, 11 Dec 2009 14:23:46 +0100 From: bud.d...@suisse.org Reply-To: OpenWrt Development List openwrt-devel@lists.openwrt.org To: OpenWrt Development List openwrt-devel@lists.openwrt.org As announced the new package broadcom-sdhc. I created a enhancement ticket here https://dev.openwrt.org/ticket/6343 Please add it to trunk and remove broadcom-mmc, which is then obsolete. Thanks bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fwd: broadcom-mmc replacement broadcom-sdhc package
Thanks a lot. What about the open actions list.. any comments? Regarding testers: I will put a request/announcement in the forum as soon the module is in the trunk. I myself am using it for months now and discovered no problems. bud On 16.01.2010 15:19, Jo-Philipp Wich wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the problem with this particular patch is the inability to test it :) Afaik none of the developers has a mmc-enabled broadcom box to try it out. I'll look into it later, to see whether it compiles and add it to trunk then. ~ JoW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktRyucACgkQdputYINPTPMdRgCcCJ4j16lTYFD1CoR1L4UwAGg/ Dp4AoJ0t/1+HRh/YARTg2d5I1XS2in+4 =XO0c -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fwd: broadcom-mmc replacement broadcom-sdhc package
Well, I extensively tested mmc mod for broadcom platform because I figured it to be the cheapest way to have more space on a openwrt router, namely the wrt54gl. Eventually I think usb is now the way to go. My tests for the sdmodded wrt54gl resulted in brcm-2.4 - broadcom-mmc, mmc 1.3.5 from forum and sdhc were stable and usable (sorted by speed) brcm47xx - mmc kernel module is essentially working but very very slow, eats all cpu time when transferring and sometimes dies for reasons I couldnt figure out. Also it was choosy which sdcard to accept. I also tried dd-wrt, they use mmc 1.3.5 by the way, and found it as stable and fast as was to be expected from the above findings. Essentially I have the wrt54gl now running the flash jffs fs overlayed with sd card ext3 overlaying root. Only draw back is that I can't use the button the anymore to switch on off the wlan because its gpio lane is used. .. I also agree, let's put it to trunk and wait, if somebody complains, especially as this is not totally new, but based on work already in trunk. .. bud On 16.01.2010 19:36, Spudz76 wrote: I have an MMC-over-GPIO enabled Broadcom but I can't get it to take a proper flash and boot for some reason with more recent checkouts. It runs (gasp) DD-WRT just fine though so I'm confused. If I can get it working again I'll test this, especially since I had to do a whole lot of fiddling with the original broadcom-mmc package to get it to work in the first place (back when it worked in general) so it would be a good fringe model to test (not a standard WRT54G with MMC mod). It's one of the old Belkin F5D7230-4 units with no serial console (no UART even) so it's that much more difficult to figure out why I get no completed boot. I may try to figure out how to install a UART so I can get the console output, but old posts regarding such said the expansion/bus header didn't have one of the higher address lines which would be required for a 16550. We need to figure out how to test things like this, or some method of deciding whether an untested patch can go in with a single vouch that it works (usually from the submitter). Something like this is probably not used that much so I'd personally say toss it in and see if anyone complains that it doesn't work, as it's not exactly a core piece that could affect a large user base if it didn't work. And, the original version doesn't really work that well in the first place in my experience, so if this one doesn't either then its not much worse at least. Other patches though certainly could use a more complete test phase, maybe set up a test zone where users could sign up and input the equipment they have available and be able to connect a patch with a capable tester? On Sat, 2010-01-16 at 15:32 +0100, bud.d...@suisse.org wrote: Thanks a lot. What about the open actions list.. any comments? Regarding testers: I will put a request/announcement in the forum as soon the module is in the trunk. I myself am using it for months now and discovered no problems. bud On 16.01.2010 15:19, Jo-Philipp Wich wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the problem with this particular patch is the inability to test it :) Afaik none of the developers has a mmc-enabled broadcom box to try it out. I'll look into it later, to see whether it compiles and add it to trunk then. ~ JoW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktRyucACgkQdputYINPTPMdRgCcCJ4j16lTYFD1CoR1L4UwAGg/ Dp4AoJ0t/1+HRh/YARTg2d5I1XS2in+4 =XO0c -END PGP SIGNATURE- ___ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] broadcom sdhc package pending inclusion
the brcm-2.4 sdhc driver is also still pending https://dev.openwrt.org/ticket/6343 .. thanks bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Update [RFC] preinit/failsafe fix/enhance
The way I do it do use the same basic boot method as for a flash filesystem, and just do the necessary things to make up for the differences between to two types of media. I can do that because I have modularized the preinit/mount_root/firstboot scripts and subsitute usb boot stuff where appropriate, without changing the parts than can stay the same. essentially I have two devices .. a wl500w that should use an usb stick as root and an sdmodded wrt54gl that should use the sdcard ... Sounds like your system would fit these purposes, I see if I'll find the time to check it against my needs.. on the other hand, as long as it's not in trunk a minor modification one liner to mount_root, could do the trick as well. You can't just pivot_root because in rc.d (which is one solution on the wiki) because then your /etc is limited to what is left on the flash after the firmware takes up space. as far as i understand the pivot has to take place before init is run, so it has to take place in preboot/mount_root - doesn't it? Felix is talking about an aufs solution, but you'd have to ask him about that, and I'm not sure what his timeline is (I suspect it wouldn't be as soon, so my solution could be viewed as an at least interim solution). @Felix: Are you reading? Any news on this topic? Is there aufs available in trunk? Couldn't find a package, seems not to be part of the kernel also ... Thanks ..bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Update [RFC] preinit/failsafe fix/enhance
I've refreshed the patches to work with current trunk (as the old patches were no longer applying cleanly due to recent changes). There are also a couple of minor functional changes some of which make the usb root stuff I'm working on easier. Do you plan to overlay the internal flash? I actually are currently working on root overlay on sdcard/usbstick. As far as my tests went, mini_fo cannot overlay an already mini_fo'ed filesystem. Therefor I am currently stuck with this current model: - absolute minimal jffs image 4MB (to keep it writeable for essentrial configuration and testing now, could be read-only squash later, but then the modifications to mount_root are bigger than one line :) - a oneliner on the end of /sbin/mountroot that runs an init script (eventually /sbin/init.d/mount_ext_root as symlink for /etc/init.d/sdcard or /etc/init.d/usbstorage, the symlink is only there if root overlaying is activated) - optional mount_ext_root could be a full blown script (en/disable,configurable), taking care of mounting the partitions and leaving device stuff to the appropriate other init scripts Drawback: - does not work on first boot Advantage: - one concept for all external media providing root filespaces .. thx bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] sdhc driver for broadcom 2.4
I just recently found an updated sdhc kernel module based upon the optimized mmc 1.3.5 from the forum. http://4mul8.ca/openwrt/source/broadcom-sdhc-2.0.1/ I tried it and it is again faster and supposedly to support sdhc cards, which I don't own, therefor can't check. Unfortunately it is for kernel 2.4 broadcom only. Is there interest to integrate it in buildroot? I contacted the original author and he would like it. .. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt.org website down?
nslookup openwrt.org 208.67.222.222 Server: resolver1.opendns.com Address: 208.67.222.222 Name:openwrt.org Address: 78.24.191.177 regards .. bud On 23.08.2009 10:36, MichelinoK wrote: i have the same problem...they've changed the ip of openwrt.org so we have to wait for the DNS around the world to be updated...(or you manually add openwrt.org to the hosts file with the new ipgrab the ip from the topic of the irc channel, cannot remember now...i'm waiting for the dns update). ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] openwrt.org website down?
getting timeouts, anybody else experiencing this? ..bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt.org website down?
would have been nice .. also maybe a little note beforehand to the list ... anyway for now I added a http://www.opendns.com/ server manually before the router in lan connections dns settings. Anybody knows the value of the dns ttl? Or how long until I can remove the alternative server again? thanks for the hint .. bud On 23.08.2009 17:53, Nils Toedtmann wrote: Imre Kaloz wrote: On 2009.08.23. 09:55:12 Benjamin Henrionb...@udev.org wrote: On Sat, Aug 22, 2009 at 5:00 AM,bud.d...@suisse.org wrote: getting timeouts, anybody else experiencing this? Time for mirrors... Time to read RFC1034 and 1035. ... in particular this bit: If a change can be anticipated, the TTL can be reduced prior to the change to minimize inconsistency during the change, and then increased back to its former value following the change. SCNR, /n. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt.org website down?
added opendns servers now to kamikaze 7.09 on my router, following this directions https://forum.openwrt.org/viewtopic.php?id=12408 here the steps in case you can't access forum.openwrt.org edit /etc/rc.d/S60dnsmasq add the following to DNS_SERVERS= DNS_SERVERS=208.67.222.222 208.67.220.220 save the file then run /etc/rc.d/S60dnsmasq restart check resolv.conf r...@openwrt:/etc/rc.d# cat /etc/resolv.conf nameserver 208.67.222.222 nameserver 208.67.220.220 nameserver 127.0.0.1 ... bud On 23.08.2009 18:43, Steven Van Ingelgem wrote: ste...@mac-mini:~/lacie/TV$ ping svn.openwrt.org PING svn.openwrt.org (195.56.146.238): 56 data bytes ste...@mac-mini:~/lacie/TV$ ping openwrt.org PING openwrt.org (195.56.146.238): 56 data bytes ste...@mac-mini:~/lacie/TV$ dig openwrt.org ; DiG 9.4.3-P3 openwrt.org ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 59701 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 ;; QUESTION SECTION: ;openwrt.org. IN A ;; ANSWER SECTION: openwrt.org.509808 IN A 195.56.146.238 ;; AUTHORITY SECTION: openwrt.org.73064 IN NS soapstone.yuri.org.uk. openwrt.org.73064 IN NS belategeuse.dune.hu. openwrt.org.73064 IN NS arrakis.dune.hu. ;; ADDITIONAL SECTION: arrakis.dune.hu.73064 IN A 195.56.146.235 soapstone.yuri.org.uk. 29204 IN A 78.47.151.105 belategeuse.dune.hu.73064 IN A 217.20.135.200 ;; Query time: 14 msec ;; SERVER: 192.168.178.1#53(192.168.178.1) ;; WHEN: Sun Aug 23 18:42:40 2009 ;; MSG SIZE rcvd: 183 2009/8/23 kloschiklos...@subsignal.org On Sun, 2009-08-23 at 18:03 +0200, bud.d...@suisse.org wrote: would have been nice .. also maybe a little note beforehand to the list ... anyway for now I added a http://www.opendns.com/ server manually before the router in lan connections dns settings. Anybody knows the value of the dns ttl? Or how long until I can remove the alternative server again? whois helps to fin out the authorative dns servers. dig helps to show the dns entries, and it looks like 604800 seconds is the ttl .. (was it rly seconds??): dig @ARRAKIS.DUNE.HU openwrt.org ; DiG 9.6.1-P1 @ARRAKIS.DUNE.HU openwrt.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 59031 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;openwrt.org. IN A ;; ANSWER SECTION: openwrt.org.604800 IN A 78.24.191.177 ;; AUTHORITY SECTION: openwrt.org.604800 IN NS soapstone.yuri.org.uk. openwrt.org.604800 IN NS arrakis.dune.hu. openwrt.org.604800 IN NS belategeuse.dune.hu. ;; ADDITIONAL SECTION: arrakis.dune.hu.604800 IN A 78.24.191.176 belategeuse.dune.hu.604800 IN A 217.20.135.200 ;; Query time: 37 msec ;; SERVER: 78.24.191.176#53(78.24.191.176) ;; WHEN: Sun Aug 23 18:36:18 2009 ;; MSG SIZE rcvd: 167 hth, kloschi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] replace /jffs with usb stick
I am in for that. I want to use an sd-modded wrt54gl and a usbsticked wl500w this way. Therefore I'd also like to put the optimized mmc module for kernel2.4 in the trunk. Any opinions? Should we keep the old and setup a kmod-broadcom-mmc2 or replace the old one (which doesn't work with my setup). How about: device node/fs/modules uci configurable if everything goes well the device is used instead of root_fs_data. While trying I came to a point where /etc/passwd was created on the stick only. This is problematic. I think the router should be able to work basically also without the extra filespace. Therefore I currently think it would make sense to overlay an existing jffs data partition. As the wl500w has 8MB space I currently tryout a setup without squashfs. But this might be impossible on 4MB devices. result would be: squashfs OVERLAYEDBY jffs (OVERLAYEDBY usb/mmc if exists) ... could anybody offer some help? I am really not experienced in the matter, but I am definitely interested in improving the situation. The result should be a switch on/works solution without fiddling the start scripts. .. bud On 19.08.2009 16:23, Brian J. Murrell wrote: On Tue, 2009-08-18 at 20:38 -0400, Stefan Monnier wrote: I am having a hard time to find the place where mounting root / really happens .. It's in /sbin/mount_root. And yes, it is not exactly trivial to find (although in retrospect I had to admit that the name should have made it pretty obvious). See below the patch I use on my WL-700gE to mount the IDE drive's partition. I really wish we could get some form of official support upstream for / mounted on USB devices. It seems that more and more people are re-inventing this wheel. Sadly. b. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] optimized mmc driver for kernel 2.4
is there a reason why the https://forum.openwrt.org/viewtopic.php?id=9653 is not in the buildroot? From my tests it is faster and more compatible than the current 'package/broadcom-mmc'. ... bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] change kernel version in buildroot
just out of interest. I see options in menuconfig to change the gcc version and others but ís the used kernel version configurable? thx bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] fix fuse on recent kernels
I'll change that and send the patch next week to the list. ... bud bud.d...@suisse.org wrote: Are you sure that it compiles with 2.6.27 ? Did you try? no :-) i was only conservative and thought that it just broke recently. Maybe it's time to disable the module by default without condition. It's part of the kernel and maintained there. Does current buildroot support kernel 2.6 younger than patchversion 14? i'm for disabling it completly. i think nobody uses such an old kernel on a current buildroot anyways. kindly regards daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Note for mips/mipsel targets running trunk
Thanks for pointing out ... bud Hi, Since changesets 16606 and 16607 we have switched to using software floating point emulation in the toolchain and we disabled the in-kernel FPU Emulator in the MIPS kernel by default. The rationale behind this is : - the FPU emulator of the kernel is slow and works by catching floating point operations exceptions, emulating them and continuing its work - software floating point emulation is only added when a program needs it and will not bloat fixed point programs (most) with software floating point code, additionnaly software floating point is faster due to the absence of the exception mechanism - for consistency, other targets (arm, powerpc) also use software floating point This allows us to have a kernel which is slightly smaller (~ 1%) and faster, and since most programs do not use floats, their memory footprint do not change while programs using float have a slightly bigger one as they require software floating point emulation. Still the tradeoff is worth :) The bad effect is that you have to recompile your mips/mipsel toolchain AND kernel otherwise you will get a device which boots the kernel then silently fails while running busybox (the later using floats). Thank you very much for your attention. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [SOLVED] KernelPackage postinstall .. WAS: character device file and packaging
I eventually reverse engineered myself through the buildroot Makefiles and came up with the following solution. define KernelPackage/fuse24/install $(call $(Package/kmod-fuse24/install)) echo mknod /dev/fuse -m 0666 c 10 229 $(1)/CONTROL/postinst endef I could find another definition that is hooked up in the right time .. after AUTOLOAD is written to CONTROL/postinst but before ipkg creates the installation archive. The Package/pkgname/postinst definition does not seem to be executed as only the KernelPackage is defined and $(eval $(call'ed in the end of the Makefile. .. Bud the definition suggested seems not to change the postinst script in ipkg/CONTROL anything different if it is a kmod only package? pls see attached Makefile thanks bud -- Le Thursday 04 June 2009 17:23:20 bud.d...@suisse.org, vous avez écrit : I currently play around with sshfs and it was missing the kernel fuse module (so it said). In reality the /dev/fuse character device was missing. Now I need a clue on how to modify the package Makefile to create /dev/fuse either on package installation or earlier and package it with the ipkg archive. Any ideas? All I know the commandline would be 'mknod /dev/fuse -m 0666 c 10 229' I suggest that you use the postinstall script defined like this: define Package/quagga/postinst #!/bin/sh mknod /dev/fuse -m 0666 c 10 229 endef Even though the device should be created automatically once the module is inserted, is not it ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] character device file and packaging
I currently play around with sshfs and it was missing the kernel fuse module (so it said). In reality the /dev/fuse character device was missing. Now I need a clue on how to modify the package Makefile to create /dev/fuse either on package installation or earlier and package it with the ipkg archive. Any ideas? All I know the commandline would be 'mknod /dev/fuse -m 0666 c 10 229' Thx in advance .. bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] character device file and packaging
on kernel 2.4 with the fuse 2.5.3 kernel module it isn't ... I'll doublecheck with kernel 2.6 fuse 2.7.4 tonight ... bud Le Thursday 04 June 2009 17:23:20 bud.d...@suisse.org, vous avez écrit : I currently play around with sshfs and it was missing the kernel fuse module (so it said). In reality the /dev/fuse character device was missing. Now I need a clue on how to modify the package Makefile to create /dev/fuse either on package installation or earlier and package it with the ipkg archive. Any ideas? All I know the commandline would be 'mknod /dev/fuse -m 0666 c 10 229' I suggest that you use the postinstall script defined like this: define Package/quagga/postinst #!/bin/sh mknod /dev/fuse -m 0666 c 10 229 endef Even though the device should be created automatically once the module is inserted, is not it ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] define device profile ntfs-3g updates
Hi all, I've got two questions. I am working with an Asus wl500w and want to set up a profile for the buildroot. I see the readymade images after the buildroot make in 'bin'. What I want is to define a profile for this router, so that all needed packages are automatically in a special wl500w flash image. Ther router is kind of specific because it needs linux 2.4 for the wlan (br mimo) and has usb2. Q1: Where can I find examples or how is it done? Also I did some enhancement on the fuse/ntfs-3g packages which can be found on https://dev.openwrt.org/ticket/5186 Q2: I have no echo since two days. Does somebody actively monitor the tickets? .. regards bud ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
