Hi,
I hit a problem when attempting to upgrade to kernel 3.17.2 on a
particular server.
Some time between 3.13 and 3.17, the bonding driver has stopped
accepting ppp devices, instead throwing an error that the MAC address
cannot be changed.
(And does not allow this to be forced)
I suspect it's unlikely.. but has anyone here encountered this issue
and found a solution?
Alternatively.. do you know where the right place to file bug report
about this would be? It's been a while since I've filed anything
against the linux kernel itself.
Cheers,
Toby
Hi Guys,
So i've approached the committee to run a networking presentation of
some form. However before I begin planning for this, i'd like understand
what knowledge is lacking out there in the group. As i'm sure you can
imagine, there are a lot of parts to networking.
My background so you can see if anything here interests you -
I have a good ISP background, in which I have worked on networks
both small and large.
Through this I have a good knowledge of DSL based services and GPON
(This is what NBN runs on).
Broadband and PPP Services inc PPPoE and PPPoL2TP
I also have a good knowledge of routing protocols such as IS-IS and
BGP, and MPLS.
Obviously throughout this I have general networking knowledge such
as, subnetting, network design, troubleshooting, Quality of Service etc.
Now the point of this email is that I want to understand what you want.
Below are some ideas that I have for topics, but feel free to comment or
add any that you would like.
- Networking 101 - Fundamentals including subnetting, OSI Model, packet
analysis and troubleshooting
- Networking in the home. Internal networking, ADSL networking
- Quality of Service - Packet marking, shaping and queuing
Let me know your thoughts,
Cheers,
Fraser
On 30/09/2015 10:45 PM, "Lev Lafayette" <lev(a)levlafayette.com> wrote:
>
> On Wed, September 30, 2015 10:58 pm, Lev Lafayette wrote:
> >
> > I have created the file ~/.android/adb_usb.ini with the following:
> >
> >
> > 0x<2207>
>
> I mean of course
>
> 0x2207
>
> .. just in case there's any confusion. :)
>
>
> --
> Lev Lafayette, BA (Hons), GradCertTerAdEd (Murdoch), GradCertPM, MBA (Tech
> Mngmnt) (Chifley)
> mobile: 0432 255 208
> RFC 1855 Netiquette Guidelines
> http://www.ietf.org/rfc/rfc1855.txt
>
> _______________________________________________
> luv-main mailing list
> luv-main(a)luv.asn.au
> http://lists.luv.asn.au/listinfo/luv-main
It _should_ be a permissions problem, I had the same issue sometime ago and
I had to add my user to the plugdev group then restart adb
Wayne
Hi LUVers,
I'm trying do a wee bit of Android work (hey, it has a Linux kernel) and
have an Aldi Bauhn AT101-014 [1] and have the latest SDK installed and
updated (./android update sdk --no-ui).
I have the device connected via USB with developer mode, USB debugging
mode on, and a MTP connection [2] and have mtpfs installed. I am using
Debian Mint as the development system.
I understand that I have to modify /etc/udev/rules.d/51-android.rules and
possibly ~/.android/adb_usb.ini to include the vendor ID. This can be
determined from running lsusb as follows:
lev@owl ~/src/android-sdk-linux/tools $ lsusb
Bus 004 Device 079: ID 2207:0011
(snip. The above is the relevant device; informative isn't it?)
I have created the file /etc/udev/rules.d/51-android.rules with the
following:
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"
I have created the file ~/.android/adb_usb.ini with the following:
0x<2207>
All of which I believe is in accord to what should be done. However when I
run
owl tools # adb start-server
owl tools # adb devices
List of devices attached
owl tools #
I would expecting some connectivity at this point.
[1] http://www.bauhn.com.au/_literature_140385/AT101-014_-_Instruction_Manual
[2] http://developer.android.com/tools/device.html
Thanks in advance,
--
Lev Lafayette, BA (Hons), GradCertTerAdEd (Murdoch), GradCertPM, MBA (Tech
Mngmnt) (Chifley)
mobile: 0432 255 208
RFC 1855 Netiquette Guidelines
http://www.ietf.org/rfc/rfc1855.txt
I have a Linksys WRT1900AC router (the version 1 hardware), currently running
OpenWRT 15.05-rc3. Now that the final release has been made, I'm contemplating
an upgrade.
According to the OpenWRT wiki, I'm supposed to download an image with a file
name ending in "sysupgrade.img" rather than "factory.img". However, I can't
find such a file on their download site.
The best I can find (again via the wiki) is
https://downloads.openwrt.org/chaos_calmer/15.05/mvebu/generic/openwrt-15.0…
Suggestions on how to perform a safe upgrade would be welcome. As with any
piece of networking hardware, the desire is to minimize risk.
On my (headless) Linux box at home, I have a soundcard with digital out
(optical), going straight to my amp. I can use various music-playing
servers to let me select the music to play remotely, with the output
emitting from the server.
However for reasons that completely elude me, the ALSA system auto-mutes
the output at the end of every song. It's infuriating.
ALSA does indeed have an "auto-mute" setting, but I have ensured it is set
to off.
I wondered if the issue was with PulseAudio for a long time, but the
problem still occurs after reconfiguring things to go direct to ALSA.
As a work-around, I could modify the open-source software I'm using, to get
it to run an unmute command after starting to play a track, but that's
ridiculous. Surely there's a way to just stop it auto-muting on close?
I don't suppose anyone else has ever encountered this, or found a solution?
Toby
I am replacing a set of 4 x 3TB disks with 4 x 6TB disks in a server that holds backups.
I did btrfs replace on one disk, and that has completed but is still showing the original size:
Total devices 4 FS bytes used 5.21TiB
devid 1 size 2.73TiB used 2.73TiB path /dev/sda3
devid 2 size 2.73TiB used 2.73TiB path /dev/sdb3
devid 3 size 2.73TiB used 2.73TiB path /dev/sdc3
devid 4 size 2.73TiB used 2.73TiB path /dev/sde3
/dev/sde3 replaced /dev/sdd3, and the partition itself is definitely the correct size:
major minor #blocks name
8 19 2929216967 sdb3
8 67 5859472967 sde3
8 51 2929216967 sdd3
8 35 2929216967 sdc3
8 3 2929216967 sda3
I've tried running a btrfs resize but it hasn't changed anything.
Google just keeps giving me the same pages telling me about how replace works and why btrfs is awesome, but nothing that will actually fix the problem so far...
Does anyone know how I might fix this?
Thanks
James
Hi all,
one of my "lingering issues" since I am back working in Linuxland
(especially CentOS):
I have the "habit" to have dedicated virtual disks (or similar) for data,
e.g. /var/lib/mysql (so I can snapshot them separately, clone and move
between VMs etc.)
But that makes SELinux unhappy. I was surprised, actually..
What do I have to add to the SELinux contexts to allow this to happen?
Regards
Peter
Hi,
I am looking for a "slimmer" NFS when I have a file server with a lkot
of space - while clients with not much.
I would like to export parts of the server file systems but do not
need to share them between the clients. So I don't need all the
overhead of leases that expire, server-side locking etc.
Instead it would be good enough to do locking on the client side and
write a journal which can be send to the file server.
The file server needs to provide read access to files and be able to
write what's given to it from the client.
UIDs etc. could be send through, the permission check would happen at
the client side.
I guess that's all needed and would be faster and less complex than NFS.
Does this kind of network file system exist?
Any other ideas for very fast access on file system level over the net welcome.
Regards
Peter
