TEN, > locale: Cannot set LC_ALL to default locale: No > such file or directory > For locale I'm not too sure what should be the > canonical approach (certainly not setting LC_ALL > which is a testing override only) to stop perl > etc. from nagging. Below was what I did to set locale. Note that everything in locale.gen should be commented out, except your locatby bodhi - Debian
Almaz Wrote: ------------------------------------------------------- > I'd like to watch my videos remotely and I don't > need any transcoding. I've used Plex before and > really liked it but so far it's available in Arch > but not in Debian. Is it possible to install Plex > or what alternatives would you suggest for > PogoPlug e02? I don't uby bodhi - Debian
TEN, > Is NAND is always > included no matter what "devices" says? Yes, devices here only meant to include storage devices type for booting. > The EHCI timeout makes no perceptible difference > as the unhandled devices are "spinning media" of a > very different kind: > http://www.dacal.com.tw/cd-library-ii/ and their > built-in USB hubs (witby bodhi - Debian
TEN, Reminder: you can go back to wheezy and run kernel 3.18.5. It does not have to be jessie. I think wheezy will last a while, hopefully what ever problem with mceusb will be fixed by the time you upgrade to jessie. BTW, this is the best we can do on the Pogo V3 OXNAS, since I have to build new kernel version for the Pogo V3 to transition to jessie because of systemd dependencies (if uby bodhi - Debian
TEN Wrote: > -20577, I am happy to report that with one more > Xlyne stick of similar speed and capacity (and > less of a Blinkenlight :)) that had been in the > mail, going through the steps for method 4b as su > (re-arranged for minimal input & risk of error) > worked just fine Cool! and to make boot log less noisy and help with low "spinnup" USB devicby bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > TEN, > > > Speaking of which, though unlikely in spite of > > negotiable USB current, is there by any chance > a > > way to completely cut & re-enable power to one > > particular port in software (that would open up > > some nice control opportunities) ? > > We coulby bodhi - Off-Topic
Dieter, Try: - Create a single EXT3 on USB - Use the 3.16 rootfs, as is. Don't change fstab or anything. It should boot with davygravy u-boot, which you've installed by running Jeff's script for squeeze/wheezy. BTW, green LED means the kernel has booted. But rootfs can not be mounted for some reason.by bodhi - Debian
@Joey, These devices tend to overheat that's why you can get it for a cheap price. Seagate had a Satellite, also ~$50. It should have a telnet back door. Install nmap on your Pogo or PC and scan the opened ports. If it shows port 23, it's likely you can log in through that port with default root account..by bodhi - Off-Topic
TEN, > Speaking of which, though unlikely in spite of > negotiable USB current, is there by any chance a > way to completely cut & re-enable power to one > particular port in software (that would open up > some nice control opportunities) ? We could do it with GPIO. I recall there is a shell utility somewhere that allows you to control the pins. In u-boot there is a bby bodhi - Off-Topic
Dieter, Ignore all other error messages, they are supposed to be there. This is what matter: Loading file "/boot/uImage" from usb device 0:1 (usbda1) ** File not found /boot/uImage ** Block device usb 1 not supported ** Block device usb 2 not supported ** Block device usb 3 not supported Loading file "/boot/uImage" from usb device 0:1 (usbda1) ** File not found /by bodhi - Debian
TEN, > Well, in these cases it did fall back into stock - > which is appreciated for this reason as it tells > how much alive the machine still is. > How's Jeff running fsck on boot? I thought some > versions of his uBoot were just alternating the > boot order between retries. U-boot itsef does not really do anything, but Jeff's env for bootcmd has a reset aby bodhi - Off-Topic
rkrug Wrote: ------------------------------------------------------- > How did you set up the home cloud? What are you > using for this? I am assuming, you are not using > the original pogoplug? I am asking because I am > thinking about setting up a home cloud myself. Almaz's suggestion are all good candidates and easier to get it working. I build my own flavor to make itby bodhi - Off-Topic
FelipeC Wrote: ------------------------------------------------------- > Hi Bodhi, i checked what you mentioned and decided > to extract again the tar.gz2 file, below the mtd > sizes: > > > root@ubuntu:/media/d4rk50u1/rootfs/tmp# ls > mtd0 mtd1 mtd2 mtd3 mtd4 > root@ubuntu:/media/d4rk50u1/rootfs/tmp# ls -lh > mtd* > -rwxrwxrwx 1 nobody nogroup 2.1M Fby bodhi - uBoot
I use some of my plugs for fun and some for more serious stuff. - NAS (HPTC, rsync backup) - Transmission - Home cloud (as in personal). - Build environment for kernel and u-boot. - Real-time Linux (PREEMPT-RT) - Research on distributed systems. When I travel I bring either a Dockstar or a GoFlex Net as portable NAS.by bodhi - Off-Topic
TEN Wrote: ------------------------------------------------------- > Very similar: Dockstar even had a power-hungry > DVB-T stick and 4-in-1 hub on it but worked well > 24/7 for half a decade. Sometimes it would need a > few cycles to launch from USB after power outages, > but I understand that was a function of Jeff's > uBoot. I think rather Jeff's setup allby bodhi - Off-Topic
I have a farm of about 20 plugs :) some located remotely, 2 off-line. They come online at various time in the last 4 years. None ever failed (majority has Ext3 USB rootfs), but a single instance with a 2TB WD Element which is known to be flaky and slow wake up cycle. This problem was solved with u-boot env usb_retry_ready patch.by bodhi - Off-Topic
Ack210 Wrote: ------------------------------------------------------- > I am having the exact same problem with a new > install on a recently reclaimed Dockstar and a new > USB stick (1 Gig). > I do not have anything in /tmp/debootstrap and my > USB is formatted roughly 512M bootable Linux (83) > and 512M Linux Swap (82). > The current uboot is installed. > >by bodhi - Debian
rkrug Wrote: ------------------------------------------------------- > Activation: The pogo plug is activated, I > contacted them directly after I received the pogo > plug - so that was sorted. > > SSH: Backdoor does not work: > > > 2:14:10 ~$ curl -k > "https://root:ceadmin@192.168.1.101/sqdiag/HBPlug? > action=command&command=dropbear%20startby bodhi - uBoot
John, > My export is so standard as it can be. I haven't > specified NFS-version anywhere. It does imply different version with the syntax. So if it's vanilla then the syntax imply v3. But if you use something specific like fsid in the parameter then it's exported as v4 (if you do have nfs v4 in the kernel). > "mount /media/music" mounts it w/o problemsby bodhi - uBoot
What Leggo said. And also note that the backdoor SSH instruction has been here for ages, right in front of our eyes :) http://projects.doozan.com/debian/by bodhi - uBoot
restamp, > PogoE02> run usb_init > (Re)start USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 3 USB Device(s) > found > scanning usb for storage devices... 1 Storage > Device(s) found > PogoE02> ext2load usb 0:1 0x800000 > /boot/uboot-original-mtd0.kwb > 524288 bytes read in 331 ms (1.5 MiB/s) > PogoE02> go 0x800200 >by bodhi - uBoot
JohnW, > By default it will use > v3, even if you don't specify it. But you have to export the NFS share as V3 by using the V3 syntax. > By default (comes with the new kernel) the rootfs > will be mounted as read-only, so you'll need to > add "rw" to "net_set_bootargs" as i did. Wasn't > needed earlier. Strange, which NFS versioby bodhi - uBoot
Joey, > On the Mint it was originally like 60-70 in > that area, and I'd read to set swappiness to 10 if > you have like 2 GB RAM or 1 if you have less than > that. I went with 6 and so far it's a hair > snappier. Keep it at 60-80 for the plugs, and use zswap to make it better. Swappiness 1-10 trick don't apply to servers, it is good for GUI based system beby bodhi - Off-Topic
> Note i'm using NFS v3 + TCP. Yes. Booting with NFS v3 has been working well for me for a couple of years. NFS v4 had some problem. I have not tried to change it, so don't know the current status for NFS v4 booting.by bodhi - uBoot
restamp, > Perhaps I'm missing a module? Ah! I remember it now. The fdisk command always erroneously tried to list mtd partitions, so it spitted out errors in dmesg about "mtd partitions don't have valid partition table". Those were scary looking messages! and misleading to say the least. So I've moved mtdblock to module, instead of compiled it in kernel. This wby bodhi - uBoot
restamp, > BTW, are > there any disadvantages to appending the DTB so > that it is a part of the uImage and booting it the > conventional way if you don't intend to move the > filesystem to another architecture? There is no disadvantage that I know of. Even though it states in the kernel config menu that's it's experimental, it works pretty well. I think thby bodhi - uBoot
TEN, If you look at the release thread, I described: Quote- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils. That's exactly what were installed on top of a Debian debootstrap rootfs from mainline.by bodhi - Debian
TEN, > some clarity on automating SSH defences > through nftables, and a cron - BTW found what > happened to that and what users should > (re)install? I have not looked at the differences in defaults for nftables and sshd config. I'd guess there were changes in the default setup for latest versions of those capabilties. I did not explicitly change the defaults at all inby bodhi - Debian
Hi restamp, > After the install of the new uboot and bodhi's > environment, I was unable > to boot to the original NAND-based OS. This was > not unexpected, nor do > I deem it particularly detrimental. I figure that > I have several USB > thumb or disk drives that are bootable on the box > and can think of very > few scenarios where the ability to bootby bodhi - uBoot
FelipeC Wrote: ------------------------------------------------------- > HI Bodhi, > > below your request. > > root@debian:/dev# ls -lh mtd* > crw------- 1 root root 90, 0 Dec 31 1969 mtd0 > crw------- 1 root root 90, 1 Dec 31 1969 mtd0ro > crw------- 1 root root 90, 2 Dec 31 1969 mtd1 > crw------- 1 root root 90, 3 Dec 31 1969 mtd1ro > crw------- 1by bodhi - uBoot